Hi,
i now was able to catch the error.
It is:
Length mismatch: :00:12.0/virtio-net-pci.rom: 4 in != 1
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
Il 14/05/2014 09:17, Stefan Priebe - Profihost AG ha scritto:
i now was able to catch the error.
It is:
Length mismatch: :00:12.0/virtio-net-pci.rom: 4 in != 1
qemu: warning: error while loading state for instance 0x0 of device 'ram'
load of migration failed
This is a bug of your
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: :00:12.0/virtio-net-pci.rom: 4 in != 1
qemu: warning: error while loading state for instance 0x0 of device 'ram'
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
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
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
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
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
* Stefan Priebe - Profihost AG (s.pri...@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
Am 09.05.2014 um 15:41 schrieb Dr. David Alan Gilbert dgilb...@redhat.com:
* Stefan Priebe - Profihost AG (s.pri...@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
* Stefan Priebe - Profihost AG (s.pri...@profihost.ag) wrote:
Am 09.05.2014 um 15:41 schrieb Dr. David Alan Gilbert
dgilb...@redhat.com:
* Stefan Priebe - Profihost AG (s.pri...@profihost.ag) wrote:
Hello list,
i was trying to migrate older Qemu (1.5 and 1.7.2) to a machine
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
Am 09.05.2014 18:29, schrieb Dr. David Alan Gilbert:
* Stefan Priebe - Profihost AG (s.pri...@profihost.ag) wrote:
Am 09.05.2014 um 15:41 schrieb Dr. David Alan Gilbert dgilb...@redhat.com:
* Stefan Priebe - Profihost AG (s.pri...@profihost.ag) wrote:
Hello list,
i was trying to migrate
)
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
14 matches
Mail list logo
