VirtualBox

Ticket #8342 (closed defect: fixed)

Opened 12 years ago

Last modified 12 years ago

Can't start VM using VBoxSDL --startvm UUID in command line => Fixed in SVN

Reported by: Mr_LinDowsMac Owned by:
Component: GUI Version: VirtualBox 4.0.2
Keywords: Cc:
Guest type: Linux Host type: Linux

Description

In previous version of VirtualBox I didn't have this problem.

After created a Virtual Machine in VirtualBox (and also run it) I try to run a virtual machine in a terminal (I'm using openSUSE Linux 11.3). Everything is fine when I use the option

VBoxSDL --startvm "VM_Name"

but If I try to use VM's UUID instead VM's name:

VBoxSDL --startvm 1234-4563-4566-a4563-asas5

VBoxSDL launch a Violation Segment error and VM doesn't launch. Obviously that UUID above is just and example, but I tried with good ones and I got that error.

I need to get this bug fixed, because I usually use a script to start the last VM reading the UUID, and is useless by this problem.

I don't attach any log file for this reason: You could test it in a terminal yourself and I don't know where this log is generated.

Change History

comment:1 Changed 12 years ago by frank

  • Summary changed from Can't start VM using VBoxSDL --startvm UUID in command line to Can't start VM using VBoxSDL --startvm UUID in command line => Fixed in SVN

Thanks for this report. We already fixed this problem in the code and the fix will be available in the next maintenance release.

comment:2 Changed 12 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use