guest now inaccessible since attempt to install v3.0.2

Discussions related to using VirtualBox on Windows hosts.
Post Reply
LDT2
Posts: 5
Joined: 20. Jan 2009, 20:37

guest now inaccessible since attempt to install v3.0.2

Post by LDT2 »

I have been successfully running version 2.2.4 for some time now on my Vista Home Premium SP2 AMD 64 x2 32bit laptop.
I received an email this morning saying that VB had a new version released, 3.0.2. I installed it with no problem, however when trying to start the XP Pro guest I got an error that the kernel couldn't be started along with some others. I immediately reinstalled v 2.2.4, which also installed fine. However now the XP Pro guest says that it's inaccessible and under the details:
vendor ID value is `FFFFFFFF' is too big (max 0xFFFF).
Result Code: E_INVALIDARG (0x80070057)
Component: USBDeviceFilter
Interface: IUSBDeviceFilter {d6831fb4-1a94-4c2c-96ef-8d0d6192066d}

Refresh does nothing.

I did a restore in two places prior to either installation, but have the same problem described above.

Any help would be appreciated. Thank you.
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: guest now inaccessible since attempt to install v3.0.2

Post by Perryg »

Was the XP pro 64 bit? Was it setup for 64 bit in 2.2.4?
Look at the io apic and see if it is set correctly.
LDT2
Posts: 5
Joined: 20. Jan 2009, 20:37

Re: guest now inaccessible since attempt to install v3.0.2

Post by LDT2 »

It was setup for 32bit which is the OS on my laptop. It ran perfectly on v2.2.4 of VB until I installed v3.0.2, which wouldn't run at all, so I returned to v2.2.4 and now it's inaccessible.

I don't understand why the restore didn't work.
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: guest now inaccessible since attempt to install v3.0.2

Post by Perryg »

If you had io apic on when you installed the new version (it supports smp) Windows will try to install the smp kernel. Happened to me as well. I had to turn off the io apic and then restore to a point before the update to get mine back up.
LDT2
Posts: 5
Joined: 20. Jan 2009, 20:37

Re: guest now inaccessible since attempt to install v3.0.2

Post by LDT2 »

I'm sure that I had the io apic disabled, but how would I access it now? I can't access any settings. All I see is the details tab with the info in my 1st post. Everything else is grayed out.
LDT2
Posts: 5
Joined: 20. Jan 2009, 20:37

Re: guest now inaccessible since attempt to install v3.0.2

Post by LDT2 »

OK. Shooting in the dark I right clicked the xml file and edited the text by shortening the FFFFFFFF to FFFF in all instances and refreshed the guest and now all the information and settings have returned.
So I tried to start XP and it began to boot and then I got an error message:

Failed to start the virtual machine Windows XP Pro

Cannot load GC module in Lr\PROGRA~1\Sun\xVM
VirtualBox/VMMGC.gc (VERR_FILE_NOT_FOUND)
Details:
Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole
{9511bc54-15ee-4ddf-808e-472aba03809c}

Any ideas?
LDT2
Posts: 5
Joined: 20. Jan 2009, 20:37

Re: guest now inaccessible since attempt to install v3.0.2

Post by LDT2 »

Well this must be my day of discovery.

I repaired the installation of v2.2.4 (which I did try multiple times in earlier attempts) after a final restore to before I installed v3.0.2.
Then I tried starting the XP guest and it started!
I did have an warning message about a potential problem with some devices as it booted so after it completed I shut it down.
I opened settings and checked the USB filters as that was in the first error message. Right clicking each one and clicking edit filter, I noticed under the name that the remaining boxes had all those FFFF things in there.
So I removed the filters and then added new ones. Checking in the edit filter screen, all the boxes were now empty.
Also there were 3 folders created in C:\Program Files named Sun(108), Sun(110) and Sun(171) as well as the regular Sun folder. I deleted those 3.
Everything seems to be working fine now.

Hopefully this may help someone else that may run into this situation.

Although why v3.0.2 scrambled all this I don't know, but all I can say is I'm not updating from 2.2.4 until the VB says there's an update next time it checks.

Perryg thanks for your input, it started me looking in the right direction.
Post Reply