Tag: xcp

xenserver 7.0 based on centos 7.2

https://docs.citrix.com/content/dam/docs/en-us/xenserver/xenserver-7-0/downloads/xenserver-7-0-installation-guide.pdf states: 

 The Control Domain: Also known as 'Domain0', or 'dom0', the Control Domain is a secure, privileged Linux VM (based on a CentOS 7.2 distribution) that runs the XenServer management toolstack. Besides providing XenServer management functions, the Control Domain also runs the driver stack that provides user created Virtual Machines (VMs) access to physical devices.

apply xen server patches in bulk

download a bunch of the buggers


for file in XS*.zip;do foo=`basename -s .zip $file`; unzip $file; bar=`xe patch-upload file-name=${foo}.xsupdate`;xe patch-apply uuid=$bar host-uuid=YOUR_HOST_UUID;done

you’ll probably want to add an rm of the zip file and an rm of the xsupdate file (exercise for the reader)

This won’t work for XS70E002 and XS70E003 until you apply XS70E004 (read the release notes).

add iso partition to xenserver

link: https://adamscheller.com/systems-administration/xenserver-local-iso-storage-new-partition/

for posterity…

figure out the name of the volume group (something like name-uuid)

pvscan

 

create the new volume

lvcreate -L 150G -n ISOs name-uuid

 

find the volume you just created

 
lvscan |grep ISO

 

create the filesystem

mkfs.ext2 /dev/other-name-uuid/ISOs

 

make the mount point

mkdir /mnt/isos

 

create the repository

xe sr-create name-label=ISOs type=iso device-config:legacy_mode=true device-config:location=/mnt/isos content-type=iso

 

mount the disk

mount -t ext2 /dev/name-uuid/ISOs /mnt/isos

	


	







	

		
		
para – virtualize to install from iso
	


	
	
	

		
http://www.xenlens.com/boot-a-guest-vm-from-cd-or-dvd-in-xenserver/ copied for posterity


In order to boot from cd or dvd you need to change the guest virtualization type from HVM (fully virtualized) to PV (paravirtualized).


xe vm-param-set HVM-boot-policy="BIOS order" uuid=[uuid of your vm]


After you have booted from dvd, change back to fully virtualized mode:


xe vm-param-set HVM-boot-policy="" uuid=[uuid of your vm]

	


	





	

		
		
xen xcp xapi change from eth0 to eth1 (after you delete eth0 eth1 becomes eth0 orn reboot)
	


	
	
	

		
#get the uuid of the box you want to add the eth1 to

xe vm-list


#list the interfaces that are associated with that box

xe vif-list | grep 


#get list of network-uuids to pick from (in my case there are only 2)

xe vif-list |grep network-uuid| sort -u


# make the eth1 interface

vif-create  device=1 vm-uuid= network-uuid=


# plug in the eth1 interface (uuid from prior step)

xe vif-plug uuid=


# unplug the eth0 interface (uuid from step 2)

xe vif-unplug uuid=


#delete the eth0 interface (after a reboot your new eth1 will be eth0)

xe vif-destroy uuid=

	


	







	

		
		
xcp add disk
	


	
	
	

		
xe sr-list #gives you a list of sr’s from which to pick a sr-uuid


xe vdi-create sr-uuid= name-label= type=user virtual-size=

#the above vdi-create outputs a vdi-uuid


xe vm-list # gives you a list of vm’s from which to pick a vm-uuid


xe vbd-create vm-uuid= vdi-uuid= bootable=false mode=RW type=Disk device= #pick an unused device name (my box had “disks” up to xvdc so I used xvdd)

# the above vbd-create outputs the vbd’s uuid


xe vbd-plug uuid=

#your new devices should now be visible from your domU