Page 1 of 2
PVSCSI cannot detedct HDD
Posted: 5. Jul 2020, 19:05
by Aphrodite
Windows 10 LTSC, already install Red Hat VirtIO SCSI pass-through controller driver, system cannot detect HDD.
Re: PVSCSI cannot detedct HDD
Posted: 5. Jul 2020, 21:40
by scottgus1
Start the guest from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the guest from within the guest OS if possible. If not possible, close the Virtualbox window for the guest with the Power Off option set.
Right-click the guest in the main Virtualbox window's guest list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.
Right-click the guest in the main Virtualbox window's guest list, choose Show in Explorer. Zip the guest's .vbox file, and post the zip file, using the forum's Upload Attachment tab.
Re: PVSCSI cannot detedct HDD
Posted: 6. Jul 2020, 05:48
by Aphrodite
.vbox & VM log
Re: PVSCSI cannot detedct HDD
Posted: 6. Jul 2020, 14:48
by scottgus1
.vbox file, zipped?
Re: PVSCSI cannot detedct HDD
Posted: 6. Jul 2020, 17:30
by Aphrodite
scottgus1 wrote:.vbox file, zipped?
OK, I uploaded .vbox & log
Re: PVSCSI cannot detedct HDD
Posted: 6. Jul 2020, 21:08
by The Raven
Problem is not confined to Windows Hosts, it happens on Linux Hosts as well.
The Virtio-SCSI controller works with Linux guests but not with Windows (10) guests.
I have already opened a ticket for this problem, see
https://www.virtualbox.org/ticket/19674
This forum entry should probably be moved to Windows Guests.
Re: PVSCSI cannot detedct HDD
Posted: 6. Jul 2020, 21:28
by scottgus1
the .vbox file wrote: <MediaRegistry>
<HardDisks>
<HardDisk uuid="{b7d64fcc-c7a3-4648-b65a-dc6078be8bd7}" location="Windows 10 LTSB (32-bit).vdi" format="VDI" type="Normal"/>
<HardDisk uuid="{
0526ab0d-d4bf-4882-b72a-873e22e3a59b}" location="
test.vdi" format="VDI" type="Normal"/>
<HardDisk uuid="{aeb019c2-c4f8-4e0d-b794-da1879667e9d}" location="test1.vdi" format="VDI" type="Normal"/>
<HardDisk uuid="{e95e0799-9b8f-40ec-82e9-d0b9ac772977}" location="test2.vdi" format="VDI" type="Normal"/>
</HardDisks>
<DVDImages>
<Image uuid="{bc34a0b9-8db5-4035-8dd6-9ebef869be5d}" location="C:/Program Files/Oracle/VirtualBox/VBoxGuestAdditions.iso"/>
<Image uuid="{18011a08-b787-4c80-a1cc-32ce938f7ded}" location="F:/Software/Microsoft/Windows/Windows 10 (x86) LTSC/SW_DVD5_WIN_ENT_LTSC_2019_32BIT_English_-2_MLF_X22-05018.ISO"/>
<Image uuid="{a8224ea8-99d5-439a-a65f-49a1cffdf956}" location="F:/Software/Virtualization/QEMU/virtio-win-0.1.171.iso"/>
</DVDImages>
</MediaRegistry>
<StorageControllers>
<StorageController name="SATA" type="AHCI" PortCount="2" useHostIOCache="false" Bootable="true" IDE0MasterEmulationPort="0" IDE0SlaveEmulationPort="1" IDE1MasterEmulationPort="2" IDE1SlaveEmulationPort="3">
<AttachedDevice passthrough="false" type="DVD" hotpluggable="false" port="1" device="0">
<Image uuid="{a8224ea8-99d5-439a-a65f-49a1cffdf956}"/>
</AttachedDevice>
<AttachedDevice type="HardDisk" hotpluggable="false" port="0" device="0">
<Image uuid="{b7d64fcc-c7a3-4648-b65a-dc6078be8bd7}"/>
</AttachedDevice>
</StorageController>
<StorageController name="
VirtIO" type="
VirtioSCSI" PortCount="1" useHostIOCache="false" Bootable="true">
<AttachedDevice type="HardDisk" hotpluggable="false" port="0" device="0">
<Image uuid="{
0526ab0d-d4bf-4882-b72a-873e22e3a59b}"/>
</AttachedDevice>
</StorageController>
<StorageController name="LsiLogic SAS" type="LsiLogicSas" PortCount="1" useHostIOCache="false" Bootable="true">
<AttachedDevice type="HardDisk" hotpluggable="false" port="0" device="0">
<Image uuid="{e95e0799-9b8f-40ec-82e9-d0b9ac772977}"/>
</AttachedDevice>
</StorageController>
<StorageController name="NVMe" type="NVMe" PortCount="1" useHostIOCache="false" Bootable="true">
<AttachedDevice type="HardDisk" hotpluggable="false" port="0" device="0">
<Image uuid="{aeb019c2-c4f8-4e0d-b794-da1879667e9d}"/>
</AttachedDevice>
</StorageController>
</StorageControllers>
the vbox.log wrote:00:00:03.051472 [/Devices/virtio-scsi/0/LUN#0/AttachedDriver/Config/] (level 6)
00:00:03.051473 BlockCache <integer> = 0x0000000000000001 (1)
00:00:03.051473 Format <string> = "VDI" (cb=4)
00:00:03.051474 Mountable <integer> = 0x0000000000000000 (0)
00:00:03.051474 Path <string> = "E:\Admin\VirtualBox VMs\Windows 10 LTSB (32-bit)\test.vdi" (cb=58)
00:00:03.051475 Type <string> = "HardDisk" (cb=9)
00:00:03.051476 UseNewIo <integer> = 0x0000000000000001 (1)
....
00:00:03.963432 AIOMgr: Endpoint for file 'E:\Admin\VirtualBox VMs\Windows 10 LTSB (32-bit)\test.vdi' (flags 000c0723) created successfully
It appears that the Virtio disk does mount inside the guest environment. Not having tried a Virtio disk before, I cannot say how to troubleshoot. I fall back to The Raven's advice: check to see if the drivers for virtio disks are compatible with Windows 10.
Re: PVSCSI cannot detedct HDD
Posted: 7. Jul 2020, 17:15
by Aphrodite
The Raven wrote:Problem is not confined to Windows Hosts, it happens on Linux Hosts as well.
The Virtio-SCSI controller works with Linux guests but not with Windows (10) guests.
I have already opened a ticket for this problem, see
https://www.virtualbox.org/ticket/19674
This forum entry should probably be moved to Windows Guests.
Quote from VirtualBox manual
Warning
The virtio-scsi controller will only be seen by OSes with device support for it. In particular, there is no built-in support in Windows. So Windows will not see such disks unless you install additional drivers.
Experience features, Virtualbox needs to improve
Re: PVSCSI cannot detedct HDD
Posted: 7. Jul 2020, 17:17
by Aphrodite
It appears that the Virtio disk does mount inside the guest environment. Not having tried a Virtio disk before, I cannot say how to troubleshoot. I fall back to The Raven's advice: check to see if the drivers for virtio disks are compatible with Windows 10.
KVM and QEMU for Windows use the virio-scsi feature.
Re: PVSCSI cannot detedct HDD
Posted: 7. Jul 2020, 19:24
by scottgus1
Raven, if you are still watching this topic, I looked through your ticket, and I have a question:
Raven's .vbox file wrote: <HardDisks>
<HardDisk uuid="{
1ed0eb06-b913-484c-a62d-72dc0b7349ed}" location="/disk/VM Storage/Data Disks/
Windows Testing Data.vdi" format="VDI" type="Normal"/>
<HardDisk uuid="{
162edc01-4413-4111-a948-64759e0c97f6}" location="
Windows Testing.vdi" format="VDI" type="Normal"/>
</HardDisks>
<StorageController name="
SATA" type="AHCI" PortCount="5" useHostIOCache="true" Bootable="true" IDE0MasterEmulationPort="0" IDE0SlaveEmulationPort="1" IDE1MasterEmulationPort="2" IDE1SlaveEmulationPort="3">
<AttachedDevice nonrotational="true" type="HardDisk" hotpluggable="false" port="0" device="0">
<Image uuid="{
162edc01-4413-4111-a948-64759e0c97f6}"/>
</AttachedDevice>
<AttachedDevice passthrough="false" type="
DVD" hotpluggable="false" port="4" device="0"/>
</StorageController>
<StorageController name="
VirtIO" type="VirtioSCSI" PortCount="1" useHostIOCache="true" Bootable="true">
<AttachedDevice type="HardDisk" hotpluggable="false" port="0" device="0">
<Image uuid="{
1ed0eb06-b913-484c-a62d-72dc0b7349ed}"/>
</AttachedDevice>
</StorageController>
Raven's vbox.log wrote: 00:00:01.114343 [/Devices/virtio-scsi/0/LUN#0/AttachedDriver/Config/] (level 6)
00:00:01.114344 Format <string> = "VDI" (cb=4)
00:00:01.114345 Mountable <integer> = 0x0000000000000000 (0)
00:00:01.114345 Path <string> = "/disk/VM Storage/Data Disks/Windows Testing Data.vdi" (cb=53)
00:00:01.114346 Type <string> = "HardDisk" (cb=9)
Raven's drives wrote:1 Drive C:
2 Description Local Fixed Disk
3 Compressed No
4 File System NTFS
5 Size 48.91 GB (52,520,800,256 bytes)
6 Free Space 30.28 GB (32,508,940,288 bytes)
7 Volume Name Windows 10 VM
8 Volume Serial Number 4C4C70E7
9
10 Drive F:
11 Description CD-ROM Disc
12
13 Drive U:
14 Description Local Fixed Disk
15 Compressed No
16 File System NTFS
17 Size 20.00 GB (21,471,686,656 bytes)
18 Free Space 19.61 GB (21,060,124,672 bytes)
19 Volume Name Windows 10 Updates
20 Volume Serial Number 3AD70661
It appears to me from the data posted in your ticket that the virtio disk does appear in your guest's disks. Am I reading this wrong? Does the disk appear in the guest OS but Windows is unable to use it?
Re: PVSCSI cannot detedct HDD
Posted: 8. Jul 2020, 20:35
by Aphrodite
It appears to me from the data posted in your ticket that the virtio disk does appear in your guest's disks. Am I reading this wrong? Does the disk appear in the guest OS but Windows is unable to use it?
There's no scsi hard drive in the system.
Re: PVSCSI cannot detedct HDD
Posted: 8. Jul 2020, 20:44
by scottgus1
OK, Aphrodite, I do see that there is only one drive showing in your Device Manager.
Hopefully Raven can show us what the U drive is in the ticket info. Also, I am trying this in a Windows 10 guest, too. Will let you know what I find.
Where did you get your Red Hat VirtIO SCSI pass-through controller driver? Please post a link?
Re: PVSCSI cannot detedct HDD
Posted: 8. Jul 2020, 21:33
by The Raven
Apologies for the delay in replying.
My SATA controller has the C: drive (Windows 10 VM) and U: drive (Windows 10 Updates) attached it.
The Virtio-SCSI controller has the Windows Testing vdi attached it but that disk does not show up within the guest.
The Virtio-SCSI controller works fine with my Linux Guests (Debian 10), including being able to boot from it.
However, as previously mentioned, the Windows driver for the controller gets installed correctly but no devices
can be seen.
The Windows driver, hosted on the Fedora site, must be ok for use with KVM, otherwise those users would be complaining.
It appears as if there must be something odd about the device emulation occurring in VirtualBox for Windows guests.
The Windows drivers for the Virtio-SCSI device are found on the Fedora site, see below
https://docs.fedoraproject.org/en-US/qu ... index.html
Re: PVSCSI cannot detedct HDD
Posted: 9. Jul 2020, 00:25
by scottgus1
Thanks, Raven. Are the C: and U: drives two partitions on the same drive?
Re: PVSCSI cannot detedct HDD
Posted: 9. Jul 2020, 10:17
by The Raven
The C: and U: drives are different vdi's.
I think there may have been some confusion with my attachments in the original ticket.
The vdi that contains the U: drive (Windows 10 Updates.vdi) is defined as hot-pluggable and is
effectively "shared" between the Windows 10 guest and a Debian Guest.
To avoid any confusion, I've now changed that and removed the U: drive vdi from the configuration.
The guest now has a SATA controller with the C: drive vdi attached to it and a CD drive.
It also has a virtio-scsi controller with the Windows Testing Data vdi attached to it.
The C: drive vdi shows as <HardDisk uuid="{162edc01-4413-4111-a948-64759e0c97f6}" location="Windows Testing.vdi" format="VDI" type="Normal"/> in the vbox file.
The testing data drive that is attached to the virtio-scsi controller is shown as
<HardDisk uuid="{1ed0eb06-b913-484c-a62d-72dc0b7349ed}" location="/disk/VM Storage/Data Disks/Windows Testing Data.vdi" format="VDI"
in the vbox file.
A screen shot from inside the Windows 10 guest of Disk Management, shows only the C: drive and the CD drive.
The Windows Testing Data vdi is missing. MSINFO shows the following
System Information report written at: 07/09/20 09:29:48
System Name: WINDOWS10-VM
[Drives]
Item Value
Drive C:
Description Local Fixed Disk
Compressed No
File System NTFS
Size 48.91 GB (52,520,800,256 bytes)
Free Space 30.66 GB (32,920,375,296 bytes)
Volume Name Windows 10 VM
Volume Serial Number 4C4C70E7
Drive F:
Description CD-ROM Disc