Our first XEN-Experience, a XenServer 5.5 testdrive
As I am in the final week before my holiday and all projects are finished, I thought it might be a good idea to check out the competition. So I downloaded the free version of Citrix’s XenServer 5.5 to see what the fuss is all about.
First I tried to install it on a spare desktop at home (P4 2,4GHz CPU, 2GB RAM) but this failed, probably because the CPU doesn’t supply Intel VT.
Yesterday at work I grabbed two desktops with a Core2Duo E6400 with Intel VT and 4GB of RAM and installed Citrix XenServer 5.5 on it.
The installation is pretty straightforward, much like ESXi, and in about 5-10 minutes you will have a XenServer up and running. The first thing I noticed is that the console is very feature rich. We all know the yellow/gray console of an ESXi server and all you can do is basic configuration tasks like set an IP address, DNS server and default gateway, give the server its name, do a few tests and that’s about it. The console of a XenServer has a lot more features. Next to all ESXi-like features you can start and stop virtual machines, configure storage, resource pools and licensing, configure back-up, restore and updates.
Next step is installing XenCenter the VI client for XenServer. This is very simple and before you know it you have a management tool and you’re ready to add your first XenServer to it. And so I did, I added the XenServer I installed earlier and browsed through the various screens, tabs and settings. The first thing you will notice when you’re used to the VI Client and the vCenter interface is that XenCenter looks very similar but you miss a lot of features and settings. It was like I installed the vCenter or VI Client Lite edition.
At first glance the options I really like are the Power action icons on the Performance tab and the Undock/Redock option on the Console tab.
Next up was installing a virtual machine, so I inserted a Windows 7 RC DVD into my laptop’s DVD player to find that it is not possible to connect the client CD or DVD. I had to insert the DVD into the XenServer DVD player or create an ISO store and upload the DVD. A very big limitation in my opinion.
After a successful and fast Windows 7 installation I also installed a Windows Server 2008 R2 virtual machine and experimented with both. When I shutdown the Windows Server 2008 virtual machine I noticed a little flaw. After 5 minutes the console kept showing the screen with the text ‘Shutting down…‘ so I thought there was something wrong with my installation until I finally noticed the text above the console screen ‘This VM is currently shut down. Click here to start it.’ Nothing big but when I shutdown a virtual machine I want it power off, this is confusing. A simple screen refresh would have been nice.
After the confusing I decided to try out live migration so I installed a second XenServer and created a 50GB LUN on our Dell EqualLogic SAN. So far so good, but how to get iSCSI working? First we dug through the Admin guide and Anne Jan informed with his friend, Google. He found out that there is really no easy way (GUI) of doing this so we had to detach NICs and configure IP addresses using the command line.
When that was fixed we could connect to our shared storage and we connected it to our first XenServer. No problems, so we tried to move the virtual machine files to the shared storage and because we are using the free version of XenServer we do not have fancy features like storage migration. We had to copy the virtual machines to our shared storage and removed the old files, this takes 20 minutes but it works.
The next step is to perform a live migration so we tried to connect our 50GB LUN to our second XenServer. This FAILED because the LUN was already in use by the first XenServer. With the Hyper-V 2.0 TechNet presentation still in mind we initially thought that XenServer had inherited the same flaw as Hyper-V 1.o, non-cluster aware storage, but this time it was our own fault. XenServer has a more logical location to place shared storage which is to be used in a XenCenter Pool. All XenServers and attached storage which is used in a pool is connected and configured in that pool. So no more configuration of cluster (storage) resources on an individual host.
Finally we could try live migration of a virtual machine to a second XenServer and again it failed. Maybe ‘failed’ is not the correct term, the migration option is just not available, not grayed out, just NOT available. Strange, because all documentation and websites claim that the free version of XenServer does have live migration. Then I notice that the Windows 7 virtual machine did have the ‘Migrate to server‘ option and the Windows Server 2008 R2 virtual machine did not.
So what’s the difference? It turned out that I had not installed the Citrix Tools for Virtual Machines or in short XenServer Tools. WTF? Do I need the XenServer Tools to perform a live migration?
Very, very strange that the live migration support is provided by tools you need to install in a virtual machine. Why? What happens if I want to run an unsupported operating system? We already found out that when you run an unsupported Linux version, you will have to choose between HA or Linux. Does this mean that if I want to run an unsupported operating system, say Linux, I can NOT use HA or Live Migration? Two great virtualization features down the drain! Maybe someone can clear this up for me?
Ok, ok. This article is about unsupported Linux versions on Hyper-V. You may ask why would you run an operating system you know is unsupported? But sometimes you simply don’t have a choice and you will have to virtualize that old server or workstation because the old hardware is about to go up in flames. And ok, the article is about Hyper-V and not about XenServer but I wouldn’t be surprised if the test came out the same. I will certainly test this.
Conclusion: When looking at Citrix XenServer with VMware eyes like mine you cannot help to compare the two and look for XenServer features in VMware places but then I still think it is a product with a lot of potential but for now it still has a long way to go before they can seriously compete with VMware in all areas. Sure, with a customer you will have to asses if all features are necessary but even then the product doesn’t give me the confidence to run a large enterprise environment. But maybe that’s just me and I need some more experience with the product and have a go with the Citrix Essentials pack.
What is really like is the feature rich XenServer console where you can start/stop a virtual machine, configure storage, resource pools and licensing, configure back-up, restore and updates. This is something I miss in VMware’s ESXi, that console is very limited so for virtual machine actions or configuration tasks you will need to access the ESXi server using the VI client.
What I do not like or miss is the option to connect your client CD/DVD to a virtual machine, the lack of iSCSI configuration options in the GUI and the need for XenServer Tools to enable Live Migration.
A test drive with the Essentials Pack is planned after my holiday so check out www.VMGuru.nl and we will keep you posted.
Tags In
Related Posts
32 Comments
Leave a Reply Cancel reply
You must be logged in to post a comment.
Hi VMGuru,
Nice post… But IP for iSCSI can be configured using XenCenter… and linux is supported by XenServer (RedHat, Suse, CentOS, Oracle, Debian)…
Just need some better learning the product before going to use it…
And I can say that with 1/10 of the ours need to use VMWare.
Hi VMGuru,
Nice post… But IP for iSCSI can be configured using XenCenter… and linux is supported by XenServer (RedHat, Suse, CentOS, Oracle, Debian)…
Just need some better learning the product before going to use it…
And I can say that with 1/10 of the ours need to use VMWare.
Do yourself a great favor and read the manual BEFORE posting a blog, since many
of us did.
Also FYI Xen was invented in the Linux world so for you to question Xen’s Linux support in any way (even a symbolic way for unsupported OSs) is absurd.
Do yourself a great favor and read the manual BEFORE posting a blog, since many
of us did.
Also FYI Xen was invented in the Linux world so for you to question Xen’s Linux support in any way (even a symbolic way for unsupported OSs) is absurd.
What Erik meant to say I think was that, although you can configure iSCSI from the GUI, it is not very clear how you dedicate one of your network cards with a specific IP address to your storage LAN. FYI, the info how to do it from the commandline came from the admin guide.
We really want a clear seperation between the storage LAN and the rest of the network. No routing, no VLANning, just seperate networks.
If you do know how to do this through the GUI, please tell. It is somewhat absurd that we had to do it by commandline.
About the statement on the unsupported Linux flavors: Yeah, Xen does come from the Linux community, yeah, a lot of Linux distributions are supported as a guest operating system BUT if you use an unssuported Linux distribution (and yes, there are much, much more than that are on the list) you have the situation as Erik described. If this is not true, please tell how it is really working then.
One of the things we try to avoid with this blog is to bash other hypervisors. Ok, we are a little biased, but if we are wrong about certain things we will acknowledge that we were in error. Just saying that we are just wrong and should read the admin guide doesn’t help us, you, or the community. It just fuels the feeling if you are Pro VMware you should be against Hyper-V and Xen, which is very bad for all of us.
What Erik meant to say I think was that, although you can configure iSCSI from the GUI, it is not very clear how you dedicate one of your network cards with a specific IP address to your storage LAN. FYI, the info how to do it from the commandline came from the admin guide.
We really want a clear seperation between the storage LAN and the rest of the network. No routing, no VLANning, just seperate networks.
If you do know how to do this through the GUI, please tell. It is somewhat absurd that we had to do it by commandline.
About the statement on the unsupported Linux flavors: Yeah, Xen does come from the Linux community, yeah, a lot of Linux distributions are supported as a guest operating system BUT if you use an unssuported Linux distribution (and yes, there are much, much more than that are on the list) you have the situation as Erik described. If this is not true, please tell how it is really working then.
One of the things we try to avoid with this blog is to bash other hypervisors. Ok, we are a little biased, but if we are wrong about certain things we will acknowledge that we were in error. Just saying that we are just wrong and should read the admin guide doesn’t help us, you, or the community. It just fuels the feeling if you are Pro VMware you should be against Hyper-V and Xen, which is very bad for all of us.
@Sergio:
If iSCSI can be configured using the GUI, please let me know how. I can configure a few iSCSI items but as Anne Jan states we want to separate iSCSI from other traffic and need a second nic with IP address. According to the admin guide this was the was to go. If you have an easier way please let me know.
With regards to the comment on Linux support, I know a lot of Linux versions are supported but there will definitely be some versions that are not support. The point I was trying to make is that you need the integration tools for live migration, what if your operating system isn’t supported. And if that operating system is RedHat, Suse, windows 98, Windows NT, OS/2 or whatever doesn’t matter.
On the hours spend trying to master XenServer, ok maybe it takes less time but the product is not as complete as VMware ESX/vSphere is. So the comparison does not hold.
Nevertheless, I took a testdrive with XenServer 5.5 and I did like what I saw. The product can not be compared to the full featured VI/vSphere suite but it certainly has potential.
Thanks for the feedback and I hope you will return and tell us how to configure iSCSI in a seperate network from the GUI.
@Sergio:
If iSCSI can be configured using the GUI, please let me know how. I can configure a few iSCSI items but as Anne Jan states we want to separate iSCSI from other traffic and need a second nic with IP address. According to the admin guide this was the was to go. If you have an easier way please let me know.
With regards to the comment on Linux support, I know a lot of Linux versions are supported but there will definitely be some versions that are not support. The point I was trying to make is that you need the integration tools for live migration, what if your operating system isn’t supported. And if that operating system is RedHat, Suse, windows 98, Windows NT, OS/2 or whatever doesn’t matter.
On the hours spend trying to master XenServer, ok maybe it takes less time but the product is not as complete as VMware ESX/vSphere is. So the comparison does not hold.
Nevertheless, I took a testdrive with XenServer 5.5 and I did like what I saw. The product can not be compared to the full featured VI/vSphere suite but it certainly has potential.
Thanks for the feedback and I hope you will return and tell us how to configure iSCSI in a seperate network from the GUI.
@Ron Kuper:
We are blogging on our first experience on, for us, a new product and I did read the manual. Maybe it would be nice of you to be less patronizing and correct us where we are wrong. The nice thing about a community like I experience it in the VMware communities is that everybody wants to help. Doesn’t matter if you’re a noob or an expert. If you don’t have anything to add to the community don’t respond.
I hope (and think) that your response is not indicative for the Citrix Xen community and our experience with it will be as pleasant as the VMware communities are.
As on the Linux support, I will repeat what I said to Sergio: I know a lot of Linux versions are supported but there will definitely be some versions that are not support. The point I was trying to make is that you need the integration tools for live migration, what if your operating system isn’t supported. And if that operating system is RedHat, Suse, windows 98, Windows NT, OS/2 or whatever doesn’t matter.
@Ron Kuper:
We are blogging on our first experience on, for us, a new product and I did read the manual. Maybe it would be nice of you to be less patronizing and correct us where we are wrong. The nice thing about a community like I experience it in the VMware communities is that everybody wants to help. Doesn’t matter if you’re a noob or an expert. If you don’t have anything to add to the community don’t respond.
I hope (and think) that your response is not indicative for the Citrix Xen community and our experience with it will be as pleasant as the VMware communities are.
As on the Linux support, I will repeat what I said to Sergio: I know a lot of Linux versions are supported but there will definitely be some versions that are not support. The point I was trying to make is that you need the integration tools for live migration, what if your operating system isn’t supported. And if that operating system is RedHat, Suse, windows 98, Windows NT, OS/2 or whatever doesn’t matter.
One response by one person is never indicative of any community.
One response by one person is never indicative of any community.
You need to be clear what you are comparing here, is it XenServer 5.5 free edition to ESXi or XenServer to vCenter?
If it’s to ESXi you need to say that Xen has live migration whereas VMware doesn’t.
If it’s to vCenter, you need to mention the price difference.
You need to be clear what you are comparing here, is it XenServer 5.5 free edition to ESXi or XenServer to vCenter?
If it’s to ESXi you need to say that Xen has live migration whereas VMware doesn’t.
If it’s to vCenter, you need to mention the price difference.
@Jim Moyle:
Your feedback is 100% correct but the intention of this article is to blog on our experience with XenServer. It is not the intention to do a full comparison.
For a full comparison see our Hypervisor comparison.
@Jim Moyle:
Your feedback is 100% correct but the intention of this article is to blog on our experience with XenServer. It is not the intention to do a full comparison.
For a full comparison see our Hypervisor comparison.
@Tazz I can appreciate that it’s not a comparison post, but it is a little confusing, also as far as I can see Xenserver without essentials isn’t on your hypervisor comparison checklist.
@Tazz I can appreciate that it’s not a comparison post, but it is a little confusing, also as far as I can see Xenserver without essentials isn’t on your hypervisor comparison checklist.
I’m still waiting for someone to tell me how to setup an iSCSI IP address using the GUI.
I’m still waiting for someone to tell me how to setup an iSCSI IP address using the GUI.
@Jim Moyle: When you look at the comparison sheet at the 2 colums for Citrix. The first 2 lines got a *1. At the bottom of the sheet you can find some comment meaning that the feature is provided with an addon, essentials in this case.
Further more the comparison is for Enterprise hyporvisors. The essentials for Xenserver are needed to make it Enterprise ready.
@Jim Moyle: When you look at the comparison sheet at the 2 colums for Citrix. The first 2 lines got a *1. At the bottom of the sheet you can find some comment meaning that the feature is provided with an addon, essentials in this case.
Further more the comparison is for Enterprise hyporvisors. The essentials for Xenserver are needed to make it Enterprise ready.
Errm..
Setup the network cards using the networks tab when you have the xenpool selected so you have access to the storage lan or vlan..
right click the xenpool and select new storage repository and walk through the wizard?
Unless im being stupid im pretty sure it is that easy. we have quite a few setups using iscsi.
I would fire up a test machine and test it but its not really that hard.
Errm..
Setup the network cards using the networks tab when you have the xenpool selected so you have access to the storage lan or vlan..
right click the xenpool and select new storage repository and walk through the wizard?
Unless im being stupid im pretty sure it is that easy. we have quite a few setups using iscsi.
I would fire up a test machine and test it but its not really that hard.
I too was stuck on this issue as I just installed XEN today. Deep in the manual there is nomenclature that is different as I was used to creating new Network Interfaces and assigning them IP’s in XEN you need to “configure a new management interface” :
To configure a new management interface
1. Select the server in the Resources pane then do one of the following:
– On the Server menu, click Management Interfaces and then click New Interface.
– Click on the NICs tab and then click Help me dedicate a NIC, below the list of NICs.
2. Enter the name of the new interface. (iSCSI)
3. Choose a network from the Network list. (Select the interface)
4. Configure the IP settings for the new interface. You must enter an IP address, but the Subnet mask and Gateway settings are optional.
5. To configure further management interfaces, click New Interface and repeat the configuration steps above.
6. When you have finished, click OK.
Hope this helps others.
I too was stuck on this issue as I just installed XEN today. Deep in the manual there is nomenclature that is different as I was used to creating new Network Interfaces and assigning them IP’s in XEN you need to “configure a new management interface” :
To configure a new management interface
1. Select the server in the Resources pane then do one of the following:
– On the Server menu, click Management Interfaces and then click New Interface.
– Click on the NICs tab and then click Help me dedicate a NIC, below the list of NICs.
2. Enter the name of the new interface. (iSCSI)
3. Choose a network from the Network list. (Select the interface)
4. Configure the IP settings for the new interface. You must enter an IP address, but the Subnet mask and Gateway settings are optional.
5. To configure further management interfaces, click New Interface and repeat the configuration steps above.
6. When you have finished, click OK.
Hope this helps others.
Thanks for the feedback
Thanks for the feedback
thank you for your article, this is the good information
thank you for your article, this is the good information
Hi.
Nice article, but allow me to add some things…
You can use all the advanced features (live migration, etc) on unsupported linux distros, you'll have to first make them paravirtualized yourself. The provided templates already have all the settings for the guest operating system (and this settings are a lot more than only the boot parameters), but you are free to create your own templates (in fact, that is why the option is there). There are some howto's in the forums explaining how to setup, say, an ubuntu paravirtualized vm.
About the iSCSI, I failed to understand where the problem is… You go and click “new storage” on XenCenter, you chose iSCSI, then you put the IP address and whatever more is needed according to your configuration and that's it.
Also, your first installation failed because you were using a 32Bit CPU. XenServer requires a 64Bit CPU and AMD-V / Intel-VT is only needed if you want to run Windows guests (for linux guests you don't need that).
Forget Linux, what about Windows NT4 or 98? People probably laugh about it but i still see them around.
Same goes for Novell.
ps. good post!