[Bug 1817832] Re: qemu crashes with `kvm_init_vcpu failed: Invalid argument` during guest boot cores >256
It is fine to be part of the linux-hwe updates in 18.04.3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817832 Title: qemu crashes with `kvm_init_vcpu failed: Invalid argument` during guest boot cores >256 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1817832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792948] Re: Failed to install grub-ieee1275 from Trusty release-pocket on a Power8 system
Fresh installation failing on IBM Power8 system. Sep 21 17:42:11 in-target: Setting up grub-ieee1275 (2.02~beta2-9ubuntu1.15) ... Sep 21 17:42:11 in-target: Installing for powerpc-ieee1275 platform. Sep 21 17:42:12 in-target: grub-install: error: cannot find a GRUB drive for /dev/sda1. Check your device.map. Sep 21 17:42:12 in-target: dpkg: error processing package grub-ieee1275 (--configure): Sep 21 17:42:12 in-target: subprocess installed post-installation script returned error exit status 1 Sep 21 17:42:12 in-target: Errors were encountered while processing: Sep 21 17:42:12 in-target: grub-ieee1275 Sep 21 17:42:12 in-target: E: Sub-process /usr/bin/dpkg returned an error code (1) Sep 21 17:42:12 in-target: Sep 21 17:42:12 in-target: tasksel: aptitude failed (100) Sep 21 17:42:12 in-target: Setting up grub-ieee1275 (2.02~beta2-9ubuntu1.15) ... Sep 21 17:42:12 in-target: Installing for powerpc-ieee1275 platform. Sep 21 17:42:12 in-target: grub-install: error: cannot find a GRUB drive for /dev/sda1. Check your device.map. Sep 21 17:42:13 in-target: dpkg: error processing package grub-ieee1275 (--configure): Sep 21 17:42:13 in-target: subprocess installed post-installation script returned error exit status 1 Sep 21 17:42:13 in-target: Errors were encountered while processing: Sep 21 17:42:13 in-target: grub-ieee1275 Sep 21 17:42:13 main-menu[1127]: WARNING **: Configuring 'pkgsel' failed with error code 1 Sep 21 17:42:13 main-menu[1127]: WARNING **: Menu item 'pkgsel' failed. Sep 21 17:42:24 main-menu[1127]: INFO: Modifying debconf priority limit from 'medium' to 'low' Sep 21 17:42:24 debconf: Setting debconf/priority to low Sep 21 17:42:50 main-menu[1127]: INFO: Menu item 'save-logs' selected ** Attachment added: "installation failure log" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1792948/+attachment/5191511/+files/installlog.tgz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792948 Title: Failed to install grub-ieee1275 from Trusty release-pocket on a Power8 system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1792948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750543] Re: [power9][Ubuntu 18.04][4.15.0-10-generic][libvirt-bin-4.0.0-1ubuntu2] KVM guest unable start from libvirt "could not find capabilities for arch=ppc64le " (kvm)
I meant by, even if the jenkins created a folder `/var/lib/libvirt/images` in first place, it should have had the right permissions as how `temp` folder I created above has the same permissions as the install'ed libvirt folder now, I do not find a convincing reason why it did not work in the first place. I hope the env does not have any local workarounds to make it work and new install of host again gets this issue :-) Regards, -Satheesh. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750543 Title: [power9][Ubuntu 18.04][4.15.0-10-generic][libvirt-bin-4.0.0-1ubuntu2] KVM guest unable start from libvirt "could not find capabilities for arch=ppc64le " (kvm) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1750543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1628101] Re: qemu-kvm: virt-install VM fails due to inconsistent virsh capabilities output due to multiple qemu instance
** Bug watch added: Debian Bug tracker #847840 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847840 ** Also affects: qemu (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847840 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1628101 Title: qemu-kvm: virt-install VM fails due to inconsistent virsh capabilities output due to multiple qemu instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1628101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1628101] Re: qemu-kvm: virt-install VM fails due to inconsistent virsh capabilities output due to multiple qemu instance
Yes, your understanding is correct, the initial issue got rectified by removing cache and removing the local qemu instance compiled with qemu-2.7. Looks like the PATH precedence is local bydefault and it can be inconsistent, so different utilities takes inconsistent values in this case, like virt-install complains about unsupported cpu. Keeping the absolute binary path in kvm wrapper will make that it always points to the system installed binary and if user wants to use his binary anyways can change wrapper "or" use it standalone?, which other distributions also follow. In that way we would have inconsistent virsh capabilities output even the custom binaries installed in the system -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1628101 Title: qemu-kvm: virt-install VM fails due to inconsistent virsh capabilities output due to multiple qemu instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1628101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
