I first used mender with a IMX board and now I also use it with QEMU machine for testing and easy deployement as a Virtual Machine.
My issue is that with KVM the disk is launched as a paravirtualized disk and Linux mount it as /dev/vda
whereas on Microsoft Hyper-V the disk is laucned as fully-virtualized and Linux mount is as /dev/sda
Is there a way to have the same image compatible with both KVM and Hyper-V ?
Sorry I meant the hardware has been alread shipped and is used on-the-field.
My first hardware was built on Zeus release when I look at the boot partition for example PartUUID using blkid
Second hardware X86
And my latest hardware QEMU
I think I will switch to PARTUUID, as explained by @kacf the LABEL are not “stuck” to the GPT partition table but to the partition itself.
Whereas PARTUUID and PARTLABEL are defined in the GPT partition table, so they are less likely to be changed.