On Wed, Aug 11, 2021 at 08:53:10PM +0200, daggs wrote:
Greetings Martin,
Sent: Wednesday, August 11, 2021 at 6:08 PM From: "daggs" <daggs@gmx.com> To: "Martin Kletzander" <mkletzan@redhat.com> Cc: dan@berrange.com, libvirt-users@redhat.com Subject: Re: issues with vm after upgrade
Greetings Martin,
Sent: Wednesday, August 11, 2021 at 4:13 PM From: "Martin Kletzander" <mkletzan@redhat.com> To: "daggs" <daggs@gmx.com> Cc: dan@berrange.com, libvirt-users@redhat.com Subject: Re: issues with vm after upgrade
On Wed, Aug 11, 2021 at 03:09:34PM +0200, daggs wrote:
Greetings Martin,
Sent: Wednesday, August 11, 2021 at 10:14 AM From: "Martin Kletzander" <mkletzan@redhat.com> To: "daggs" <daggs@gmx.com> Cc: dan@berrange.com, libvirt-users@redhat.com Subject: Re: issues with vm after upgrade
[...]
2) To your issue with starting the domain it would be good to know what is the error you get from virsh (or however you are starting the domain) and the debug logs of libvirtd, ideally just for the part of the domain starting.
that is the issue, there wasn't any error. the vm just didn't booted.
Oh, so I misunderstood. What was the state of the VM in libvirt? "paused" or "running"? Was there serial console working? it was marked as running and there was no serial
That's a pity we could not examine what was actually happening.
I can diff the original xml with the new one to see the diffs and post them here if you wish
Would be nice to see if there are any differences. The newly created one works then?
I'll sent it later today
Unfortunately there are many differences there. The machine type changes _something_ in qemu, there is different PCI(e) topology, and I do not think I will be able to figure this out without the non-working machine. So if your current setup works for you right now I'd leave figuring out the previous issue to others, if there is anyone wanting to figure out if there is some libvirt issue. Have a nice day