Re: issues with vm after upgrade
On Sun, 29 Aug 2021 16:25:53 -0400 Laine Stump wrote: > I just looked back at the code that decides whether a device is > conventional PCI or PCIe for the first time in a few years > (virPCIDeviceInit) and it looks like it might consider integrated > chipset devices to be conventional PCI (since they don't have any > "Express Capabilities Data"); this would explain why it's wanting to > assign it to a pcie-to-pci-bridge. Maybe we should just always assign > devices to PCIe slots when the guest is Q35 though. Alex - what's your > opinion about this? The only certainty is that you're going to be wrong sometimes. Technically all PCIe devices should have a PCIe capability, but that's commonly not the case for Root Complex Integrated Endpoints, presumably because the PCIe capability also describes PCIe links but integrated endpoints don't expose such aspects of how they're connected to the RC. So, if you assume these are conventional PCI devices, you're probably wrong and if you assume they're PCIe devices, well they don't have a PCIe capability like they really ought to if they're under a downstream port. We just hope that software doesn't care in that case. Would libvirt want a special rule for hostdev devices on the host root bus? If you were to set the default location for any such device to the guest root bus then your rules about config space size for determining conventional vs express become more consistent for the remaining devices. But then, do we have root bus hotplug on q35? Thanks, Alex
Re: issues with vm after upgrade
(Alex - search for your name down in the middle of this - there is one question for you. You can probably save your neurons the trouble of reading the rest) On 8/28/21 6:56 AM, daggs wrote: Greetings Laine, Sent: Wednesday, August 25, 2021 at 7:53 PM From: "Laine Stump" To: "daggs" Cc: "Martin Kletzander" , libvirt-users@redhat.com Subject: Re: issues with vm after upgrade On 8/20/21 12:07 PM, daggs wrote: Greetings Laine, Sent: Monday, August 16, 2021 at 12:57 AM From: "Laine Stump" To: "daggs" Cc: "Martin Kletzander" , libvirt-users@redhat.com Subject: Re: issues with vm after upgrade On 8/14/21 6:05 AM, daggs wrote: Greetings Martin, Sent: Thursday, August 12, 2021 at 2:07 PM From: "daggs" To: "Martin Kletzander" Cc: d...@berrange.com, libvirt-users@redhat.com Subject: Re: issues with vm after upgrade Sent: Thursday, August 12, 2021 at 11:49 AM From: "Martin Kletzander" To: "daggs" Cc: d...@berrange.com, libvirt-users@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" To: "Martin Kletzander" Cc: d...@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" To: "daggs" Cc: d...@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" To: "daggs" Cc: d...@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 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. Are you basing this claim on the libvirt XML? Or on what you see with lspci in the guest? When libvirt is assigning PCI addresses to devices in a guest, it will never auto-assign a non-0 function. This will only happen if the user explicitly requests it (and even then, iirc, libvirt should generate an error if function 0 of the same slot has no device - something to the effect of "no device on function 0 of a multifunction device"). Anyway, when I looked back at the XML diff you posted earlier (see below), I didn't see any hostdev device assigned to 02:00.2. What I *did* see was that in both the old and the new version of the diff, the hostdev devices were assigned to function 0 of different *slots* on a dmi-to-pci-bridge controller, which should cause no problems (unless there is a bug in QEMU's dmi-to-pci-bridge). (The important thing, though, is that there is no hostdev device on a non-0 function, and when it is on a non-0 slot, that's because it's on a dmi-to-pci-bridge (which has 32 slots). I saw it in guest, But I didn't see it in the XML diffs that you had posted. as mentioned below, here is the xml of the new vm but with the sound problem: https://dpaste.com/BB9EDY6BK the relevant entry is at https://dpaste.com/BB9EDY6BK#l
Re: issues with vm after upgrade
Greetings Laine, > Sent: Wednesday, August 25, 2021 at 7:53 PM > From: "Laine Stump" > To: "daggs" > Cc: "Martin Kletzander" , libvirt-users@redhat.com > Subject: Re: issues with vm after upgrade > > On 8/20/21 12:07 PM, daggs wrote: > > Greetings Laine, > > > >> Sent: Monday, August 16, 2021 at 12:57 AM > >> From: "Laine Stump" > >> To: "daggs" > >> Cc: "Martin Kletzander" , libvirt-users@redhat.com > >> Subject: Re: issues with vm after upgrade > >> > >> > >> > >> On 8/14/21 6:05 AM, daggs wrote: > >>> Greetings Martin, > >>> > >>>> Sent: Thursday, August 12, 2021 at 2:07 PM > >>>> From: "daggs" > >>>> To: "Martin Kletzander" > >>>> Cc: d...@berrange.com, libvirt-users@redhat.com > >>>> Subject: Re: issues with vm after upgrade > >>>> > >>>>> Sent: Thursday, August 12, 2021 at 11:49 AM > >>>>> From: "Martin Kletzander" > >>>>> To: "daggs" > >>>>> Cc: d...@berrange.com, libvirt-users@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" > >>>>>>> To: "Martin Kletzander" > >>>>>>> Cc: d...@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" > >>>>>>>> To: "daggs" > >>>>>>>> Cc: d...@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" > >>>>>>>>>> To: "daggs" > >>>>>>>>>> Cc: d...@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 > >>>>>>>> o
Re: issues with vm after upgrade
On 8/20/21 12:07 PM, daggs wrote: Greetings Laine, Sent: Monday, August 16, 2021 at 12:57 AM From: "Laine Stump" To: "daggs" Cc: "Martin Kletzander" , libvirt-users@redhat.com Subject: Re: issues with vm after upgrade On 8/14/21 6:05 AM, daggs wrote: Greetings Martin, Sent: Thursday, August 12, 2021 at 2:07 PM From: "daggs" To: "Martin Kletzander" Cc: d...@berrange.com, libvirt-users@redhat.com Subject: Re: issues with vm after upgrade Sent: Thursday, August 12, 2021 at 11:49 AM From: "Martin Kletzander" To: "daggs" Cc: d...@berrange.com, libvirt-users@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" To: "Martin Kletzander" Cc: d...@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" To: "daggs" Cc: d...@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" To: "daggs" Cc: d...@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 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. Are you basing this claim on the libvirt XML? Or on what you see with lspci in the guest? When libvirt is assigning PCI addresses to devices in a guest, it will never auto-assign a non-0 function. This will only happen if the user explicitly requests it (and even then, iirc, libvirt should generate an error if function 0 of the same slot has no device - something to the effect of "no device on function 0 of a multifunction device"). Anyway, when I looked back at the XML diff you posted earlier (see below), I didn't see any hostdev device assigned to 02:00.2. What I *did* see was that in both the old and the new version of the diff, the hostdev devices were assigned to function 0 of different *slots* on a dmi-to-pci-bridge controller, which should cause no problems (unless there is a bug in QEMU's dmi-to-pci-bridge). (The important thing, though, is that there is no hostdev device on a non-0 function, and when it is on a non-0 slot, that's because it's on a dmi-to-pci-bridge (which has 32 slots). I saw it in guest, But I didn't see it in the XML diffs that you had posted. I'd assume that if libvirt defines a device on a specific bdf, the guest will not change it. That's not exactly true - the bus "number" in libvirt isn't given to qemu as an actual number, but as an alphanumeric device id (called "alias name" in libvirt XML). QEMU doesn't have any concept of "bus number", because (afaiu) there is no way to convey such info to the guest firmware/OS; instead, QEMU creates a topology of interconnected controllers, the firmware and/or OS traverses this topology and assigns numbers to the encountered control
Re: issues with vm after upgrade
Greetings Laine, > Sent: Monday, August 16, 2021 at 12:57 AM > From: "Laine Stump" > To: "daggs" > Cc: "Martin Kletzander" , libvirt-users@redhat.com > Subject: Re: issues with vm after upgrade > > > > On 8/14/21 6:05 AM, daggs wrote: > > Greetings Martin, > > > >> Sent: Thursday, August 12, 2021 at 2:07 PM > >> From: "daggs" > >> To: "Martin Kletzander" > >> Cc: d...@berrange.com, libvirt-users@redhat.com > >> Subject: Re: issues with vm after upgrade > >> > >>> Sent: Thursday, August 12, 2021 at 11:49 AM > >>> From: "Martin Kletzander" > >>> To: "daggs" > >>> Cc: d...@berrange.com, libvirt-users@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" > >>>>> To: "Martin Kletzander" > >>>>> Cc: d...@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" > >>>>>> To: "daggs" > >>>>>> Cc: d...@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" > >>>>>>>> To: "daggs" > >>>>>>>> Cc: d...@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 > >>>>> > >>>> > >>>> 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. > >> > >
Re: issues with vm after upgrade
On 8/14/21 6:05 AM, daggs wrote: Greetings Martin, Sent: Thursday, August 12, 2021 at 2:07 PM From: "daggs" To: "Martin Kletzander" Cc: d...@berrange.com, libvirt-users@redhat.com Subject: Re: issues with vm after upgrade Sent: Thursday, August 12, 2021 at 11:49 AM From: "Martin Kletzander" To: "daggs" Cc: d...@berrange.com, libvirt-users@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" To: "Martin Kletzander" Cc: d...@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" To: "daggs" Cc: d...@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" To: "daggs" Cc: d...@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 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. Are you basing this claim on the libvirt XML? Or on what you see with lspci in the guest? When libvirt is assigning PCI addresses to devices in a guest, it will never auto-assign a non-0 function. This will only happen if the user explicitly requests it (and even then, iirc, libvirt should generate an error if function 0 of the same slot has no device - something to the effect of "no device on function 0 of a multifunction device"). Anyway, when I looked back at the XML diff you posted earlier (see below), I didn't see any hostdev device assigned to 02:00.2. What I *did* see was that in both the old and the new version of the diff, the hostdev devices were assigned to function 0 of different *slots* on a dmi-to-pci-bridge controller, which should cause no problems (unless there is a bug in QEMU's dmi-to-pci-bridge). (The important thing, though, is that there is no hostdev device on a non-0 function, and when it is on a non-0 slot, that's because it's on a dmi-to-pci-bridge (which has 32 slots). On the topic of having a dmi-to-pci-bridge show up in your XML: I don't remember what versions the changes were in (it was at least a year or two ago), but only a fairly old version of libvirt woud do that - 1) recent libvirt will assume that any hostdev PCI device is a PCIe device, so it will add a pcie-root-port and assign the hostdev device to slot 0 of that root-port, and even before that 2) we switched from using dmi-to-pci-bridge to using pcie-to-pci-bridge quite some time ago as well. So if you're generating new XML based on config that doesn't have pci controllers already in it, and you're seeing hostdevs (or any other PCI devices) assigned to an automatically-added dmi-to-pci-bridge, then your libvirt version is severely out of date. On 8/11/21 2:53 PM, daggs wrote: >> From: "daggs" >>> From: "Martin Kletzander" >>>
Re: issues with vm after upgrade
Greetings Martin, > Sent: Thursday, August 12, 2021 at 2:07 PM > From: "daggs" > To: "Martin Kletzander" > Cc: d...@berrange.com, libvirt-users@redhat.com > Subject: Re: issues with vm after upgrade > > > Sent: Thursday, August 12, 2021 at 11:49 AM > > From: "Martin Kletzander" > > To: "daggs" > > Cc: d...@berrange.com, libvirt-users@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" > > >> To: "Martin Kletzander" > > >> Cc: d...@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" > > >> > To: "daggs" > > >> > Cc: d...@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" > > >> > >> To: "daggs" > > >> > >> Cc: d...@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 > > >> > > > > > >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.
Re: issues with vm after upgrade
> Sent: Thursday, August 12, 2021 at 11:49 AM > From: "Martin Kletzander" > To: "daggs" > Cc: d...@berrange.com, libvirt-users@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" > >> To: "Martin Kletzander" > >> Cc: d...@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" > >> > To: "daggs" > >> > Cc: d...@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" > >> > >> To: "daggs" > >> > >> Cc: d...@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 > >> > > > >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
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" To: "Martin Kletzander" Cc: d...@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" > To: "daggs" > Cc: d...@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" > >> To: "daggs" > >> Cc: d...@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 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 signature.asc Description: PGP signature
Re: issues with vm after upgrade
Greetings Martin, > Sent: Wednesday, August 11, 2021 at 6:08 PM > From: "daggs" > To: "Martin Kletzander" > Cc: d...@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" > > To: "daggs" > > Cc: d...@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" > > >> To: "daggs" > > >> Cc: d...@berrange.com, libvirt-users@redhat.com > > >> Subject: Re: issues with vm after upgrade > > >> > > >> On Tue, Aug 10, 2021 at 09:21:00PM +0200, daggs wrote: > > >> >Greetings Martin, Dan > > >> > > > >> >> Sent: Wednesday, August 04, 2021 at 1:54 PM > > >> >> From: "daggs" > > >> >> To: "Martin Kletzander" > > >> >> Cc: libvirt-users@redhat.com, d...@berrange.com > > >> >> Subject: Re: issues with vm after upgrade > > >> >> > > >> >> Greetings Martin, > > >> >> > > >> >> > Sent: Wednesday, August 04, 2021 at 11:52 AM > > >> >> > From: "Martin Kletzander" > > >> >> > To: "daggs" > > >> >> > Cc: libvirt-users@redhat.com, d...@berrange.com > > >> >> > Subject: Re: issues with vm after upgrade > > >> >> > > > >> >> > On Wed, Aug 04, 2021 at 10:30:29AM +0200, daggs wrote: > > >> >> > >Greetings Martin , > > >> >> > > > > >> >> > >> Sent: Wednesday, August 04, 2021 at 11:11 AM > > >> >> > >> From: "Martin Kletzander" > > >> >> > >> To: "daggs" > > >> >> > >> Cc: libvirt-users@redhat.com, d...@berrange.com > > >> >> > >> Subject: Re: issues with vm after upgrade > > >> >> > >> > > >> >> > >> On Tue, Aug 03, 2021 at 08:47:20PM +0200, daggs wrote: > > >> >> > >> >> Sent: Tuesday, August 03, 2021 at 6:51 PM > > >> >> > >> >> From: "daggs" > > >> >> > >> >> To: d...@berrange.com > > >> >> > >> >> Cc: "Martin Kletzander" , > > >> >> > >> >> libvirt-users@redhat.com > > >> >> > >> >> Subject: Re: issues with vm after upgrade > > >> >> > >> >> > > >> >> > >> >> Greetings Daniel, > > >> >> > >> >> > > >> >> > >> >> > Sent: Tuesday, August 03, 2021 at 6:39 PM > > >> >> > >> >> > From: "Daniel P. Berrange" > > >> >> > >> >> > To: "daggs" > > >> >> > >> >> > Cc: "Martin Kletzander" , > > >> >> > >> >> > libvirt-users@redhat.com > > >> >> > >> >> > Subject: Re: issues with vm after upgrade > > >> >> > >> >> > > > >> >> > >> >> > On Tue, Aug 03, 2021 at 05:34:53PM +0200, daggs wrote: > > >> >> > >> >> > > > Sent: Tuesday, August 03, 2021 at 6:29 PM > > >> >> > >> >> > > > From: "Daniel P. Berrange" > > >> >> > >> >> > > > To: "daggs" > > >> >> > >> >> > > > Cc: "Martin Kletzander" , > > >> >> > >> >> > > > libvirt-users@redhat.com > > >> >> > >> >> > > > Subject: Re: issues with vm after upgrade > > >> >> > >> >> > > > > > >> >> > >> >> > > > On Tue, Aug 03, 2021 at 05:21:52PM +0200, daggs wrote: > > >> >> > >> >> > > > > Greetings Daniel, > > >> >> > >> >> > > > > > > >>
Re: issues with vm after upgrade
Greetings Martin, > Sent: Wednesday, August 11, 2021 at 4:13 PM > From: "Martin Kletzander" > To: "daggs" > Cc: d...@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" > >> To: "daggs" > >> Cc: d...@berrange.com, libvirt-users@redhat.com > >> Subject: Re: issues with vm after upgrade > >> > >> On Tue, Aug 10, 2021 at 09:21:00PM +0200, daggs wrote: > >> >Greetings Martin, Dan > >> > > >> >> Sent: Wednesday, August 04, 2021 at 1:54 PM > >> >> From: "daggs" > >> >> To: "Martin Kletzander" > >> >> Cc: libvirt-users@redhat.com, d...@berrange.com > >> >> Subject: Re: issues with vm after upgrade > >> >> > >> >> Greetings Martin, > >> >> > >> >> > Sent: Wednesday, August 04, 2021 at 11:52 AM > >> >> > From: "Martin Kletzander" > >> >> > To: "daggs" > >> >> > Cc: libvirt-users@redhat.com, d...@berrange.com > >> >> > Subject: Re: issues with vm after upgrade > >> >> > > >> >> > On Wed, Aug 04, 2021 at 10:30:29AM +0200, daggs wrote: > >> >> > >Greetings Martin , > >> >> > > > >> >> > >> Sent: Wednesday, August 04, 2021 at 11:11 AM > >> >> > >> From: "Martin Kletzander" > >> >> > >> To: "daggs" > >> >> > >> Cc: libvirt-users@redhat.com, d...@berrange.com > >> >> > >> Subject: Re: issues with vm after upgrade > >> >> > >> > >> >> > >> On Tue, Aug 03, 2021 at 08:47:20PM +0200, daggs wrote: > >> >> > >> >> Sent: Tuesday, August 03, 2021 at 6:51 PM > >> >> > >> >> From: "daggs" > >> >> > >> >> To: d...@berrange.com > >> >> > >> >> Cc: "Martin Kletzander" , > >> >> > >> >> libvirt-users@redhat.com > >> >> > >> >> Subject: Re: issues with vm after upgrade > >> >> > >> >> > >> >> > >> >> Greetings Daniel, > >> >> > >> >> > >> >> > >> >> > Sent: Tuesday, August 03, 2021 at 6:39 PM > >> >> > >> >> > From: "Daniel P. Berrange" > >> >> > >> >> > To: "daggs" > >> >> > >> >> > Cc: "Martin Kletzander" , > >> >> > >> >> > libvirt-users@redhat.com > >> >> > >> >> > Subject: Re: issues with vm after upgrade > >> >> > >> >> > > >> >> > >> >> > On Tue, Aug 03, 2021 at 05:34:53PM +0200, daggs wrote: > >> >> > >> >> > > > Sent: Tuesday, August 03, 2021 at 6:29 PM > >> >> > >> >> > > > From: "Daniel P. Berrange" > >> >> > >> >> > > > To: "daggs" > >> >> > >> >> > > > Cc: "Martin Kletzander" , > >> >> > >> >> > > > libvirt-users@redhat.com > >> >> > >> >> > > > Subject: Re: issues with vm after upgrade > >> >> > >> >> > > > > >> >> > >> >> > > > On Tue, Aug 03, 2021 at 05:21:52PM +0200, daggs wrote: > >> >> > >> >> > > > > Greetings Daniel, > >> >> > >> >> > > > > > >> >> > >> >> > > > > > Sent: Tuesday, August 03, 2021 at 4:12 PM > >> >> > >> >> > > > > > From: "Daniel P. Berrange" > >> >> > >> >> > > > > > To: "daggs" > >> >> > >> >> > > > > > Cc: "Martin Kletzander" , > >> >> > >> >> > > > > > libvirt-users@redhat.com > >> >> > >> >> > > > > > Subject: Re: issues with vm a
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" To: "daggs" Cc: d...@berrange.com, libvirt-users@redhat.com Subject: Re: issues with vm after upgrade On Tue, Aug 10, 2021 at 09:21:00PM +0200, daggs wrote: >Greetings Martin, Dan > >> Sent: Wednesday, August 04, 2021 at 1:54 PM >> From: "daggs" >> To: "Martin Kletzander" >> Cc: libvirt-users@redhat.com, d...@berrange.com >> Subject: Re: issues with vm after upgrade >> >> Greetings Martin, >> >> > Sent: Wednesday, August 04, 2021 at 11:52 AM >> > From: "Martin Kletzander" >> > To: "daggs" >> > Cc: libvirt-users@redhat.com, d...@berrange.com >> > Subject: Re: issues with vm after upgrade >> > >> > On Wed, Aug 04, 2021 at 10:30:29AM +0200, daggs wrote: >> > >Greetings Martin , >> > > >> > >> Sent: Wednesday, August 04, 2021 at 11:11 AM >> > >> From: "Martin Kletzander" >> > >> To: "daggs" >> > >> Cc: libvirt-users@redhat.com, d...@berrange.com >> > >> Subject: Re: issues with vm after upgrade >> > >> >> > >> On Tue, Aug 03, 2021 at 08:47:20PM +0200, daggs wrote: >> > >> >> Sent: Tuesday, August 03, 2021 at 6:51 PM >> > >> >> From: "daggs" >> > >> >> To: d...@berrange.com >> > >> >> Cc: "Martin Kletzander" , libvirt-users@redhat.com >> > >> >> Subject: Re: issues with vm after upgrade >> > >> >> >> > >> >> Greetings Daniel, >> > >> >> >> > >> >> > Sent: Tuesday, August 03, 2021 at 6:39 PM >> > >> >> > From: "Daniel P. Berrange" >> > >> >> > To: "daggs" >> > >> >> > Cc: "Martin Kletzander" , libvirt-users@redhat.com >> > >> >> > Subject: Re: issues with vm after upgrade >> > >> >> > >> > >> >> > On Tue, Aug 03, 2021 at 05:34:53PM +0200, daggs wrote: >> > >> >> > > > Sent: Tuesday, August 03, 2021 at 6:29 PM >> > >> >> > > > From: "Daniel P. Berrange" >> > >> >> > > > To: "daggs" >> > >> >> > > > Cc: "Martin Kletzander" , libvirt-users@redhat.com >> > >> >> > > > Subject: Re: issues with vm after upgrade >> > >> >> > > > >> > >> >> > > > On Tue, Aug 03, 2021 at 05:21:52PM +0200, daggs wrote: >> > >> >> > > > > Greetings Daniel, >> > >> >> > > > > >> > >> >> > > > > > Sent: Tuesday, August 03, 2021 at 4:12 PM >> > >> >> > > > > > From: "Daniel P. Berrange" >> > >> >> > > > > > To: "daggs" >> > >> >> > > > > > Cc: "Martin Kletzander" , libvirt-users@redhat.com >> > >> >> > > > > > Subject: Re: issues with vm after upgrade >> > >> >> > > > > > >> > >> >> > > > > > The element just refers to the *host* backend used for audio >> > >> >> > > > > > playback. It would not affect guest hardware. Further, this has always >> > >> >> > > > > > existed - it just wasn't exposed in the XML previously. >> > >> >> > > > > > >> > >> >> > > > > > >> > >> >> > > > > >> > >> >> > > > > the upgrade changed something, here is the qemu cmd before the upgrade: https://dpaste.com/F2N5T8CT8 >> > >> >> > > > > here is after https://dpaste.com/F2N5T8CT8 >> > >> >> > > > >> > >> >> > > > Those links are both the same I'm afraid >> > >> >> > > > >> > >> >> > > >> > >> >> > > Duh! my bad! >> > >> >> > > good log: http://dpaste.com/F2N5T8CT8 >> > >> >> > > bad log: http://dpaste.com/6ECUHD2J8 >> > >> >> > >> > >> >> &g
Re: issues with vm after upgrade
Greetings Martin, > Sent: Wednesday, August 11, 2021 at 10:14 AM > From: "Martin Kletzander" > To: "daggs" > Cc: d...@berrange.com, libvirt-users@redhat.com > Subject: Re: issues with vm after upgrade > > On Tue, Aug 10, 2021 at 09:21:00PM +0200, daggs wrote: > >Greetings Martin, Dan > > > >> Sent: Wednesday, August 04, 2021 at 1:54 PM > >> From: "daggs" > >> To: "Martin Kletzander" > >> Cc: libvirt-users@redhat.com, d...@berrange.com > >> Subject: Re: issues with vm after upgrade > >> > >> Greetings Martin, > >> > >> > Sent: Wednesday, August 04, 2021 at 11:52 AM > >> > From: "Martin Kletzander" > >> > To: "daggs" > >> > Cc: libvirt-users@redhat.com, d...@berrange.com > >> > Subject: Re: issues with vm after upgrade > >> > > >> > On Wed, Aug 04, 2021 at 10:30:29AM +0200, daggs wrote: > >> > >Greetings Martin , > >> > > > >> > >> Sent: Wednesday, August 04, 2021 at 11:11 AM > >> > >> From: "Martin Kletzander" > >> > >> To: "daggs" > >> > >> Cc: libvirt-users@redhat.com, d...@berrange.com > >> > >> Subject: Re: issues with vm after upgrade > >> > >> > >> > >> On Tue, Aug 03, 2021 at 08:47:20PM +0200, daggs wrote: > >> > >> >> Sent: Tuesday, August 03, 2021 at 6:51 PM > >> > >> >> From: "daggs" > >> > >> >> To: d...@berrange.com > >> > >> >> Cc: "Martin Kletzander" , > >> > >> >> libvirt-users@redhat.com > >> > >> >> Subject: Re: issues with vm after upgrade > >> > >> >> > >> > >> >> Greetings Daniel, > >> > >> >> > >> > >> >> > Sent: Tuesday, August 03, 2021 at 6:39 PM > >> > >> >> > From: "Daniel P. Berrange" > >> > >> >> > To: "daggs" > >> > >> >> > Cc: "Martin Kletzander" , > >> > >> >> > libvirt-users@redhat.com > >> > >> >> > Subject: Re: issues with vm after upgrade > >> > >> >> > > >> > >> >> > On Tue, Aug 03, 2021 at 05:34:53PM +0200, daggs wrote: > >> > >> >> > > > Sent: Tuesday, August 03, 2021 at 6:29 PM > >> > >> >> > > > From: "Daniel P. Berrange" > >> > >> >> > > > To: "daggs" > >> > >> >> > > > Cc: "Martin Kletzander" , > >> > >> >> > > > libvirt-users@redhat.com > >> > >> >> > > > Subject: Re: issues with vm after upgrade > >> > >> >> > > > > >> > >> >> > > > On Tue, Aug 03, 2021 at 05:21:52PM +0200, daggs wrote: > >> > >> >> > > > > Greetings Daniel, > >> > >> >> > > > > > >> > >> >> > > > > > Sent: Tuesday, August 03, 2021 at 4:12 PM > >> > >> >> > > > > > From: "Daniel P. Berrange" > >> > >> >> > > > > > To: "daggs" > >> > >> >> > > > > > Cc: "Martin Kletzander" , > >> > >> >> > > > > > libvirt-users@redhat.com > >> > >> >> > > > > > Subject: Re: issues with vm after upgrade > >> > >> >> > > > > > > >> > >> >> > > > > > The element just refers to the *host* backend > >> > >> >> > > > > > used for audio > >> > >> >> > > > > > playback. It would not affect guest hardware. Further, > >> > >> >> > > > > > this has always > >> > >> >> > > > > > existed - it just wasn't exposed in the XML previously. > >> > >> >> > > > > > > >> > >> >> > > > > > > >> > >> >> > > > > > >> > >> >> > > > > the upgrade changed something, here is the qemu cmd before > >> > >> >> &
Re: issues with vm after upgrade
On Tue, Aug 10, 2021 at 09:21:00PM +0200, daggs wrote: Greetings Martin, Dan Sent: Wednesday, August 04, 2021 at 1:54 PM From: "daggs" To: "Martin Kletzander" Cc: libvirt-users@redhat.com, d...@berrange.com Subject: Re: issues with vm after upgrade Greetings Martin, > Sent: Wednesday, August 04, 2021 at 11:52 AM > From: "Martin Kletzander" > To: "daggs" > Cc: libvirt-users@redhat.com, d...@berrange.com > Subject: Re: issues with vm after upgrade > > On Wed, Aug 04, 2021 at 10:30:29AM +0200, daggs wrote: > >Greetings Martin , > > > >> Sent: Wednesday, August 04, 2021 at 11:11 AM > >> From: "Martin Kletzander" > >> To: "daggs" > >> Cc: libvirt-users@redhat.com, d...@berrange.com > >> Subject: Re: issues with vm after upgrade > >> > >> On Tue, Aug 03, 2021 at 08:47:20PM +0200, daggs wrote: > >> >> Sent: Tuesday, August 03, 2021 at 6:51 PM > >> >> From: "daggs" > >> >> To: d...@berrange.com > >> >> Cc: "Martin Kletzander" , libvirt-users@redhat.com > >> >> Subject: Re: issues with vm after upgrade > >> >> > >> >> Greetings Daniel, > >> >> > >> >> > Sent: Tuesday, August 03, 2021 at 6:39 PM > >> >> > From: "Daniel P. Berrange" > >> >> > To: "daggs" > >> >> > Cc: "Martin Kletzander" , libvirt-users@redhat.com > >> >> > Subject: Re: issues with vm after upgrade > >> >> > > >> >> > On Tue, Aug 03, 2021 at 05:34:53PM +0200, daggs wrote: > >> >> > > > Sent: Tuesday, August 03, 2021 at 6:29 PM > >> >> > > > From: "Daniel P. Berrange" > >> >> > > > To: "daggs" > >> >> > > > Cc: "Martin Kletzander" , libvirt-users@redhat.com > >> >> > > > Subject: Re: issues with vm after upgrade > >> >> > > > > >> >> > > > On Tue, Aug 03, 2021 at 05:21:52PM +0200, daggs wrote: > >> >> > > > > Greetings Daniel, > >> >> > > > > > >> >> > > > > > Sent: Tuesday, August 03, 2021 at 4:12 PM > >> >> > > > > > From: "Daniel P. Berrange" > >> >> > > > > > To: "daggs" > >> >> > > > > > Cc: "Martin Kletzander" , libvirt-users@redhat.com > >> >> > > > > > Subject: Re: issues with vm after upgrade > >> >> > > > > > > >> >> > > > > > The element just refers to the *host* backend used for audio > >> >> > > > > > playback. It would not affect guest hardware. Further, this has always > >> >> > > > > > existed - it just wasn't exposed in the XML previously. > >> >> > > > > > > >> >> > > > > > > >> >> > > > > > >> >> > > > > the upgrade changed something, here is the qemu cmd before the upgrade: https://dpaste.com/F2N5T8CT8 > >> >> > > > > here is after https://dpaste.com/F2N5T8CT8 > >> >> > > > > >> >> > > > Those links are both the same I'm afraid > >> >> > > > > >> >> > > > >> >> > > Duh! my bad! > >> >> > > good log: http://dpaste.com/F2N5T8CT8 > >> >> > > bad log: http://dpaste.com/6ECUHD2J8 > >> >> > > >> >> > The new log has a CLI flag > >> >> > > >> >> > -audiodev id=audio1,driver=none > >> >> > > >> >> > but the old log has an env variable > >> >> > > >> >> > QEMU_AUDIO_DRV=none > >> >> > > >> >> > which should be functionally identical, as QEMU will parse them both > >> >> > to the same internal config. > >> >> > > >> >> > The obvious difference in the logs which can cause your guest to fail > >> >> > is the different QEMU version. The old log shows QEMU 5.2.0, while the > >> >> > new log shows QEMU 6.0.0 > >> >> > > >> >> > >> >> thanks for the help, I went to look why the efi fw and found out that the nvram en
Re: issues with vm after upgrade
Greetings Martin, Dan > Sent: Wednesday, August 04, 2021 at 1:54 PM > From: "daggs" > To: "Martin Kletzander" > Cc: libvirt-users@redhat.com, d...@berrange.com > Subject: Re: issues with vm after upgrade > > Greetings Martin, > > > Sent: Wednesday, August 04, 2021 at 11:52 AM > > From: "Martin Kletzander" > > To: "daggs" > > Cc: libvirt-users@redhat.com, d...@berrange.com > > Subject: Re: issues with vm after upgrade > > > > On Wed, Aug 04, 2021 at 10:30:29AM +0200, daggs wrote: > > >Greetings Martin , > > > > > >> Sent: Wednesday, August 04, 2021 at 11:11 AM > > >> From: "Martin Kletzander" > > >> To: "daggs" > > >> Cc: libvirt-users@redhat.com, d...@berrange.com > > >> Subject: Re: issues with vm after upgrade > > >> > > >> On Tue, Aug 03, 2021 at 08:47:20PM +0200, daggs wrote: > > >> >> Sent: Tuesday, August 03, 2021 at 6:51 PM > > >> >> From: "daggs" > > >> >> To: d...@berrange.com > > >> >> Cc: "Martin Kletzander" , > > >> >> libvirt-users@redhat.com > > >> >> Subject: Re: issues with vm after upgrade > > >> >> > > >> >> Greetings Daniel, > > >> >> > > >> >> > Sent: Tuesday, August 03, 2021 at 6:39 PM > > >> >> > From: "Daniel P. Berrange" > > >> >> > To: "daggs" > > >> >> > Cc: "Martin Kletzander" , > > >> >> > libvirt-users@redhat.com > > >> >> > Subject: Re: issues with vm after upgrade > > >> >> > > > >> >> > On Tue, Aug 03, 2021 at 05:34:53PM +0200, daggs wrote: > > >> >> > > > Sent: Tuesday, August 03, 2021 at 6:29 PM > > >> >> > > > From: "Daniel P. Berrange" > > >> >> > > > To: "daggs" > > >> >> > > > Cc: "Martin Kletzander" , > > >> >> > > > libvirt-users@redhat.com > > >> >> > > > Subject: Re: issues with vm after upgrade > > >> >> > > > > > >> >> > > > On Tue, Aug 03, 2021 at 05:21:52PM +0200, daggs wrote: > > >> >> > > > > Greetings Daniel, > > >> >> > > > > > > >> >> > > > > > Sent: Tuesday, August 03, 2021 at 4:12 PM > > >> >> > > > > > From: "Daniel P. Berrange" > > >> >> > > > > > To: "daggs" > > >> >> > > > > > Cc: "Martin Kletzander" , > > >> >> > > > > > libvirt-users@redhat.com > > >> >> > > > > > Subject: Re: issues with vm after upgrade > > >> >> > > > > > > > >> >> > > > > > The element just refers to the *host* backend used > > >> >> > > > > > for audio > > >> >> > > > > > playback. It would not affect guest hardware. Further, this > > >> >> > > > > > has always > > >> >> > > > > > existed - it just wasn't exposed in the XML previously. > > >> >> > > > > > > > >> >> > > > > > > > >> >> > > > > > > >> >> > > > > the upgrade changed something, here is the qemu cmd before > > >> >> > > > > the upgrade: https://dpaste.com/F2N5T8CT8 > > >> >> > > > > here is after https://dpaste.com/F2N5T8CT8 > > >> >> > > > > > >> >> > > > Those links are both the same I'm afraid > > >> >> > > > > > >> >> > > > > >> >> > > Duh! my bad! > > >> >> > > good log: http://dpaste.com/F2N5T8CT8 > > >> >> > > bad log: http://dpaste.com/6ECUHD2J8 > > >> >> > > > >> >> > The new log has a CLI flag > > >> >> > > > >> >> > -audiodev id=audio1,driver=none > > >> >> > > > >> >> > but the old log has an env variable > > >> >> > > > >> >> > QEMU_
Re: issues with vm after upgrade
Greetings Martin, > Sent: Wednesday, August 04, 2021 at 11:52 AM > From: "Martin Kletzander" > To: "daggs" > Cc: libvirt-users@redhat.com, d...@berrange.com > Subject: Re: issues with vm after upgrade > > On Wed, Aug 04, 2021 at 10:30:29AM +0200, daggs wrote: > >Greetings Martin , > > > >> Sent: Wednesday, August 04, 2021 at 11:11 AM > >> From: "Martin Kletzander" > >> To: "daggs" > >> Cc: libvirt-users@redhat.com, d...@berrange.com > >> Subject: Re: issues with vm after upgrade > >> > >> On Tue, Aug 03, 2021 at 08:47:20PM +0200, daggs wrote: > >> >> Sent: Tuesday, August 03, 2021 at 6:51 PM > >> >> From: "daggs" > >> >> To: d...@berrange.com > >> >> Cc: "Martin Kletzander" , libvirt-users@redhat.com > >> >> Subject: Re: issues with vm after upgrade > >> >> > >> >> Greetings Daniel, > >> >> > >> >> > Sent: Tuesday, August 03, 2021 at 6:39 PM > >> >> > From: "Daniel P. Berrange" > >> >> > To: "daggs" > >> >> > Cc: "Martin Kletzander" , > >> >> > libvirt-users@redhat.com > >> >> > Subject: Re: issues with vm after upgrade > >> >> > > >> >> > On Tue, Aug 03, 2021 at 05:34:53PM +0200, daggs wrote: > >> >> > > > Sent: Tuesday, August 03, 2021 at 6:29 PM > >> >> > > > From: "Daniel P. Berrange" > >> >> > > > To: "daggs" > >> >> > > > Cc: "Martin Kletzander" , > >> >> > > > libvirt-users@redhat.com > >> >> > > > Subject: Re: issues with vm after upgrade > >> >> > > > > >> >> > > > On Tue, Aug 03, 2021 at 05:21:52PM +0200, daggs wrote: > >> >> > > > > Greetings Daniel, > >> >> > > > > > >> >> > > > > > Sent: Tuesday, August 03, 2021 at 4:12 PM > >> >> > > > > > From: "Daniel P. Berrange" > >> >> > > > > > To: "daggs" > >> >> > > > > > Cc: "Martin Kletzander" , > >> >> > > > > > libvirt-users@redhat.com > >> >> > > > > > Subject: Re: issues with vm after upgrade > >> >> > > > > > > >> >> > > > > > The element just refers to the *host* backend used > >> >> > > > > > for audio > >> >> > > > > > playback. It would not affect guest hardware. Further, this > >> >> > > > > > has always > >> >> > > > > > existed - it just wasn't exposed in the XML previously. > >> >> > > > > > > >> >> > > > > > > >> >> > > > > > >> >> > > > > the upgrade changed something, here is the qemu cmd before the > >> >> > > > > upgrade: https://dpaste.com/F2N5T8CT8 > >> >> > > > > here is after https://dpaste.com/F2N5T8CT8 > >> >> > > > > >> >> > > > Those links are both the same I'm afraid > >> >> > > > > >> >> > > > >> >> > > Duh! my bad! > >> >> > > good log: http://dpaste.com/F2N5T8CT8 > >> >> > > bad log: http://dpaste.com/6ECUHD2J8 > >> >> > > >> >> > The new log has a CLI flag > >> >> > > >> >> > -audiodev id=audio1,driver=none > >> >> > > >> >> > but the old log has an env variable > >> >> > > >> >> > QEMU_AUDIO_DRV=none > >> >> > > >> >> > which should be functionally identical, as QEMU will parse them both > >> >> > to the same internal config. > >> >> > > >> >> > The obvious difference in the logs which can cause your guest to fail > >> >> > is the different QEMU version. The old log shows QEMU 5.2.0, while the > >> >> > new log shows QEMU 6.0.0 > >> >> > > >> >> > >> >> thanks for the help, I went to look why the efi fw and found out that > >> >> the nvram entry in /et
Re: issues with vm after upgrade
On Wed, Aug 04, 2021 at 10:30:29AM +0200, daggs wrote: Greetings Martin , Sent: Wednesday, August 04, 2021 at 11:11 AM From: "Martin Kletzander" To: "daggs" Cc: libvirt-users@redhat.com, d...@berrange.com Subject: Re: issues with vm after upgrade On Tue, Aug 03, 2021 at 08:47:20PM +0200, daggs wrote: >> Sent: Tuesday, August 03, 2021 at 6:51 PM >> From: "daggs" >> To: d...@berrange.com >> Cc: "Martin Kletzander" , libvirt-users@redhat.com >> Subject: Re: issues with vm after upgrade >> >> Greetings Daniel, >> >> > Sent: Tuesday, August 03, 2021 at 6:39 PM >> > From: "Daniel P. Berrange" >> > To: "daggs" >> > Cc: "Martin Kletzander" , libvirt-users@redhat.com >> > Subject: Re: issues with vm after upgrade >> > >> > On Tue, Aug 03, 2021 at 05:34:53PM +0200, daggs wrote: >> > > > Sent: Tuesday, August 03, 2021 at 6:29 PM >> > > > From: "Daniel P. Berrange" >> > > > To: "daggs" >> > > > Cc: "Martin Kletzander" , libvirt-users@redhat.com >> > > > Subject: Re: issues with vm after upgrade >> > > > >> > > > On Tue, Aug 03, 2021 at 05:21:52PM +0200, daggs wrote: >> > > > > Greetings Daniel, >> > > > > >> > > > > > Sent: Tuesday, August 03, 2021 at 4:12 PM >> > > > > > From: "Daniel P. Berrange" >> > > > > > To: "daggs" >> > > > > > Cc: "Martin Kletzander" , libvirt-users@redhat.com >> > > > > > Subject: Re: issues with vm after upgrade >> > > > > > >> > > > > > The element just refers to the *host* backend used for audio >> > > > > > playback. It would not affect guest hardware. Further, this has always >> > > > > > existed - it just wasn't exposed in the XML previously. >> > > > > > >> > > > > > >> > > > > >> > > > > the upgrade changed something, here is the qemu cmd before the upgrade: https://dpaste.com/F2N5T8CT8 >> > > > > here is after https://dpaste.com/F2N5T8CT8 >> > > > >> > > > Those links are both the same I'm afraid >> > > > >> > > >> > > Duh! my bad! >> > > good log: http://dpaste.com/F2N5T8CT8 >> > > bad log: http://dpaste.com/6ECUHD2J8 >> > >> > The new log has a CLI flag >> > >> > -audiodev id=audio1,driver=none >> > >> > but the old log has an env variable >> > >> > QEMU_AUDIO_DRV=none >> > >> > which should be functionally identical, as QEMU will parse them both >> > to the same internal config. >> > >> > The obvious difference in the logs which can cause your guest to fail >> > is the different QEMU version. The old log shows QEMU 5.2.0, while the >> > new log shows QEMU 6.0.0 >> > >> >> thanks for the help, I went to look why the efi fw and found out that the nvram entry in /etc/libvirt/eqmu.conf was deleted upon update. >> I'm sure fixing this will solve he boot issue, hopefully audio issue too. >> >> Thanks, >> >> Dagg. >> > >unfortunately, that didn't helped, vm still wont come up, latest log at http://dpaste.com/2XZA4VQZA >any ideas? > Seems like the issue is: 2021-07-16T10:29:19.259409Z qemu-system-x86_64: vfio: Cannot reset device :00:1f.3, no available reset mechanism. 2021-07-16T10:29:19.369391Z qemu-system-x86_64: vfio: Cannot reset device :00:1f.3, no available reset mechanism. did you upgrade anything else? are you sure? you can see the same prints in the good log at http://dpaste.com/F2N5T8CT8 Oh, sorry, my bad. Then I do not see why it would not start. You said you managed to make the VM start on your own, what was the change that made it boot? Maybe there's a bug somewhere in qemu... signature.asc Description: PGP signature
Re: issues with vm after upgrade
Greetings Martin , > Sent: Wednesday, August 04, 2021 at 11:11 AM > From: "Martin Kletzander" > To: "daggs" > Cc: libvirt-users@redhat.com, d...@berrange.com > Subject: Re: issues with vm after upgrade > > On Tue, Aug 03, 2021 at 08:47:20PM +0200, daggs wrote: > >> Sent: Tuesday, August 03, 2021 at 6:51 PM > >> From: "daggs" > >> To: d...@berrange.com > >> Cc: "Martin Kletzander" , libvirt-users@redhat.com > >> Subject: Re: issues with vm after upgrade > >> > >> Greetings Daniel, > >> > >> > Sent: Tuesday, August 03, 2021 at 6:39 PM > >> > From: "Daniel P. Berrange" > >> > To: "daggs" > >> > Cc: "Martin Kletzander" , libvirt-users@redhat.com > >> > Subject: Re: issues with vm after upgrade > >> > > >> > On Tue, Aug 03, 2021 at 05:34:53PM +0200, daggs wrote: > >> > > > Sent: Tuesday, August 03, 2021 at 6:29 PM > >> > > > From: "Daniel P. Berrange" > >> > > > To: "daggs" > >> > > > Cc: "Martin Kletzander" , > >> > > > libvirt-users@redhat.com > >> > > > Subject: Re: issues with vm after upgrade > >> > > > > >> > > > On Tue, Aug 03, 2021 at 05:21:52PM +0200, daggs wrote: > >> > > > > Greetings Daniel, > >> > > > > > >> > > > > > Sent: Tuesday, August 03, 2021 at 4:12 PM > >> > > > > > From: "Daniel P. Berrange" > >> > > > > > To: "daggs" > >> > > > > > Cc: "Martin Kletzander" , > >> > > > > > libvirt-users@redhat.com > >> > > > > > Subject: Re: issues with vm after upgrade > >> > > > > > > >> > > > > > The element just refers to the *host* backend used for > >> > > > > > audio > >> > > > > > playback. It would not affect guest hardware. Further, this has > >> > > > > > always > >> > > > > > existed - it just wasn't exposed in the XML previously. > >> > > > > > > >> > > > > > > >> > > > > > >> > > > > the upgrade changed something, here is the qemu cmd before the > >> > > > > upgrade: https://dpaste.com/F2N5T8CT8 > >> > > > > here is after https://dpaste.com/F2N5T8CT8 > >> > > > > >> > > > Those links are both the same I'm afraid > >> > > > > >> > > > >> > > Duh! my bad! > >> > > good log: http://dpaste.com/F2N5T8CT8 > >> > > bad log: http://dpaste.com/6ECUHD2J8 > >> > > >> > The new log has a CLI flag > >> > > >> > -audiodev id=audio1,driver=none > >> > > >> > but the old log has an env variable > >> > > >> > QEMU_AUDIO_DRV=none > >> > > >> > which should be functionally identical, as QEMU will parse them both > >> > to the same internal config. > >> > > >> > The obvious difference in the logs which can cause your guest to fail > >> > is the different QEMU version. The old log shows QEMU 5.2.0, while the > >> > new log shows QEMU 6.0.0 > >> > > >> > >> thanks for the help, I went to look why the efi fw and found out that the > >> nvram entry in /etc/libvirt/eqmu.conf was deleted upon update. > >> I'm sure fixing this will solve he boot issue, hopefully audio issue too. > >> > >> Thanks, > >> > >> Dagg. > >> > > > >unfortunately, that didn't helped, vm still wont come up, latest log at > >http://dpaste.com/2XZA4VQZA > >any ideas? > > > > Seems like the issue is: > > 2021-07-16T10:29:19.259409Z qemu-system-x86_64: vfio: Cannot reset device > :00:1f.3, no available reset mechanism. > 2021-07-16T10:29:19.369391Z qemu-system-x86_64: vfio: Cannot reset device > :00:1f.3, no available reset mechanism. > > did you upgrade anything else? > are you sure? you can see the same prints in the good log at http://dpaste.com/F2N5T8CT8 Dagg
Re: issues with vm after upgrade
On Tue, Aug 03, 2021 at 08:47:20PM +0200, daggs wrote: Sent: Tuesday, August 03, 2021 at 6:51 PM From: "daggs" To: d...@berrange.com Cc: "Martin Kletzander" , libvirt-users@redhat.com Subject: Re: issues with vm after upgrade Greetings Daniel, > Sent: Tuesday, August 03, 2021 at 6:39 PM > From: "Daniel P. Berrange" > To: "daggs" > Cc: "Martin Kletzander" , libvirt-users@redhat.com > Subject: Re: issues with vm after upgrade > > On Tue, Aug 03, 2021 at 05:34:53PM +0200, daggs wrote: > > > Sent: Tuesday, August 03, 2021 at 6:29 PM > > > From: "Daniel P. Berrange" > > > To: "daggs" > > > Cc: "Martin Kletzander" , libvirt-users@redhat.com > > > Subject: Re: issues with vm after upgrade > > > > > > On Tue, Aug 03, 2021 at 05:21:52PM +0200, daggs wrote: > > > > Greetings Daniel, > > > > > > > > > Sent: Tuesday, August 03, 2021 at 4:12 PM > > > > > From: "Daniel P. Berrange" > > > > > To: "daggs" > > > > > Cc: "Martin Kletzander" , libvirt-users@redhat.com > > > > > Subject: Re: issues with vm after upgrade > > > > > > > > > > The element just refers to the *host* backend used for audio > > > > > playback. It would not affect guest hardware. Further, this has always > > > > > existed - it just wasn't exposed in the XML previously. > > > > > > > > > > > > > > > > > > the upgrade changed something, here is the qemu cmd before the upgrade: https://dpaste.com/F2N5T8CT8 > > > > here is after https://dpaste.com/F2N5T8CT8 > > > > > > Those links are both the same I'm afraid > > > > > > > Duh! my bad! > > good log: http://dpaste.com/F2N5T8CT8 > > bad log: http://dpaste.com/6ECUHD2J8 > > The new log has a CLI flag > > -audiodev id=audio1,driver=none > > but the old log has an env variable > > QEMU_AUDIO_DRV=none > > which should be functionally identical, as QEMU will parse them both > to the same internal config. > > The obvious difference in the logs which can cause your guest to fail > is the different QEMU version. The old log shows QEMU 5.2.0, while the > new log shows QEMU 6.0.0 > thanks for the help, I went to look why the efi fw and found out that the nvram entry in /etc/libvirt/eqmu.conf was deleted upon update. I'm sure fixing this will solve he boot issue, hopefully audio issue too. Thanks, Dagg. unfortunately, that didn't helped, vm still wont come up, latest log at http://dpaste.com/2XZA4VQZA any ideas? Seems like the issue is: 2021-07-16T10:29:19.259409Z qemu-system-x86_64: vfio: Cannot reset device :00:1f.3, no available reset mechanism. 2021-07-16T10:29:19.369391Z qemu-system-x86_64: vfio: Cannot reset device :00:1f.3, no available reset mechanism. did you upgrade anything else? Dagg signature.asc Description: PGP signature
Re: issues with vm after upgrade
> Sent: Tuesday, August 03, 2021 at 6:51 PM > From: "daggs" > To: d...@berrange.com > Cc: "Martin Kletzander" , libvirt-users@redhat.com > Subject: Re: issues with vm after upgrade > > Greetings Daniel, > > > Sent: Tuesday, August 03, 2021 at 6:39 PM > > From: "Daniel P. Berrange" > > To: "daggs" > > Cc: "Martin Kletzander" , libvirt-users@redhat.com > > Subject: Re: issues with vm after upgrade > > > > On Tue, Aug 03, 2021 at 05:34:53PM +0200, daggs wrote: > > > > Sent: Tuesday, August 03, 2021 at 6:29 PM > > > > From: "Daniel P. Berrange" > > > > To: "daggs" > > > > Cc: "Martin Kletzander" , libvirt-users@redhat.com > > > > Subject: Re: issues with vm after upgrade > > > > > > > > On Tue, Aug 03, 2021 at 05:21:52PM +0200, daggs wrote: > > > > > Greetings Daniel, > > > > > > > > > > > Sent: Tuesday, August 03, 2021 at 4:12 PM > > > > > > From: "Daniel P. Berrange" > > > > > > To: "daggs" > > > > > > Cc: "Martin Kletzander" , > > > > > > libvirt-users@redhat.com > > > > > > Subject: Re: issues with vm after upgrade > > > > > > > > > > > > The element just refers to the *host* backend used for audio > > > > > > playback. It would not affect guest hardware. Further, this has > > > > > > always > > > > > > existed - it just wasn't exposed in the XML previously. > > > > > > > > > > > > > > > > > > > > > > the upgrade changed something, here is the qemu cmd before the > > > > > upgrade: https://dpaste.com/F2N5T8CT8 > > > > > here is after https://dpaste.com/F2N5T8CT8 > > > > > > > > Those links are both the same I'm afraid > > > > > > > > > > Duh! my bad! > > > good log: http://dpaste.com/F2N5T8CT8 > > > bad log: http://dpaste.com/6ECUHD2J8 > > > > The new log has a CLI flag > > > > -audiodev id=audio1,driver=none > > > > but the old log has an env variable > > > > QEMU_AUDIO_DRV=none > > > > which should be functionally identical, as QEMU will parse them both > > to the same internal config. > > > > The obvious difference in the logs which can cause your guest to fail > > is the different QEMU version. The old log shows QEMU 5.2.0, while the > > new log shows QEMU 6.0.0 > > > > thanks for the help, I went to look why the efi fw and found out that the > nvram entry in /etc/libvirt/eqmu.conf was deleted upon update. > I'm sure fixing this will solve he boot issue, hopefully audio issue too. > > Thanks, > > Dagg. > unfortunately, that didn't helped, vm still wont come up, latest log at http://dpaste.com/2XZA4VQZA any ideas? Dagg
Re: issues with vm after upgrade
Greetings Daniel,
> Sent: Tuesday, August 03, 2021 at 4:12 PM
> From: "Daniel P. Berrange"
> To: "daggs"
> Cc: "Martin Kletzander" , libvirt-users@redhat.com
> Subject: Re: issues with vm after upgrade
>
> On Tue, Aug 03, 2021 at 02:54:39PM +0200, daggs wrote:
> > Greetings Martin,
> >
> > > Sent: Tuesday, August 03, 2021 at 11:37 AM
> > > From: "Martin Kletzander"
> > > To: "daggs"
> > > Cc: libvirt-users@redhat.com
> > > Subject: Re: issues with vm after upgrade
> > >
> > > On Mon, Aug 02, 2021 at 04:33:20PM +0200, daggs wrote:
> > > >Greetings Martin,
> > > >
> > > >> Sent: Monday, August 02, 2021 at 12:17 PM
> > > >> From: "Martin Kletzander"
> > > >> To: "daggs"
> > > >> Cc: libvirt-users@redhat.com
> > > >> Subject: Re: issues with vm after upgrade
> > > >>
> > > >> On Sat, Jul 31, 2021 at 12:19:59PM +0200, daggs wrote:
> > > >> >Greetings,
> > > >> >
> > > >> >a few weeks ago I've upgraded my system, this resulted with qemu and
> > > >> >libvirt being upgraded to 6.0.0 and ~7.5.0 respectfully.
> > > >> >I have two vms running on my system, router and streamer.
> > > >> >the router vm works great, the streamer vm doesn't.
> > > >> >after the streamer vm start, the monitor screen gets black and thats
> > > >> >it. no relevant error are found in the log, see:
> > > >> >http://dpaste.com/ERWDEJQPC
> > > >> >the xml ca be found at https://dpaste.com/FQDN6NTN2
> > > >> >in contrast the following oneliner works: qemu-system-x86_64 \
> > > >> >-machine pc-q35-5.0,accel=kvm,usb=off,smm=on,dump-guest-core=off \
> > > >> >-cpu host,migratable=on \
> > > >> >-m 15360 \
> > > >> >-smp 4,sockets=1,dies=1,cores=2,threads=2 \
> > > >> >-drive
> > > >> >file=/home/streamer/streamer.img.qcow2.new,if=virtio,format=qcow2 \
> > > >> >-device
> > > >> >vfio-pci,host=:00:02.0,romfile=/home/streamer/gpu-8086:5912-uefi.rom,multifunction=on
> > > >> > \
> > > >> >-device vfio-pci,host=:00:1f.3,multifunction=on \
> > > >> >-usb \
> > > >> >-device usb-host,vendorid=0x046d,productid=0xc52e \
> > > >> >-device usb-host,vendorid=0x2548,productid=0x1002 \
> > > >> >-display none \
> > > >> >-netdev
> > > >> >tap,id=hostnet0,ifname=virtsw-streamer,script=no,downscript=no \
> > > >> >-device e1000e,netdev=hostnet0,id=net0,mac=52:54:00:5a:4c:8c \
> > > >> >-blockdev
> > > >> >'{"driver":"file","filename":"/usr/share/edk2-ovmf/OVMF_CODE.secboot.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}'
> > > >> > \
> > > >> >-blockdev
> > > >> >'{"driver":"file","filename":"/var/lib/libvirt/qemu/nvram/streamer-vm-q35_VARS.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}'
> > > >> >
> > > >> >another issue encountered caused by this param: "-audiodev
> > > >> >id=audio1,driver=none" which is auto added to the qemu line.
> > > >> >if I add the line to the above oneliner, the guest doesn't detects
> > > >> >the pt sound card. without it it does and it works.
> > > >> >
> > > >>
> > > >> The links have expired, so I cannot look at the XML. However do you
> > > >> have any in the XML at all? I believe that without it we are
> > > >> disabling any audio backends since no audio HW was requested.
> > > >>
> > > >
> > > >here are the links:
> > > >1. xml: https://dpaste.com/D6JANX3Z3
> > > >2. log: https://dpaste.com/FMUDZY9PD
> > > >
> > > >as for the audio entry, "" is in the xml
> > > >I didn't added it
> > > >
> > >
> > > So let get this straight. You want the VM to use the HW GPU that you
> > > assigned to it and also use the audio on that GPU (e.g. HDMI or DP
&
Re: issues with vm after upgrade
Greetings Daniel, > Sent: Tuesday, August 03, 2021 at 6:39 PM > From: "Daniel P. Berrange" > To: "daggs" > Cc: "Martin Kletzander" , libvirt-users@redhat.com > Subject: Re: issues with vm after upgrade > > On Tue, Aug 03, 2021 at 05:34:53PM +0200, daggs wrote: > > > Sent: Tuesday, August 03, 2021 at 6:29 PM > > > From: "Daniel P. Berrange" > > > To: "daggs" > > > Cc: "Martin Kletzander" , libvirt-users@redhat.com > > > Subject: Re: issues with vm after upgrade > > > > > > On Tue, Aug 03, 2021 at 05:21:52PM +0200, daggs wrote: > > > > Greetings Daniel, > > > > > > > > > Sent: Tuesday, August 03, 2021 at 4:12 PM > > > > > From: "Daniel P. Berrange" > > > > > To: "daggs" > > > > > Cc: "Martin Kletzander" , > > > > > libvirt-users@redhat.com > > > > > Subject: Re: issues with vm after upgrade > > > > > > > > > > The element just refers to the *host* backend used for audio > > > > > playback. It would not affect guest hardware. Further, this has always > > > > > existed - it just wasn't exposed in the XML previously. > > > > > > > > > > > > > > > > > > the upgrade changed something, here is the qemu cmd before the upgrade: > > > > https://dpaste.com/F2N5T8CT8 > > > > here is after https://dpaste.com/F2N5T8CT8 > > > > > > Those links are both the same I'm afraid > > > > > > > Duh! my bad! > > good log: http://dpaste.com/F2N5T8CT8 > > bad log: http://dpaste.com/6ECUHD2J8 > > The new log has a CLI flag > > -audiodev id=audio1,driver=none > > but the old log has an env variable > > QEMU_AUDIO_DRV=none > > which should be functionally identical, as QEMU will parse them both > to the same internal config. > > The obvious difference in the logs which can cause your guest to fail > is the different QEMU version. The old log shows QEMU 5.2.0, while the > new log shows QEMU 6.0.0 > thanks for the help, I went to look why the efi fw and found out that the nvram entry in /etc/libvirt/eqmu.conf was deleted upon update. I'm sure fixing this will solve he boot issue, hopefully audio issue too. Thanks, Dagg.
Re: issues with vm after upgrade
On Tue, Aug 03, 2021 at 05:34:53PM +0200, daggs wrote: > > Sent: Tuesday, August 03, 2021 at 6:29 PM > > From: "Daniel P. Berrange" > > To: "daggs" > > Cc: "Martin Kletzander" , libvirt-users@redhat.com > > Subject: Re: issues with vm after upgrade > > > > On Tue, Aug 03, 2021 at 05:21:52PM +0200, daggs wrote: > > > Greetings Daniel, > > > > > > > Sent: Tuesday, August 03, 2021 at 4:12 PM > > > > From: "Daniel P. Berrange" > > > > To: "daggs" > > > > Cc: "Martin Kletzander" , libvirt-users@redhat.com > > > > Subject: Re: issues with vm after upgrade > > > > > > > > The element just refers to the *host* backend used for audio > > > > playback. It would not affect guest hardware. Further, this has always > > > > existed - it just wasn't exposed in the XML previously. > > > > > > > > > > > > > > the upgrade changed something, here is the qemu cmd before the upgrade: > > > https://dpaste.com/F2N5T8CT8 > > > here is after https://dpaste.com/F2N5T8CT8 > > > > Those links are both the same I'm afraid > > > > Duh! my bad! > good log: http://dpaste.com/F2N5T8CT8 > bad log: http://dpaste.com/6ECUHD2J8 The new log has a CLI flag -audiodev id=audio1,driver=none but the old log has an env variable QEMU_AUDIO_DRV=none which should be functionally identical, as QEMU will parse them both to the same internal config. The obvious difference in the logs which can cause your guest to fail is the different QEMU version. The old log shows QEMU 5.2.0, while the new log shows QEMU 6.0.0 With regards, Daniel -- |: https://berrange.com -o-https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o-https://fstop138.berrange.com :| |: https://entangle-photo.org-o-https://www.instagram.com/dberrange :|
Re: issues with vm after upgrade
> Sent: Tuesday, August 03, 2021 at 6:29 PM > From: "Daniel P. Berrange" > To: "daggs" > Cc: "Martin Kletzander" , libvirt-users@redhat.com > Subject: Re: issues with vm after upgrade > > On Tue, Aug 03, 2021 at 05:21:52PM +0200, daggs wrote: > > Greetings Daniel, > > > > > Sent: Tuesday, August 03, 2021 at 4:12 PM > > > From: "Daniel P. Berrange" > > > To: "daggs" > > > Cc: "Martin Kletzander" , libvirt-users@redhat.com > > > Subject: Re: issues with vm after upgrade > > > > > > The element just refers to the *host* backend used for audio > > > playback. It would not affect guest hardware. Further, this has always > > > existed - it just wasn't exposed in the XML previously. > > > > > > > > > > the upgrade changed something, here is the qemu cmd before the upgrade: > > https://dpaste.com/F2N5T8CT8 > > here is after https://dpaste.com/F2N5T8CT8 > > Those links are both the same I'm afraid > Duh! my bad! good log: http://dpaste.com/F2N5T8CT8 bad log: http://dpaste.com/6ECUHD2J8
Re: issues with vm after upgrade
On Tue, Aug 03, 2021 at 05:21:52PM +0200, daggs wrote: > Greetings Daniel, > > > Sent: Tuesday, August 03, 2021 at 4:12 PM > > From: "Daniel P. Berrange" > > To: "daggs" > > Cc: "Martin Kletzander" , libvirt-users@redhat.com > > Subject: Re: issues with vm after upgrade > > > > The element just refers to the *host* backend used for audio > > playback. It would not affect guest hardware. Further, this has always > > existed - it just wasn't exposed in the XML previously. > > > > > > the upgrade changed something, here is the qemu cmd before the upgrade: > https://dpaste.com/F2N5T8CT8 > here is after https://dpaste.com/F2N5T8CT8 Those links are both the same I'm afraid With regards, Daniel -- |: https://berrange.com -o-https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o-https://fstop138.berrange.com :| |: https://entangle-photo.org-o-https://www.instagram.com/dberrange :|
Re: issues with vm after upgrade
On Tue, Aug 03, 2021 at 02:54:39PM +0200, daggs wrote:
> Greetings Martin,
>
> > Sent: Tuesday, August 03, 2021 at 11:37 AM
> > From: "Martin Kletzander"
> > To: "daggs"
> > Cc: libvirt-users@redhat.com
> > Subject: Re: issues with vm after upgrade
> >
> > On Mon, Aug 02, 2021 at 04:33:20PM +0200, daggs wrote:
> > >Greetings Martin,
> > >
> > >> Sent: Monday, August 02, 2021 at 12:17 PM
> > >> From: "Martin Kletzander"
> > >> To: "daggs"
> > >> Cc: libvirt-users@redhat.com
> > >> Subject: Re: issues with vm after upgrade
> > >>
> > >> On Sat, Jul 31, 2021 at 12:19:59PM +0200, daggs wrote:
> > >> >Greetings,
> > >> >
> > >> >a few weeks ago I've upgraded my system, this resulted with qemu and
> > >> >libvirt being upgraded to 6.0.0 and ~7.5.0 respectfully.
> > >> >I have two vms running on my system, router and streamer.
> > >> >the router vm works great, the streamer vm doesn't.
> > >> >after the streamer vm start, the monitor screen gets black and thats
> > >> >it. no relevant error are found in the log, see:
> > >> >http://dpaste.com/ERWDEJQPC
> > >> >the xml ca be found at https://dpaste.com/FQDN6NTN2
> > >> >in contrast the following oneliner works: qemu-system-x86_64 \
> > >> >-machine pc-q35-5.0,accel=kvm,usb=off,smm=on,dump-guest-core=off \
> > >> >-cpu host,migratable=on \
> > >> >-m 15360 \
> > >> >-smp 4,sockets=1,dies=1,cores=2,threads=2 \
> > >> >-drive
> > >> >file=/home/streamer/streamer.img.qcow2.new,if=virtio,format=qcow2 \
> > >> >-device
> > >> >vfio-pci,host=:00:02.0,romfile=/home/streamer/gpu-8086:5912-uefi.rom,multifunction=on
> > >> > \
> > >> >-device vfio-pci,host=:00:1f.3,multifunction=on \
> > >> >-usb \
> > >> >-device usb-host,vendorid=0x046d,productid=0xc52e \
> > >> >-device usb-host,vendorid=0x2548,productid=0x1002 \
> > >> >-display none \
> > >> >-netdev tap,id=hostnet0,ifname=virtsw-streamer,script=no,downscript=no \
> > >> >-device e1000e,netdev=hostnet0,id=net0,mac=52:54:00:5a:4c:8c \
> > >> >-blockdev
> > >> >'{"driver":"file","filename":"/usr/share/edk2-ovmf/OVMF_CODE.secboot.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}'
> > >> > \
> > >> >-blockdev
> > >> >'{"driver":"file","filename":"/var/lib/libvirt/qemu/nvram/streamer-vm-q35_VARS.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}'
> > >> >
> > >> >another issue encountered caused by this param: "-audiodev
> > >> >id=audio1,driver=none" which is auto added to the qemu line.
> > >> >if I add the line to the above oneliner, the guest doesn't detects the
> > >> >pt sound card. without it it does and it works.
> > >> >
> > >>
> > >> The links have expired, so I cannot look at the XML. However do you
> > >> have any in the XML at all? I believe that without it we are
> > >> disabling any audio backends since no audio HW was requested.
> > >>
> > >
> > >here are the links:
> > >1. xml: https://dpaste.com/D6JANX3Z3
> > >2. log: https://dpaste.com/FMUDZY9PD
> > >
> > >as for the audio entry, "" is in the xml
> > >I didn't added it
> > >
> >
> > So let get this straight. You want the VM to use the HW GPU that you
> > assigned to it and also use the audio on that GPU (e.g. HDMI or DP
> > output). When you add the "-audiodev driver=none" the VM cannot see the
> > audio device on that GPU card? Or is that unrelated?
> >
> > There were some strict definitions added for audio devices lately, I
> > presume to make sure that no data gets leaked in/out the VM and in order
> > to get audio anywhere else than from/to VNC/spice you'd need to
> > configure that. It should not affect device assignment as far as I
> > understand it, although there might be some misunderstanding.
> >
>
> I'll try to explain, I'm passing the computer's O/B gpu and O/B sound card to
>
Re: issues with vm after upgrade
Greetings Martin,
> Sent: Tuesday, August 03, 2021 at 11:37 AM
> From: "Martin Kletzander"
> To: "daggs"
> Cc: libvirt-users@redhat.com
> Subject: Re: issues with vm after upgrade
>
> On Mon, Aug 02, 2021 at 04:33:20PM +0200, daggs wrote:
> >Greetings Martin,
> >
> >> Sent: Monday, August 02, 2021 at 12:17 PM
> >> From: "Martin Kletzander"
> >> To: "daggs"
> >> Cc: libvirt-users@redhat.com
> >> Subject: Re: issues with vm after upgrade
> >>
> >> On Sat, Jul 31, 2021 at 12:19:59PM +0200, daggs wrote:
> >> >Greetings,
> >> >
> >> >a few weeks ago I've upgraded my system, this resulted with qemu and
> >> >libvirt being upgraded to 6.0.0 and ~7.5.0 respectfully.
> >> >I have two vms running on my system, router and streamer.
> >> >the router vm works great, the streamer vm doesn't.
> >> >after the streamer vm start, the monitor screen gets black and thats it.
> >> >no relevant error are found in the log, see: http://dpaste.com/ERWDEJQPC
> >> >the xml ca be found at https://dpaste.com/FQDN6NTN2
> >> >in contrast the following oneliner works: qemu-system-x86_64 \
> >> >-machine pc-q35-5.0,accel=kvm,usb=off,smm=on,dump-guest-core=off \
> >> >-cpu host,migratable=on \
> >> >-m 15360 \
> >> >-smp 4,sockets=1,dies=1,cores=2,threads=2 \
> >> >-drive file=/home/streamer/streamer.img.qcow2.new,if=virtio,format=qcow2 \
> >> >-device
> >> >vfio-pci,host=:00:02.0,romfile=/home/streamer/gpu-8086:5912-uefi.rom,multifunction=on
> >> > \
> >> >-device vfio-pci,host=:00:1f.3,multifunction=on \
> >> >-usb \
> >> >-device usb-host,vendorid=0x046d,productid=0xc52e \
> >> >-device usb-host,vendorid=0x2548,productid=0x1002 \
> >> >-display none \
> >> >-netdev tap,id=hostnet0,ifname=virtsw-streamer,script=no,downscript=no \
> >> >-device e1000e,netdev=hostnet0,id=net0,mac=52:54:00:5a:4c:8c \
> >> >-blockdev
> >> >'{"driver":"file","filename":"/usr/share/edk2-ovmf/OVMF_CODE.secboot.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}'
> >> > \
> >> >-blockdev
> >> >'{"driver":"file","filename":"/var/lib/libvirt/qemu/nvram/streamer-vm-q35_VARS.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}'
> >> >
> >> >another issue encountered caused by this param: "-audiodev
> >> >id=audio1,driver=none" which is auto added to the qemu line.
> >> >if I add the line to the above oneliner, the guest doesn't detects the pt
> >> >sound card. without it it does and it works.
> >> >
> >>
> >> The links have expired, so I cannot look at the XML. However do you
> >> have any in the XML at all? I believe that without it we are
> >> disabling any audio backends since no audio HW was requested.
> >>
> >
> >here are the links:
> >1. xml: https://dpaste.com/D6JANX3Z3
> >2. log: https://dpaste.com/FMUDZY9PD
> >
> >as for the audio entry, "" is in the xml
> >I didn't added it
> >
>
> So let get this straight. You want the VM to use the HW GPU that you
> assigned to it and also use the audio on that GPU (e.g. HDMI or DP
> output). When you add the "-audiodev driver=none" the VM cannot see the
> audio device on that GPU card? Or is that unrelated?
>
> There were some strict definitions added for audio devices lately, I
> presume to make sure that no data gets leaked in/out the VM and in order
> to get audio anywhere else than from/to VNC/spice you'd need to
> configure that. It should not affect device assignment as far as I
> understand it, although there might be some misunderstanding.
>
I'll try to explain, I'm passing the computer's O/B gpu and O/B sound card to
the vm so I can use them inside the vm which serves as streamer.
all was working well until I've upgraded both qemu and libvirt (target versions
are started in the original mail)
since then, the vm doesn't boot at all.
I was able to bisect the qemu cmd libvirt generates partially and go the vm up.
this points to a config issue.
as part of the testing I've found out that when the vm boots, it has no sound
card.
following your suggestion, I've found that the xml has this: I have never added it to the xml so I assume that it was added as
part of the upgrade.
based on this I assume that there is another config which prevents my vm from
booting.
unfortunately, I don't have the xml prior to the upgrade to diff them.
Dagg.
Re: issues with vm after upgrade
On Mon, Aug 02, 2021 at 04:33:20PM +0200, daggs wrote:
Greetings Martin,
Sent: Monday, August 02, 2021 at 12:17 PM
From: "Martin Kletzander"
To: "daggs"
Cc: libvirt-users@redhat.com
Subject: Re: issues with vm after upgrade
On Sat, Jul 31, 2021 at 12:19:59PM +0200, daggs wrote:
>Greetings,
>
>a few weeks ago I've upgraded my system, this resulted with qemu and libvirt
being upgraded to 6.0.0 and ~7.5.0 respectfully.
>I have two vms running on my system, router and streamer.
>the router vm works great, the streamer vm doesn't.
>after the streamer vm start, the monitor screen gets black and thats it. no
relevant error are found in the log, see: http://dpaste.com/ERWDEJQPC
>the xml ca be found at https://dpaste.com/FQDN6NTN2
>in contrast the following oneliner works: qemu-system-x86_64 \
>-machine pc-q35-5.0,accel=kvm,usb=off,smm=on,dump-guest-core=off \
>-cpu host,migratable=on \
>-m 15360 \
>-smp 4,sockets=1,dies=1,cores=2,threads=2 \
>-drive file=/home/streamer/streamer.img.qcow2.new,if=virtio,format=qcow2 \
>-device
vfio-pci,host=:00:02.0,romfile=/home/streamer/gpu-8086:5912-uefi.rom,multifunction=on
\
>-device vfio-pci,host=:00:1f.3,multifunction=on \
>-usb \
>-device usb-host,vendorid=0x046d,productid=0xc52e \
>-device usb-host,vendorid=0x2548,productid=0x1002 \
>-display none \
>-netdev tap,id=hostnet0,ifname=virtsw-streamer,script=no,downscript=no \
>-device e1000e,netdev=hostnet0,id=net0,mac=52:54:00:5a:4c:8c \
>-blockdev
'{"driver":"file","filename":"/usr/share/edk2-ovmf/OVMF_CODE.secboot.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}'
\
>-blockdev
'{"driver":"file","filename":"/var/lib/libvirt/qemu/nvram/streamer-vm-q35_VARS.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}'
>
>another issue encountered caused by this param: "-audiodev
id=audio1,driver=none" which is auto added to the qemu line.
>if I add the line to the above oneliner, the guest doesn't detects the pt
sound card. without it it does and it works.
>
The links have expired, so I cannot look at the XML. However do you
have any in the XML at all? I believe that without it we are
disabling any audio backends since no audio HW was requested.
here are the links:
1. xml: https://dpaste.com/D6JANX3Z3
2. log: https://dpaste.com/FMUDZY9PD
as for the audio entry, "" is in the xml
I didn't added it
So let get this straight. You want the VM to use the HW GPU that you
assigned to it and also use the audio on that GPU (e.g. HDMI or DP
output). When you add the "-audiodev driver=none" the VM cannot see the
audio device on that GPU card? Or is that unrelated?
There were some strict definitions added for audio devices lately, I
presume to make sure that no data gets leaked in/out the VM and in order
to get audio anywhere else than from/to VNC/spice you'd need to
configure that. It should not affect device assignment as far as I
understand it, although there might be some misunderstanding.
Thanks,
Dagg
signature.asc
Description: PGP signature
Re: issues with vm after upgrade
Greetings Martin,
> Sent: Monday, August 02, 2021 at 12:17 PM
> From: "Martin Kletzander"
> To: "daggs"
> Cc: libvirt-users@redhat.com
> Subject: Re: issues with vm after upgrade
>
> On Sat, Jul 31, 2021 at 12:19:59PM +0200, daggs wrote:
> >Greetings,
> >
> >a few weeks ago I've upgraded my system, this resulted with qemu and libvirt
> >being upgraded to 6.0.0 and ~7.5.0 respectfully.
> >I have two vms running on my system, router and streamer.
> >the router vm works great, the streamer vm doesn't.
> >after the streamer vm start, the monitor screen gets black and thats it. no
> >relevant error are found in the log, see: http://dpaste.com/ERWDEJQPC
> >the xml ca be found at https://dpaste.com/FQDN6NTN2
> >in contrast the following oneliner works: qemu-system-x86_64 \
> >-machine pc-q35-5.0,accel=kvm,usb=off,smm=on,dump-guest-core=off \
> >-cpu host,migratable=on \
> >-m 15360 \
> >-smp 4,sockets=1,dies=1,cores=2,threads=2 \
> >-drive file=/home/streamer/streamer.img.qcow2.new,if=virtio,format=qcow2 \
> >-device
> >vfio-pci,host=:00:02.0,romfile=/home/streamer/gpu-8086:5912-uefi.rom,multifunction=on
> > \
> >-device vfio-pci,host=:00:1f.3,multifunction=on \
> >-usb \
> >-device usb-host,vendorid=0x046d,productid=0xc52e \
> >-device usb-host,vendorid=0x2548,productid=0x1002 \
> >-display none \
> >-netdev tap,id=hostnet0,ifname=virtsw-streamer,script=no,downscript=no \
> >-device e1000e,netdev=hostnet0,id=net0,mac=52:54:00:5a:4c:8c \
> >-blockdev
> >'{"driver":"file","filename":"/usr/share/edk2-ovmf/OVMF_CODE.secboot.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}'
> > \
> >-blockdev
> >'{"driver":"file","filename":"/var/lib/libvirt/qemu/nvram/streamer-vm-q35_VARS.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}'
> >
> >another issue encountered caused by this param: "-audiodev
> >id=audio1,driver=none" which is auto added to the qemu line.
> >if I add the line to the above oneliner, the guest doesn't detects the pt
> >sound card. without it it does and it works.
> >
>
> The links have expired, so I cannot look at the XML. However do you
> have any in the XML at all? I believe that without it we are
> disabling any audio backends since no audio HW was requested.
>
here are the links:
1. xml: https://dpaste.com/D6JANX3Z3
2. log: https://dpaste.com/FMUDZY9PD
as for the audio entry, "" is in the xml
I didn't added it
Thanks,
Dagg
Re: issues with vm after upgrade
On Sat, Jul 31, 2021 at 12:19:59PM +0200, daggs wrote:
Greetings,
a few weeks ago I've upgraded my system, this resulted with qemu and libvirt
being upgraded to 6.0.0 and ~7.5.0 respectfully.
I have two vms running on my system, router and streamer.
the router vm works great, the streamer vm doesn't.
after the streamer vm start, the monitor screen gets black and thats it. no
relevant error are found in the log, see: http://dpaste.com/ERWDEJQPC
the xml ca be found at https://dpaste.com/FQDN6NTN2
in contrast the following oneliner works: qemu-system-x86_64 \
-machine pc-q35-5.0,accel=kvm,usb=off,smm=on,dump-guest-core=off \
-cpu host,migratable=on \
-m 15360 \
-smp 4,sockets=1,dies=1,cores=2,threads=2 \
-drive file=/home/streamer/streamer.img.qcow2.new,if=virtio,format=qcow2 \
-device
vfio-pci,host=:00:02.0,romfile=/home/streamer/gpu-8086:5912-uefi.rom,multifunction=on
\
-device vfio-pci,host=:00:1f.3,multifunction=on \
-usb \
-device usb-host,vendorid=0x046d,productid=0xc52e \
-device usb-host,vendorid=0x2548,productid=0x1002 \
-display none \
-netdev tap,id=hostnet0,ifname=virtsw-streamer,script=no,downscript=no \
-device e1000e,netdev=hostnet0,id=net0,mac=52:54:00:5a:4c:8c \
-blockdev
'{"driver":"file","filename":"/usr/share/edk2-ovmf/OVMF_CODE.secboot.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}'
\
-blockdev
'{"driver":"file","filename":"/var/lib/libvirt/qemu/nvram/streamer-vm-q35_VARS.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}'
another issue encountered caused by this param: "-audiodev
id=audio1,driver=none" which is auto added to the qemu line.
if I add the line to the above oneliner, the guest doesn't detects the pt sound
card. without it it does and it works.
The links have expired, so I cannot look at the XML. However do you
have any in the XML at all? I believe that without it we are
disabling any audio backends since no audio HW was requested.
help on solving both issues will be appreciated.
Thanks,
Dagg
signature.asc
Description: PGP signature
issues with vm after upgrade
Greetings,
a few weeks ago I've upgraded my system, this resulted with qemu and libvirt
being upgraded to 6.0.0 and ~7.5.0 respectfully.
I have two vms running on my system, router and streamer.
the router vm works great, the streamer vm doesn't.
after the streamer vm start, the monitor screen gets black and thats it. no
relevant error are found in the log, see: http://dpaste.com/ERWDEJQPC
the xml ca be found at https://dpaste.com/FQDN6NTN2
in contrast the following oneliner works: qemu-system-x86_64 \
-machine pc-q35-5.0,accel=kvm,usb=off,smm=on,dump-guest-core=off \
-cpu host,migratable=on \
-m 15360 \
-smp 4,sockets=1,dies=1,cores=2,threads=2 \
-drive file=/home/streamer/streamer.img.qcow2.new,if=virtio,format=qcow2 \
-device
vfio-pci,host=:00:02.0,romfile=/home/streamer/gpu-8086:5912-uefi.rom,multifunction=on
\
-device vfio-pci,host=:00:1f.3,multifunction=on \
-usb \
-device usb-host,vendorid=0x046d,productid=0xc52e \
-device usb-host,vendorid=0x2548,productid=0x1002 \
-display none \
-netdev tap,id=hostnet0,ifname=virtsw-streamer,script=no,downscript=no \
-device e1000e,netdev=hostnet0,id=net0,mac=52:54:00:5a:4c:8c \
-blockdev
'{"driver":"file","filename":"/usr/share/edk2-ovmf/OVMF_CODE.secboot.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}'
\
-blockdev
'{"driver":"file","filename":"/var/lib/libvirt/qemu/nvram/streamer-vm-q35_VARS.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}'
another issue encountered caused by this param: "-audiodev
id=audio1,driver=none" which is auto added to the qemu line.
if I add the line to the above oneliner, the guest doesn't detects the pt sound
card. without it it does and it works.
help on solving both issues will be appreciated.
Thanks,
Dagg
