VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1627 - 1629 of 16363)

Ticket Resolution Summary Owner Reporter
#1661 worksforme AMD Phenom seems to cause BSOD 0x0000008E -> update your BIOS Daniel
Description

Host : Windows XP x86 Service Pack 3 Guest : Windows XP x86 Service Pack 3

With an AMD64 Socket 939 (ECS Nforce4 motherboard) everything worked fine.

Upgraded (old motherboard died) to AMD AM2+ Phenom (with an Asus M2 motherboard) and got a 0x0000008E blue screen.

I see a pattern here, pointing to AM2+ Phenom.

This ticket

http://www.virtualbox.org/ticket/1627

Looks awfully similar to my situation. But, as far as I understood, he manages to boot into the OS. I can't even do that.

The exact scenario is:

  • When installing XP from scratch, on a new virtual HD, the first install phase (the one in Text Mode in which you choose the install partition and a first batch of file copying takes place) all goes through fine. When the system boots, for the second install phase, that one with an actual GUI, before the GUI appears the 0x0000008E happens.

Interesting facts:

  • Microsoft's Virtual PC 2007 (with and without Service Pack 1) has the EXACT same behaviour.
  • VMWare Workstation works fine! And thats exactly what I found out last night and used as a workaround. I created a vmware machine using a link to the "3rd party" virtual hard disk. And it managed to boot fine and I had my old vm back.

Sun and Microsoft need to do whatever magic VMWare does to coupe with whatever AMD Phenom is doing.

#1662 obsolete vbox goes to 100% CPU after resume on Ubuntu Hardy, 2.6.24-17-generic Marco Walther
Description

After some OS updates, my vboxes behave badly after a suspend/resume cycle. The vbox starts to use 100% CPU (basically one core on a dual-core laptop) but it does not do much anymore. It's very slow to respond and getting it to cleanly shut down is impossible.

VirtualBox: 1.6.0 (downloaded)

Host: Kubuntu 8.04, patched as of today, Linux kernel 2.6.24-17-generic

Guests:

  • Linux 2.6.23??
  • OpenSolaris release
#1663 duplicate NAT related crash dkaaden
Description

After my upgrade to 1.6.0 i am having problems. I upgraded to 1.6.0 on the 29th of May and experienced 2 crashes since then. The vm was running for over 2 months with 1.5.6 without any problem.

There is ony one line related to these crashes in /var/log/messages on the host: 1st crash: VBoxHeadless[7972] trap int3 rip:2aaab04b0863 rsp:412a7c10 error:0 2nd crash: kernel: VBoxHeadless[32069] trap int3 rip:2aaaac4af863 rsp:412a7c50 error:0

There is nothing about this crash in /var/log/messages on the vm.

I found these crash logs on the host:

Log created: 2008-06-01T02:30:37.261990000Z Executable: /opt/VirtualBox-1.6.0/VBoxHeadless Arg[0]: /opt/VirtualBox-1.6.0/VBoxHeadless Arg[1]: -comment Arg[2]: opensuse10.3 Arg[3]: -startvm Arg[4]: 3b1a4d38-1210-402d-74a9-4913e56f31ee

!!Assertion Failed!! Expression: <NULL> Location : /home2/vbox/vbox/lnx64-rel/src/VBox/Devices/Network/slirp/tcp_subr.c(1341) VBoxU32PtrHashSlow NAT pointer hash error. pv=000000000085c8b0 cpvHashUsed=232 cpvHashCollisions=134


Log created: 2008-06-03T13:01:23.274514000Z Executable: /opt/VirtualBox-1.6.0/VBoxHeadless Arg[0]: /opt/VirtualBox-1.6.0/VBoxHeadless Arg[1]: -comment Arg[2]: opensuse10.3 Arg[3]: -startvm Arg[4]: 3b1a4d38-1210-402d-74a9-4913e56f31ee

!!Assertion Failed!! Expression: <NULL> Location : /home2/vbox/vbox/lnx64-rel/src/VBox/Devices/Network/slirp/tcp_subr.c(1341) VBoxU32PtrHashSlow NAT pointer hash error. pv=00000000016e30a0 cpvHashUsed=182 cpvHashCollisions=67


The host is mandriva 2008.1 x86-64 running VirtualBox-1.6.0-Linux_amd64.run. The vm is opensuse 10.3 i386

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy