HP BL680c XenServer Virtual Machine Installation 4.1.0 - Page 25

Preparing to clone a Linux VM, 4.6.1. Machine Name, 4.6.2. IP address

Get HP BL680c - ProLiant - G5 PDF manuals and user guides
UPC - 884420396314
View all HP BL680c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 25 highlights

Installing Linux VMs It is important to install this agent and keep it up-to-date (see Chapter 5, Updating VMs) as you upgrade your XenServer host. Procedure 4.4. To install the guest agent 1. The files required are present on the built-in xs-tools.iso CD image, or alternatively by using the "Install Tools" option in XenCenter. 2. Mount the image into the guest via: mount /dev/xvdd /mnt 3. Execute the installation script as the root user: /mnt/Linux/install.sh 4. If the VM was upgraded from XenServer 3.1, you will also need to run: chkconfig xengmond off 5. If the kernel has been upgraded, or the VM was upgraded from a previous version, reboot the VM now. Note CD-ROM drives and ISOs attached to Linux Virtual Machines appear as /dev/xvdd instead of as / dev/cdrom as you might reasonably expect. This is because they are not "true" CD-ROM devices, but normal devices. When the CD is ejected by either XenCenter or the CLI, it hot-unplugs the device from the VM and the device disappears. This is different from Windows Virtual Machines, where the CD remains in the VM in an empty state. 4.6. Preparing to clone a Linux VM When a Linux VM is cloned, some virtual hardware parameters are changed in the new VM. The VM may need to be customized in order to be aware of these changes. For instructions for specific supported Linux distributions, please see Section 4.9, "Release Notes". 4.6.1. Machine Name Of course, a cloned VM is another computer, and like any new computer in a network, it must have a unique name within the network domain it is part of. 4.6.2. IP address A cloned VM must have a unique IP address within the network domain it is part of. This is not a problem in general if DHCP is used to assign addresses; when the VM boots the DHCP server will assign it an IP address. If the cloned VM had a static IP address, the clone must be given an unused IP address before being booted. 20

  • 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
Installing Linux VMs
20
It is important to install this agent and keep it up-to-date (see Chapter 5,
Updating VMs
) as you upgrade
your XenServer host.
Procedure 4.4. To install the guest agent
1.
The files required are present on the built-in
xs-tools.iso
CD image, or alternatively by using the
“Install Tools” option in XenCenter.
2.
Mount the image into the guest via:
mount /dev/xvdd /mnt
3.
Execute the installation script as the root user:
/mnt/Linux/install.sh
4.
If the VM was upgraded from XenServer 3.1, you will also need to run:
chkconfig xengmond off
5.
If the kernel has been upgraded, or the VM was upgraded from a previous version, reboot the VM now.
Note
CD-ROM drives and ISOs attached to Linux Virtual Machines appear as
/dev/xvdd
instead of as
/
dev/cdrom
as you might reasonably expect. This is because they are not "true" CD-ROM devices,
but normal devices. When the CD is ejected by either XenCenter or the CLI, it hot-unplugs the
device from the VM and the device disappears. This is different from Windows Virtual Machines,
where the CD remains in the VM in an empty state.
4.6. Preparing to clone a Linux VM
When a Linux VM is cloned, some virtual hardware parameters are changed in the new VM. The VM may
need to be customized in order to be aware of these changes. For instructions for specific supported Linux
distributions, please see Section 4.9, “Release Notes”.
4.6.1. Machine Name
Of course, a cloned VM is another computer, and like any new computer in a network, it must have a unique
name within the network domain it is part of.
4.6.2. IP address
A cloned VM must have a unique IP address within the network domain it is part of. This is not a problem
in general if DHCP is used to assign addresses; when the VM boots the DHCP server will assign it an IP
address. If the cloned VM had a static IP address, the clone must be given an unused IP address before
being booted.