[Qemu-devel] Migration from older Qemu to Qemu 2.0.0 does not work

[Qemu-devel] Migration from older Qemu to Qemu 2.0.0 does not work

[Stefan Priebe - Profihost AG]

Hello list,

i was trying to migrate older Qemu (1.5 and 1.7.2) to a machine running
Qemu 2.0.

I started the target machine with:

-machine type=pc-i440fx-1.5 / -machine type=pc-i440fx-1.7

But the migration simply fails. Migrating Qemu 2.0 to Qemu 2.0 succeeds.

I see no output at the monitor of Qemu 2.0.

# migrate -d tcp:a.b.c.d:6000

# info migrate
capabilities: xbzrle: off x-rdma-pin-all: off auto-converge: on
zero-blocks: off
Migration status: failed
total time: 0 milliseconds

The target machine is still running at this point with no output.

Stefan

Re: [Qemu-devel] Migration from older Qemu to Qemu 2.0.0 does not work

[Dr. David Alan Gilbert]

* Stefan Priebe - Profihost AG (s.priebe@profihost.ag) wrote:
> Hello list,
> 
> i was trying to migrate older Qemu (1.5 and 1.7.2) to a machine running
> Qemu 2.0.
> 
> I started the target machine with:
> 
> -machine type=pc-i440fx-1.5 / -machine type=pc-i440fx-1.7

I'd expect you to have to run with the same machine type on both sides.
I ran some simple virt-test migrate tests (just the basic one) and got
v1.5.3->v1.6.2
v1.5.3->v1.7.1
v1.5.3->v2.0.0-rc1
   working for most machine types, pc-i440fx-1.5 passed with all of those.
Note that's only the simplest test.

Dave
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

Re: [Qemu-devel] Migration from older Qemu to Qemu 2.0.0 does not work

[Stefan Priebe - Profihost AG]

> Am 09.05.2014 um 15:41 schrieb "Dr. David Alan Gilbert" <dgilbert@redhat.com>:
> 
> * Stefan Priebe - Profihost AG (s.priebe@profihost.ag) wrote:
>> Hello list,
>> 
>> i was trying to migrate older Qemu (1.5 and 1.7.2) to a machine running
>> Qemu 2.0.
>> 
>> I started the target machine with:
>> 
>> -machine type=pc-i440fx-1.5 / -machine type=pc-i440fx-1.7
> 
> I'd expect you to have to run with the same machine type on both sides.
> I ran some simple virt-test migrate tests (just the basic one) and got
> v1.5.3->v1.6.2
> v1.5.3->v1.7.1
> v1.5.3->v2.0.0-rc1
>   working for most machine types, pc-i440fx-1.5 passed with all of those.
> Note that's only the simplest test.

My test involved USB Controller virtio Network cards and rbd virtio-scsi drives.

Can you give me your simple start line so I could test if this works for me while adding some more arguments.

Thanks!

Stefan

> 
> Dave
> --
> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

Re: [Qemu-devel] Migration from older Qemu to Qemu 2.0.0 does not work

[Dr. David Alan Gilbert]

* Stefan Priebe - Profihost AG (s.priebe@profihost.ag) wrote:
> 
> > Am 09.05.2014 um 15:41 schrieb "Dr. David Alan Gilbert" <dgilbert@redhat.com>:
> > 
> > * Stefan Priebe - Profihost AG (s.priebe@profihost.ag) wrote:
> >> Hello list,
> >> 
> >> i was trying to migrate older Qemu (1.5 and 1.7.2) to a machine running
> >> Qemu 2.0.
> >> 
> >> I started the target machine with:
> >> 
> >> -machine type=pc-i440fx-1.5 / -machine type=pc-i440fx-1.7
> > 
> > I'd expect you to have to run with the same machine type on both sides.
> > I ran some simple virt-test migrate tests (just the basic one) and got
> > v1.5.3->v1.6.2
> > v1.5.3->v1.7.1
> > v1.5.3->v2.0.0-rc1
> >   working for most machine types, pc-i440fx-1.5 passed with all of those.
> > Note that's only the simplest test.
> 
> My test involved USB Controller virtio Network cards and rbd virtio-scsi drives.

That probably makes things more interesting :-) I'd start with the simplest
config you can find and add each one of those until it breaks.

> Can you give me your simple start line so I could test if this works for me while adding some more arguments.

I've got a slightly hacked up libvirt, but I'm doing

  ./run -t qemu --machine-type=$MACTYPE -g Linux.JeOS.19.x86_64.i440fx --qemu-bin=$SRC --qemu-dst-bin=$DST --qemu_sandbox=off --tests migrate.default.tcp --disk-bus=ide

