What happens if a Pass Through Disk/Partition changed size?

mio19

New Member
Jan 27, 2024
7
0
1
I used this command to attach a disk to my vm
Code:
qm set 100 -scsi7 /dev/disk/by-id/ata-HUH721010ALE601_7JHDJ6RC-part1,backup=0,replicate=0,cache=writeback,iothread=1
There is a "size" parameter visible in gui and config
Code:
scsi7: /dev/disk/by-id/ata-HUH721010ALE601_7JHDJ6RC-part1,backup=0,cache=writeback,iothread=1,replicate=0,size=8766219600K
Recently I decided to recreate part2 and I enlarged part1. Right after I powered up the vm I remembered that there is the "size" param. I killed the vm and re-attached the partition. Then I told the filesystem in vm to resize. After this everything seems working perfectly.

Why could the vm start normally with a pass through disk/partition with a mismatched size? What could potentially happen during the period?
 
Why could the vm start normally with a pass through disk/partition with a mismatched size? What could potentially happen during the period?
AFAIK, this is only relevant for the GUI, the disk size is not passed through to the QEMU/KVM process as you can see if you inspect the command line arguments to the kvm process.
 

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!