[Bug 524447] Re: virsh save is very slow

2012-03-09 Thread Jeff Snider
I tested that other bug. As far as I can tell it is not fixed. I haven't gotten any sort of response on it for a week. So... now what? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/524447 Title:

[Bug 592010] Re: hardy2lucid upgrade: qemu-common should replace qemu as well as qemu-kvm / package qemu-common (not installed) failed to install/upgrade: trying to overwrite '/usr/share/qemu/keymaps/

2012-03-06 Thread Jeff Snider
Could somebody tell me if I tested that correctly or not? I'd like to get this either working or rolled back soon. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/592010 Title: hardy2lucid

[Bug 592010] Re: hardy2lucid upgrade: qemu-common should replace qemu as well as qemu-kvm / package qemu-common (not installed) failed to install/upgrade: trying to overwrite '/usr/share/qemu/keymaps/

2012-03-02 Thread Jeff Snider
I'm starting on testing this. Results in a little while. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/592010 Title: hardy2lucid upgrade: qemu-common should replace qemu as well as qemu- kvm /

[Bug 524447] Re: virsh save is very slow

2012-03-02 Thread Jeff Snider
I'll go stand up some vms to test that one out. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/524447 Title: virsh save is very slow To manage notifications about this bug go to:

[Bug 592010] Re: hardy2lucid upgrade: qemu-common should replace qemu as well as qemu-kvm / package qemu-common (not installed) failed to install/upgrade: trying to overwrite '/usr/share/qemu/keymaps/

2012-03-02 Thread Jeff Snider
Ok so I spent a while at this and it does not appear to be fixed to me. I'm not really familiar with release upgrades so it might just be my unfamiliarity, if so someone with more understanding of what is going on will need to verify this instead. Here's what I did. I installed hardy server

[Bug 524447] Re: virsh save is very slow

2012-02-19 Thread Jeff Snider
Lucid 10.04.4 amd64 host. 2.6.32-38-server. All packages up to date. Guest: Win 7 64bit 1Gb RAM (all in use in guest) 2 vproc VirtIO disk (virtio-win-0.1-22) VirtIO network 2 IDE cdroms VNC display virsh save:

[Bug 524447] Re: virsh save is very slow

2011-07-28 Thread Jeff Snider
Michael: Yes, that is the correct patch. -- 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/524447 Title: virsh save is very slow To manage notifications about this bug go to:

[Bug 524447] Re: virsh save is very slow

2011-07-28 Thread Jeff Snider
Michael: Yes, that is the correct patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/524447 Title: virsh save is very slow To manage notifications about this bug go to:

[Bug 524447] Re: virsh save is very slow

2011-07-27 Thread Jeff Snider
The page you referenced doesn't include anything that I can find about the ticket priority level. It states that Stable release updates will, in general, only be issued in order to fix high-impact bugs and provides several examples. Among them is Bugs which do not fit under above categories,

[Bug 524447] Re: virsh save is very slow

2011-07-27 Thread Jeff Snider
The page you referenced doesn't include anything that I can find about the ticket priority level. It states that Stable release updates will, in general, only be issued in order to fix high-impact bugs and provides several examples. Among them is Bugs which do not fit under above categories,

[Bug 524447] Re: virsh save is very slow

2011-07-22 Thread Jeff Snider
Tested 0.12.3+noroms-0ubuntu9.14 on Lucid amd64 with all available updates. Save speed is now approx 3 seconds for a 256Mb guest. Tested virsh with start, stop, save, restore, suspend, resume, shutdown, destroy. Tested guest with smp, virtio disk, virtio net, vnc display. Everything worked as

[Bug 524447] Re: virsh save is very slow

2011-07-22 Thread Jeff Snider
Tested 0.12.3+noroms-0ubuntu9.14 on Lucid amd64 with all available updates. Save speed is now approx 3 seconds for a 256Mb guest. Tested virsh with start, stop, save, restore, suspend, resume, shutdown, destroy. Tested guest with smp, virtio disk, virtio net, vnc display. Everything worked as

[Bug 524447] Re: virsh save is very slow

2011-07-21 Thread Jeff Snider
I'd like to help get this fixed, particularly in Lucid. What can I do? Does #21 and #22 still need testing? -- 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/524447 Title: virsh

[Bug 524447] Re: virsh save is very slow

2011-07-21 Thread Jeff Snider
Ok, great! Thanks for the quick response. I did just now get finished testing the packages you attached in #21 using my lucid box. Saves of a 256Mb guest went from ~50 seconds to ~3. So it does seem to fix the issue. I can set up a Maverick box if you need it tested there as well. I checked

[Bug 524447] Re: virsh save is very slow

2011-07-21 Thread Jeff Snider
I'd like to help get this fixed, particularly in Lucid. What can I do? Does #21 and #22 still need testing? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/524447 Title: virsh save is very slow To

[Bug 524447] Re: virsh save is very slow

2011-07-21 Thread Jeff Snider
Ok, great! Thanks for the quick response. I did just now get finished testing the packages you attached in #21 using my lucid box. Saves of a 256Mb guest went from ~50 seconds to ~3. So it does seem to fix the issue. I can set up a Maverick box if you need it tested there as well. I checked