Openstack Deployment Summary: Create a Windows 2003 mirror with a unique SID through QEMU-KVM

when creating an instance using Windows 2003 mirroring in OpenStack , the same SID will occur, the same SID can cause network and security issues, in order to prevent this situation, the creation of the Mirror requires Windows 2003 encapsulation, this article is a detailed description of the process

Create an IMG file

First create an IMG file

Make ImageInstallation System

the next operation requires VIRTIO-WIN-1.1.16.VFD and virtio-win-0.1-74.iso two file files (http://www.linux-kvm.org/page/ Windowsguestdrivers/download_drivers), execute the following command

/usr/libexec/qemu-kvm-m 1024-cdrom cn_win_srv_2003_r2_enterprise_with_sp2_vl_cd1.iso-drive file=windows32.img,if= VIRTIO,BOOT=ON-FDA virtio-win-1.1.16.vfd-boot order=d,menu=on-usbdevice Tablet-nographic-vnc 192.168.40.148:3

Then quickly with vncviewer access to view, press F12, skip to menu options, otherwise it will automatically enter the hard drive boot mode, if inadvertently enter, kill the KVM process, and then restart KVM try to quickly press F12, select 2 (Disc boot)

Quickly press F6 when the following interface appears

Press F3 to restart if the following conditions occur

F3 Restart, quickly press F12, choose to boot from the CD, prompted below to press F6 when prompted by F6

This time press S, the next page, because it is a 32-bit system,

Select the second, enter the page after the effect of the following

You can see the following interface after you return

Press F8 (or Shift+f8) to enter the partition

Format to FAT32, do not know the NTFS line does not work, here is fat, not ntfs! press C to create the disk

Press ENTER to start the installation,

after formatting, the system will restart after installation, press F12 , select Virtio disk Pci:0:4 option, boot from hard drive, install 2003,

If the following interface appears during installation, it is possible that the system was installed before the image file F3 exit

After the installation is successful, the login system opens the Remote Desktop

Shutting down a virtual machine

Restart the virtual machine image, load the Virtio driver, install the NIC driver, execute the following command

/usr/libexec/qemu-kvm-m 1024-drive file=windows32.img  -cdrom virtio-win-0.1-81.iso-netnic,model=virtio-net User-boot Order=c-usbdevice Tablet-nographic-vnc:1

The driver can be mounted from the CD-ROM.

After installing the Virtio drive, power off, the second disc has some application tools, you can selectively install the second CD-ROM,

/usr/libexec/qemu-kvm-m 1024-drive file=windows32.img  -cdromcn_win_srv_2003_r2_enterprise_with_sp2_vl_ Cd2.iso-net nic,model=virtio-netuser-boot Order=c-usbdevice Tablet-nographic-vnc:3

after entering the system interface, select "Install Windows Server 2003" and "Perform other tasks-" Installation management tool on the CD.

Packaging Systems

Cloning Windows systems in the context of a virtual machine, the same SID will appear ... the same SID system accesses each other, such as the addition of domains. There will be problems, all need to encapsulate the system, generate a new SID, you can use "Whoami/user" in Windows Server 2003 to view the SID of the system

(1) Shut down the system and re-mount the system installation disk CD1

/usr/libexec/qemu-kvm-m 1024-drive file=windows32.img  -cdromcn_win_srv_2003_r2_enterprise_with_sp2_vl_ Cd1.iso-net nic,model=virtio-netuser-boot Order=c-usbdevice Tablet-nographic-vnc:3

(2) After you start the system, go to the Deploy.cab folder in the Support/tools directory on the disc

(3) Extract all files under the folder to the C:\sysgrep directory

(4) Create an answer file

Packaged system, the first launch will have a dialog box to require users to provide the necessary information, such as: host name, regional language settings, etc. for the batch deployment of virtual machines each of the manual input is certainly inconvenient, for this reason, Microsoft provides automatic answer files so that the first boot of the packaged system does not require the user to manually enter information, The following steps are specified:

Execute Setupmgr.exe, create answer file

The following configuration includes some system configuration, such as language, time, secret key, auto-generated computer name , etc.

After the step, according to the actual needs of input can be.

To end the wizard, an answer file called Sysprep.inf is generated under the Sysprep directory, such as:

(5) to the C:\sysgrep directory, run the Sysprep.exe, in the warning point "OK"

(6) Click "OK" in the warning window of the popup to start the package, about 15 seconds after the package is ready, the system automatically shuts down

uploading images to OpenStack

Once the mirror is created, you can upload the image to OpenStack

Glance add Name= "Win2003" is_public=truecontainer_format=ovf  

Use this image to create two instances, the first boot time may be a bit long, the "whoami/user" command to view the SID

Virtual Machine 1

Virtual Machine 2

Issues that occur during installation

Simple solution for VNC viewer connection Flash back

to Option-->advanced-->expert Find Colourlevel , the default value is Pal8 , modified to rgb222 or Full . Reconnect, no problem.

Description: rgb111--8 Colours , rgb222--64 Colours , Pal8--256colours , Full – Full colours

Openstack Deployment Summary: Create a Windows 2003 mirror with a unique SID through QEMU-KVM