I can't reproduce the situation using 2 disks + cache='none' + io='native +
bus='virtio'.
So my 1xDisk scenario was because I was exhausting the disk.
Disk 1 -> vg01 -> Host disk ("/")
Disk 2 -> vg02 -> Pool for KVM Guest
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
└─sda1 8:1 0 465.8G 0 part
└─vg01-root 252:0 0 372.5G 0 lvm /
sdb 8:16 0 465.8G 0 disk
└─vg02-kvmguest01 252:1 0 18.6G 0 lvm
# Idle
$ time update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.4.0-64-generic
Found initrd image: /boot/initrd.img-4.4.0-64-generic
done
real 0m0.782s
user 0m0.272s
sys 0m0.120s
# With my contact protocol to reproduce the situation :
$ time update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.4.0-64-generic
Found initrd image: /boot/initrd.img-4.4.0-64-generic
done
real 0m0.782s
user 0m0.272s
sys 0m0.120s
So the more I look at this, and the more I think it's not a bug but
something in my contact's system that maybe is competing for writes, I
agree that having some iostat date from my contact's system will help
identifying how the I/O looks like with and without his protocol.
- Eric
--
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
