[Expired for qemu-kvm (Ubuntu) because there has been no activity for 60
days.]
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
I still haven't had the chance to test this properly. (server is in
production), but the problem manifested itself by accident. So, here's a
little bit of information.
I started downloading (rsync) a qcow image from the file server and
noticed it was bit slow. 14MB/sec max - 790kB/s after a
Thanks for the info, Alvin. So I wonder if we could reproduce this without
qemu, simply creating two LVM partitions, one with a snapshot, with both
originals mounted, rsyncing to the one while trying to get something done
(maybe a slower rate-limited rsync) in the other.
--
You received this
I've tried again to reproduce this to no avail.
Do you get different behavior if you do
qemu-img convert -f raw -O raw /dev/yourvg/yourlv lv1.raw
and if you do
dd if=/dev/yourvg/yourlv of=lv2.raw
?
If not, then the compression if you're using it, or simply memory
pressure appears to be
It's not good to let this bug expire. LVM snapshots are a severe risk
and an important feature on file servers.
** Changed in: qemu-kvm (Ubuntu)
Status: Expired = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in
Does this:
kvm D 0 9632 1 0x
8801a4269ca8 0086 00015bc0 00015bc0
8802004fdf38 8801a4269fd8 00015bc0 8802004fdb80
00015bc0 8801a4269fd8 00015bc0 8802004fdf38
Call Trace:
[815596b7]
Unfortunately, this shows up in both host and guests.
I haven't tried to use qemu-img on a snapshot, but I will. I fear it
will not make much difference. Just having snapshots (without accessing
them) is enough to bring the system down on moments with heavy I/O.
Sometime this week, I will warn
Quoting Alvin (i...@alvin.be):
Unfortunately, this shows up in both host and guests.
I haven't tried to use qemu-img on a snapshot, but I will. I fear it
will not make much difference. Just having snapshots (without accessing
them) is enough to bring the system down on moments with heavy
[Expired for qemu-kvm (Ubuntu) because there has been no activity for 60
days.]
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
You're right about the errors. Apparently I had a full snapshot, but it
doesn't make a difference.
Meanwhile, I've had the time to test this. It is easy to reproduce:
- Create a snapshot (1 is enough)
- Cause some I/O, like qemu-img convert (this does /not/ have to be the
snapshotted volume)
-
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
https://bugs.launchpad.net/bugs/712392
Title:
qemu-img convert blocks other tasks
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify
Thanks for taking the time to report this bug and helping to make Ubuntu
better.
For my own test on a natty server, I started with a 30G qcow2 disk with
a lucid install on it. It had about 1G allocated. Conversion from
qcow2 to raw took probably less than 10 seconds. Conversion back to
qcow
12 matches
Mail list logo
