Hello all,
I've trouble getting a shared folder to work in the following
(automated) setup:
host: Linux, OpenSuSE 11.4
guest: Windows Vista Home
After launch of the VM, I do:
VBoxManage guestcontrol WindowsVista32Raw execute --image "cmd.exe" \
--username **** --password **** --wait-stdout --wait-exit \
--wait-stderr -- /C net use T: \\VBOXSVR\test
This only succeeds if both of the following conditions are met with:
a. the VM was launched with "VBoxManage startvm", and
b. I was physically present at the keybord/monitor to log on to the
system from the GUI, before issuing the above VBoxManage command.
In the case of launching the VM with VBoxHeadless, or when not being
logged on to the system, the following error message is returned
(translated from Dutch[*]):
System error 67.
Cannot find the network name.
The purpose of the whole exercise is to have the shared folder available
for automated software testing. Therefore, not needing
to log on through the GUI is essential.
It seems that mounting the shared folder is the only barrier that
prevents me from complete automation. Can this barrier be overcome in
any way?
Thanks for any insight,
Erik Leunissen
--
[*]
Systeemfout 67.
Kan de netwerknaam niet vinden.
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
VBox-users-community mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
_______________________________________________
Unsubscribe:
mailto:[email protected]?subject=unsubscribe
