Openstack Juno -Windows 2012 STD/ R2 fails after sysprep

edit

Hi Adrian, I checked and both the environment has the above setting in nova.conf file.

Moreover, you need the virtio drivers provided by fedora, to be installed if you are using virtio-scsi or virtio-net: fedorapeople.org/groups/virt/virtio-win/

I have installed the virtIO drivers as well. The image works on one environment and fails on other.

I understand. If possible, can you provide the qemu-kvm command used in either environments on a pastebin? The command can be retrieved by issuing a 'ps aux | grep kvm' on the compute nodes. I would like to see if there is any difference between the commands, in order to reproduce your issue. Thanks

Hi Please find the outout for working : http://pastebin.com/1kZS2mGj and non working : http://pastebin.com/Kr9tp0SE

You have an issue with the unattend file and the error is a sysprep one. There are 4 log files where you can check what the actual error is: C:\Windows\Panther\setupact.log/setuperr.log and C:\Windows\Panther\UnattendGC\setupact.log/setuperr.log

There is a high probability that the error you are getting is network or driver related. If you can provide the log files I have mentioned above, it would suffice to get to the bottom of your issue.

I will. However what surprise me is that the same image works on my other environment with the same unattend file. I will try to get the above mentioned logs.

I was unable to copy/paste the logs or copy the file to working machine hence I have taken the screenshot. the link for the same is : https://drive.google.com/folderview?id=0B4-mb8IaKpTsVEt6MzVjRmxET0E&usp=sharing

I would suggest adding to your unattend.xml the section that disables devices drivers persistence: http://paste.ubuntu.com/18170474/ . As a side note, I strongly advise to use the already tested generation scripts: https://github.com/cloudbase/windows-openstack-imaging-tools .

I made the changes in my unattend file as per the link and disabled the drive driver persistence and created a new image. I was able to create one instance from it and then it failed again for the subsequent instance.

setuperr.log says unable to modify bcd boot entries - the error is now different than the previous one.

Can you try to reproduce the issue using our qcow2 trial image? you can download it from here:https://cloudbase.it/windows-cloud-images/ .

I have already tried it and unfortunately it is also failing in the similar way after creating one instance on this environment. We took the trial image - converted it to RAW from Qcow2 - installed patches on it and then created a syspreped image.

It might be an issue with the re-syspreped image you are creating. Does the unmodified cloudbase image also fail?

The unmodified image still works.

Hi, I was able to make the image working for one environment after modifying the unattend file. however it again fails in the other environment after creating 4 instance. Below is the unattend file.