Windows administration is not my strong suit but occasionally I find myself having to coax MS products into action. I was surprised when I couldn’t find any specific guidance for slipstreaming virtio since…you know…openstack. Anyway, the following process was undertaken on a Win 2012 server (64-bit) with the resulting image also being Win 2012. Since this version of Windows appears to be little more than Windows 8 without the magnificently atrocious Metro interface, it should work on there as well…that is if you can keep random crap from popping up and stealing focus while you’re trying to work. Good luck on that.
– Windows 2012 Server install ISO
– The latest signed virtio drivers for windows from RedHat. As of the time of writing, these are contained within virtio-win-0.1-59.iso
– ImgBurn or any other tool capable of manipulting ISO images. That we’re in the year CE 2013 and this functionality is not included out of the box on every version of windows is nothing short of criminal. You’re free to open the iso’s in linux and grab what you need as well.
– That’s pretty much it. Everything else, amazingly, is included with a standard windows installation.
- I’ve found relative paths to be a bit of a foreign concept in windows-land (%WINDIR% being the-difficult-to-type exception) so, for ease of explanation, I’ve created the following:
Go ahead and put the windows and virtio iso images in c:\iso.
- Using ImgBurn or the tool of your choice, extract the contents of the windows install iso to c:\iso\ms-iso.
- Extract the contents of the virtio iso into c:\iso\virtio-iso. Alternatively, you could just mount the iso and reference the appropriate path when you reach step #5. I’m just trying to keep this walk-through simple and tidy.
- Next, we’ll use dism to mount the wim image. From an elevated command prompt:
- Time to insert the drivers. Note that due to linux’s own historical baggage, the driver directory is named AMD64. In spite of the name, the drivers are perfectly compatible with all 64-bit x86-derivative platforms.
- If all went well, 5 of 5 drivers will have successfully ‘installed’. Now we seal the deal:
- Now we have to run through the same process but this time we’re updating boot.wimso that we can see the virtual drive during the install process.
- Now all that’s left is to glue the iso back together. In ImgBurn this accomplished by:
- Mode -> Build
- In the ‘Source’ section, click the ‘Browse for a folder’ icon. Select c:\iso\ms-iso.
- In the ‘Destination’ section, click the ‘Browse for a file’ icon. Give your iso a name and put it where you’d like.
- Under the Options tab on the right, set ‘File System’ to ‘UDF’ and ensure that ‘Recurse Subdirectories’ is checked.
- Under the Labels tab, set an appropriate label (eg., ‘win2012-virtio’) in the UDF field.
- Under the Advanced -> Bootable Disc tab:
- Check the ‘Make Image Bootable’ checkbox
- Emulation Type: None (Custom)
- Boot Image: c:\iso\ms-iso\boot\etfsboot.com
- Platform ID: 80×86
- Developer ID: Microsoft Corporation
- Load Segment: 07C0
- Sectors to Load: 8 (for Vista and earlier, this would be 4)
- Patch Information Table: Unchecked
- Finally, click the ‘Build Image’ button on the bottom left.
dism /mount-image /imagefile:c:\iso\ms-iso\sources\install.wim /index:1 /mountdir:c:\iso\ms-mount
dism /image:c:\iso\ms-mount /add-driver /driver:c:\iso\virtio-iso\WIN8\AMD64 /recurse
I find myself recursing quite a bit when interacting with dos’ archaic shell but, alas, we’re almost through. Don’t even get me started on the wildly verbose and pseudo-random command syntax of powershell.
dism /unmount-wim /mountdir:c:\iso\ms-mount /commit
dism /mount-image /imagefile:c:\iso\ms-iso\sources\boot.wim /index:1 /mountdir:c:\iso\ms-mount dism /image:c:\iso\ms-mount /add-driver /driver:c:\iso\virtio-iso\WIN8\AMD64 /recurse dism /unmount-wim /mountdir:c:\iso\ms-mount /commit
All done. I’ve noticed that ImgBurn seems to be under regular development so the UI may present additional features beyond those listed here. If so, use your best judgement or google (preferred).