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
- 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.
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 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
