On Tue, Nov 20, 2018, 16:49 <matthias.barmeier(a)sourcepark.de wrote: When the vm does not boot, can extract the vm xml and post here? You can find it in vdsm log, or use virsh: 1. Find the vm virsh -r list 2. Get the xml virsh -r dumpxml <vm-id-or-name> Nir

Hi, we have the same issue since oVirt 4.0. Because we need always several disks, we have the boot disk as virtio and all others as virtio-scsi. With this approach, boot disk is always vda and all other disks are then sda, sdb and so on. They change nearly every time, we reboot. In Linux, you can mount also disks not only by /dev/sdX, you can also mount them via UUID of the disk or by label, ... With this, the disks can always be correctly identified and mounted. Here an example: LABEL=cloudimg-rootfs / ext4 defaults 0 0 /dev/disk/by-label/log /var/log auto defaults,comment=cloudconfig 0 0 /dev/disk/by-label/tmp /tmp ext4 defaults 0 0 BR Florian ----- Ursprüngliche Mail ----- Von: "matthias barmeier" <matthias.barmeier(a)sourcepark.de&gt; An: "users" <users(a)ovirt.org&gt; Gesendet: Dienstag, 20. November 2018 15:48:42 Betreff: [ovirt-users] After adding a disk via GUI the VM does not start anymore Hi, when I add a disk to a debian 9 VM the VM cannot boot anymore. The VM is stating that /dev/sda1 cannot be found anymore. When I remove the added disk everything works as before. Could someone please give me a hint what went wrong ? The hypervisor host is a Centos 7.5 system. Matze _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/YEUCBROVHUR...

Hi Nir, we started with oVirt 4.0, but I wanted to say, that we have this problem from the beginning... Here is an example, where I have added a disk while VM was running and after a shutdown und start, the devices have changed: /dev/vda1 9.7G 3.5G 6.2G 36% / /dev/sdb 976M 15M 895M 2% /tmp /dev/sda 976M 4.4M 905M 1% /var/log /dev/vda1 9.7G 3.5G 6.2G 36% / /dev/sdc 976M 1.3M 908M 1% /tmp /dev/sda 976M 4.0M 905M 1% /var/log New disk became suddenly sdb instead of sdc. Unfortunately, this happened last month and I don't have the logs anymore, nor do I know the exact time. Only had my terminals still open... ;) I tried to reproduce it with shutdown and start 5 times, but still same order. I think it is only changing when you add a new disk to the VM... @matthias, when it is not to much work for you, you should all the fstabs of your linux VMs and change sda... to the disk UUID. These should never change... BR Florian Von: "Nir Soffer" <nsoffer(a)redhat.com&gt; An: "Florian Schmid" <fschmid(a)ubimet.com&gt; CC: "matthias barmeier" <matthias.barmeier(a)sourcepark.de&gt;, "users" <users(a)ovirt.org&gt; Gesendet: Mittwoch, 21. November 2018 09:28:40 Betreff: Re: [ovirt-users] Re: After adding a disk via GUI the VM does not start anymore On Wed, Nov 21, 2018, 09:02 Florian Schmid < [ mailto:fschmid@ubimet.com | fschmid(a)ubimet.com ] wrote: Hi, we have the same issue since oVirt 4.0. Did it work before 4.0? BQ_BEGIN Because we need always several disks, we have the boot disk as virtio and all others as virtio-scsi. With this approach, boot disk is always vda and all other disks are then sda, sdb and so on. They change nearly every time, we reboot. BQ_END I think we try to keep the disks order, and we fixed similar bug few uears ago. If you can reproduce this please file a bug. BQ_BEGIN In Linux, you can mount also disks not only by /dev/sdX, you can also mount them via UUID of the disk or by label, ... With this, the disks can always be correctly identified and mounted. Here an example: LABEL=cloudimg-rootfs / ext4 defaults 0 0 /dev/disk/by-label/log /var/log auto defaults,comment=cloudconfig 0 0 /dev/disk/by-label/tmp /tmp ext4 defaults 0 0 BQ_END Sure this is the recommended way, regardless of oVirt effort to keep disks order between reboots. Nir BQ_BEGIN BR Florian ----- Ursprüngliche Mail ----- Von: "matthias barmeier" < [ mailto:matthias.barmeier@sourcepark.de | matthias.barmeier(a)sourcepark.de ] > An: "users" < [ mailto:users@ovirt.org | users(a)ovirt.org ] > Gesendet: Dienstag, 20. November 2018 15:48:42 Betreff: [ovirt-users] After adding a disk via GUI the VM does not start anymore Hi, when I add a disk to a debian 9 VM the VM cannot boot anymore. The VM is stating that /dev/sda1 cannot be found anymore. When I remove the added disk everything works as before. Could someone please give me a hint what went wrong ? The hypervisor host is a Centos 7.5 system. Matze _______________________________________________ Users mailing list -- [ mailto:users@ovirt.org | users(a)ovirt.org ] To unsubscribe send an email to [ mailto:users-leave@ovirt.org | users-leave(a)ovirt.org ] Privacy Statement: [ https://www.ovirt.org/site/privacy-policy/ | https://www.ovirt.org/site/privacy-policy/ ] oVirt Code of Conduct: [ https://www.ovirt.org/community/about/community-guidelines/ | https://www.ovirt.org/community/about/community-guidelines/ ] List Archives: [ https://lists.ovirt.org/archives/list/users@ovirt.org/message/YEUCBROVHUR... | https://lists.ovirt.org/archives/list/users@ovirt.org/message/YEUCBROVHUR... ] _______________________________________________ Users mailing list -- [ mailto:users@ovirt.org | users(a)ovirt.org ] To unsubscribe send an email to [ mailto:users-leave@ovirt.org | users-leave(a)ovirt.org ] Privacy Statement: [ https://www.ovirt.org/site/privacy-policy/ | https://www.ovirt.org/site/privacy-policy/ ] oVirt Code of Conduct: [ https://www.ovirt.org/community/about/community-guidelines/ | https://www.ovirt.org/community/about/community-guidelines/ ] List Archives: [ https://lists.ovirt.org/archives/list/users@ovirt.org/message/TEN733K5JNC... | https://lists.ovirt.org/archives/list/users@ovirt.org/message/TEN733K5JNC... ] BQ_END