From:
win-pv-devel-bounces@xxxxxxxxxxxxxxxxxxxx [mailto:win-pv-devel-bounces@xxxxxxxxxxxxxxxxxxxx]
On Behalf Of Joel Noyce-Barnham
Sent: 14 September 2015 18:21
To: win-pv-devel@xxxxxxxxxxxxxxxxxxxx
Subject: [win-pv-devel] PV Drivers Offline Removal
Hi All,
We are currently using the GPLPV drivers but are hoping to move to the new Xen WINPV drivers as they are actively developed and have some new features which we are interested in. We currently have a process where VMs can be moved from our Xen hypervisor into
EC2. This process relies on the fact that we are able to remove the drivers from an offline image. Previously we have been removing the drivers successfully by converting the disk images to a VHD file, using Dism to remove the drivers (https://technet.microsoft.com/en-GB/library/dd744355%28v=ws.10%29.aspx)
and then importing the resulting VHD into EC2. This works with the GPLPV drivers but with the new WINPV drivers it creates an unbootable image (the import into EC2 fails and the image can also not be booted on the original hypervisor).
I have found some previous posts on this mailing list (http://lists.xenproject.org/archives/html/win-pv-devel/2015-03/msg00076.html) discussing removing the drivers and
I am able to successfully remove the drivers from an online image but sadly our process requires that this removal be performed offline.
I am just wondering if anyone else is using Dism in windows to remove the PV drivers from an offline image? Or if anyone else has successfully removed the WINPV drivers from an offline image at all? Any pointers anyone can give would be appreciated. The only
way we have so far found to make the image boot after removing the drivers with Dism is by manual modification of a large number of registry keys which seems like a far from ideal solution.
Thanks for any help,
Joel
Zynstra is a private limited company registered in England and Wales (registered number 07864369). Our registered
office and Headquarters are at The Innovation Centre, Broad Quay, Bath, BA1 1UD. This email, its contents and any attachments are confidential. If you have received this message in error please delete it from your system and advise the sender immediately.
