Re: [Qemu-devel] [PATCH 0/3] non-migratable devices

2011-07-08 Thread Gerd Hoffmann
On 07/08/11 14:59, Paolo Bonzini wrote: On 07/08/2011 02:47 PM, Gerd Hoffmann wrote: One possibility is to add device name remapping to machine types, like "ide is actually ide-0.14 when using pc-0.14" and put a different VMState in ide-0.14. That isn't very different from subsections. Probl

Re: [Qemu-devel] [PATCH 0/3] non-migratable devices

2011-07-08 Thread Paolo Bonzini
On 07/08/2011 02:47 PM, Gerd Hoffmann wrote: One possibility is to add device name remapping to machine types, like "ide is actually ide-0.14 when using pc-0.14" and put a different VMState in ide-0.14. That isn't very different from subsections. Problem is that the old qemu version doesn't h

Re: [Qemu-devel] [PATCH 0/3] non-migratable devices

2011-07-08 Thread Gerd Hoffmann
Hi, If desired, in the future we can revert this behavior for pc-0.14 and earlier machines. And I'm still looking for a sane way to handle *this*. One possibility is to add device name remapping to machine types, like "ide is actually ide-0.14 when using pc-0.14" and put a different VMStat

Re: [Qemu-devel] [PATCH 0/3] non-migratable devices

2011-07-08 Thread Gerd Hoffmann
Hi, scsi-cd is new in 0.15, older versions have scsi-disk only. That's why we should take the occasion to add the empty vmstate at least to it. Ok, good opportunity in that specific case. For other devices, it's better to make the breakage in a single version. It also allows to make 0.15 t

Re: [Qemu-devel] [PATCH 0/3] non-migratable devices

2011-07-08 Thread Paolo Bonzini
On 07/08/2011 01:47 PM, Gerd Hoffmann wrote: scsi-cd is new in 0.15, older versions have scsi-disk only. That's why we should take the occasion to add the empty vmstate at least to it. Ok, good opportunity in that specific case. For other devices, it's better to make the breakage in a sing

Re: [Qemu-devel] [PATCH 0/3] non-migratable devices

2011-07-08 Thread Markus Armbruster
Gerd Hoffmann writes: > Hi, > >> For scsi-cd and other empty-but-generally-migratable devices we should >> probably add an empty vmstate, so that any further addition can be done >> as subsections. > > That will break migration to older versions which don't know about the > new sections, even i

Re: [Qemu-devel] [PATCH 0/3] non-migratable devices

2011-07-08 Thread Paolo Bonzini
On 07/08/2011 11:59 AM, Gerd Hoffmann wrote: For scsi-cd and other empty-but-generally-migratable devices we should probably add an empty vmstate, so that any further addition can be done as subsections. That will break migration to older versions which don't know about the new sections, eve

Re: [Qemu-devel] [PATCH 0/3] non-migratable devices

2011-07-08 Thread Paolo Bonzini
On 07/08/2011 10:53 AM, Gerd Hoffmann wrote: Hi, This patch series adds an easy way to tag devices as non-migratable puts it into use for ahci and ehci. Gerd Hoffmann (3): vmstate: add no_migrate flag to VMStateDescription ahci doesn't support migration ehci doesn't support migratio

Re: [Qemu-devel] [PATCH 0/3] non-migratable devices

2011-07-08 Thread Gerd Hoffmann
Hi, For scsi-cd and other empty-but-generally-migratable devices we should probably add an empty vmstate, so that any further addition can be done as subsections. That will break migration to older versions which don't know about the new sections, even if they are empty ... cheers, Gerd

[Qemu-devel] [PATCH 0/3] non-migratable devices

2011-07-08 Thread Gerd Hoffmann
Hi, This patch series adds an easy way to tag devices as non-migratable puts it into use for ahci and ehci. Gerd Hoffmann (3): vmstate: add no_migrate flag to VMStateDescription ahci doesn't support migration ehci doesn't support migration hw/hw.h |1 + hw/ide/ich.c |6 ++