error message:
Failed to open a session for the virtual machine XP.
Failed to open image 'G:\VirtualBox\XPmode\VirtualXP.VHD' for writing due to wrong permissions (VERR_VD_IMAGE_READ_ONLY).
PIIX3 cannot attach drive to the Primary Master (VERR_VD_IMAGE_READ_ONLY).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
how do i fix this?
Failed to open a session
-
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: Failed to open a session
The error message seems very clear to me. Obviously you need to make the VHD not read-only.alkalk wrote: how do i fix this?
Btw, an XPMode VM probably isn't going to work in VirtualBox. Those XP images were only ever licensed on Win7 hosts, they will not activate anywhere else.
Re: Failed to open a session
i had opened up the permissions to full control for everyone on the vhd file and now i have done the same for the folder and it's children also. now i get:
-----------
Failed to open a session for the virtual machine XP2.
Raw-mode is unavailable courtesy of Hyper-V. (VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
-----------
btw, i have my original XPpro disc and lisence key. does that get me around the XPmode limitations?
also does it need to be activated to run?
-----------
Failed to open a session for the virtual machine XP2.
Raw-mode is unavailable courtesy of Hyper-V. (VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
-----------
btw, i have my original XPpro disc and lisence key. does that get me around the XPmode limitations?
also does it need to be activated to run?
-
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: Failed to open a session
Regarding the Hyper-v error, read: HMR3Init: Attempting fall back to NEM (Hyper-V is active).
Regarding your XP Pro installer: I'm pretty sure that you can't update the product key on an XP mode VM. But, you can easily create a new VM using an XP setup CD (ISO), provided it isn't locked to a particular manufacturer's BIOS (e.g. Dell and HP used to do that). You may also have difficulty with online activation as the necessary servers may no longer exist. Phone activation may still work (don't know - it is many years since I last tried to activate XP).
Regarding your XP Pro installer: I'm pretty sure that you can't update the product key on an XP mode VM. But, you can easily create a new VM using an XP setup CD (ISO), provided it isn't locked to a particular manufacturer's BIOS (e.g. Dell and HP used to do that). You may also have difficulty with online activation as the necessary servers may no longer exist. Phone activation may still work (don't know - it is many years since I last tried to activate XP).
Re: Failed to open a session
ok, i got it running by turning off all hyperV .
it's apparently in 30 day mode. does activating get around this?
it's apparently in 30 day mode. does activating get around this?
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: Failed to open a session
30-day mode is because it is not activated. Web-search how to activate XP in 2020/2021 and something will come up.