On Wed, Feb 22, 2017 at 8:30 AM, ChristianEhrhardt < [email protected]> wrote:
> Discussed on IRC, > > TL;DR of that: > The real customer case is different than we assumed so far: > sda <- Host root > sdb <- VG <- Guest Disk > > 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? > - 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. > > Eric check exact disk types and reproduce in a similar env. > He then will come back with iostat and blktrace data of good/bad case. > > ** Changed in: qemu (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > 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 > -- 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
