[ovirt-users] Re: No bootable device

2022-03-24 Thread nicolas
Hi, The checkbox is already checked, when you mark a disk as "OS" it's marked automatically. Still it won't boot. Thanks. El 2022-03-23 15:23, Angus Clarke escribió: Hi Nicolas In oVirt 4.3: Compute -> Virtual Machines -> Select VM On the VM screen: Disks -> Highlight disk -> Edit

[ovirt-users] Unable to start VMs after upgrade from 4.4.9 to 4.4.10

2022-03-24 Thread Christoph Timm
Hi List, I receive the following error while starting some of our VMs after the upgrade to 4.4.10. VM v4-probe is down with error. Exit message: internal error: process exited while connecting to monitor: 2022-03-24T11:27:23.098838Z qemu-kvm: -blockdev {"node-name":"libvirt-1-format","read-

[ovirt-users] gluster in ovirt-node in 4.5

2022-03-24 Thread Yedidyah Bar David
Hi all, In relation to a recent question here (thread "[ovirt-devel] [ANN] Schedule for oVirt 4.5.0"), we are now blocked with the following chain of changes/dependencies: 1. ovirt-ansible-collection recently moved from ansible-2.9 to ansible-core 2.12. 2. ovirt-hosted-engine-setup followed it. 3

[ovirt-users] Re: gluster in ovirt-node in 4.5

2022-03-24 Thread Gobinda Das
Adding @Ritesh Chikatwar On Thu, Mar 24, 2022 at 7:36 PM Yedidyah Bar David wrote: > Hi all, > > In relation to a recent question here (thread "[ovirt-devel] [ANN] > Schedule for oVirt 4.5.0"), we are now blocked with the following > chain of changes/dependencies: > > 1. ovirt-ansible-collecti

[ovirt-users] Re: No bootable device

2022-03-24 Thread Abe E
Is it set as bootable? I have seen some QCOWs not be read correctly by ovirt. In that case I would take an OVA file and convert it manually to QCOW using the CLI, sometimes the QCOW works only with IDE from what I have seen. My way is somewhat long but usually works for me: Upload to Disk page in

[ovirt-users] Re: Unable to start VMs after upgrade from 4.4.9 to 4.4.10

2022-03-24 Thread Christoph Timm
Good morning, please note that I got a bit further with my investigation. It might be a bug in the VDSM as I see the following while powering down the problematic VM: MainProcess|libvirt/events::ERROR::2022-03-24 20:43:48,740::supervdsm_server::99::SuperVdsm.ServerCallback::(wrapper) Error

[ovirt-users] Re: dnf update fails with oVirt 4.4 on centos 8 stream due to ansible package conflicts.

2022-03-24 Thread Christoph Timm
Good morning, please note that I have performed some tests and I'm quite sure that oVirt is not compatible with ansible-core-2.12. I run into issues with hosts installation and the check for updates results into a Null pointer exception. So I have reverted back to ansible-2.9 which is also pr