VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (742 - 744 of 16363)

Ticket Resolution Summary Owner Reporter
#21031 worksforme After upgrade to 6.1.36 on Windows 10, can't launch RHEL guest Clowers
Description

I upgraded VB on my Windows 10 host to release 6.1.36, and now when I try to launch my RHEL guest, there is an error, and the guest won't run. The host is running Windows 10 Version 21H2 (OS Build 19044.1826) on a Dell XPS 8930 tower. The error message that is copied to the clipboard when I click "Copy" on the window that comes up when it fails, is: ===== Failed to open a session for the virtual machine RHEL first. The virtual machine 'RHEL first' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\paulc\VirtualBox VMs\RHEL first\Logs\VBoxHardening.log'. Result Code: E_FAIL (0x80004005) Component: MachineWrap Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df} ===== The file VBoxHardening.log suggests to run a command, the output of that command is:


C:\Users\paulc\VirtualBox VMs\RHEL first\Logs>sc.exe query vboxdrv [SC] EnumQueryServicesStatus:OpenService FAILED 1060:

The specified service does not exist as an installed service.


I don't see a way to attach files to this web interface, I'll see if I can attach them after posting

#11659 obsolete VT-x setting cannot be disabled if VT-x is not supported CoJaBo
Description

The option to turn VT-x on or off is only shown if VT-x is supported by the host CPU. This makes it impossible to use a VM created on a VT-x capable machine on another machine that does not support VT-x; when attempting to start such a machine, VirtualBox complains that VT-x is not supported, but there is no way to turn it off. Additionally, turning off the VT-x related settings through the command line does not appear to work either; there is no error, but the settings do not get changed.

  1. Create a VM on a machine that supports VT-x; make sure VT-x is enabled (which appears to be the default)
  2. Export the VM; in my case, it was to a .OVA file.
  3. Set the machine on fire (optional)
  4. Import the VM on another machine that does not support VT-x
  5. Attempt to start the VM

The only work-around I could find was to re-create the machine from scratch, using only the existing virtual disks; this results in loss of snapshot data though. The VM booted up just fine after this, without VT-x support. Suposedly, editing the XML files also works, but this does not appear possible with .OVA format VMs.

Rather than outright disabling access to the VT-x settings when not supported, the GUI ought to just mark them invalid like every other settings page does; this would allow the problem to be corrected.

Importing the machine on a VT-x machine and disabling it there ought to work, of course, but in my case I did not have access to any other machine that supported it. The same issue also happens when downloading VMs created by others.

#7925 worksforme You don't have permission to access CodeZero
Description

when i try to download VirtualBox 4.0 Oracle VM VirtualBox Extension Pack i get the following message: You don't have permission to access "http://dlc.sun.com.edgesuite.net/virtualbox/4.0.0/Oracle_VM_VirtualBox_Extension_Pack-4.0.0-69151.vbox-extpack" on this server. Reference #18.85447b5c.1293513786.131fb75b

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