virtualbox.org

Hi
I can't seem to use remote desktop to start VMs on Virtual Box. I'm using an XP sp3 client to connect to a Windows 7 Ultimate client on a Home Network. I can connect to the Windows 7 client and open programs and save etc. I can open Virtual Box as well but when I start any VM I get:

Failed to open a session for the virtual machine Win7 Client.
Cannot open host device 'E:' for readonly access. Check the permissions of that device (VERR_ACCESS_DENIED).
Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {db7ab4ca-2a3f-4183-9243-c1208da92392}

Does anyone no how to give access please. The VMs open no problem on the Win 7 computer.

Please read Minimum information needed for assistance.

OK Pardon.

Please find log attached.
VBox ver 4.2.0 r80737
Host: Win 7 Ultra 64bit 12Gb
Remote desktop client: XP sp3 32bit 512kb
Virtual Machine: Win 7 64bit base mem 512kb but same problem regardless of VM I am trying to open

Error message given above.
All VMs will open directly on host but will not open via XP Client using remote desktop.

Please can you help if you know how to grant access to VMs from remote client.

What is assigned to the DVD reader of the virtual machine which you are trying to open? Will the vm start remotely if you remove it (from the settings of the vm accessed from the VirtualBox Manager screen)?

If BillG suggestion doesn't work, I would recommend updating your VB installation.

Looks like VB and remote access to host are not very happy.

Using simple Windows 7 setup

Tried TightVNC to host, VB was already running, locked up the display and all mouse click events.

so...

Tried RDP to host VB was already running VB crashed and restarted, tried starting a clone process and VB reported access readonly to empty CD drive. Several attempts yielded same results with crashes of VB.

Conclusion: VB does not like it when the host is running from a remote access. Limitation, improper configuration settings or bug, who is to say. Personally I say it is a bug, could not find appropriate configuration settings, if this is a limitation then why?

I remote into our server-class machine running Windows 7 professional 64bit, Virtualbox, and several guests including a SBS2003 domain controller guest, all the time using UltraVNC on the host with no problems (except when I am testing a guest that doesn't have guest additions installed or keyboard & mouse integration is turned off - the host seems to be freezing, but the mouse/keyboard are just captured by the guest - a quick tap on the Host key releases them).
I can see Microsoft Remote Desktop could posibly cause problems, since their implemetation of remote control seems to be heavily tied into the logged-on account, and Virtualbox's default configuration requires a logged-on user.
Maybe TightVNC just had a glitch or was on View Only? Try it again, or try a different VNC flavor.

Cool,

UltraVNC worked

Had to install service (just running the service did not work) also allows me to scroll across all 4 monitors.