If you add new physical network interface to the hardware that runs XenServer it won’t appear in XenCenter by default.
In order to attach it to VMs or change its settings you’ll need to type in a few commands to XenServer’s CLI.
1. Connect XenServer via SSH using root rights:
ssh email@example.com -v
2. Make sure that new NIC is attached to hardware and detected by Linux, in below command’s output you can see there are three Ethernet controllers (the last one was just attached to hardware):
[root@localhost ~]# lspci | grep -i ethernet
10:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
1e:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5723 Gigabit Ethernet PCIe (rev 10)
30:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
As you can see this NIC isn’t shown in XenCenter and below command doesn’t show its UID among detected interfaces:
root@localhost ~]# xe pif-list
uuid ( RO) : 095abcc1-4d64-7925-200f-a91d558ec872
device ( RO): eth1
currently-attached ( RO): true
VLAN ( RO): -1
network-uuid ( RO): 9da74476-ffcb-6824-25ad-62d46f34e252
Citrix XenServer is powerful hypervisor that is based on Linux (Redhat/Centos/Fedora family) and competes with Vmware ESXi and offer wide range of virtualization features for data centers. In general you can do a bare-metal installation of XenServer to your hardware server and create multiple virtual machines (VMs) inside XenServer host. Obviously you’ll need to have the possibility to boot VM from DVD-Rom to start installation of, let’s say, Linux Mint. You can do it using hardware DVD-Rom of the host XenServer or attach ISO image and make VM to boot into it.
By default XenServer can attach ISO images and make them available to VMs if ISOs are stored on a separate NFS server. In this post you’ll see how to avoid creation of NFS share and attach ISO image stored on XenServer host locally.
1. Connect to XenServer SSH service via management interface using root password:
where 192.168.1.99 is IP address of XenServer host.
2. Create directory where you will store ISO images and then exit from XenServer’s SSH.
3. Copy ISO images to newly created directory. I assume my readers are Linux users so you can use below command to transfer files via SSH. Btw, command is the same if you’re using OS X:
scp Downloads/your_image.iso firstname.lastname@example.org:/var/opt/xen/iso_import/ISO1
4. Make local ISO library available for VMs in XenServer:
xe sr-create name-label=ISO1 type=iso \
5. Make sure ISO_Library is attached to XenServer:
In case of success you’ll something like this in the output:
uuid ( RO) : 025c79f8-02dc-4950-8da5-d60f4675ca77
name-label ( RW): your_image.iso
name-description ( RW):
sr-uuid ( RO): 3caefbd6-8683-cc4b-e642-e3540d0fe13e
virtual-size ( RO): 168099840
sharable ( RO): false
read-only ( RO): true
That’s it, you’ll see new ISO in XenCenter after this step:
WARNING: When copying ISO images to XenServer’s local filesystem keep an eye on free disk space – XenServer allocates not to much gigabytes for hypervisor itself so three or four ISO images may take all free HDD space and cause problems with systems running in VMs. Use command ‘df -h /’ to get info about free space in root filesystem.