VirtualBox

Ticket #8356 (new defect)

Opened 3 years ago

Last modified 3 years ago

guest: booting Xen kernel hangs VM and confuses host

Reported by: Helmut S. Owned by:
Priority: major Component: other
Version: VirtualBox 4.0.2 Keywords: Xen
Cc: "Schumacher, Bernd" <bernd.schumacher@…> Guest type: Linux
Host type: Linux

Description

Currently, we have the requirement to simulate hardware running Debian and Xen virtualization, within virtual box (or another virtualization environment). The setup works with vmware. However, the Xen Linux guest hangs on vbox. If hardware virtualization is active for the guest, the setup obviously destabilizes the host system to a degree, where a system reboot is required to make things work again.

We use virtual box 4.0.2_OSEr35621 on Debian Linux 6.0 'Squeeze', Kernel 2.6.32-5-amd64, but observed the very same problem on Lenny. Virtual box has been built from source (retrieved via 'apt-get source sid') for Squeeze, to replace the bundled version 3.2, which showed the same issue.

We try to boot Debian Linux 5.0 'Lenny', using Kernel 2.6.26-2-xen-amd64 and 2.6.26-2-xen-686 - neither works.

Attachments

VBox.log.pt1 Download (108.9 KB) - added by Helmut S. 3 years ago.
VM Guru Meditation
VBox.log.pt2 Download (73.2 KB) - added by Helmut S. 3 years ago.
VM Guru Meditation pt 2
syslogpart_oops_64bit Download (6.1 KB) - added by Helmut S. 3 years ago.
kernel oops caused by vbox driver
VBox.log.64bit_2 Download (46.1 KB) - added by Helmut S. 3 years ago.
4.04 VBox.log

Change History

Changed 3 years ago by Helmut S.

VM Guru Meditation

Changed 3 years ago by Helmut S.

VM Guru Meditation pt 2

Changed 3 years ago by Helmut S.

kernel oops caused by vbox driver

comment:1 Changed 3 years ago by Helmut S.

We tested again, using new vbox release 4.04. The behaviour seems to have changed a bit - no Guru Meditation, but kernel oops (syslog excerpt attached).

comment:2 Changed 3 years ago by frank

Please attach the VBox.log file of the 4.0.4 VM session as well.

Changed 3 years ago by Helmut S.

4.04 VBox.log

comment:3 Changed 3 years ago by Helmut S.

Can't retrieve vm state via vboxmanage or GUI - it just freezes everything concerning that particular vm. Other VMs running at the same time, however seem to remain intact.

comment:4 Changed 3 years ago by UFO

I ran into the same problem. Some googling suggests some command line options to try. For me, redirecting the xen console somewhere else (append "console=none" or "console=com1" to the Xen commandline) seems to have 'fixed' the problem.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use