WinXP - VMWare convert with ovf tool to VBox - crash on Import

Discussions about using Windows guests in VirtualBox.
Post Reply
HH-TFI
Posts: 3
Joined: 9. Apr 2019, 16:43

WinXP - VMWare convert with ovf tool to VBox - crash on Import

Post by HH-TFI »

Hello all,
i converted a VMWare WinXP image with the VMWare ovf tool.
(Removed the VMWare tools from the guest system)

The import of the ovf file back to VMWare works normal. The import to VBox shows an error:
Failed to import appliance .

Callee RC: RPC_S_SERVER_UNAVAILABLE 0x800706BA (0x800706BA)
Can someone explain me what i need to do to make the ovf file import to VBox will be successfull :-)

Thanks for help
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: WinXP - VMWare convert with ovf tool to VBox - crash on Import

Post by mpack »

ISTM that VirtualBox has not been installed properly. Try again, using "Run as adminstrator" to run the installer while logged in as the correct user (i.e. not the Admin named account).
Dolorosus
Posts: 1
Joined: 25. May 2019, 13:29

Re: WinXP - VMWare convert with ovf tool to VBox - crash on Import

Post by Dolorosus »

Hi,

same problem here, import the ovf on Vbox crashes, reinstall didn't help. This is my log:

Code: Select all

00:00:00.000000 main     VirtualBox COM Service 6.0.8 r130520 win.amd64 (May 13 2019 14:14:44) release log
00:00:00.000000 main     Log opened 2019-05-25T11:21:03.610802800Z
00:00:00.000000 main     Build Type: release
00:00:00.000000 main     OS Product: Windows 7
00:00:00.000000 main     OS Release: 6.1.7601
00:00:00.000000 main     OS Service Pack: 1
00:00:00.031200 main     DMI Product Name: Latitude E5540
00:00:00.093600 main     DMI Product Version: 00
00:00:00.093600 main     Host RAM: 8097MB (7.9GB) total, 3756MB (3.6GB) available
00:00:00.093600 main     Executable: C:\Program Files\Oracle\VirtualBox\VBoxSDS.exe
00:00:00.093600 main     Process ID: 3660
00:00:00.093600 main     Package type: WINDOWS_64BITS_GENERIC
00:00:00.093600 main     WinMain: VBoxSDS: InitializeSecurity: 0
00:00:00.109200          registerVBoxSVC: aVBoxSVC=0000000000323588 aPid=4640 (0x1220)
00:00:00.109200          i_lookupOrCreatePerUserData: Created new entry for S-1-5-21-5079566473-2578209370-2019731724-1000 (lanxxxx/xxxx)
00:00:00.109200          registerVBoxSVC: Making aPid=4640 (0x1220) the chosen one for user S-1-5-21-5079566473-2578209370-2019731724-1000 (lanxxxx/xxxx)!
00:02:16.074532          registerVBoxSVC: aVBoxSVC=0000000000323eb8 aPid=10204 (0x27dc)
00:02:16.074532          registerVBoxSVC: Seems VBoxSVC instance died.  Dropping it and letting caller take over. (hrc=RPC_S_SERVER_UNAVAILABLE 0x800706BA)
00:02:16.074532          i_unchooseTheOne: Irregular release ... (pid=4640 (0x1220) user=lanxxxx/xxxx sid=S-1-5-21-5079566473-2578209370-2019731724-1000)
00:02:16.074532          i_unchooseTheOne: ... done.
Any idea or solution for this (except using Vmware)?

Ok it seems that Vbox isn't able to import ovf's with snapshots (stunning)...
Besides Vbox crashing commentless, this is missing in the documentation.
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: WinXP - VMWare convert with ovf tool to VBox - crash on Import

Post by mpack »

Dolorosus wrote: Ok it seems that Vbox isn't able to import ovf's with snapshots (stunning)...
And never has supported that, AFAIK it isn't even part of the OVF spec - snapshots are always merged when exporting an appliance.
Post Reply