VirtualBox

Opened 15 years ago

Closed 15 years ago

#3199 closed defect (fixed)

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

Reported by: Lyle Merdan Owned by:
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 (1)

VBox.log.3 (874 bytes ) - added by Lyle Merdan 15 years ago.
logfile of vbox failing to start with vboxheadless

Download all attachments as: .zip

Change History (6)

by Lyle Merdan, 15 years ago

Attachment: VBox.log.3 added

logfile of vbox failing to start with vboxheadless

comment:1 by Lyle Merdan, 15 years ago

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.

comment:2 by Frank Mehnert, 15 years ago

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.

comment:3 by Lyle Merdan, 15 years ago

That worked around the issue.

comment:4 by Frank Mehnert, 15 years ago

Summary: S10 U6 patched up on 11/24, not working with VBoxHeadlessS10 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.

comment:5 by Frank Mehnert, 15 years ago

Resolution: fixed
Status: newclosed

Fix contained in 2.1.4.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use