The same VDI file on two host PCs - Only one works

Discussions related to using VirtualBox on Windows hosts.
Post Reply
freddy
Posts: 1
Joined: 28. Feb 2013, 13:27
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: XP32
Location: Belgium

The same VDI file on two host PCs - Only one works

Post by freddy »

Two host PC (Windows 7-64bit), the same guest (XP32 sp3) works perfectly on the first one and not on the other.
I use the same VDI file, on the two hosts.
Thank you in advance.

Here is the log (attached)
Attachments
VBox.log
(64.36 KiB) Downloaded 4 times
noteirak
Site Moderator
Posts: 5231
Joined: 13. Jan 2012, 11:14
Primary OS: Debian other
VBox Version: OSE Debian
Guest OSses: Debian, Win 2k8, Win 7
Contact:

Re: The same VDI file on two host PCs - Only one works

Post by noteirak »

The provided log does not show issues, so I assume it is the log of the working VM? If yes, we need the log of the not working one as well.
How do you transfer the VDI file? How do you link it to the VM on both your hosts?
You also say it doesn't work - what doesn't work? What error message do you get?
The output of the following command on both hosts would be useful aswell :

Code: Select all

vboxmanage showvminfo <vmname> --details
Attach the outputs as a zip file.

You need to provide us with more information so we can understand what is going on
Hyperbox - Virtual Infrastructure Manager - https://apps.kamax.lu/hyperbox/
Manage your VirtualBox infrastructure the free way!
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: The same VDI file on two host PCs - Only one works

Post by mpack »

"doesn't work on the other" is not useful. We need an accurate description of the problem. What doesn't work? What error messages or other symptoms do you see.

I should say however that copying a VDI to a new VM on a new PC is the equivalent of taking the hard disk out of one PC and putting it in another. A lot of things can do wrong. You need to narrow it down for us. A better idea would have been for you to copy the entire VM, not just one of the components.
Post Reply