[Users] VM migrate Failed to migrate the VM: PRL_ERR_READ_XML_CONTENT

jehan.procaccia at imtbs-tsp.eu jehan.procaccia at imtbs-tsp.eu
Mon Aug 19 16:45:36 MSK 2019


Hello

I found a workaround to that pb of vzmigrate  VM: PRL_ERR_READ_XML_CONTENT
I virsh edit the VM and changed multiple parameters with no success, 
then with change in graphics vnc parameters it became possible to 
migrate again ! now I have:
    <graphics type='vnc' port='-1' autoport='yes' websocket='-1' 
listen='::1' passwd='secret'>
autoport was set to "no" and a static portnumber was set

Now that I can migrate the VM , I am still stuck in another pb , that VM 
that has a hda drive on an IDE controler, cannot start on a VZ host , 
but can on another one [1] and can always with virsh start !?

/[root at olymp qemu]# prlctl start eonimte//
//Starting the VM...//
//Failed to start the VM: Operation failed. Failed to execute the 
operation. (Details: unsupported configuration: Only scsi disk supports 
vendor and product)//
//[root at olymp qemu]# uname -a //
//Linux olymp.int.fr 3.10.0-862.20.2.vz7.73.29 #1 SMP Thu Feb 21 
17:35:43 MSK 2019 x86_64 x86_64 x86_64 GNU/Linux/

I am still searching why .
If you have any idea why IDE disk cannot be started by prlctl command !?
it can be started with KVM virsh start though !

thanks for your help .

regards .

PS [1] where IDE drive works is on: qemu-kvm-vz-2.10.0-21.7.vz7.67.x86_64
where it doesn't : qemu-kvm-vz-2.12.0-18.6.3.vz7.21.6.x86_64

Le 07/08/2019 à 12:58, Jehan PROCACCIA a écrit :
> Hello
>
> I cannot migrate a VM from one host to another, it fails with 
> message:  Failed to migrate the VM: PRL_ERR_READ_XML_CONTENT
> here are the details :
>
> [root at server2 ~]# prlctl migrate eonimtev root at server1 -v 16
> Logging in
> server uuid={e998a2d4-d719-4b26-ab7b-aa11f2c4a812}
> sessionid={2fadf244-cf8a-420c-8f31-21cdd264900a}
> The virtual machine found: eonimtev
> Migrate the VM eonimtev on server1  ()
> security_level=0
> PrlCleanup::register_hook: 6386a500
> EVENT type=100030
> Migration started.
> EVENT type=100001
> EVENT type=100033
> Operation progress ... 1%EVENT type=100033
> Operation progress ... 2%EVENT type=100033
> ...
> Operation progress ...99%EVENT type=100033
> Operation progress    100%
> EVENT type=100031
> Migration cancelled!
> EVENT type=100008
> EVENT type=100001
>
> Failed to migrate the VM: PRL_ERR_READ_XML_CONTENT
> resultCount: 0
> PrlCleanup::unregister_hook: 6386a500
> Logging off
>
> I must admit that I did edit the VM definition with virsh edit in 
> order to specify a different disk name (created from another KVM only 
> machine)
> My initial concern is to convert a KVM machine to virtuozzo prlctl 
> management tools, so I clone an existing virtuozzo VM and changed it's 
> disk image name to the one's of the KVM only image:
>  <disk type='file' device='disk'>
>       <driver name='qemu' type='qcow2'/>
>       <source 
> file='*/vz/vmprivate/60d7f6ed-bfa0-40d4-8bc2-c5a705ebb553/eonimtevIDE.qcow2'*/>
>       <target dev='hda' bus='ide'/>
>       <boot order='1'/>
>       <address type='drive' controller='0' bus='0' target='0' unit='0'/>
>     </disk>
>
> [root at server2 ~]# ls -al /etc/libvirt/qemu/
> total 28
> drwx------ 3 root root 4096  6 août  23:35 .
> drwx------ 5 root root 4096  6 août  22:44 ..
> -rw------- 1 root root 4685  6 août  23:35 eonimtev.xml
>
> 1) What is wrong with this  VM: PRL_ERR_READ_XML_CONTENT ?
>
> 2) Is there a way to "register" to virtuozzo a KVM VM  by copying it's 
> /etc/libvirt/qemu/vm.xml and disk image to a  
> '*/vz/vmprivate/$uuidgen/*hardisk.hdd
> somthing like prlctl register $uuidgen vmname ... ?
>
> thanks .
>
> 		
> *Jehan PROCACCIA*
> Ingénieur systèmes et réseaux
> Membre du comité de pilotage REVE :
> Réseau d’Évry Val d'Essonne et THD
> +33160764436
> 9 rue Charles Fourier - 91011 Evry Cedex
> *www.imt-bs.eu* <https://www.imt-bs.eu> - *www.telecom-sudparis.eu* 
> <https://www.telecom-sudparis.eu>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/users/attachments/20190819/0c2e3289/attachment.html>


More information about the Users mailing list