Skip to main content

XenEnterprise4 tested

Honestly, I am dug knee deep with my International Virtualization project where we have chosen VMware's ESX, and have not been able to find anytime at all to try out XenSource's. Geert found some time and has published some print screens.

It is a bit weird you can define more VCPUs than cores in the physical box. In the screenshot above I defined 4 vCPUs while the physical box (DL380 G5) only has one dual-core CPU. After doing that, the machine refused to boot and I had to revert to 2 vCPUs. Logical but the UI should prevent the user from making that choice.

You can note from the General tab's screenshot that the Virtualization: label reads Optimized. Like before, you have to install the XenSource tools in the Windows virtual machine to provide it with optimized drivers. The XenSource tools are on an iso (xs-tools.iso) that is automatically mounted when you select the option Install XenSource Tools from the VM menu in XenCenter.

Some quirkiness here and some quirkiness there. Looks like a viridian cousin to me, that one too did the 8 core show on the vid we showed you guys sometime back.

Anyways , here's to Geert's effort to spend some time with XenSource. link here.

Comments

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op

Virtualization is hot and sexy!

If this does not convince you to virtualize, believe me, nothing will :-) As you will hear these gorgeous women mention VMware, Akkori, Pano Logic, Microsoft and VKernel. They forgot to mention rackspace ;-) virtualization girl video I'm convinced, aren't you? Check out their site as well!