Digimer at 00:54, 2 September 2011

2011-09-02T00:54:23Z

← Older revision		Revision as of 00:54, 2 September 2011
Line 4:		Line 4:

	= Storage Concerns =		= Storage Concerns =

			Pre-provision tasks:

			== FOR KVM ==

			yum install virtio-win

	== Aligning Partitions ==		== Aligning Partitions ==

Digimer at 20:12, 31 August 2011

2011-08-31T20:12:06Z

← Older revision		Revision as of 20:12, 31 August 2011
Line 4:		Line 4:

	= Storage Concerns =		= Storage Concerns =

			== Aligning Partitions ==

	The first thing we need to do is make sure that the partition under the Windows VM starts on a cylinder that is an even 64[[KiB]].		The first thing we need to do is make sure that the partition under the Windows VM starts on a cylinder that is an even 64[[KiB]].
Line 71:		Line 73:

	Extra options:		Extra options:
	<source lang="~~bash~~">		<source lang="text">
	Command (m for help): x		Command (m for help): x
	</source>		</source>
Line 140:		Line 142:

	Unlike Linux, which "just works", you will want to do a few things to optimize Windows on your cluster.		Unlike Linux, which "just works", you will want to do a few things to optimize Windows on your cluster.

			== Install The GPLPV Drivers ==

	* Switch to "Test-signing" mode. This is required in order to install the drivers in the next step. '''DO NOT SKIP THIS STEP'''! Doing so could corrupt your Windows VM.		* Switch to "Test-signing" mode. This is required in order to install the drivers in the next step. '''DO NOT SKIP THIS STEP'''! Doing so could corrupt your Windows VM.
Line 147:		Line 151:
	Click in <span class="code">Start</span> and the type <span class="code">cmd</span> in the search bar.		Click in <span class="code">Start</span> and the type <span class="code">cmd</span> in the search bar.

	<source lang="~~bash~~">		<source lang="text">
	bcdedit /set testsigning on		bcdedit /set testsigning on
	</source>		</source>

Digimer: Created page with "{{howto_header}} Installing a Windows 2008 R2 domU under Xen on an EL2 Cluster requires some extra planning to maintain optimal perfor..."

2011-08-31T20:10:31Z

Created page with "{{howto_header}} Installing a Windows 2008 R2 domU under Xen on an EL2 Cluster requires some extra planning to maintain optimal perfor..."

Páàjì titun

{{howto_header}}

Installing a Windows 2008 R2 [[domU]] under Xen on an [[Red Hat Cluster Service 2 Tutorial|EL2 Cluster]] requires some extra planning to maintain optimal performance.

= Storage Concerns =

The first thing we need to do is make sure that the partition under the Windows VM starts on a cylinder that is an even 64[[KiB]].

{{warning|1=The following steps WILL DESTROY YOUR DATA! Do not do this on a production server. These steps must be done before using the partitions in any part of the cluster.}}

To do this, first run fdisk -u /dev/sda. If you have software RAID, you will need to delete any RAID arrays using the partition that will host your Windows VMs, then run the following steps on all drives in the array. For simplicity's sake, this tutorial will assume that you have a single disk (or are using a RAID controller that presents the array as a single disk).

<source lang="bash">
fdisk -u /dev/sda
</source>
<source lang="text">
The number of cylinders for this disk is set to 30401.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
</source>

Print the current configuration.

<source lang="text">
Command (m for help): p
</source>
<source lang="text">
Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 63 530144 265041 83 Linux
/dev/sda2 530145 84421574 41945715 83 Linux
/dev/sda3 84421575 92807504 4192965 82 Linux swap / Solaris
/dev/sda4 92807505 488392064 197792280 5 Extended
/dev/sda5 92807568 285603569 96398001 83 Linux
/dev/sda6 285603633 478399634 96398001 83 Linux
/dev/sda7 478399698 488392064 4996183+ 83 Linux
</source>

We are going to put Windows on the /dev/sda5 partition, which is showing a start sector of 92807568. To determine if this is on a 64 [[KiB]] boundary, we need to do some math.

If we look at Units = sectors of 1 * 512 = 512 bytes, we know that each unit shown is itself 512 [[bytes]] long. That means that each 64 KiB block will use 128 sectors. So, our starting sector needs to be evenly divisible by 128.

