7.4.16 Update Issue

kromberg

Member
Nov 24, 2021
87
6
13
53
I updated to the following here:
Code:
Kernel Version Linux 5.15.108-1-pve #1 SMP PVE 5.15.108-2 (2023-07-20T10:06Z)
PVE Manager Version pve-manager/7.4-16/0f39f621

Now I have a VM that is dead where it cant boot. Looks like it is not finding the os on the hard disk and is defaulting to booting over IP. I really would like to get this VM back up and running rather than creating a new install instance of it. I restored a backup of the VM and it is having the same issue starting. Not really seeing anything in syslog, but I am not sure what I should be looking for. Can anyone point in the direction of what I can do to get the VM back up and running?

Here is the VM config
Code:
agent: 1,fstrim_cloned_disks=1
args: -device 'vfio-pci,sysfsdev=/sys/bus/mdev/devices/966af734-b5e6-4096-9a1f-2066cfb34
a43,display=off,id=hostpci0.0,bus=ich9-pcie-port-1,addr=0x0.0,x-pci-vendor-id=0x10de,x-p
ci-device-id=0x1BB0,x-pci-sub-vendor-id=0x10de,x-pci-sub-device-id=0x11A0' -uuid 966af73
4-b5e6-4096-9a1f-2066cfb34a43
bios: ovmf
boot: order=sata0;ide2;net0
cores: 8
efidisk0: rpool-nvme1:vm-405-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M
ide2: none,media=cdrom
machine: pc-q35-6.1
memory: 16384
meta: creation-qemu=6.1.0,ctime=1639312363
name: ancalagon
net0: virtio=42:86:7C:6A:84:F1,bridge=vmbr1,mtu=9000,queues=4
net1: virtio=E2:03:4E:77:EF:16,bridge=vmbr2,mtu=9000,queues=2
numa: 0
ostype: win10
sata0: rpool-nvme1:vm-405-disk-1,size=200G
scsihw: virtio-scsi-pci
smbios1: uuid=0e343f5f-1585-447a-b665-b188fa8ddaa9
sockets: 1
vmgenid: a0e56842-2056-4cfb-b9c6-126cb0406500
 
Last edited:
Looks like it, the disk has no partition table. Do we have an ETA on the fix? Having this occur during backups kinda defeats the purpose of doing a backup ;)
 
Looks like it, the disk has no partition table. Do we have an ETA on the fix?
Unfortunately not. It's not clear what the root cause of the issue is yet. It's very likely a bug in the SATA/IDE emulation code under rare circumstances. It's recommended to use VirtIO SCSI or block instead also for performance reasons. For Windows, you need the https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers first.
 
This is great, I have had 3 more vm get killed by their hard disk loosing the partition table. This is now far from 'rare' and down right common. Can this please get prioritized higher?
 
This also isnt a bug in the SATA/IDE emulation code as all three of these VM where using the VirtIO SCSI controller for the disks.
 
This also isnt a bug in the SATA/IDE emulation code as all three of these VM where using the VirtIO SCSI controller for the disks.
The configuration you posted clearly has
Code:
sata0: rpool-nvme1:vm-405-disk-1,size=200G
Since it's a SATA emulation, it does not use a SCSI controller. If other VMs with SCSI disks are affected, it is a different bug, please post the configurations for those and the output of pveversion -v.
 

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!