Funny story……
Imagine – you have brand new physical server… And you don’t want to use HyperV (I understand this), but still you want to use the Windows licence that is bundled with the machine on OEM DVD.
You start booting…….. And then – you end with message that you can install this image only on the machine that it belongs to. Luckily in KVM we can “fake” the machine. 😉
OK let’s start with preparing the ISO image and put it somewhere where we can access it with libvirt. Let’s say /tmp
|
1 2 3 |
dd if=/dev/sr0 of=windows.iso mv ./windows.iso /tmp/ chmod 444 /tmp/windows.iso |
2nd step is to get information from BIOS with dmidecode and again copy it somewhere where it can be read by libvirt. Because we need it for later use – this time /etc is better than /tmp
|
1 2 3 4 5 6 7 8 9 10 |
dmidecode –t 0 dmidecode –t 0 > bios dmidecode –t 1 > system ls /sys/firmware/acpi/tables/ mkdir /etc/libvirt/acpitables cp /sys/firmware/acpi/tables/* /etc/libvirt/acpitables/ cd /etc/libvirt/ chmod 444 ./acpitables/ cd acpitables/ chmod 444 * |
If you want to use virtio drivers in Windows we need to get also the virtio-win CD.
We have multiple choices – the easiest one is to download ISO.
In case you want to have the always the latest fresh version – you can add the repository. In our case we are using CentOS 7, but there’s no official repo for CentOS. But still we can use the Fedora repo without any problem.
With the following part we will get the latest images (CDrom/floppy/etc) stored in /usr/share/virtio-win/
|
1 2 |
wget https://fedorapeople.org/groups/virt/virtio–win/virtio–win.repo –O /etc/yum.repos.d/virtio–win.repo yum install virtio–win |
Then just update the xml (define the machine the way you like… for example with virt-install and then just do the virsh edit).
Few tricky thingy….
* put xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0' in domain definition. Otherwise the parser will cream with additional commandline options
* in case of Lenovo some of the values from BIOS were in format blablabla -[xyz]- In this moment parser was stopping. No idea if it was because of XSLT/my typo/or because it was Saturday…… But it was pretty late and I was lazy and it is working perfectly fine just with part without brackets
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 |
<domain type=‘kvm’ xmlns:qemu=‘http://libvirt.org/schemas/domain/qemu/1.0’> <uuid>1f897773-08de-41fc-bf66-9d716001589a</uuid> …. <sysinfo type=‘smbios’> <bios> <entry name=‘vendor’>LENOVO</entry> <entry name=‘version’>TAE108I-1.20</entry> </bios> <system> <entry name=‘manufacturer’>LENOVO</entry> <entry name=‘product’>System x3500 M5 </entry> <entry name=‘version’>08</entry> <entry name=‘serial’>a</entry> <entry name=‘uuid’>1f897773-08de-41fc-bf66-9d716001589a</entry> <entry name=‘family’>X</entry> </system> </sysinfo> <os> <type arch=‘x86_64’ machine=‘pc-i440fx-rhel7.0.0’>hvm</type> <boot dev=‘cdrom’/> <boot dev=‘hd’/> <smbios mode=‘sysinfo’/> </os> … <devices> <disk type=‘file’ device=‘cdrom’> <driver name=‘qemu’ type=‘raw’/> <source file=‘/tmp/windows.iso’/> <backingStore/> <target dev=‘hda’ bus=‘ide’/> <readonly/> <alias name=‘ide0-0-0’/> <address type=‘drive’ controller=‘0’ bus=‘0’ target=‘0’ unit=‘0’/> </disk> <disk type=‘file’ device=‘cdrom’> <driver name=‘qemu’ type=‘raw’/> <source file=‘/usr/share/virtio-win/virtio-win.iso’/> <backingStore/> <target dev=‘hdb’ bus=‘ide’/> <readonly/> <alias name=‘ide0-0-0’/> <address type=‘drive’ controller=‘0’ bus=‘0’ target=‘0’ unit=‘1’/> </disk> … </devices> <qemu:commandline> <qemu:arg value=‘-acpitable’/> <qemu:arg value=‘file=/etc/libvirt/acpitables/MSDM’/> <qemu:arg value=‘-acpitable’/> <qemu:arg value=‘file=/etc/libvirt/acpitables/SLIC’/> </qemu:commandline> </domain> |
Now cross your fingers, start the machine and your KVM environment should pretend to be nice Lenovo piece of hardware.