and looking at the logs we have:

/opt/qemu/v1.5.3/bin/qemu-system-x86_64 \
    -S  \
    -name 'virt-tests-vm1'  \
    -sandbox off  \
    -M pc-i440fx-1.5  \
    -nodefaults  \
    -vga std  \
    -chardev socket,id=hmp_id_hmp1,path=/tmp/monitor-hmp1-20140415-104517-rAfzfDef,server,nowait \
    -mon chardev=hmp_id_hmp1,mode=readline  \
    -chardev socket,id=serial_id_serial0,path=/tmp/serial-serial0-20140415-104517-rAfzfDef,server,nowait \
    -device isa-serial,chardev=serial_id_serial0  \
    -chardev socket,id=seabioslog_id_20140415-104517-rAfzfDef,path=/tmp/seabios-20140415-104517-rAfzfDef,server,nowait \
    -device isa-debugcon,chardev=seabioslog_id_20140415-104517-rAfzfDef,iobase=0x402 \
    -device ich9-usb-uhci1,id=usb1,bus=pci.0,addr=03 \
    -drive id=drive_image1,if=none,file=/home/dgilbert/virt-test/shared/data/images/jeos-19-64.qcow2 \
    -device virtio-blk-pci,id=image1,drive=drive_image1,bootindex=0,bus=pci.0,addr=04 \
    -device virtio-net-pci,mac=9a:18:19:1a:1b:1c,id=idz0uWFP,vectors=4,netdev=idMwmdMc,bus=pci.0,addr=05  \
    -netdev user,id=idMwmdMc,hostfwd=tcp::5000-:22  \
    -m 1024  \
    -smp 2,maxcpus=2,cores=1,threads=1,sockets=2  \
    -cpu 'SandyBridge' \
    -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1  \
    -vnc :1  \
    -rtc base=utc,clock=host,driftfix=none  \
    -boot order=cdn,once=c,menu=off \
    -enable-kvm

Dave

> Thanks!
> 
> Stefan
> 
> > 
> > Dave
> > --
> > Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

Re: [Qemu-devel] Migration from older Qemu to Qemu 2.0.0 does not work

[Stefan Priebe]

Am 09.05.2014 18:29, schrieb Dr. David Alan Gilbert:
> * Stefan Priebe - Profihost AG (s.priebe@profihost.ag) wrote:
>>
>>> Am 09.05.2014 um 15:41 schrieb "Dr. David Alan Gilbert" <dgilbert@redhat.com>:
>>>
>>> * Stefan Priebe - Profihost AG (s.priebe@profihost.ag) wrote:
>>>> Hello list,
>>>>
>>>> i was trying to migrate older Qemu (1.5 and 1.7.2) to a machine running
>>>> Qemu 2.0.
>>>>
>>>> I started the target machine with:
>>>>
>>>> -machine type=pc-i440fx-1.5 / -machine type=pc-i440fx-1.7
>>>
>>> I'd expect you to have to run with the same machine type on both sides.
>>> I ran some simple virt-test migrate tests (just the basic one) and got
>>> v1.5.3->v1.6.2
>>> v1.5.3->v1.7.1
>>> v1.5.3->v2.0.0-rc1
>>>    working for most machine types, pc-i440fx-1.5 passed with all of those.
>>> Note that's only the simplest test.
>>
>> My test involved USB Controller virtio Network cards and rbd virtio-scsi drives.
>
> That probably makes things more interesting :-) I'd start with the simplest
> config you can find and add each one of those until it breaks.
>
>> Can you give me your simple start line so I could test if this works for me while adding some more arguments.
>
> I've got a slightly hacked up libvirt, but I'm doing
>
>    ./run -t qemu --machine-type=$MACTYPE -g Linux.JeOS.19.x86_64.i440fx --qemu-bin=$SRC --qemu-dst-bin=$DST --qemu_sandbox=off --tests migrate.default.tcp --disk-bus=ide
>
> and looking at the logs we have:
>
> /opt/qemu/v1.5.3/bin/qemu-system-x86_64 \
>      -S  \
>      -name 'virt-tests-vm1'  \
>      -sandbox off  \
>      -M pc-i440fx-1.5  \
>      -nodefaults  \
>      -vga std  \
>      -chardev socket,id=hmp_id_hmp1,path=/tmp/monitor-hmp1-20140415-104517-rAfzfDef,server,nowait \
>      -mon chardev=hmp_id_hmp1,mode=readline  \
>      -chardev socket,id=serial_id_serial0,path=/tmp/serial-serial0-20140415-104517-rAfzfDef,server,nowait \
>      -device isa-serial,chardev=serial_id_serial0  \
>      -chardev socket,id=seabioslog_id_20140415-104517-rAfzfDef,path=/tmp/seabios-20140415-104517-rAfzfDef,server,nowait \
>      -device isa-debugcon,chardev=seabioslog_id_20140415-104517-rAfzfDef,iobase=0x402 \
>      -device ich9-usb-uhci1,id=usb1,bus=pci.0,addr=03 \
>      -drive id=drive_image1,if=none,file=/home/dgilbert/virt-test/shared/data/images/jeos-19-64.qcow2 \
>      -device virtio-blk-pci,id=image1,drive=drive_image1,bootindex=0,bus=pci.0,addr=04 \
>      -device virtio-net-pci,mac=9a:18:19:1a:1b:1c,id=idz0uWFP,vectors=4,netdev=idMwmdMc,bus=pci.0,addr=05  \
>      -netdev user,id=idMwmdMc,hostfwd=tcp::5000-:22  \
>      -m 1024  \
>      -smp 2,maxcpus=2,cores=1,threads=1,sockets=2  \
>      -cpu 'SandyBridge' \
>      -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1  \
>      -vnc :1  \
>      -rtc base=utc,clock=host,driftfix=none  \
>      -boot order=cdn,once=c,menu=off \
>      -enable-kvm
>
> Dave

