Sorry. I meant the ip address it is listening on. You can set it to
127.0.0.1, the hypervisors actual ip or 0.0.0.0 which can be defined
in your XML. If it is the hypervisors ip address it won't be able to
move it.
Sent from my iPhone
On Sep 3, 2011, at 12:02 PM, Jatin Kumar <cs5090243(a)cse.iitd.ernet.in> wrote:
testvm1 is using port 5901 on host1 and the same is free on host2.
So port unavailability is definitely not the problem.
--
Jatin
On Sat, Sep 3, 2011 at 6:58 PM, Joseph Harnish <bigjoe1008(a)gmail.com> wrote:
> I have seen this when the port or the ip of the hypervisor was defined
> in the XML config so it couldn't bind to that address when it migrated
> over.
>
> --Joe
>
> Sent from my iPhone
>
> On Sep 3, 2011, at 9:22 AM, Jatin Kumar <cs5090243(a)cse.iitd.ernet.in> wrote:
>
>> Hello,
>> I have been trying to migrate a guest from one host to another.
>> But it is showing this error:
>>
>> virsh --connect qemu+ssh://root@host1/system migrate --live
>> --undefinesource testvm3 qemu+ssh://root@host2/system
>> tcp://host2:48160
>> error: operation failed: failed to retrieve chardev info in qemu with
>> 'info chardev'
>>
>> I have tried this command from the host1 also but it shows the same error.
>> Another thing i would like to ask is the that whats the use of
>> migrateuri in migrate command ?
>>
>> --
>> Jatin Kumar
>>
>> _______________________________________________
>> libvirt-users mailing list
>> libvirt-users(a)redhat.com
>>
https://www.redhat.com/mailman/listinfo/libvirt-users
>
>