VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1681 - 1683 of 16363)

Ticket Resolution Summary Owner Reporter
#18442 invalid Can't start VM Timtamourn71
Description

Failed to open a session for the virtual machine Minix 3.

Raw-mode is unavailable courtesy of Hyper-V. (VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT).

Result Code: E_FAIL (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

* I got the above error and I think it is a bug. Please advise.

Thanks,

Tim

#15293 obsolete Can't start VM after configuring host only network HackerBaloo
Description

Running Windows 7 sp1 on the host, a 64-bit Debian (wheezy) server with first network adapter connected to hostonlyif - "VirtualBox Host-Only Ethernet Adapter"

Steps to reproduce:

  1. Setup my Debian VM (see above)
  2. Start it - it works
  3. Run my script test.py (attached), that tears down and sets up the hostonly configuration I would like, using vboxmanage
  4. Try to start vm again - fails with error, see below
  5. Uninstall VirtualBox
  6. Install VirtualBox
  7. Note that the Hostonly configuration is still there
  8. goto 2, and repeat as many times as you like

I would also like to point out that a lot of related defects have been closed after people have tried another version, but the thing is, it always works after reinstall, but the issue is still not fixed. So I believe this way to reproduce could be a nice opportunity to finally solve this problem.

Error message when it fails: Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND).

Perhaps related: https://www.virtualbox.org/ticket/15103 https://www.virtualbox.org/ticket/15060

Tested with 5.0.10, 5.0.12, 5.0.14, 5.0.16, 5.0.17-106359

#8342 fixed Can't start VM using VBoxSDL --startvm UUID in command line => Fixed in SVN Mr_LinDowsMac
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.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy