An alternative approach would be leave the file unprotected, and re-applying this modification after Citrix-supplied updates have been applied. However, this may cause updates provided by Citrix to fail at the point of installation. This means that the file cannot be overwritten, prevents the loss of this modification in the event of a system update. The "chattr" line above makes the replacement file "immutable". If you now shutdown and re-start your Citrix virtual machines, they will have an emulated e1000 device. Then chmod (to make it executable) and chattr it (to stop it being overwritten): Then make a replacement /usr/lib/xen/bin/qemu-dm file like /usr/lib/xen/bin/qemu-dm.orig $newstring # mv /usr/lib/xen/bin/qemu-dm /usr/lib/xen/bin/qemu-dm.orig Then do the following:įirst rename /usr/lib/xen/bin/qemu-dm to /usr/lib/xen/bin/qemu-dm.orig It implements an 'OS bypass' mechanism, where fast path processing and rx/tx data transfers are performed without kernel assistance (i.e.
#XENSERVER 6.5 INTEL E1000 NIC DRIVER#
You'll need to ssh into your Citrix server and become root. User-space E1000 driver library LibE1000 is a user-space library for Intel Gigabit Ethernet adapters. This emulation mode is available under Citrix XenServer, but is a hidden feature, due to hard-coding of the Realtek driver option. Apart of the additional speed, this device also supports jumbo ethernet frames. Apart of the additional speed, this device also supports jumbo ethernet frames. Those familiar with the open source version of Xen will know that the underlying QEMU device emulation that Xen uses can emulate an Intel 1Gbit/sec adapter, called 'e1000'. Those familiar with the open source version of Xen will know that the underlying QEMU device emulation that Xen uses can emulate an Intel 1Gbit/sec adapter, called "e1000".
![xenserver 6.5 intel e1000 nic xenserver 6.5 intel e1000 nic](https://2.bp.blogspot.com/-z6VxyVmgC-Y/VHiAx1Cwy0I/AAAAAAAABp0/P5aByoXjImI/s1600/SearchVMwareHCL1.png)
Sure, you can go and rebuild your kernel with the right paravirtualised drivers, but that's not always an option. However, if you're running a system with a customised non-standard kernel that doesn't support Citrix Xen paravirtualisation, you'll be stuck with a 100Mbit/sec bottleneck in your network. The paravirtualised drivers will outperform any emulated device.
![xenserver 6.5 intel e1000 nic xenserver 6.5 intel e1000 nic](https://www.tecmint.com/wp-content/uploads/2016/07/Select-XenServer-7-Installation-Source.png)
![xenserver 6.5 intel e1000 nic xenserver 6.5 intel e1000 nic](https://blogs.serioustek.net/wp-content/uploads/2016/07/Capture-2.png)
Under these Linux operating systems, your entire kernel must be replaced by a Citrix supplied kernel. This is usually a very good idea and just fine if you're using Windows, or a major supported OS such as Red Hat, CentOS or Ubuntu.
#XENSERVER 6.5 INTEL E1000 NIC INSTALL#
The standard device that is emulated is a Realtek 8139 (RTL8139), which is a 100Mbit/sec Fast Ethernet card.Ĭitrix themselves do not view this as a major issue, as they expect you to install paravirtualised drivers within your guest operating system. The commercial version of the Citrix XenServer does not allow you to choose the type of ethernet adapter to emulate within your VM. If you choose to follow this guide, you do so at your own risk. The following howto describes modification to critical system software.