OK biggest bummer it works fine with all freshly started VMs. No idea why.

So i'll try with paolos idea migrating old VMs.

>
>> Thanks!
>>
>> Stefan
>>
>>>
>>> Dave
>>> --
>>> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
> --
> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
>

Re: [Qemu-devel] Migration from older Qemu to Qemu 2.0.0 does not work

[Paolo Bonzini]

Il 09/05/2014 15:13, Stefan Priebe - Profihost AG ha scritto:
>
> I see no output at the monitor of Qemu 2.0.
>
> # migrate -d tcp:a.b.c.d:6000
>
> # info migrate
> capabilities: xbzrle: off x-rdma-pin-all: off auto-converge: on
> zero-blocks: off
> Migration status: failed
> total time: 0 milliseconds
>
> The target machine is still running at this point with no output.

Anything on its stdout?

Another test you could do, in addition to changing the devices, is this:

1) try with commit 6141f3bd6904df7cf9519c6444a14a608b9874c4 on the 
destination (the next one caused a migration problem that was fixed 
later).  If it passes, go to step 1a.  If it fails, go to step 2.

1a) try with commit c01a71c1a56fa27f43449ff59e5d03b2483658a2.  If it 
passes, go to step 1b.  If it fails, report it here.

1b) bisect between v2.0.0 (known-bad) and 
c01a71c1a56fa27f43449ff59e5d03b2483658a2 (known-good) to find the 
culprit.  Report results.

2) change the source to v1.7.0 and bisect between v1.7.0 and 
6141f3bd6904df7cf9519c6444a14a608b9874c4.  Report results.

Thanks!

Paolo

Re: [Qemu-devel] Migration from older Qemu to Qemu 2.0.0 does not work

[Stefan Priebe]

)

Am 09.05.2014 19:05, schrieb Paolo Bonzini:
> Il 09/05/2014 15:13, Stefan Priebe - Profihost AG ha scritto:
>>
>> I see no output at the monitor of Qemu 2.0.
>>
>> # migrate -d tcp:a.b.c.d:6000
>>
>> # info migrate
>> capabilities: xbzrle: off x-rdma-pin-all: off auto-converge: on
>> zero-blocks: off
>> Migration status: failed
>> total time: 0 milliseconds
>>
>> The target machine is still running at this point with no output.
>
> Anything on its stdout?

Sadly no.

But far more complex than i thought. I'm seeing this problem only on 
machines originally started under qemu 1.5 ten migrated to qemu 1.7 with 
machine type=pc440fc-1.5 . Only those do not work. But they also do not 
work migrating them to qemu 1.7.1.

So let's ignore the whole fact and thanks for your bisect ideas. I will 
just shut them down all and start them with a fresh qemu 2.0.

