apaitu::server::configuration

intermittent communication failure between computers
that are running Windows XP or Windows Server 2003
http://support.microsoft.com/kb/904946/
To work around this problem, turn off checksum offloading on the network adapter. To do this, follow these steps:
1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
3. In the right pane, make sure that the DisableTaskOffload registry entry exists. If this entry does not exist, follow these steps to add the entry:
a. On the Edit menu, point to New, and then click DWORD Value.
b. Type DisableTaskOffload, and then press ENTER.
4. Click DisableTaskOffload.
5. On the Edit menu, click Modify.
6. Type 1 in the Value data box, and then press ENTER.
7. Exit Registry Editor.

—————-

2. Use the registry editor and locate the “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\xennet\nics” key.

3. Each key under nics will have an associated MAC address for each VIF.

4. Locate the “IPAddress” value and double click to edit.

5. The value contains two lines, one the IPv4 address of the interface and one an IPv6 address.

6. Delete the IPv6 address on the second line and leave the IPv4 address.

7. Under SubnetMask key, delete the corresponding subnet value for IPv6.

8. Reboot the VM.

—————–

1. Install the XenTools and reboot the VM.

2. Use the registry editor and locate the “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters\Interfaces” key.

3. Look at settings under each GUID to find the corresponding IPAddress and SubnetMask values.

4. Edit both the “IPAddress? and ?SubnetMask” value.

5. The value contains two lines, one the IPv4 address of the interface and one an IPv6 address.

6. Delete the IPv6 address on the second line and leave the IPv4 address.

7. Under SubnetMask key delete the corresponding subnet value for IPv6

8. Reboot the VM.

9. VM Networking, VIFs, and XenTools drivers should work as expected.

1) Retrieve the UUID on the GuestVM, say your GuestVM is drbd-01

[root@xenserver-home log]# xe vm-list name-label=drbd-01 params=uuid
uuid ( RO)    : da2a9648-732c-74d6-1cdf-a475a57acc88

2)  Enable the BIOS Order function

[root@xenserver-home log]# xe vm-param-set uuid=da2a9648-732c-74d6-1cdf-a475a57acc88 HVM-boot-policy=”BIOS order”

3) Go to the General Tab of your GuestVM
a) click Properties
b) click Startup Options
c) adjust Boot Order For CentOS.iso in virtual drive you have mounted with option under the GUI for the xenserver console.

Do all you want inside the Recovery

1) SCP the ISO files into the folder called /ISO or any folders that you like

2) symbol link it.
====
cd /var/opt/xen/iso_import
ln -s /opt/xensource/packages/iso/CentOS-5.3-i386-bin-DVD.iso .
====

3) rescan the ISO files folder.in order to have it appear under the XenServer Client Console

xe sr-create name-label=ISOs type=iso device-config:location=/var/opt/xen/iso_import device-config:legacy_mode=true content-type=iso

Done

xm create -c xen_1521

Assume that the tap disk is using xvda

1) losetup /dev/loop0 /vm/xen_xxx/data

where /vm/xen_xxx/data is your xen image

2) Once this is mounted, You can do a fdisk to check the partition inside /dev/loop0

3) kpartx -a /dev/loop0 to reload the partition layout

4)  mount /dev/mapper/loop0p1 /mnt to mount the partition into /mnt

Cheers.