<source lang="text">
92807568 ÷ 128 = 725059.125
</source>

We have a remainder, so it's not on an even 64 KiB block. Now we need to figure out what sector above 92807568 is evenly divisible by 128. To do that, lets add 127 (one sector shy of the next 64 KiB block), divide by 128 to get the number of 64 KiB blocks (with a remainder), remove the remainder to get an even number (do not round, you just want the bare integer), then finally multiply by 128 to get the sector number. This will give us the sector number we want our partition to start on.

<source lang="text">
92807568 + 127 = 92807695
</source>
<source lang="text">
92807695 ÷ 128 = 725060.1171875
</source>
<source lang="text">
int(725060.1171875) = 725060
</source>
<source lang="text">
725060 x 128 = 92807680
</source>

So now we know that sector number 92807680 is the first sector above 92807568 that falls on an even 64 KiB block. Now we need to alter our partition's starting sector. To do this, we will need to go into fdisk's extra functions.

Back in fdisk, type;

Extra options:
<source lang="bash">
Command (m for help): x
</source>

Change the start block:
<source lang="text">
Expert command (m for help): b
</source>

Change partition number 5:
<source lang="text">
Partition number (1-7): 5
</source>

Set the start block to 92807680;
<source lang="text">
New beginning of data (92807568-285603569, default 92807568): 92807680
</source>

Return to the previous menu;
<source lang="text">
Expert command (m for help): r
</source>

Print the new partition configuration and confirm that the start of partition 5 is where we want it.
<source lang="text">
Command (m for help): p
</source>
<source lang="text">
Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 63 530144 265041 83 Linux
/dev/sda2 530145 84421574 41945715 83 Linux
/dev/sda3 84421575 92807504 4192965 82 Linux swap / Solaris
/dev/sda4 92807505 488392064 197792280 5 Extended
/dev/sda5 92807680 285603569 96397945 83 Linux
/dev/sda6 285603633 478399634 96398001 83 Linux
/dev/sda7 478399698 488392064 4996183+ 83 Linux
</source>

Voila! Now write out the changes.
<source lang="text">
Command (m for help): w
</source>
<source lang="text">
The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
The kernel still uses the old table.
The new table will be used at the next reboot.
Syncing disks.
</source>

Now either run partprobe /dev/sda or reboot the server, which ever you feel more comfortable with. Personally, I like to reboot.

{{note|1=As you layer on storage layers, make sure that whatever block size they use can evenly divide into 64 KiB blocks. How you do this will depend on the storage layers you use.}}

== Creating a 64 KiB Aligned DRBD Resource ==

ToDo

= Post-Install Steps for Windows 2008 R2 Server =

Unlike Linux, which "just works", you will want to do a few things to optimize Windows on your cluster.

* Switch to "Test-signing" mode. This is required in order to install the drivers in the next step. '''DO NOT SKIP THIS STEP'''! Doing so could corrupt your Windows VM.

Open up a command prompt window and type:

Click in Start and the type cmd in the search bar.

<source lang="bash">
bcdedit /set testsigning on
</source>

[[Image:windows2008_r2_setting_test_signing_01.png|thumb|center|700px|Enabling "testsigning" mode in Windows 2008 R2.]]

Once done, you '''must''' reboot.

* Installing the drivers.

First, download the latest driver [http://www.meadowcourt.org/downloads/ from here]. You will want to pick the latest version with the name http://www.meadowcourt.org/downloads/gplpv_Vista2008x64_<version>.msi. At the time of this writing, the most recent version was
[http://www.meadowcourt.org/downloads/gplpv_Vista2008x64_0.11.0.308.msi gplpv_Vista2008x64_0.11.0.308.msi].


<source lang="bash">
</source>
<source lang="text">
</source>

{{footer}}

Windows 2008 R2 Xen domU Notes - Revision history

Digimer at 00:54, 2 September 2011

Digimer at 20:12, 31 August 2011

Digimer: Created page with "{{howto_header}} Installing a Windows 2008 R2 domU under Xen on an EL2 Cluster requires some extra planning to maintain optimal perfor..."