id summary reporter owner description type status component version resolution keywords cc guest host 8824 64 bit guests fail during boot on hosts using AMD E-350 mainboards => fixed in SVN/4.1.2 John Clark "Hi there, I have recently taken delivery of a system based on the ASUS E35M1-I Deluxe motherboard. This board uses the new AMD E-350 fusion APU's (""Zacate"" cores). These E-350 APU's (the new name for CPU+GPU combined cores) are 64 bit and support AMD-V and RVI. Attempts to boot 64bit linux distro (in my case, Linux Mint 10, which is derived from Ubuntu Maverick) fails almost immediately. The host system is brand new and running an absolutely stock standard install of Linux Mint 10 64 bit OS. Naturally, the initial step in building a Linux guest from scratch is to make the guest virtual CDROM use the Linux distro live/install ISO (in my case the Linux Mint 10 64 bit live/install ISO). The guest begins booting off the virtual CDROM ISO and dies indelicately almost immediately after Grub hands off to the Linux Mint boot process. The guest dies due to a kernel panic (screenshot attached). To try and isolate the cause of the problem, I installed VMWare 7.1 on the host and can report that it booted the Mint 64bit guest with no problems at all. So whatever the problem is, VMWare 7.1 doesn't suffer from it. It seemed worthwhile to try fiddling with the guest settings to see if I could get around the problem. The only change that seemed relevant was to turn off RVI (virtualbox calls it ""nested paging""). Alas, the guest still failed to boot but this time with a segfault instead of a kernel panic. Screenshot attached. The virtualbox host is not adversely affected in any way by the failure of the guest. The paniced/segfaulted guest can be powered off as per normal. Attached is a log file anyway. All BIOS updates for the host system have been applied. Other vbox users are reporting similar problems - see the forums here (I was one of the posters): http://forums.virtualbox.org/viewtopic.php?f=6&t=39361 Searching the interwebs revealed a few other people reporting the same problem with E-350 based hosts, and acknowledgement that VMWare will run 64 bit guests on E-350 hosts without issue. I much prefer vbox so am looking forward to a resolution of this problem. I suspect it's a nuance of the E-350 spec that's causing the problem. Not overly surprising as these cores are quite new. But they are getting more and more popular so I expect more and more vbox users are going to be experiencing this issue over the coming weeks/months. At a stretch, I'm willing to provide a vbox developer with access to this system if absolutely necessary to root out the bug - this system isn't running in a production environment currently (mostly because of this bug). Looking forward to a solution. John" defect closed VMM/HWACCM VirtualBox 4.1.0 fixed 64bit guest AMD E-350 E350 amdfusion zacate Linux Linux