[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [Bug 1723161] Re: Migration failing in qemu-2.10.1 but
From: |
William Tambe |
Subject: |
Re: [Qemu-devel] [Bug 1723161] Re: Migration failing in qemu-2.10.1 but working qemu-2.9.1 and earlier with same options |
Date: |
Thu, 12 Oct 2017 20:53:36 -0000 |
Hi David,
Please let me know if you have preferred name.
I am an AMD employee.
Including my colleagues to this thread ...
The only error on the source side is the migration failure reported on
the source monitor when doing "info migration" .
It was indeed something related to the pflash, because migration will
work when removing the following entries:
-drive if=pflash,format=raw,unit=0,file=OVMF_CODE.fd,readonly
-drive if=pflash,format=raw,unit=1,file=OVMF_VARS.fd
I will take a look at the migration/block.c block_load code as you
suggested.
Sincerely,
William Tambe
On Thu, Oct 12, 2017 at 2:24 PM, Dr. David Alan Gilbert
<address@hidden> wrote:
> Interesting; As a test could you try removing the cdrom entry (I doubt
> that'll help but it's worth a go).
> Also, is it possible for you to try a bisection?
>
> If I was to guess, I'd bet it's something relating to the pflash, but I
> don't know; it's unfortunate the block migration doesn't say what it got
> upset by.
>
> Are there no errors on the source side?
>
> Assuming there are no errors on the source side, I'd have to suggest
> taking a printf to migration/block.c block_load to find out which exit
> it's falling out of in there (at least I think that's what would cause
> that error)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1723161
>
> Title:
> Migration failing in qemu-2.10.1 but working qemu-2.9.1 and earlier
> with same options
>
> Status in QEMU:
> New
>
> Bug description:
>
> Qemu-2.10.1 migration failing with the following error:
> Receiving block device images
> qemu-system-x86_64: error while loading section id 2(block)
> qemu-system-x86_64: load of migration failed: Input/output error
>
> Migration is setup on the destination system of the migration using:
> -incoming tcp:0:4444
>
> Migration is initiated from the source using the following commands in its
> qemu monitor:
> migrate -b "tcp:localhost:4444"
>
> The command-line used in both the source and destination is:
> qemu-system-x86_64 \
> -nodefaults \
> -pidfile vm0.pid \
> -enable-kvm \
> -machine q35 \
> -cpu host -smp 2 \
> -m 4096M \
> -drive if=pflash,format=raw,unit=0,file=OVMF_CODE.fd,readonly \
> -drive if=pflash,format=raw,unit=1,file=OVMF_VARS.fd \
> -drive file=${HDRIVE},format=qcow2 \
> -drive media=cdrom \
> -usb -device usb-tablet \
> -vga std -vnc :0 \
> -net nic,macaddr=${TAPMACADDR} -net
> user,net=192.168.2.0/24,dhcpstart=192.168.2.10 \
> -serial stdio \
> -monitor unix:${MONITORSOCKET},server,nowait
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/qemu/+bug/1723161/+subscriptions
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1723161
Title:
Migration failing in qemu-2.10.1 but working qemu-2.9.1 and earlier
with same options
Status in QEMU:
New
Bug description:
Qemu-2.10.1 migration failing with the following error:
Receiving block device images
qemu-system-x86_64: error while loading section id 2(block)
qemu-system-x86_64: load of migration failed: Input/output error
Migration is setup on the destination system of the migration using:
-incoming tcp:0:4444
Migration is initiated from the source using the following commands in its
qemu monitor:
migrate -b "tcp:localhost:4444"
The command-line used in both the source and destination is:
qemu-system-x86_64 \
-nodefaults \
-pidfile vm0.pid \
-enable-kvm \
-machine q35 \
-cpu host -smp 2 \
-m 4096M \
-drive if=pflash,format=raw,unit=0,file=OVMF_CODE.fd,readonly \
-drive if=pflash,format=raw,unit=1,file=OVMF_VARS.fd \
-drive file=${HDRIVE},format=qcow2 \
-drive media=cdrom \
-usb -device usb-tablet \
-vga std -vnc :0 \
-net nic,macaddr=${TAPMACADDR} -net
user,net=192.168.2.0/24,dhcpstart=192.168.2.10 \
-serial stdio \
-monitor unix:${MONITORSOCKET},server,nowait
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1723161/+subscriptions
- [Qemu-devel] [Bug 1723161] [NEW] Migration failing in qemu-2.10.1 but working qemu-2.9.1 and earlier with same options, William Tambe, 2017/10/12
- [Qemu-devel] [Bug 1723161] Re: Migration failing in qemu-2.10.1 but working qemu-2.9.1 and earlier with same options, Dr. David Alan Gilbert, 2017/10/12
- Re: [Qemu-devel] [Bug 1723161] Re: Migration failing in qemu-2.10.1 but working qemu-2.9.1 and earlier with same options,
William Tambe <=
- [Qemu-devel] [Bug 1723161] Re: Migration failing in qemu-2.10.1 but working qemu-2.9.1 and earlier with same options, Dr. David Alan Gilbert, 2017/10/13
- [Qemu-devel] [Bug 1723161] Re: Migration failing in qemu-2.10.1 but working qemu-2.9.1 and earlier with same options, Fam Zheng, 2017/10/13
- [Qemu-devel] [Bug 1723161] Re: Migration failing in qemu-2.10.1 but working qemu-2.9.1 and earlier with same options, Dr. David Alan Gilbert, 2017/10/13
- [Qemu-devel] [Bug 1723161] Re: Migration failing in qemu-2.10.1 but working qemu-2.9.1 and earlier with same options, Dr. David Alan Gilbert, 2017/10/13