HDD UUID changes when passed-through from server to VM.
I performed HDD passthrough via the following command on PVE 6.2-4.
In the VM when I view the disks by-id I get the following UUIDs instead:
I assumed that I would see "native" (?) UUID vs. Qemu-xxx
Any concern with this or is this expected and not an issue?
I performed HDD passthrough via the following command on PVE 6.2-4.
root@pve:~# qm set 140 -sata1 /dev/disk/by-id/ata-WDC_WD4003FZEX-00Z4SA0_WD-WMC5D0D5H090
update VM 140: -sata1 /dev/disk/by-id/ata-WDC_WD4003FZEX-00Z4SA0_WD-WMC5D0D5H090
root@pve:~# qm set 140 -sata2 /dev/disk/by-id/ata-WDC_WD4003FZEX-00Z4SA0_WD-WCC5DAJC41SR
update VM 140: -sata2 /dev/disk/by-id/ata-WDC_WD4003FZEX-00Z4SA0_WD-WCC5DAJC41SR
In the VM when I view the disks by-id I get the following UUIDs instead:
root@omv:/dev/disk/by-id# ls
ata-QEMU_DVD-ROM_QM00003 ata-QEMU_HARDDISK_QM00009 scsi-0QEMU_QEMU_HARDDISK_drive-scsi0-part1
ata-QEMU_HARDDISK_QM00007 ata-QEMU_HARDDISK_QM00009-part1 scsi-0QEMU_QEMU_HARDDISK_drive-scsi0-part2
ata-QEMU_HARDDISK_QM00007-part1 scsi-0QEMU_QEMU_HARDDISK_drive-scsi0 scsi-0QEMU_QEMU_HARDDISK_drive-scsi0-part5
I assumed that I would see "native" (?) UUID vs. Qemu-xxx
Any concern with this or is this expected and not an issue?