Page 1 of 1
fault when start with vboxmanage but np with voxheadless....
Posted: 15. Dec 2011, 10:42
by xzyyy
[root@www /]# VBoxManage startvm win2003
Waiting for VM "win2003" to power on...
VBoxManage: error: The virtual machine 'win2003' has terminated unexpectedly during startup with exit code 0
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component Machine, interface IMachine, callee
firstly, i set my guest with vrdp(start vm with vboxheadless), but when i open the port 3389 on the guest os, i set vrdp off and start my guest os with vboxmanage startvm, but it failed....
is there any suggestion?
thanks a lot
Re: fault when start with vboxmanage but np with voxheadless
Posted: 17. Dec 2011, 17:50
by xzyyy
Any suggestion? Thanks....
Re: fault when start with vboxmanage but np with voxheadless
Posted: 18. Dec 2011, 03:16
by Perryg
Don't run the host as root.
Seriously why are you running as root? Anyway your answers are in the VirtualBox users manual.
VBoxManage startvm must have an additional key, but VBoxHeadless does not.
See chapter 7.1.2 VBoxHeadless, the remote desktop server in your VirtualBox users manual
Re: fault when start with vboxmanage but np with voxheadless
Posted: 18. Dec 2011, 17:16
by xzyyy
thanks, i have check the manual and solve the problem.
Re: fault when start with vboxmanage but np with voxheadless
Posted: 18. Dec 2011, 17:51
by xzyyy
Hi, Perryg
is there anyway to migrate the vm register by root to another user in linux? i have configured my guest system but i can't list it under a common user.
thanks in advance.
Re: fault when start with vboxmanage but np with voxheadless
Posted: 18. Dec 2011, 18:05
by Perryg
If you have been running and installing everything as root the permissions will all be so restrictive that you are in for some heavy work figuring it all out.
Normally you would simply set the VBOX_USER_HOME environment and be done with it, but that probably will not help much in this case.
See chapter 10.1.3 Global configuration data in your VirtualBox users guide.
Re: fault when start with vboxmanage but np with voxheadless
Posted: 18. Dec 2011, 18:52
by xzyyy
Hi Perryg,
Thanks for your help firstly, i try to solve the problem, cp all files including global setting and guest setting files to /home/vboxuser/, change all files owner to vboxuser, now i can find my guest system with VBoxManage, but when i start it without VRDE, it returns me the same error.
Waiting for VM "win2003" to power on...
VBoxManage: error: The virtual machine 'win2003' has terminated unexpectedly during startup with exit code 0
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component Machine, interface IMachine, callee
is there any suggestion? i don't know what the meaning of "VBoxManage startvm must have an additional key" is in your post, could you please send me a url talked about it?
thanks a lot.
Re: fault when start with vboxmanage but np with voxheadless
Posted: 18. Dec 2011, 18:55
by Perryg
See chapter 7.1.2 VBoxHeadless, the remote desktop server in your VirtualBox users manual
Re: fault when start with vboxmanage but np with voxheadless
Posted: 18. Dec 2011, 19:04
by xzyyy
Thanks a lot, i can start my guest system with VBoxHeadless --vrde=off
btw, that means, i can't start a guest system with VBoxManage if i don't have a local graphical interface on host system and disable vrde mode, am i right?
Re: fault when start with vboxmanage but np with voxheadless
Posted: 18. Dec 2011, 19:11
by Perryg
VBoxManage is the command line interface. It does not use/need a graphical interface. If this is not what you mean then you will need to explain better.
Re: fault when start with vboxmanage but np with voxheadless
Posted: 18. Dec 2011, 19:18
by xzyyy
sorry for my poor english, i mean, if i want to start a guest system with VBoxManage, i need enable vrde setting, or i need a x windows to start it. am i right?
Re: fault when start with vboxmanage but np with voxheadless
Posted: 18. Dec 2011, 19:31
by Perryg
If the host does not have X then you must use vrdp/rdp/vnc. something to be able to see the guest if you plan to actually work in the guest. The only exception is running a fixed server or anything CLI that you can use SFTP, SSH, Etc..