On Wed, Feb 22, 2017 at 3:53 PM, Ryan Harper <[email protected]> wrote:
> What sort of disks and connections are we talking about on the host? How > are they attached? Is sda in any of the LVM groups? > Any way we can get a sosreport from the host? > https://pastebin.canonical.com/180330/ Eric already took the todo to ask for the types to reproduce on the right setup. We all know there can be a huge diff between spinning and nvme and all in between I just heard he has sosreport and can attach it. I wonder if we can find the disk type in there. > > - In the guest it writes to Guest Disk. > > - This can only fill up sdb directly (the queue of sda should be > untouched > > by the guests activity) > > - Update-Grub is in the Host, so should be sda only > > > > Could still be locking up CPU/IRQ. > > > > Yes, 'virsh capabilities' from the host and 'virsh dumpxml <guest>' would > be > helpful to understand the hypervisor/guest topology better. > Yeah that will help as well to reproduce the same case -- Christian Ehrhardt Software Engineer, Ubuntu Server Canonical Ltd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1666555 Title: update-grub slow with raw LVM source dev + VirtIO bus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1666555/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
