7:06 a.m.
Hi,
I tried to migrate qemu domains between same two Freescale PPC platforms.
1) Migrate test domain from Host1(10.193.20.109) to Host2(10.193.20.181).
root@ppc-host1:~# virsh migrate test qemu+tls://10.193.20.181/system
or
root@ppc-host2:~# virsh -c qemu+tls://10.193.20.109/system migrate test qemu:///system
I waited for a while and finally got error message as below:
error: Unable to read from monitor: Connection reset by peer
Exactly, when waiting (I guess during migration), the migrated domain is pasued on
both source and destination nodes.
root@ppc-host1:~# virsh -c qemu:///system list --all
Id Name State
----------------------------------------------------
5 test paused
And meanwhile, the destination domain is also paused when waiting
root@ppc-host2:~# virsh -c qemu:///system list --all
Id Name State
----------------------------------------------------
2 test paused
Finally, the migrated domain on source node is shut off.
root@ppc-host1:~# virsh -c qemu:///system list --all
Id Name State
----------------------------------------------------
- test shut off
But can't find any domain on destination node any longer.
root@ppc-host2:~# virsh -c qemu:///system list --all
Id Name State
----------------------------------------------------
As I know qemu-system-ppc doesn't support live migration on Freescale PPC platform
yet.
My question is whether it depends on qemu implementation to migrate qemu hypervisor with
libvirt?
From the above experiment, it seemed that migration happened but not
succeeded finally.
Best Regards,
Olivia
11:01 p.m.
On 2013年03月28日 20:06, Yin Olivia-R63875 wrote:
Hi,
I tried to migrate qemu domains between same two Freescale PPC platforms.
1) Migrate test domain from Host1(10.193.20.109) to Host2(10.193.20.181).
root@ppc-host1:~# virsh migrate test qemu+tls://10.193.20.181/system
or
root@ppc-host2:~# virsh -c qemu+tls://10.193.20.109/system migrate test qemu:///system
I waited for a while and finally got error message as below:
error: Unable to read from monitor: Connection reset by peer
I think debug log
should be useful.
Exactly, when waiting (I guess during migration), the migrated domain
is pasued on
both source and destination nodes.
root@ppc-host1:~# virsh -c qemu:///system list --all
Id Name State
----------------------------------------------------
5 test paused
And meanwhile, the destination domain is also paused when waiting
root@ppc-host2:~# virsh -c qemu:///system list --all
Id Name State
----------------------------------------------------
2 test paused
Finally, the migrated domain on source node is shut off.
root@ppc-host1:~# virsh -c qemu:///system list --all
Id Name State
----------------------------------------------------
- test shut off
But can't find any domain on destination node any longer.
root@ppc-host2:~# virsh -c qemu:///system list --all
Id Name State
----------------------------------------------------
As I know qemu-system-ppc doesn't support live migration on Freescale PPC platform
yet.
My question is whether it depends on qemu implementation to migrate qemu hypervisor with
libvirt?
Ah, I think it needs QEMU's support. :)
>From the above experiment, it seemed that migration happened but not succeeded
finally.
Best Regards,
Olivia
--
libvir-list mailing list
libvir-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
5:16 a.m.
Hi Cindy,
Thanks for your reply.
Since LXC is an independent driver in libvirt, I guess to migrate LXC domains
doesn't depend on external program.
But it failed with different error messages on source and destination nodes.
1) Migrate the virtual machine to the destination host
root@ppc-host1:~# virsh -c lxc:/// list --all
Id Name State
----------------------------------------------------
3396 vm1 running
root@ppc-host1:~# virsh migrate vm1 lxc+tls://10.193.20.181/
error: failed to get domain 'vm1'
error: Domain not found: no domain with matching name 'vm1'
2) Migrate the virtual machine back
root@ppc-host2:~# virsh -c lxc+tls://root@10.193.20.109/ list --all
Id Name State
----------------------------------------------------
3396 vm1 running
root@ppc-host2:~# virsh -c lxc+tls://10.193.20.109/ migrate vm1 lxc:///
error: this function is not supported by the connection driver: virDomainMigrate2
Do you have any idea?
Best Regards,
Olivia
-----Original Message-----
From: Li Zhang [mailto:zhlcindy@gmail.com]
Sent: Friday, March 29, 2013 12:02 PM
To: Yin Olivia-R63875
Cc: libvir-list(a)redhat.com; libvirt-users(a)redhat.com
Subject: Re: [libvirt] migrate qemu domains
On 2013年03月28日 20:06, Yin Olivia-R63875 wrote:
> Hi,
>
> I tried to migrate qemu domains between same two Freescale PPC platforms.
>
> 1) Migrate test domain from Host1(10.193.20.109) to Host2(10.193.20.181).
> root@ppc-host1:~# virsh migrate test qemu+tls://10.193.20.181/system
> or root@ppc-host2:~# virsh -c qemu+tls://10.193.20.109/system migrate
> test qemu:///system
>
> I waited for a while and finally got error message as below:
> error: Unable to read from monitor: Connection reset by peer
I think debug log should be useful.
> Exactly, when waiting (I guess during migration), the migrated domain
> is pasued on both source and destination nodes.
> root@ppc-host1:~# virsh -c qemu:///system list --all
> Id Name State
> ----------------------------------------------------
> 5 test paused
>
>
> And meanwhile, the destination domain is also paused when waiting
> root@ppc-host2:~# virsh -c qemu:///system list --all
> Id Name State
> ----------------------------------------------------
> 2 test paused
>
> Finally, the migrated domain on source node is shut off.
> root@ppc-host1:~# virsh -c qemu:///system list --all
> Id Name State
> ----------------------------------------------------
> - test shut off
>
>
> But can't find any domain on destination node any longer.
> root@ppc-host2:~# virsh -c qemu:///system list --all
> Id Name State
> ----------------------------------------------------
>
>
> As I know qemu-system-ppc doesn't support live migration on Freescale PPC
platform yet.
> My question is whether it depends on qemu implementation to migrate qemu
hypervisor with libvirt?
Ah, I think it needs QEMU's support. :)
>
> >From the above experiment, it seemed that migration happened but not
succeeded finally.
>
> Best Regards,
> Olivia
>
>
> --
> libvir-list mailing list
> libvir-list(a)redhat.com
> https://www.redhat.com/mailman/listinfo/libvir-list
4253
days inactive
4257
days old
2 comments
2 participants
participants (2)
-
Li Zhang -
Yin Olivia-R63875