Re: [Qemu-devel] savevm/loadvm

2013-11-02 Thread Alexey Kardashevskiy
On 11/02/2013 01:16 AM, Max Reitz wrote: > Hi, > > Sorry I'm just now replying to this. I ran into the same issue (and > another one) and it should be fixed by the upstream commits > eedff66f21e542650d895801549ce05ac108278b and > 6e13610aa454beba52944e8df6d93158d68ab911. Those have been merged to

Re: [Qemu-devel] savevm/loadvm

2013-11-01 Thread Max Reitz
Hi, Sorry I'm just now replying to this. I ran into the same issue (and another one) and it should be fixed by the upstream commits eedff66f21e542650d895801549ce05ac108278b and 6e13610aa454beba52944e8df6d93158d68ab911. Those have been merged to master yesterday, so could you re-build qemu from mas

Re: [Qemu-devel] savevm/loadvm

2013-11-01 Thread Alexey Kardashevskiy
On 10/16/2013 05:51 PM, Alexey Kardashevskiy wrote: > On 10/10/2013 02:50 PM, Alexey Kardashevskiy wrote: >> On 10/09/2013 06:47 PM, Paolo Bonzini wrote: >>> Il 09/10/2013 09:15, Alexey Kardashevskiy ha scritto: Sorry for my ignorance (I never ever touched this part of qemu) but how can y

Re: [Qemu-devel] savevm/loadvm

2013-10-15 Thread Alexey Kardashevskiy
On 10/10/2013 02:50 PM, Alexey Kardashevskiy wrote: > On 10/09/2013 06:47 PM, Paolo Bonzini wrote: >> Il 09/10/2013 09:15, Alexey Kardashevskiy ha scritto: >>> Sorry for my ignorance (I never ever touched this part of qemu) but how can >>> you possibly avoid block.c while doing savevm? The qcow2 dr

Re: [Qemu-devel] savevm/loadvm

2013-10-09 Thread Alexey Kardashevskiy
On 10/09/2013 06:47 PM, Paolo Bonzini wrote: > Il 09/10/2013 09:15, Alexey Kardashevskiy ha scritto: >> Sorry for my ignorance (I never ever touched this part of qemu) but how can >> you possibly avoid block.c while doing savevm? The qcow2 driver must not >> use posix read()/write(), right? So no m

Re: [Qemu-devel] savevm/loadvm

2013-10-09 Thread Paolo Bonzini
Il 09/10/2013 09:15, Alexey Kardashevskiy ha scritto: > Sorry for my ignorance (I never ever touched this part of qemu) but how can > you possibly avoid block.c while doing savevm? The qcow2 driver must not > use posix read()/write(), right? So no matter how, all writes end up in > bdrv_co_do_write

Re: [Qemu-devel] savevm/loadvm

2013-10-09 Thread Alexey Kardashevskiy
On 10/08/2013 08:33 PM, Paolo Bonzini wrote: > Il 08/10/2013 11:23, Kevin Wolf ha scritto: I think you need to modify qcow2_save_vmstate to save and restore bs->total_sectors. Can you test that and if so post the patch? >> It's a regression introduced by commit df2a6f29, right? > > Yes,

Re: [Qemu-devel] savevm/loadvm

2013-10-08 Thread Paolo Bonzini
Il 08/10/2013 11:23, Kevin Wolf ha scritto: >> > I think you need to modify qcow2_save_vmstate to save and restore >> > bs->total_sectors. Can you test that and if so post the patch? > It's a regression introduced by commit df2a6f29, right? Yes, that's what introduced the "if". > What you sugges

Re: [Qemu-devel] savevm/loadvm

2013-10-08 Thread Kevin Wolf
Am 08.10.2013 um 11:04 hat Paolo Bonzini geschrieben: > Il 08/10/2013 10:40, Alexey Kardashevskiy ha scritto: > > However qcow2_save_vmstate() sets bs->growable to 1 for a short time > > (commit 178e08a58f40dd5aef2ce774fe0850f5d0e56918 from 2009) and this > > triggers a branch in bdrv_co_do_writev(

Re: [Qemu-devel] savevm/loadvm

2013-10-08 Thread Paolo Bonzini
Il 08/10/2013 10:40, Alexey Kardashevskiy ha scritto: > However qcow2_save_vmstate() sets bs->growable to 1 for a short time > (commit 178e08a58f40dd5aef2ce774fe0850f5d0e56918 from 2009) and this > triggers a branch in bdrv_co_do_writev() which changes bs->total_sectors. > So when QEMU writes snaps

[Qemu-devel] savevm/loadvm

2013-10-08 Thread Alexey Kardashevskiy
Hi! I need the community help with savevm/loadvm. I run QEMU like this: ./qemu-system-ppc64 \ -drive file=virtimg/fc19_16GB.qcow2 \ -nodefaults \ -m "2048" \ -machine "pseries" \ -nographic \ -vga "none" \ -enable-kvm The disk image is an 16GB qcow2 image. Now I start the guest and do