On 16/02/2015 22:08, Alexander Graf wrote:
> > Can you make it a capability?
> When did live migration start to have capability negotiation? :)
Only capability without negotiation. :)
Negotiation is done above QEMU.
Paolo
On 16.02.15 22:06, Paolo Bonzini wrote:
>
>
> On 16/02/2015 21:24, Alexander Graf wrote:
>>> As mentioned on IRC; I'm still worried though that this is only
a fix for loading on newer versions; migration to an older QEMU
with the same machine type would fail.
(Yes I know mythical
On 16/02/2015 21:24, Alexander Graf wrote:
>> As mentioned on IRC; I'm still worried though that this is only
>> > a fix for loading on newer versions; migration to an older QEMU
>> > with the same machine type would fail.
>> > (Yes I know mythically that no one cares about this; but I do).
> Yea
On 16.02.15 19:57, Dr. David Alan Gilbert wrote:
> * Alexander Graf (ag...@suse.de) wrote:
>
>
>
>> Can you please test whether the patch below makes things work for you again?
>
> The patch below fixes RDMA migration (same host); however, see comments.
>
>> Alex
>>
>> From ef6fde21007e62529
* Alexander Graf (ag...@suse.de) wrote:
> Can you please test whether the patch below makes things work for you again?
The patch below fixes RDMA migration (same host); however, see comments.
> Alex
>
> From ef6fde21007e62529799264f57a65c6bb3d0d414 Mon Sep 17 00:00:00 2001
> From: Alexander G
On 13.02.15 12:23, Lucas Meneghel Rodrigues wrote:
>
>
> On Fri, Feb 13, 2015 at 9:18 AM, Alexander Graf wrote:
>>
>>
>> On 13.02.15 10:04, Dr. David Alan Gilbert wrote:
>>> * Alexander Graf (ag...@suse.de) wrote:
On 13.02.15 01:29, Lucas Meneghel Rodrigues wrote:
> Copyi
On Fri, Feb 13, 2015 at 9:18 AM, Alexander Graf wrote:
On 13.02.15 10:04, Dr. David Alan Gilbert wrote:
* Alexander Graf (ag...@suse.de) wrote:
On 13.02.15 01:29, Lucas Meneghel Rodrigues wrote:
Copying Alex.
OK, after bisecting, this is what I've got:
8118f0950fc77cce7873002a502
* Alexander Graf (ag...@suse.de) wrote:
>
>
> On 13.02.15 10:04, Dr. David Alan Gilbert wrote:
> > * Alexander Graf (ag...@suse.de) wrote:
> >>
> >>
> >> On 13.02.15 01:29, Lucas Meneghel Rodrigues wrote:
> >>> Copying Alex.
> >>>
> >>> OK, after bisecting, this is what I've got:
> >>>
> >>> 8118
On 13.02.15 10:04, Dr. David Alan Gilbert wrote:
> * Alexander Graf (ag...@suse.de) wrote:
>>
>>
>> On 13.02.15 01:29, Lucas Meneghel Rodrigues wrote:
>>> Copying Alex.
>>>
>>> OK, after bisecting, this is what I've got:
>>>
>>> 8118f0950fc77cce7873002a5021172dd6e040b5 is the first bad commit
>>>
Alex, Dave:
Virt-Test fd migration starts by sending a fd to the source vm
22:20:40 DEBUG| Send file descriptor migfd_28_1423786840 to source VM.
22:20:40 DEBUG| (monitor hmp1) Sending command 'getfd
migfd_28_1423786840'
later on...
22:20:42 INFO | Migrating to fd:migfd_28_1423786840
22:20:4
* Alexander Graf (ag...@suse.de) wrote:
>
>
> On 13.02.15 01:29, Lucas Meneghel Rodrigues wrote:
> > Copying Alex.
> >
> > OK, after bisecting, this is what I've got:
> >
> > 8118f0950fc77cce7873002a5021172dd6e040b5 is the first bad commit
> > commit 8118f0950fc77cce7873002a5021172dd6e040b5
> >
On 13.02.15 01:29, Lucas Meneghel Rodrigues wrote:
> Copying Alex.
>
> OK, after bisecting, this is what I've got:
>
> 8118f0950fc77cce7873002a5021172dd6e040b5 is the first bad commit
> commit 8118f0950fc77cce7873002a5021172dd6e040b5
> Author: Alexander Graf mailto:ag...@suse.de>>
> Date: Thu
Copying Alex.
OK, after bisecting, this is what I've got:
8118f0950fc77cce7873002a5021172dd6e040b5 is the first bad commit
commit 8118f0950fc77cce7873002a5021172dd6e040b5
Author: Alexander Graf
Date: Thu Jan 22 15:01:39 2015 +0100
migration: Append JSON description of migration stream
On Thu, Feb 12, 2015 at 8:56 PM, Lucas Meneghel Rodrigues wrote:
> OK, indeed I can reproduce the problem. It's specific to the
> filedescriptor migration. An easy way to reproduce it is by doing:
>
> git clone https://github.com/autotest/virt-test.git
>
> cd virt-test
> ./run -t qemu --bootstrap
OK, indeed I can reproduce the problem. It's specific to the filedescriptor
migration. An easy way to reproduce it is by doing:
git clone https://github.com/autotest/virt-test.git
cd virt-test
./run -t qemu --bootstrap
./run -t qemu
--tests type_specific.io-github-autotest-qemu.migrate.default.fd
>From what the log says, after a round of migrations 'info migrate' does not
respond after 4 minutes, timing out. Virt Test then shuts down the VM. When
it tries to check the qcow2 image, it is corrupted. I'm checking out the
latest master to see how reproducible this problem is.
On Thu, Feb 12, 2
Hi
while testing my changes I noticed that virt-test was failing. I
check-out master, and failures are there.
This is one extract of the log after the 1st failure. Notice that it
fails randomly, not every time.
I have to go to bed right now, so if anybody beats me with a fix, I
would be happy
17 matches
Mail list logo
