qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Lieven <pl@dlh.net>
To: Juan Quintela <quintela@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Re: Qemu-KVM Livate Migration 0.12.2 -> 0.12.3/4 broken?
Date: Wed, 12 May 2010 15:42:46 +0200	[thread overview]
Message-ID: <4BEAB056.4080903@dlh.net> (raw)
In-Reply-To: <m3sk5yxcde.fsf@trasno.mitica>

Hi,

I can confirm that reverting this patch makes Live Migration from 0.12.2 
to 0.12.4
again possible.

Br,
Peter

Juan Quintela wrote:
> Peter Lieven <pl@dlh.net> wrote:
>   
>> Hi Qemu/KVM Devel Team,
>>
>> Live Migration from a 0.12.2 qemu-kvm to a 0.12.3 (and 0.12.4)
>> does not work: "load of migration failed"
>>
>> Is there any way to find out, why exactly it fails? I have
>> a lot of VMs running on 0.12.2 and would like to migrate
>> them to 0.12.4
>>
>> cmdline:
>> -net tap,vlan=6,script=no,downscript=no,ifname=tap7 -net
>> nic,vlan=6,model=e1000,macaddr=52:54:00:fe:00:88   -net
>> tap,vlan=651,script=no,downscript=no,ifname=tap8 -net
>> nic,vlan=651,model=e1000,macaddr=52:54:00:ff:00:69   -drive
>> file=/dev/mapper/iqn.2001-05.com.equallogic:0-8a0906-b6eca7604-6280020bc4b4bde8-quagga,if=ide,boot=on,cache=none,aio=native
>> -m 256 -monitor tcp:0:4090,server,nowait -vnc :90 -name 'Quagga' -boot
>> order=dc,menu=on  -k de  -incoming tcp:172.21.59.132:5090 -pidfile
>> /var/run/qemu/vm-148.pid  -rtc base=utc,clock=vm  -usb -usbdevice
>> tablet  -no-kvm-irqchip  -vga cirrus
>>
>> Any hints would be appreciated!
>>     
>
> Can you try reverting this patch?
>
> commit 3fa017e24b0a0f0e68619a689b9b02fe486dae9e
> Author: Marcelo Tosatti <mtosatti@redhat.com>
> Date:   Thu Feb 11 18:19:44 2010 -0200
>
>     ide save/restore pio/atapi cmd transfer fields and io buffer
>
> and told me if it works?
>
> Later, Juan.
>
>
>
>   


-- 
Mit freundlichen Grüßen/Kind Regards

Peter Lieven

..........................................................................................................

   KAMP Netzwerkdienste GmbH
   Vestische Str. 89-91 | 46117 Oberhausen
   Tel: +49 (0) 208.89 402-50 | Fax: +49 (0) 208.89 402-40
   mailto:pl@kamp.de | http://www.kamp.de

   Geschäftsführer: Heiner Lante | Michael Lante
   Amtsgericht Duisburg | HRB Nr. 12154
   USt-Id-Nr.: DE 120607556

......................................................................................................... 

  reply	other threads:[~2010-05-12 13:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-11 10:59 [Qemu-devel] Qemu-KVM Livate Migration 0.12.2 -> 0.12.3/4 broken? Peter Lieven
2010-05-11 23:11 ` [Qemu-devel] " Juan Quintela
2010-05-12 13:42   ` Peter Lieven [this message]
2010-05-16 12:02   ` Avi Kivity
2010-05-16 14:42     ` Juan Quintela
2010-05-16 14:47       ` Avi Kivity
2010-05-16 20:04         ` Juan Quintela
2010-05-17  7:00           ` Avi Kivity
2010-05-17  8:23             ` Michael Tokarev
2010-05-17  9:07               ` Juan Quintela
2010-05-17  9:11                 ` Michael Tokarev
2010-05-17  9:38                   ` Alexander Graf
2010-05-16 18:03       ` Jan Kiszka
2010-05-16 20:06         ` Juan Quintela
2010-05-17 10:35           ` Jan Kiszka
2010-06-08  9:54             ` Peter Lieven

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BEAB056.4080903@dlh.net \
    --to=pl@dlh.net \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).