I have been running an small application developed for Windows XP using Virtualbox. Now it is time to move the VM to Virtualbox on another PC.
I got the information that it is just to move the VM to the new Virtualbox installation on the new PC.
I followed the information and doubble clicked the .vbox file on the new host.
The result was very positive and I could display the snapshots and select the last one.
However when starting the machine i got this error.
Failed to open a session for the virtual machine Windows XP Mode.
The VM session was closed before any attempt to power it on.
Result Code: E_FAIL (0x80004005)
Component: SessionMachine
Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}
See the screenshot
What does that mean?
Move VM to a new PC
Move VM to a new PC
- Attachments
-
- Session-closed.PNG (56.9 KiB) Viewed 1392 times
Last edited by stawes on 27. Oct 2021, 20:15, edited 1 time in total.
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Move VM to a new PC
Please provide a VM log file. Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.
Re: Move VM to a new PC
The file is very short.
- Attachments
-
- XP-vbox.zip
- (856 Bytes) Downloaded 7 times
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Move VM to a new PC
Well, less to read then.stawes wrote:The file is very short.
At least it tells that a saved-state file is missing. Generally speaking, a VM in a saved state is like a paused PC, and can usually only continue on the same (physical and virtual) hardware. If this is the only problem, the easy solution is to discard the saved-state by right-clicking on the VM in the VirtualBox Manager and selecting Discard Saved State..., and the more complex solution is to shut down the guest OS on your original VM before copying it anew. When you choose the easy solution, you only lose the content of the guest OS memory, not the content of the guest OS disks.
Last edited by fth0 on 16. Nov 2021, 18:57, edited 1 time in total.
Re: Move VM to a new PC
The new host operating system is now 64 bit home edition and not 64bit Pro. Is the resultit likely to change if I upgrade to Pro?
New error message with current changed state:
Failed to open a session for the virtual machine Windows XP Mode.
Could not open the medium 'C:\KIT\XPMode\XPMode-write\VirtualXP.VHD'.
VD: error VERR_PATH_NOT_FOUND opening image file 'C:\KIT\XPMode\XPMode-write\VirtualXP.VHD' (VERR_PATH_NOT_FOUND).
Result Code: E_FAIL (0x80004005)
Component: MediumWrap
Interface: IMedium {ad47ad09-787b-44ab-b343-a082a3f2dfb1}
Should I save a copy of the saved VM before shutting down the current VM so I can change back to the current workin VM?
I definitely dont want to get back to the state where I need to give the administrator password.
New error message with current changed state:
Failed to open a session for the virtual machine Windows XP Mode.
Could not open the medium 'C:\KIT\XPMode\XPMode-write\VirtualXP.VHD'.
VD: error VERR_PATH_NOT_FOUND opening image file 'C:\KIT\XPMode\XPMode-write\VirtualXP.VHD' (VERR_PATH_NOT_FOUND).
Result Code: E_FAIL (0x80004005)
Component: MediumWrap
Interface: IMedium {ad47ad09-787b-44ab-b343-a082a3f2dfb1}
Should I save a copy of the saved VM before shutting down the current VM so I can change back to the current workin VM?
I definitely dont want to get back to the state where I need to give the administrator password.
- Attachments
-
- XP-changed state VBox-log.zip
- (892 Bytes) Downloaded 7 times