VirtualBox GUI crashes when booting ArchLinux CD as guest
Posted: 28. Aug 2009, 09:31
Hi,
I use the VB on Windows XP with Linux OS's as guests. I run CentOS and Gentoo successfully, but I would like to install the ArchLinux now, and that's the problem. When I try to boot up an ArchLinux live CD, the VirtualBox crashes with a message "VirtualBox GUI has encountered a problem and needs to close" (approximately, it shows up in my local language and I'm not able to convince it to use english). The crash occures after much of the kernel is already loaded and initialized so not at very begining. As I change parameters of the guest (e.g. type of IDE controller) and booted kernel (e.g. old IDE support vs new IDE support), the point of the crash moves significantly so it doesn't seem the crash relates to a particular kernel code just running. Does anybody have similar experience? Any idea how to solve the problem? I consider this behaviour to be a VB bug because if something is wrong with a guest OS boot, the guest OS should the one who exclaims the problem (or hangs at the worst case).
host: HP dc7800, Pentium Dual Core, Windows XP
guest: ArchLinux live CD - archlinux-2009.08-core-i686.iso (on physical HW fully working)
VB guest log: see an attachment
I use the VB on Windows XP with Linux OS's as guests. I run CentOS and Gentoo successfully, but I would like to install the ArchLinux now, and that's the problem. When I try to boot up an ArchLinux live CD, the VirtualBox crashes with a message "VirtualBox GUI has encountered a problem and needs to close" (approximately, it shows up in my local language and I'm not able to convince it to use english). The crash occures after much of the kernel is already loaded and initialized so not at very begining. As I change parameters of the guest (e.g. type of IDE controller) and booted kernel (e.g. old IDE support vs new IDE support), the point of the crash moves significantly so it doesn't seem the crash relates to a particular kernel code just running. Does anybody have similar experience? Any idea how to solve the problem? I consider this behaviour to be a VB bug because if something is wrong with a guest OS boot, the guest OS should the one who exclaims the problem (or hangs at the worst case).
host: HP dc7800, Pentium Dual Core, Windows XP
guest: ArchLinux live CD - archlinux-2009.08-core-i686.iso (on physical HW fully working)
VB guest log: see an attachment