> Another test you could do, in addition to changing the devices, is this:
>
> 1) try with commit 6141f3bd6904df7cf9519c6444a14a608b9874c4 on the
> destination (the next one caused a migration problem that was fixed
> later).  If it passes, go to step 1a.  If it fails, go to step 2.
>
> 1a) try with commit c01a71c1a56fa27f43449ff59e5d03b2483658a2.  If it
> passes, go to step 1b.  If it fails, report it here.
>
> 1b) bisect between v2.0.0 (known-bad) and
> c01a71c1a56fa27f43449ff59e5d03b2483658a2 (known-good) to find the
> culprit.  Report results.
>
> 2) change the source to v1.7.0 and bisect between v1.7.0 and
> 6141f3bd6904df7cf9519c6444a14a608b9874c4.  Report results.
>
> Thanks!
>
> Paolo

Re: [Qemu-devel] Migration from older Qemu to Qemu 2.0.0 does not work

[Stefan Priebe - Profihost AG]

Hi,

i now was able to catch the error.

It is:
Length mismatch: 0000:00:12.0/virtio-net-pci.rom: 40000 in != 10000
qemu: warning: error while loading state for instance 0x0 of device 'ram'
load of migration failed

Stefan

Am 09.05.2014 19:05, schrieb Paolo Bonzini:
> Il 09/05/2014 15:13, Stefan Priebe - Profihost AG ha scritto:
>>
>> I see no output at the monitor of Qemu 2.0.
>>
>> # migrate -d tcp:a.b.c.d:6000
>>
>> # info migrate
>> capabilities: xbzrle: off x-rdma-pin-all: off auto-converge: on
>> zero-blocks: off
>> Migration status: failed
>> total time: 0 milliseconds
>>
>> The target machine is still running at this point with no output.
> 
> Anything on its stdout?
> 
> Another test you could do, in addition to changing the devices, is this:
> 
> 1) try with commit 6141f3bd6904df7cf9519c6444a14a608b9874c4 on the
> destination (the next one caused a migration problem that was fixed
> later).  If it passes, go to step 1a.  If it fails, go to step 2.
> 
> 1a) try with commit c01a71c1a56fa27f43449ff59e5d03b2483658a2.  If it
> passes, go to step 1b.  If it fails, report it here.
> 
> 1b) bisect between v2.0.0 (known-bad) and
> c01a71c1a56fa27f43449ff59e5d03b2483658a2 (known-good) to find the
> culprit.  Report results.
> 
> 2) change the source to v1.7.0 and bisect between v1.7.0 and
> 6141f3bd6904df7cf9519c6444a14a608b9874c4.  Report results.
> 
> Thanks!
> 
> Paolo

Re: [Qemu-devel] Migration from older Qemu to Qemu 2.0.0 does not work

[Paolo Bonzini]

Il 14/05/2014 09:17, Stefan Priebe - Profihost AG ha scritto:
> i now was able to catch the error.
>
> It is:
> Length mismatch: 0000:00:12.0/virtio-net-pci.rom: 40000 in != 10000
> qemu: warning: error while loading state for instance 0x0 of device 'ram'
> load of migration failed

This is a bug of your distribution.  The file sizes for ROMs should 
never change.  In particular, if you round the sizes up to the next 
power of 2 you should always have:

128k for bios.bin
256k for bios-256k.bin
64k for pxe-*.rom
256k for efi-*.rom
64k for vgabios-*

Unfortunately, most distribution get pxe-*.rom sizes wrong, because at 
some point iPXE grew more features and didn't fit in 64k anymore with 
the default configuration.  I know at least Fedora does.

The solution is to copy the binaries from the QEMU git repository 
(directory pc-bios/) to /usr/share/qemu.

Paolo

Re: [Qemu-devel] Migration from older Qemu to Qemu 2.0.0 does not work

[Stefan Priebe - Profihost AG]

Am 14.05.2014 10:11, schrieb Paolo Bonzini:
> Il 14/05/2014 09:17, Stefan Priebe - Profihost AG ha scritto:
>> i now was able to catch the error.
>>
>> It is:
>> Length mismatch: 0000:00:12.0/virtio-net-pci.rom: 40000 in != 10000
>> qemu: warning: error while loading state for instance 0x0 of device 'ram'
>> load of migration failed
> 
> This is a bug of your distribution.  The file sizes for ROMs should
> never change.  In particular, if you round the sizes up to the next
> power of 2 you should always have:
> 
> 128k for bios.bin
> 256k for bios-256k.bin
> 64k for pxe-*.rom
> 256k for efi-*.rom
> 64k for vgabios-*
> 
> Unfortunately, most distribution get pxe-*.rom sizes wrong, because at
> some point iPXE grew more features and didn't fit in 64k anymore with
> the default configuration.  I know at least Fedora does.
> 
> The solution is to copy the binaries from the QEMU git repository
> (directory pc-bios/) to /usr/share/qemu.

