VirtualBox

Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#5314 closed defect (fixed)

All VM's stuck or crash after upgrade to 3.0.10

Reported by: Andrew Owned by:
Component: other Version: VirtualBox 3.0.10
Keywords: stuck, upgrade Cc:
Guest type: other Host type: other

Description

I upgraded from 3.0.8 to 3.0.10 by uninstalling the old version and installing the new one. All three of my VMs (RHEL 5.4, Win Server 03, Win Server 08)will not load after upgrade.

Attachments (4)

VBox.log (185.4 KB ) - added by Andrew 14 years ago.
RHEL 5.4 log
VBox.png (959 bytes ) - added by Andrew 14 years ago.
RHEL 5.4 image
VBox.2.log (176.3 KB ) - added by Andrew 14 years ago.
Server 03 Log
VBox.2.png (5.8 KB ) - added by Andrew 14 years ago.
Server 03 image

Download all attachments as: .zip

Change History (14)

by Andrew, 14 years ago

Attachment: VBox.log added

RHEL 5.4 log

by Andrew, 14 years ago

Attachment: VBox.png added

RHEL 5.4 image

by Andrew, 14 years ago

Attachment: VBox.2.log added

Server 03 Log

by Andrew, 14 years ago

Attachment: VBox.2.png added

Server 03 image

comment:1 by Andrew, 14 years ago

Host system: OS - Windows 7 Professional 64 bit Processor - Intel Pentium Dual Core T2330 1.6Ghz Ram - 4GB Model - Dell Inspiron 1525 Laptop Hard Drive - 320GB Optical Drive - DVD+-RW

comment:2 by Knitebane, 14 years ago

I'm getting the same error running 3.0.10 on Ubuntu 9.04 32-bit running two Ubuntu 8.04 guests.

I get:

Guru Meditation -2403 (VERR_TRPM_DONT_PANIC)

EIP is not in any code known to VMM!

I reverted to 3.0.8 and I'm back running again.

Oddly, on a different machine I upgraded VirtualBox to 3.0.10 and it's working fine. (Ubuntu 8.04 32-bit host, Windows XP guest.)

comment:3 by palomino, 14 years ago

I've got the same problem on 2 computers.Hosts are ubuntu 9.10 64bit,and guests are win2003 32bit. One's cpu is Intel Celeron E3200(support VT-x), the other's is Intel Pentium E5200(not support VT-x) The guest os can boot when I enabled VT-x in the vm settings on E3200. I guess it might be a software virtualization problem?

comment:4 by Frank Mehnert, 14 years ago

Bug confirmed, a last-minute regression. Currently fixing. The 3.0.10 binaries are currently withdrawn and rebuilt. Thanks for the report.

comment:5 by Frank Mehnert, 14 years ago

Summary: All VM's stuck after upgrade to 3.0.10 from 3.0.8All VM's stuck or crash after upgrade to 3.0.10

comment:6 by Frank Mehnert, 14 years ago

priority: majorblocker

comment:7 by Frank Mehnert, 14 years ago

Host type: Windowsother

comment:8 by Sander van Leeuwen, 14 years ago

Resolution: fixed
Status: newclosed

3.0.10 has been refreshed. Download again please.

comment:9 by anonymous, 14 years ago

worked for me. thanks for the fast fix

comment:10 by Knitebane, 14 years ago

Works for me too. Thanks!

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use