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

Re: [libvirt] Allow to change the maximum migration downtime -- bug 561935



Hi Daniel,
The guest can be successfully migrated, but it will spend very very long time,
and I will retest the bug based on you and Jiri suggestion, thanks.

Regards,
Alex
----- Original Message -----
From: "Daniel P. Berrange" <berrange redhat com>
To: "Alex Jia" <ajia redhat com>
Cc: libvir-list redhat com
Sent: Monday, July 5, 2010 9:34:27 AM GMT +00:00 Monrovia
Subject: Re: Allow to change the maximum migration downtime -- bug 561935

On Fri, Jul 02, 2010 at 06:32:58AM -0400, Alex Jia wrote:
> And then running migration, and open another terminal set maximum migration 
> downtime 60000 milliseconds, the following error information is raised by
> libvirt:
> 
> 1.open one terminal run migrate
> # virsh migrate rhel6 qemu+ssh://10.66.70.152/system
> root 10 66 70 152's password: 
> 
> 2.open another terminal set maximum migration downtime
> # virsh migrate-setmaxdowntime --domain rhel6 --downtime 60000
> error: Requested operation is not valid: domain is not being migrated
> 
> In fact, step 1 will never be finished.

This is odd. I wonder if perhaps the migrate API never even got started.
Probably need to capture debug logs from libvirtd with log_filters="1:qemu"
set.

Daniel
-- 
|: Red Hat, Engineering, London    -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :|
|: http://autobuild.org        -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|


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