Re: Problems with live block migration

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Sorry for the noise around this, the solution was pretty straight forward.

And also it turns out that I don’t need the floppy either.

I kept it on the destination end but ejected it on the source.

'{"execute":"eject", "arguments": { "device": "drive-fdc0-0-0" } }’

It seems to run smooth now, thanks for the help :)

Regards,
Josef

> On 08 Sep 2016, at 10:33, Josef Johansson <josef86@xxxxxxxxx> wrote:
> 
> Sorry for the noise around this, the solution was pretty straight forward.
> 
> And also it turns out that I don’t need the floppy either.
> 
> I kept it on the destination end but ejected it on the source.
> 
> It seems to run smooth now, thanks for the help :)
> 
> Regards,
> Josef
> 
>> On 08 Sep 2016, at 10:24, Josef Johansson <josef86@xxxxxxxxx> wrote:
>> 
>> Sorry for the noise around this, the solution was pretty straight forward.
>> 
>> And also it turns out that I don’t need the floppy either.
>> 
>> I kept it on the destination end but ejected it on the source.
>> 
>> '{"execute":"eject", "arguments": { "device": "drive-fdc0-0-0" } }’
>> 
>> It seems to run smooth now, thanks for the help :)
>> 
>> Regards,
>> Josef
>> 
>>> On 08 Sep 2016, at 06:56, Josef Johansson <josef86@xxxxxxxxx> wrote:
>>> 
>>> Will do.
>>> 
>>> 
>>> On Wed, 7 Sep 2016, 21:34 Stefan Hajnoczi, <stefanha@xxxxxxxxx> wrote:
>>> On Tue, Sep 06, 2016 at 07:50:58AM +0200, Josef Johansson wrote:
>>> > I did hook up gdb to the process and stepped it to get a more decent error code and I would up in bdrv_rw_co
>>> >
>>> > Inside vmstate_load it runs the following (savevm.c):
>>> > 1609:        return se->load_state(f, se->opaque, version_id);
>>> > And that goes to (block-migration.c):
>>> > 484:static int block_load(QEMUFile *f, void *opaque, int version_id)
>>> > and it all fails on (block-migration.c):
>>> > 517:            ret = bdrv_write(bs, addr, buf, BDRV_SECTORS_PER_DIRTY_CHUNK);
>>> > 518:
>>> > 519:            qemu_free(buf);
>>> > 520:            if (ret < 0) {
>>> > 521:                return ret;
>>> > 522:            }
>>> >
>>> > print ret in gdb gives med -13 here. Now this is where I’m lost, what would that mean? Permission Denied?
>>> 
>>> EACCES -> read only disk
>>> 
>>> > -drive file=/root/grub.img,if=none,id=drive-fdc0-0-0,readonly=on,format=raw
>>> 
>>> Can you try migrating without this read-only drive or make it read-write?
>>> 
>>> Looks like your CentOS 6 QEMU binary is missing commit
>>> d246673dcb9911218ff555bcdf28b250e38fa46c ("block migration: Fix test for
>>> read-only drive").
>>> 
>>> Stefan
>> 
> 

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux