5:05 a.m.
Greetings Martin,
Sent: Thursday, August 12, 2021 at 2:07 PM
From: "daggs" <daggs(a)gmx.com>
To: "Martin Kletzander" <mkletzan(a)redhat.com>
Cc: dan(a)berrange.com, libvirt-users(a)redhat.com
Subject: Re: issues with vm after upgrade
> Sent: Thursday, August 12, 2021 at 11:49 AM
> From: "Martin Kletzander" <mkletzan(a)redhat.com>
> To: "daggs" <daggs(a)gmx.com>
> Cc: dan(a)berrange.com, libvirt-users(a)redhat.com
> Subject: Re: issues with vm after upgrade
>
> 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(a)gmx.com>
> >> To: "Martin Kletzander" <mkletzan(a)redhat.com>
> >> Cc: dan(a)berrange.com, libvirt-users(a)redhat.com
> >> Subject: Re: issues with vm after upgrade
> >>
> >> Greetings Martin,
> >>
> >> > Sent: Wednesday, August 11, 2021 at 4:13 PM
> >> > From: "Martin Kletzander" <mkletzan(a)redhat.com>
> >> > To: "daggs" <daggs(a)gmx.com>
> >> > Cc: dan(a)berrange.com, libvirt-users(a)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(a)redhat.com>
> >> > >> To: "daggs" <daggs(a)gmx.com>
> >> > >> Cc: dan(a)berrange.com, libvirt-users(a)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
> >>
> >
> >here: https://dpaste.com/5VBUU8Z9W
> >
>
> 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
>
my current setup works beside the hdmi audio, this I still need to investigate.
thanks for your help.
Dagg
just to update, I've solved the sound issue, frankly, I don't understand how the
guest showed a soundcard in the first place.
from what I gather, libvirt sets the -nodefaults flag to prepare the vm's properties
from scratch.
in this situation, the sound card is a function in the host machine's pci tree.
when libvirt created the pci tree for the guest, it placed the card as a function of a
device as well, in my case 02:00.2
however it didn't created a device at 02:00.0.
my fix was to move the device to 00:1f.4 in the guest.
I won't be surprised this was the issue why the vm didn't booted after the upgrade
with the old xml.
Dagg.