Windows 10 IoT Raspberry - VirtualBox

[Manoj Shenoy]

I want to run the Windows 10 IoT Raspberry on VirtualBox.

I followed all steps explained http://www.newventuresoftware.com/blog/ ... l-machine/

I'm getting this error:

Code: Select all

Failed to open a session for the virtual machine w10IoT.

Failed to open image 'G:\VM_Workstations\wIoTTest\kmdF41E.vhd' for writing due to wrong permissions (VERR_VD_IMAGE_READ_ONLY).

Failed to attach driver below us! Image is read-only. (VERR_VD_IMAGE_READ_ONLY).

AHCI: Failed to attach drive to Port0 (VERR_VD_IMAGE_READ_ONLY).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

I tried for both MinnowBoardMax and also for Raspberry.

I have no Raspberry board, so help needed to run this on VirtualBox.

[mpack]

"Windows 10 IoT Raspberry"? Is that as in Raspberry Pi? If it requires an ARM CPU then it isn't going to run in VirtualBox.

Apart from that, a permissions issue on your host is something you have to fix yourself. You need to ensure that your user has write access to the VM folder, and that none of the files are read only.

[scottgus1]

If ARM processor problem is not an issue, and your guest will run on an X86 processor, and drive G is a USB drive, see this: viewtopic.php?f=2&t=38007 "error IMAGE_READ_ONLY on USB-based vdi"

[Manoj Shenoy]

Its can be used refer here
Www[.]newventuresoftware[.]com/blog/running-windows-10-iot-core-in-a-virtual-machine/

I'm just getting error of permission,

Pls help

[Manoj Shenoy]

None of the files are readonly,
I've run VirtualBox as Admin.

It is not usb, its a VHD, virtual hard disk, attached to storage management in Windows 10.

[BillG]

I read through the article referenced. If the OP followed the directions he should have a 32-bit X86 compatible VHD file.

It looks like a straight-forward Windows permissions issue to me.

Did you install VirtualBox using your usual username with admin privilege? Who does Windows show as the owner of the .vhd file?

[Manoj Shenoy]

I have only one user on my system, so the same user is Admin,
However I uninstalled VirtualBox and Installed as Admin, also after that I selected "Run as Admin" while opening VirtualBox.
But same error.

[andyp73]

It is not usb, its a VHD, virtual hard disk, attached to storage management in Windows 10.

This statement would seem to imply that you didn't follow step 4 in section on creating the virtual machine in the blog post.

The instructions in step 4 are to run mmc.exe on your Windows host and add the "Disk Management" snap-in so that you can detach the VHD file from Windows. I'm not an expert but if the Windows host thinks it is still in control of the mounted VHD file then I can see why it might only make it available in read only mode to other applications trying to access it at the same time.

I have followed the instructions in the blog post to the letter and didn't have any problems.

Andy.

[scottgus1]

It is not usb, its a VHD, virtual hard disk, attached to storage management in Windows 10.

I didn't ask if the vhd file is a USB drive.

If . . . drive G is a USB drive, see this"

I asked if the disk it's on, drive G, is a USB drive. Please read carefully.

You report that it is "attached to storage management". That piece of info needed to be in your first post. That would have clued us all in quickly. Your host PC is using the vhd, so it cannot be used by Virtualbox. Thus the permissions error. Andy is correct, looks like you didn't follow the instructions. More of "Please read carefully" needed.

[Manoj Shenoy]

scottgus1 : I'm sorry, I would have mention about VHD in the initial query,

But If VirtualBox is not allowed for accessing the VHD, I really wonder how this guy (www[.]newventuresoftware[.]com/blog/running-windows-10-iot-core-in-a-virtual-machine/) is doing it, I have followed each and every instruction in this reference.

If possible pls have a look.

KeyNote : Windows doesn't allow to move VHD files when it is being accessed, So as u said at step 4, I have detached to and moved VHD file to some-other drive, and on attaching back, "G" drive is being assigned.

[scottgus1]

Virtualbox can access VHDs just fine, if the VHD is not being used by another program. If you have disconnected the VHD file from the host OS as step 4 in the blog says, then you have some other problem.

Is the drive you put the VHD file on an external USB drive?

[mpack]

What type of drive is G: ? (local hd, external hd, CD/DVD, network?)

[Manoj Shenoy]

scottgus1 : I have detached the VHD copied it to G drive, then again attached to OS(Windows 10).

I dont think the VHD is being used by any other process.

G is a partition on my physical harddisk

[scottgus1]

G is a partition on my physical harddisk

I will assume your "physical harddisk" is internal, attached via SATA or parallel ATA, not USB. (USB drives are "physical harddisks" too.)

I dont think the VHD is being used by any other process.

Yes it is still being used by another process, this one:

then again attached to OS(Windows 10).

You will not be able to use the VHD in Virtualbox while the host OS has it attached.

[Manoj Shenoy]

scottgus1: It worked after detaching from the OS,

Thanks alot.