VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (625 - 627 of 16363)

Ticket Resolution Summary Owner Reporter
#19674 fixed VirtIO-SCSI controller fails to see disk Feline
Description

I appreciate that the VirtIO-SCSI support is currently experimental but I have been doing some testing of it. It works fine with my Debian guests, both for attaching data volumes and to boot from.

However, when using Windows 10, I cannot get any disks that are attached to the controller to be seen inside the Windows 10 guest. I have installed the RedHat drivers for Windows from the Fedora site, both the current stable version and the latest build but they both exhibit the same behaviour.

The controller shows up in Device Manager but the disk attached to it does not show in either Device Manager or Disk Management. The Event log seems to show an error when it attempts to start the device but I may have misread the entry.

My Host is Debian 10.4 running VirtualBox 6.1.10. The guest is Windows 10 (Update 2004, OS Build 19041.329) The virtio-scsi drivers are the current stable version - 100.77.104.17100

I have attached the guests machine log and .vbox file. Furthermore, I have attached prints of the Storage Controller and Disks section from Device manager, which show the drive details and the controller information within the Windows 10 guest. I have also attached the guest Event Log entries for the controller.

If there are any other troubleshooting procedures I can take, please ask.

Thank you.

#19667 wontfix I need to install version 6.0 on fedora 32. SkipMMT
Description

I need to install version 6.0 on fedora 32. Currently, only version 6.1 is available for fedora 32. See ticket #19537. I cannot upgrade to version 6.1 because of ticket #19313.

#19659 invalid Nested VT-X can be enabled with VBoxManage when CPU doesn't provide the VMCS Shadowing feature fth0
Description

Many current Intel mobile CPUs do not provide the VMCS Shadowing feature that VirtualBox needs to provide efficient nested virtualization.

While the VirtualBox Manager prevents the user from enabling Nested VT-X in this case (by greying out), the VBoxManage modifyvm <vm name> --nested-hw-virt on command allows the user to enable Nested VT-X. But then VirtualBox does not even provide EPT to the primary VM. Is this an oversight, or is this working as intended?

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