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, > > >> >> > >> >> > > > > > > >> >> > >> >> > > > > > 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
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 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
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 >> > >> >> > >> > >> >> > 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... >> > >> >> since the upgrade I wasn't able to boot it using libvirt.
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 > >> > >> >> > > > > 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
Re: vmware ESXi in KVM
I made a couple machines like this last year. Why on earth did I add "os-variant=fedora10"? Can't remember. I had issues mixing libvirt and VMware. I ran into some odd SSL errors, and the machines couldn't see each other. I didn't get to the bottom of those problems. HOST=esxi7-1 OS_DISK=/var/lib/libvirt/images/$HOST.qcow2 DATASTORE_DISK=/var/lib/libvirt/images/$HOST-datastore.qcow2 INSTALL_ISO=/var/lib/libvirt/images/VMware-VMvisor-Installer-7.0U2-17630552.x86_64.iso IF1_MAC=52:54:00:00:00:10 IF2_MAC=52:54:00:00:00:11 HOST=esxi7-2 OS_DISK=/var/lib/libvirt/images/$HOST.qcow2 DATASTORE_DISK=/var/lib/libvirt/images/$HOST-datastore.qcow2 INSTALL_ISO=/var/lib/libvirt/images/VMware-VMvisor-Installer-7.0U2-17630552.x86_64.iso IF1_MAC=52:54:00:00:00:12 IF2_MAC=52:54:00:00:00:13 virt-install \ --name="$HOST" \ --vcpus=8 \ --ram=20480 \ --cpu host-passthrough \ --disk path=$OS_DISK,size=20,bus=sata \ --disk path=$DATASTORE_DISK,size=200,bus=sata \ --os-type linux \ --os-variant=fedora10 \ --network network=pubbr0,mac=$IF1_MAC,model=e1000e \ --network network=privbr0,mac=$IF2_MAC,model=e1000e \ --boot uefi,menu=on,cdrom,hd \ --graphics vnc \ --video qxl \ --cdrom $INSTALL_ISO \ --noautoconsole \ --features kvm_hidden=on \ --machine q35 On Wed, Aug 11, 2021 at 9:58 AM Martin Kletzander wrote: > On Tue, Aug 10, 2021 at 09:45:37PM +0200, Gunnar wrote: > >I am trying to install esxi7 inside a KVM machine > > > >virt-install --name=esxi7 \ > >--vcpus=2 \ > >--memory=4096 \ > > > --cdrom=/home/username/isos/VMware-VMvisor-Installer-7.0U2a-17867351.x86_64.iso > >\ > >--disk size=33 \ > >--os-variant=unknown > > > >the installation process starts but does not get fails with a "No > >network adapters" error. This does not happen with other VM's. > >What do I have to add to above command in order to attach the default > >network adapter to the machine? > > > > First look if the machine has any network interface. If it does, the > guest OS probably does not support the model, so you can change that. > If it does not have one, then you probably want to use '--network > network=default' in your virt-install command and you can always look > that up in the man page as well (e.g. man virt-install). > > >or is there any other trick I have to be aware of when it comes to > >installing ESXi > > > > No idea as I have never installed anything like that. > > >thx ... Gunnar > > Hope that helped, > Martin >
Re: vmware ESXi in KVM
On Tue, Aug 10, 2021 at 09:45:37PM +0200, Gunnar wrote: I am trying to install esxi7 inside a KVM machine virt-install --name=esxi7 \ --vcpus=2 \ --memory=4096 \ --cdrom=/home/username/isos/VMware-VMvisor-Installer-7.0U2a-17867351.x86_64.iso \ --disk size=33 \ --os-variant=unknown the installation process starts but does not get fails with a "No network adapters" error. This does not happen with other VM's. What do I have to add to above command in order to attach the default network adapter to the machine? First look if the machine has any network interface. If it does, the guest OS probably does not support the model, so you can change that. If it does not have one, then you probably want to use '--network network=default' in your virt-install command and you can always look that up in the man page as well (e.g. man virt-install). or is there any other trick I have to be aware of when it comes to installing ESXi No idea as I have never installed anything like that. thx ... Gunnar Hope that helped, Martin signature.asc Description: PGP signature
vmware ESXi in KVM
I am trying to install esxi7 inside a KVM machine virt-install --name=esxi7 \ --vcpus=2 \ --memory=4096 \ --cdrom=/home/username/isos/VMware-VMvisor-Installer-7.0U2a-17867351.x86_64.iso \ --disk size=33 \ --os-variant=unknown the installation process starts but does not get fails with a "No network adapters" error. This does not happen with other VM's. What do I have to add to above command in order to attach the default network adapter to the machine? or is there any other trick I have to be aware of when it comes to installing ESXi thx ... Gunnar
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 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... > since the upgrade I wasn't able to boot it using libvirt. however the following qemucmd 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 \
