guest: booting Xen kernel hangs VM and confuses host

[Helmut Schulz]

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.

[Helmut Schulz]

VM Guru Meditation

[Helmut Schulz]

VM Guru Meditation pt 2

[Helmut Schulz]

kernel oops caused by vbox driver

[Helmut Schulz]

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).

[Frank Mehnert]

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

[Helmut Schulz]

4.04 VBox.log

[Helmut Schulz]

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.

[Ivo Smits]

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.

[aeichner]

Please reopen if still relevant with a recent VirtualBox release.