Disk passthrough looks like it worked, but not showing up in Windows

Ryan_Malone

Member
Mar 31, 2024
54
6
8
I followed this simple tutorial to passthrough an NVMe disk to a gaming I'm building. Everything seemed to work swimmingly except the most important part, it showing up in partition manager so I can configure it! Can anyone see any problem with my configuration?

VM config
GNU nano 7.2 /etc/pve/nodes/pve3/qemu-server/101.conf
agent: 1
balloon: 0
bios: ovmf
boot: order=ide2;ide0;scsi0;net0
cores: 8
cpu: x86-64-v2-AES
efidisk0: local:101/vm-101-disk-0.qcow2,efitype=4m,pre-enrolled-keys=1,size=528K
hostpci0: 0000:01:00,pcie=1,x-vga=1
ide0: local:iso/virtio-win-0.1.266.iso,media=cdrom,size=707456K
ide2: local:iso/Win11_24H2_English_x64.iso,media=cdrom,size=5683090K
machine: pc-q35-9.0
memory: 64000
meta: creation-qemu=9.0.2,ctime=1735438709
name: Win11-Gaming
net0: virtio=BC:24:11:AE:8F:D1,bridge=vmbr1,firewall=1
numa: 0
ostype: win11
scsi0: fastthinpool1:vm-101-disk-0,cache=writeback,discard=on,iothread=1,size=250G
scsihw: virtio-scsi-single
smbios1: uuid=81e43cb6-f3d0-4cf3-823a-2ce732fbea30
sockets: 1
tpmstate0: fastthinpool1:vm-101-disk-1,size=4M,version=v2.0
vga: virtio
virtio2: /dev/disk/by-id/nvme-CT4000P3SSD8_2343E8820891,backup=0,size=3907018584K
vmgenid: d35f9fd5-d3bf-4874-81da-63fba3d9ec9b

VM settings GUI.png

Disk to passthrough.png
 
SOLVED
Turns out the drivers I installed for Windows to install the initial drive (also NVMe strangely) weren;t sufficient for the second drive. I needed to add the Win11 drivers from the viostor folder and then it worked.
 
  • Like
Reactions: waltar
viostor driver is indeed for virtio blk.
scsi is recommended as it's virtio scsi when controller is Virtio scsi (this is the default).
Can you explain why different drivers are needed for the boot drive (also NVMe) than for the additional drive (NVMe)? I’m sure you’re right, but I don’t understand why different drivers would be needed.
 
look at your .conf, you have set different disk type :
one with scsi, the other with virtio.
virtio provide two disk controller, each has its own driver, virtio BLK and virtio SCSI.
An yes. I think that makes sense. Since one is passed through (BLK) and the other is a vdisk (vfio) that use different drivers. Please correct me if I'm wrong.
 
Just for clarification, using the example you followed from that video tutorial;
Code:
qm set [VMID] -virtio2 /dev/disk/by-id/[DISK-ID]

# For your user-case environment;
# you could/should have used instead:

qm set [VMID] -scsi1 /dev/disk/by-id/[DISK-ID]
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!