On Wed, Aug 8, 2012 at 7:18 AM, Eric Blake <eblake@redhat.com> wrote:
On 08/08/2012 08:09 AM, Yih Chuang wrote:
Hi,
I had a VM running on c3rh2 under 'vmc' user: [vmc@c3rh2 .ssh]$ virsh list --all Id Name State ---------------------------------------------------- 1 vs2relocate_nonRoot running
What do you get on this host if you do 'virsh uri'? Is it qemu:///session?
Yes. [vmc@c3rh2 yih]$ virsh uri qemu:///session
After the virsh migration command, "virsh migrate --live --unsafe vs2relocate_nonRoot qemu+ssh://vmc@c3rh1.kirkland.ibm.com/session",
this VM
successfully got migrated to the target host c3rh1. However, it was not visible to 'vmc' user but 'root'.
[vmc@c3rh1 .ssh]$ virsh list --all Id Name State ----------------------------------------------------
[vmc@c3rh1 .ssh]$ sudo virsh list --all Id Name State ---------------------------------------------------- 1 vs2relocate_nonRoot running
Again, on this machine, what do:
virsh uri sudo virsh uri
[vmc@c3rh1 yih]$ virsh uri qemu:///session
[vmc@c3rh1 yih]$ sudo virsh uri qemu:///system
display? It looks like migration went from a session to a system libvirtd. To be honest, I have no idea if session migration is even supposed to work. So it's possible you have exposed a bug.
* The libvirt version is libvirt-0.9.10-21.el6_3.1.x86_64 on both hosts.
Since you are using RHEL libvirt, would you mind opening a support ticket with Red Hat?
No, I don't mind at all. Do you have the instructions?
-- Eric Blake eblake@redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org