Re: [ovirt-users] Error while using REST API with Ovirt

Dear Juan, Thanks for the prompt reply and support. As advised I did the registry editing and then created a template and tried to give the hostname in the manner told to the deployed vm but no luck. It does not give any error but on checking the hostname through machine console it is not set there. Please find attached the screen shot of the registry editing done. Also for ip configuration if any other method is possible other than DHCP server option please tell . Thanks & Regards Ruchita Agarwal From: Juan Hernandez <jhernand(a)redhat.com&gt; To: Chandrahasa S <chandrahasa.s(a)tcs.com&gt; Cc: Agarwal Ruchita <agarwal.ruchita(a)tcs.com&gt;, users(a)ovirt.org Date: 09/23/2014 09:23 PM Subject: Re: [ovirt-users] Error while using REST API with Ovirt On 09/23/2014 04:55 PM, Chandrahasa S wrote: Ok. I don't have a 2008 machine to tests, but I tested with Windows 7, which should be quite similar. These are my suggestions: * Take into account that Windows 2008 uses an XML format for the answers file, and that the file name that sysprep will look for is "Unattend.xml". On the other hand the engine will always generate a file named "sysprep.inf", so you need to alter the registry settings of the VM before creating the template. In particular you need to create a key named "UnattendFile" entry under "HKEY-LOCAL-MACHINE -> SYSTEM -> Setup". The value should be the location of the file. For the files generated by the engine it should be "A:\sysprep.inf". With this the sysprep support should work if you use it from the GUI. * The guest agent is nice to have, but not required in order to use sysprep, and it won't allow you to change the IP configuration of the guest, only to view it. * As far as I know sysprep doesn't allow you to configure the IP addresses, only the machine name, so I believe you will have to use a different mechanism, like configuring your DHCP server so that it assigns IP addresses based on MAC addresses or host names. * You don't need to provide the content of the sysprep file, it is automatically generated by the engine, merging the parameters that you pass with the static content in the templte file /usr/share/ovirt-engine/conf/sysprep.2k8. So, to summarize, after preparing correctly the image, you should send a request like this (assuming that the VM is already created from the template): PUT /api/vms/7dac74d2-c504-4bbd-8659-c8773a844cb3 <vm> <initialization> <host_name>WIN-AS05EOADAwerwer</host_name> <domain>ultimatixuat.net</domain> </initialization> </vm> Then you can start it like this: POST /api/vms/7dac74d2-c504-4bbd-8659-c8773a844cb3/start <action/> And sysprep should trigger and configure the VM. Take into account that this only works the first time you start the VM, so if you are testing multiple times remember to remove and create it again. To debug this, once the VM is started, go to the hypervisor where it is running and find the qemu process: # ps -ef | grep -- '-name the_name_of_your_vm' That should be a very long command line, including a "-drive" option corresponding to the sysprep floppy that the engine created and added to the VM: -drive file=/var/run/vdsm/payload/27faa0ce-3e4d-4705-adf8-30d6e9fde741.a659e9a9747fe55a8eb0c7ecbc549c86.img Copy that .img file somewhere, mount and inspect it: # cp /var/run/vdsm/payload/27faa0ce-3e4d-4705-adf8-30d6e9fde741.a659e9a9747fe55a8eb0c7ecbc549c86.img /tmp/f.img # mount -o loop,ro /tmp/f.img /mnt # find /mnt/ /mnt/ /mnt/sysprep.inf Check the content of the /mnt/sysprep.inf file, it should contain your settings. If the content of the floppy and the sysprep.inf file are correct but your VM is still not being configured then there is something wrong with the preparation of the template. successfully a work +"<fqdn>WIN-AS05EOADAwerwer</fqdn>"+"</reported_device>"+"<reported_devices>"; StringEntity(inputXML1); "application/xml"); " and to ------------------------------------------------------------------------ but '"bootProtocol" Ovirt ------------------------------------------------------------------------ version cloud be need S.L. -- Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain Inscrita en el Reg. Mercantil de Madrid ? C.I.F. B82657941 - Red Hat S.L.