Andrew Gormanly wrote: > Hi, > > Installing VirtualBox 2.1.0 (specifically, starting the service from > init.d) causes my host OS to fall over and die instantly, sending the > machine back to the BIOS. I assume this is a conflict with Xen, as this > doesn't happen if I reboot to a non-Xen kernel. > > OS is RHEL 5.2 Server x86_64 which by default runs the Xen kernel, but > VirtualBox starts itself on installation and does not check if it is > running in a Xen Dom0 at startup. Could a sanity check be added to > future releases? > > Andy
Actually, it's worse than that: starting up a guest machine has killed 2 seperate RHEL5.2 hosts (hard lock-ups) using the non-Xen kernel. Common features have been a host with the 2.6.18-92.1.22.el5 x86_64 kernel, and guests with host networking, SATA disks and 512MB of memory; the 2 attempts had different guest network cards and hard disk sizes. Neither gets as far as booting the install media (SLES10 server x86_64 iso image). Host details: (1) Sun Fire X4440 with 1 Opteron 2356, 8GB, 2* 73GB 15k SAS drives, RHEL 5.2 Server; (2) Dell XPS M1210 with Core 2 T7200, 2GB, 120GB SATA disk. Any suggestions? Andy -- Andrew Gormanly London Centre for Nanotechnology University College London Tel: 020 7679 3400 17-19 Gordon Street Fax: 020 7679 0595 London WC1H 0AJ a.gormanly AT ucl.ac.uk _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