Hi,

i compile qemu on my own.

I have the rom files under /usr/share/kvm and they look like this:
ls -la /usr/share/kvm/*.rom
-rw-r--r-- 1 root root 173568 May 14 09:39 /usr/share/kvm/efi-e1000.rom
-rw-r--r-- 1 root root 174592 May 14 09:39 /usr/share/kvm/efi-eepro100.rom
-rw-r--r-- 1 root root 173056 May 14 09:39 /usr/share/kvm/efi-ne2k_pci.rom
-rw-r--r-- 1 root root 173056 May 14 09:39 /usr/share/kvm/efi-pcnet.rom
-rw-r--r-- 1 root root 176640 May 14 09:39 /usr/share/kvm/efi-rtl8139.rom
-rw-r--r-- 1 root root 171008 May 14 09:39 /usr/share/kvm/efi-virtio.rom
-rw-r--r-- 1 root root  67072 May 14 09:39 /usr/share/kvm/pxe-e1000.rom
-rw-r--r-- 1 root root  61440 May 14 09:39 /usr/share/kvm/pxe-eepro100.rom
-rw-r--r-- 1 root root  61440 May 14 09:39 /usr/share/kvm/pxe-ne2k_pci.rom
-rw-r--r-- 1 root root  61440 May 14 09:39 /usr/share/kvm/pxe-pcnet.rom
-rw-r--r-- 1 root root  61440 May 14 09:39 /usr/share/kvm/pxe-rtl8139.rom
-rw-r--r-- 1 root root  60416 May 14 09:39 /usr/share/kvm/pxe-virtio.rom

currently i don't know what's wrong.

Stefan

Re: [Qemu-devel] Migration from older Qemu to Qemu 2.0.0 does not work

[Paolo Bonzini]

Il 14/05/2014 10:29, Stefan Priebe - Profihost AG ha scritto:
> Hi,
>
> i compile qemu on my own.
>
> I have the rom files under /usr/share/kvm and they look like this:
> ls -la /usr/share/kvm/*.rom
> -rw-r--r-- 1 root root 173568 May 14 09:39 /usr/share/kvm/efi-e1000.rom
> -rw-r--r-- 1 root root 174592 May 14 09:39 /usr/share/kvm/efi-eepro100.rom
> -rw-r--r-- 1 root root 173056 May 14 09:39 /usr/share/kvm/efi-ne2k_pci.rom
> -rw-r--r-- 1 root root 173056 May 14 09:39 /usr/share/kvm/efi-pcnet.rom
> -rw-r--r-- 1 root root 176640 May 14 09:39 /usr/share/kvm/efi-rtl8139.rom
> -rw-r--r-- 1 root root 171008 May 14 09:39 /usr/share/kvm/efi-virtio.rom
> -rw-r--r-- 1 root root  67072 May 14 09:39 /usr/share/kvm/pxe-e1000.rom
> -rw-r--r-- 1 root root  61440 May 14 09:39 /usr/share/kvm/pxe-eepro100.rom
> -rw-r--r-- 1 root root  61440 May 14 09:39 /usr/share/kvm/pxe-ne2k_pci.rom
> -rw-r--r-- 1 root root  61440 May 14 09:39 /usr/share/kvm/pxe-pcnet.rom
> -rw-r--r-- 1 root root  61440 May 14 09:39 /usr/share/kvm/pxe-rtl8139.rom
> -rw-r--r-- 1 root root  60416 May 14 09:39 /usr/share/kvm/pxe-virtio.rom
>
> currently i don't know what's wrong.

What about the source machine?

Paolo

Re: [Qemu-devel] Migration from older Qemu to Qemu 2.0.0 does not work

[Stefan Priebe - Profihost AG]

Am 14.05.2014 10:36, schrieb Paolo Bonzini:
> Il 14/05/2014 10:29, Stefan Priebe - Profihost AG ha scritto:
>> Hi,
>>
>> i compile qemu on my own.
>>
>> I have the rom files under /usr/share/kvm and they look like this:
>> ls -la /usr/share/kvm/*.rom
>> -rw-r--r-- 1 root root 173568 May 14 09:39 /usr/share/kvm/efi-e1000.rom
>> -rw-r--r-- 1 root root 174592 May 14 09:39
>> /usr/share/kvm/efi-eepro100.rom
>> -rw-r--r-- 1 root root 173056 May 14 09:39
>> /usr/share/kvm/efi-ne2k_pci.rom
>> -rw-r--r-- 1 root root 173056 May 14 09:39 /usr/share/kvm/efi-pcnet.rom
>> -rw-r--r-- 1 root root 176640 May 14 09:39 /usr/share/kvm/efi-rtl8139.rom
>> -rw-r--r-- 1 root root 171008 May 14 09:39 /usr/share/kvm/efi-virtio.rom
>> -rw-r--r-- 1 root root  67072 May 14 09:39 /usr/share/kvm/pxe-e1000.rom
>> -rw-r--r-- 1 root root  61440 May 14 09:39
>> /usr/share/kvm/pxe-eepro100.rom
>> -rw-r--r-- 1 root root  61440 May 14 09:39
>> /usr/share/kvm/pxe-ne2k_pci.rom
>> -rw-r--r-- 1 root root  61440 May 14 09:39 /usr/share/kvm/pxe-pcnet.rom
>> -rw-r--r-- 1 root root  61440 May 14 09:39 /usr/share/kvm/pxe-rtl8139.rom
>> -rw-r--r-- 1 root root  60416 May 14 09:39 /usr/share/kvm/pxe-virtio.rom
>>
>> currently i don't know what's wrong.
> 
> What about the source machine?

Currently it has the same as i already updated the package there too.

So you mean i had done a mistake compiling the old package - so it had
wrong sizes?

Greets.
Stefan

Re: [Qemu-devel] Migration from older Qemu to Qemu 2.0.0 does not work

[Paolo Bonzini]

Il 14/05/2014 10:38, Stefan Priebe - Profihost AG ha scritto:
> Currently it has the same as i already updated the package there too.
>
> So you mean i had done a mistake compiling the old package - so it had
> wrong sizes?

Yes, probably.

Can you do an "info mtree" for a machine that's running on the source?

Paolo

Re: [Qemu-devel] Migration from older Qemu to Qemu 2.0.0 does not work

[Stefan Priebe - Profihost AG]

Am 14.05.2014 11:00, schrieb Paolo Bonzini:
> Il 14/05/2014 10:38, Stefan Priebe - Profihost AG ha scritto:
>> Currently it has the same as i already updated the package there too.
>>
>> So you mean i had done a mistake compiling the old package - so it had
>> wrong sizes?
> 
> Yes, probably.
> 
> Can you do an "info mtree" for a machine that's running on the source?
> 
> Paolo

here it is:
# info mtree
memory
0000000000000000-7ffffffffffffffe (prio 0, RW): system
  0000000000000000-00000000dfffffff (prio 0, RW): alias ram-below-4g
@pc.ram 0000000000000000-00000000dfffffff
  00000000000a0000-00000000000bffff (prio 1, RW): alias smram-region
@pci 00000000000a0000-00000000000bffff
  00000000000c0000-00000000000c3fff (prio 1, R-): alias pam-rom @pc.ram
00000000000c0000-00000000000c3fff
  00000000000c4000-00000000000c7fff (prio 1, R-): alias pam-rom @pc.ram
00000000000c4000-00000000000c7fff
  00000000000c8000-00000000000cbfff (prio 1, R-): alias pam-rom @pc.ram
00000000000c8000-00000000000cbfff
  00000000000ca000-00000000000ccfff (prio 1000, RW): alias kvmvapic-rom
@pc.ram 00000000000ca000-00000000000ccfff
  00000000000cc000-00000000000cffff (prio 1, R-): alias pam-rom @pc.ram
00000000000cc000-00000000000cffff
  00000000000d0000-00000000000d3fff (prio 1, RW): alias pam-ram @pc.ram
00000000000d0000-00000000000d3fff
  00000000000d4000-00000000000d7fff (prio 1, RW): alias pam-ram @pc.ram
00000000000d4000-00000000000d7fff
  00000000000d8000-00000000000dbfff (prio 1, RW): alias pam-ram @pc.ram
00000000000d8000-00000000000dbfff
  00000000000dc000-00000000000dffff (prio 1, RW): alias pam-ram @pc.ram
00000000000dc000-00000000000dffff
  00000000000e0000-00000000000e3fff (prio 1, RW): alias pam-ram @pc.ram
00000000000e0000-00000000000e3fff
  00000000000e4000-00000000000e7fff (prio 1, RW): alias pam-ram @pc.ram
00000000000e4000-00000000000e7fff
  00000000000e8000-00000000000ebfff (prio 1, RW): alias pam-ram @pc.ram
00000000000e8000-00000000000ebfff
  00000000000ec000-00000000000effff (prio 1, RW): alias pam-ram @pc.ram
00000000000ec000-00000000000effff
  00000000000f0000-00000000000fffff (prio 1, R-): alias pam-rom @pc.ram
00000000000f0000-00000000000fffff
  00000000e0000000-00000000ffffffff (prio 0, RW): alias pci-hole @pci
00000000e0000000-00000000ffffffff
  00000000fec00000-00000000fec00fff (prio 0, RW): kvm-ioapic
  00000000fed00000-00000000fed003ff (prio 0, RW): hpet
  00000000fee00000-00000000feefffff (prio 4096, RW): icc-apic-container
    00000000fee00000-00000000feefffff (prio 0, RW): kvm-apic-msi
  0000000100000000-000000021fffffff (prio 0, RW): alias ram-above-4g
@pc.ram 00000000e0000000-00000001ffffffff
  0000000220000000-400000021fffffff (prio 0, RW): alias pci-hole64 @pci
0000000220000000-400000021fffffff
I/O
0000000000000000-000000000000ffff (prio 0, RW): io
  0000000000000000-0000000000000007 (prio 0, RW): dma-chan
  0000000000000008-000000000000000f (prio 0, RW): dma-cont
  0000000000000020-0000000000000021 (prio 0, RW): kvm-pic
  0000000000000040-0000000000000043 (prio 0, RW): kvm-pit
  0000000000000060-0000000000000060 (prio 0, RW): i8042-data
  0000000000000061-0000000000000061 (prio 0, RW): elcr
  0000000000000064-0000000000000064 (prio 0, RW): i8042-cmd
  0000000000000070-0000000000000071 (prio 0, RW): rtc
  000000000000007e-000000000000007f (prio 0, RW): kvmvapic
  0000000000000080-0000000000000080 (prio 0, RW): ioport80
  0000000000000081-0000000000000083 (prio 0, RW): alias dma-page
@dma-page 0000000000000081-0000000000000083
  0000000000000087-0000000000000087 (prio 0, RW): alias dma-page
@dma-page 0000000000000087-0000000000000087
  0000000000000089-000000000000008b (prio 0, RW): alias dma-page
@dma-page 0000000000000089-000000000000008b
  000000000000008f-000000000000008f (prio 0, RW): alias dma-page
@dma-page 000000000000008f-000000000000008f
  0000000000000092-0000000000000092 (prio 0, RW): port92
  00000000000000a0-00000000000000a1 (prio 0, RW): kvm-pic
  00000000000000b2-00000000000000b3 (prio 0, RW): apm-io
  00000000000000c0-00000000000000cf (prio 0, RW): dma-chan
  00000000000000d0-00000000000000df (prio 0, RW): dma-cont
  00000000000000f0-00000000000000f0 (prio 0, RW): ioportF0
  0000000000000170-0000000000000177 (prio 0, RW): alias ide @ide
0000000000000170-0000000000000177
  00000000000001f0-00000000000001f7 (prio 0, RW): alias ide @ide
00000000000001f0-00000000000001f7
  0000000000000376-0000000000000376 (prio 0, RW): alias ide @ide
0000000000000376-0000000000000376
  00000000000003b0-00000000000003df (prio 0, RW): cirrus-io
  00000000000003f1-00000000000003f5 (prio 0, RW): alias fdc @fdc
00000000000003f1-00000000000003f5
  00000000000003f6-00000000000003f6 (prio 0, RW): alias ide @ide
00000000000003f6-00000000000003f6
  00000000000003f7-00000000000003f7 (prio 0, RW): alias fdc @fdc
00000000000003f7-00000000000003f7
  00000000000004d0-00000000000004d0 (prio 0, RW): kvm-elcr
  00000000000004d1-00000000000004d1 (prio 0, RW): kvm-elcr
  0000000000000505-0000000000000505 (prio 0, RW): pvpanic
  0000000000000510-0000000000000511 (prio 0, RW): fwcfg
  0000000000000cf8-0000000000000cfb (prio 0, RW): pci-conf-idx
  0000000000000cf9-0000000000000cf9 (prio 1, RW): piix3-reset-control
  0000000000000cfc-0000000000000cff (prio 0, RW): pci-conf-data
  0000000000005658-0000000000005658 (prio 0, RW): vmport
  000000000000ae00-000000000000ae0e (prio 0, RW): apci-pci-hotplug
  000000000000af00-000000000000af1f (prio 0, RW): apci-cpu-hotplug
  000000000000afe0-000000000000afe3 (prio 0, RW): apci-gpe0
  000000000000b000-000000000000b03f (prio 0, RW): piix4-pm
    000000000000b000-000000000000b003 (prio 0, RW): acpi-evt
    000000000000b004-000000000000b005 (prio 0, RW): acpi-cnt
    000000000000b008-000000000000b00b (prio 0, RW): acpi-tmr
  000000000000b100-000000000000b13f (prio 0, RW): pm-smbus
  000000000000c000-000000000000c03f (prio 1, RW): virtio-pci
  000000000000c040-000000000000c05f (prio 1, RW): uhci
  000000000000c060-000000000000c07f (prio 1, RW): virtio-pci
  000000000000c080-000000000000c09f (prio 1, RW): virtio-pci
  000000000000c0a0-000000000000c0af (prio 1, RW): piix-bmdma-container
    000000000000c0a0-000000000000c0a3 (prio 0, RW): piix-bmdma
    000000000000c0a4-000000000000c0a7 (prio 0, RW): bmdma
    000000000000c0a8-000000000000c0ab (prio 0, RW): piix-bmdma
    000000000000c0ac-000000000000c0af (prio 0, RW): bmdma
aliases
pc.ram
0000000000000000-00000001ffffffff (prio 0, RW): pc.ram
pci
0000000000000000-7ffffffffffffffe (prio 0, RW): pci
  00000000000a0000-00000000000bffff (prio 1, RW): cirrus-lowmem-container
    00000000000a0000-00000000000bffff (prio 0, RW): cirrus-low-memory
  00000000000c0000-00000000000dffff (prio 1, RW): pc.rom
  00000000000e0000-00000000000fffff (prio 1, R-): alias isa-bios
@pc.bios 0000000000000000-000000000001ffff
  00000000fc000000-00000000fdffffff (prio 1, RW): cirrus-pci-bar0
    00000000fc000000-00000000fc7fffff (prio 1, RW): vga.vram
    00000000fc000000-00000000fc7fffff (prio 0, RW): cirrus-linear-io
    00000000fd000000-00000000fd3fffff (prio 0, RW): cirrus-bitblt-mmio
  00000000febd0000-00000000febd0fff (prio 1, RW): cirrus-mmio
  00000000febd1000-00000000febd1fff (prio 1, RW): virtio-scsi-pci-msix
    00000000febd1000-00000000febd103f (prio 0, RW): msix-table
    00000000febd1800-00000000febd1807 (prio 0, RW): msix-pba
  00000000febd2000-00000000febd2fff (prio 1, RW): virtio-net-pci-msix
    00000000febd2000-00000000febd202f (prio 0, RW): msix-table
    00000000febd2800-00000000febd2807 (prio 0, RW): msix-pba
  00000000fffe0000-00000000ffffffff (prio 0, R-): pc.bios
dma-page
0000000000000000-7ffffffffffffffe (prio 0, RW): dma-page
dma-page
0000000000000000-7ffffffffffffffe (prio 0, RW): dma-page
dma-page
0000000000000000-7ffffffffffffffe (prio 0, RW): dma-page
dma-page
0000000000000000-7ffffffffffffffe (prio 0, RW): dma-page
ide
0000000000000000-7ffffffffffffffe (prio 0, RW): ide
ide
0000000000000000-7ffffffffffffffe (prio 0, RW): ide
ide
0000000000000000-7ffffffffffffffe (prio 0, RW): ide
fdc
0000000000000000-7ffffffffffffffe (prio 0, RW): fdc
ide
0000000000000000-7ffffffffffffffe (prio 0, RW): ide
fdc
0000000000000000-7ffffffffffffffe (prio 0, RW): fdc
pc.bios
00000000fffe0000-00000000ffffffff (prio 0, R-): pc.bios


Stefan

Re: [Qemu-devel] Migration from older Qemu to Qemu 2.0.0 does not work

[Paolo Bonzini]

Il 14/05/2014 11:25, Stefan Priebe - Profihost AG ha scritto:
>>> >> Currently it has the same as i already updated the package there too.
>>> >>
>>> >> So you mean i had done a mistake compiling the old package - so it had
>>> >> wrong sizes?
>> >
>> > Yes, probably.
>> >
>> > Can you do an "info mtree" for a machine that's running on the source?
>> >
>> > Paolo
> here it is:
> # info mtree

Sorry, unfortunately it doesn't help.

Paolo