VirtualBox

Ticket #3199 (closed defect: fixed)

Opened 10 months ago

Last modified 9 months ago

S10 U6 patched up on 11/24, not working with VBoxHeadless => Fixed in SVN

Reported by: standardrockets Assigned to:
Priority: major Component: other
Version: VirtualBox 2.1.2 Keywords: VBoxHeadless clipboard
Cc: Guest type: Windows
Host type: Solaris

Description

When launching VirtualBox headless, the VM does not start. If you look at the attached log file, it hangs at this line: 00:00:00.305 Initializing host clipboard service

Everything after that log message is after I CONTROL-C the program.

I'm launching it like this: root:=> VBoxHeadless -startvm billing

I see no errors on the screen.

If I launch it on the console (JDS) things work great. The log file for a successful launch looks the same up to the "Initializing host clipboard service" and continues just fine.

Attachments

VBox.log.3 (0.9 kB) - added by standardrockets on 2009-01-27 20:24:37.
logfile of vbox failing to start with vboxheadless

Change History

2009-01-27 20:24:37 changed by standardrockets

  • attachment VBox.log.3 added.

logfile of vbox failing to start with vboxheadless

2009-01-28 13:11:05 changed by standardrockets

I used the GUI to disable the clipboard service and the virtual machine still does not start. The log file looks exactly the same as attached with the exception of the clipboard messages missing. So it does not appear to be tied to the clipboard.

2009-02-03 10:08:43 changed by frank

What happens if you start the VBoxHeadless session like this: 

unset DISPLAY
VBoxHeadless ...

I'm not sure which shell you are using so the command for unsetting the DISPLAY environment variable might be different.

2009-02-03 15:00:59 changed by standardrockets

That worked around the issue.

2009-02-04 11:48:06 changed by frank

  • summary changed from S10 U6 patched up on 11/24, not working with VBoxHeadless to S10 U6 patched up on 11/24, not working with VBoxHeadless => Fixed in SVN.

Thanks for testing this. This problem will be properly fixed in the upcoming bugfix release.

2009-02-16 20:19:24 changed by frank

  • status changed from new to closed.
  • resolution set to fixed.

Fix contained in 2.1.4.

© 2009 Sun Microsystems, Inc.
Contact – Privacy policy