VirtualBox update woes
Not sure what happened here but upgrading from VirtualBox 3.x to 4.06 (with Oracle branding too – eek), killed a few of my VMs. First USB 2.0 support is now a part of some separate package, and then 4 out of 9 VMs would not start with messages like:
unknown configuration node //DB2
At this point i was thinking how the hell did VirtualBox know about my DB2 installation – assuming that my DB2 database installed on that VM was an issue. A little confusing here too given that i would get the VM window and then it would just close so it wasn’t getting anywhere near starting the OS – WindowsXP.
Anyway a bit of digging about and then this:
takisd@fitter:~> VBoxManage getextradata WindowsXP-1 enumerate Key: GUI/LastCloseAction, Value: powerOff Key: GUI/LastGuestSizeHint, Value: 640,480 Key: GUI/LastNormalWindowPosition, Value: 1437,47,640,527 Key: GUI/LastWindowPostion, Value: 1422,111,1224,867 Key: GUI/MiniToolBarAlignment, Value: bottom Key: GUI/MiniToolBarAutoHide, Value: on Key: GUI/SaveMountedAtRuntime, Value: yes Key: GUI/ShowMiniToolBar, Value: yes Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/DB2/GuestPort, Value: 50000 Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/DB2/HostPort, Value: 50000 Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/DB2/Protocol, Value: TCP Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/Firebird/GuestPort, Value: 3050 Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/Firebird/HostPort, Value: 3050 Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/Firebird/Protocol, Value: TCP Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/Oracle/GuestPort, Value: 1521 Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/Oracle/HostPort, Value: 1521 Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/Oracle/Protocol, Value: TCP Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/SQLServer/GuestPort, Value: 1433 Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/SQLServer/HostPort, Value: 1433 Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/SQLServer/Protocol, Value: TCP
…where WindowsXP-1 is the name of the virtual machine.
So all my intalled DBs on that particular VM had a setting on them for respective ports. I use most VMs for testing against various databases for various apps and mainly for Execute Query.
I vaguely recalled setting these some time ago – probably as a network response for forwarding – either way i didn’t really remember and resetting these with empty values fixed the problem like this:
VBoxManage setextradata WindowsXP-1 "VBoxInternal/Devices/pcnet/0/LUN#0/Config/DB2/GuestPort"
…and so on for the other nodes. Restarting the OS worked just fine and I now have my VMs back. Not sure if this documented anywhere by Oracle – quite the gotcha for seemingly simple upgrade.
…and here i was thinking WTF did Oracle do now…
About Takis Diakoumis
I am a software developer from Melbourne, Australia. I promote and support open source software and release whatever I can of my own work under the GPL license.
No Comments