Archive for October, 2007

VMworld Open 365 Days of the Year

Thursday, October 4th, 2007

“VMworld.com now extends the success of the VMworld conference to an online virtualization destination open to anyone to learn and share what they know about virtualization. VMworld.com is an independent virtualization resource available 24×7. While not a replacement for the unique face-to-face networking opportunity of the conference, you can now get access to valuable information and conference sessions, talk with vendors, get tips and tricks from other virtualization users, and hear the latest virtualization buzz every day online. Access the latest resources and information you need to make informed decisions about implementing virtualization.” 

Link:

http://www.vmworld.com

 

The Old Chestnut: Microsoft Support for Virtualisation

Wednesday, October 3rd, 2007

Although I am now thru-and-thru a VMware guy, I still stay subscribed to all those newsletters on matters relating to vendors I used to teach/consult in – including Novell, Microsoft and Citrix. Windows IT Pro has an interesting blog entry from Karen Forster which outlines her woes in getting support for ISA Server and RRAS in a VM. You can read the full article here:

Link: Very long url here

What I thought was interesting about Karen’s article was a couple of things. As you might imagine WindowITpro is quite “pro” (if you forgive the pun) Microsoft, but even these guys are getting frustrated with Microsoft level of support. Secondly, Karen’s article has generated an offical MS responses – and lastly that response does appear to suggest that MS is moving to a more “privileged” level/quality of support for people who run Windows in a MS VM, as opposed to a “3rd Party” virtualisation layer (read: VMware!).  The two KB articles are these:

http://support.microsoft.com/kb/897615/ (Non-Microsoft Virtualization)
http://support.microsoft.com/kb/897613  (Microsoft Virtualization)

The key phrase in 897613 is “Microsoft supports Windows Server System software running within a Microsoft Virtual Server environment subject to the Microsoft Support Lifecycle policy and use of the virtual hard disk (.vhd) format. We will make commercially reasonable efforts to investigate the issue and, if necessary, attempt to reproduce the issue on the appropriate hardware.”

Whereas the key phrase in 897615 is “Microsoft does not test or support Microsoft software running in conjunction with non-Microsoft hardware virtualization software. For Microsoft customers who do not have a Premier-level support agreement, Microsoft will require the issue to be reproduced independently from the non-Microsoft hardware virtualization software. Where the issue is confirmed to be unrelated to the non-Microsoft hardware virtualization software, Microsoft will support its software in a manner that is consistent with support provided when that software is not running in conjunction with non-Microsoft hardware virtualization software.

For Microsoft customers who have a Premier-level support agreement, Microsoft will use commercially reasonable efforts to investigate potential issues with Microsoft software running in conjunction with non-Microsoft hardware virtualization software. As part of that investigation, Microsoft may require the issue to be reproduced independently from the non-Microsoft hardware virtualization software. Where issues are confirmed to be unrelated to the non-Microsoft hardware virtualization software, Microsoft will support its software in a manner that is consistent with support provided when that software is not running in conjunction with non-Microsoft hardware virtualization software.”

No doubt many corporates will continue to sign “end-to-end” agreements with their hardware vendors – so their hardware, VMware and VMs are fully supported by one vendor – rather than having to wade through the mine-field of MS support.

More VMworld ESX3i Memory Stick Experiments

Tuesday, October 2nd, 2007

If like me you picked up the VMworld ESX3i Beta Memory stick a couple of weeks ago. It might interest you to know that it can be duplicated to an image file (IMG) and mounted using an ILO’s “Virtual Media” feature. I used the Linux command DD (device to device) to duplicate the memory stick. I did try to pick up more than one of the memory sticks offered to delegates at VMworld. I wanted 4 for each of my HP DL 385 and another two for some instructor buddies of mine. Unfortunately, there was no extra memory sticks “going spare”. Fortunately, duplicating the memory stick was very easy.

I inserted the memory stick into one of my ESX hosts, and worked out the Linux Dev(ice) name. This was easy to do using dmseg | grep ‘removable disk’ (note the single ‘ quotes are required). This returned the information

“Attached scsi removable disk sdk at scsi1, channel 0, id 0, and lun 0″

So now I knew the memory stick was /dev/sdk. I used fdisk -l /dev/sdk to double check I had found the correct device/disk. I then used the dd command to duplicate the stick with dd if=/dev/sdk of=/tmp/esx3i-beta.img. Next I upload the IMG file to shared location on a Windows file server and mounted it with my HP ILO’s virtual media options using “Floppy Disk” as the type. I was able to configure the servers root password, hostname and network settings.

I doubt this duplication process sticks to the absolute letter of the EULA. But as I am using the IMG internally and not distributing it then I don’t see the problem, and did ask very politely for more than one memory stick. :-)

VMworld ESX3i Memory Stick Experiments

Tuesday, October 2nd, 2007

Today I finally got some quality time with ESX3i using the memory stick. I’ve been working on documenting the current usage of ESX3i beta. Unfortunately, I am not at liberty to release this document as I am covered by the restrictions of the Beta Programme and the EULA. However, I don’t think what I am about write breaches that (at least I hope not!) :-)

Anyway, it states very clearly on the ESX3i packaging/release notes that the ESX3i Beta is NOT yet VirtualCenter 2.0.2 aware. I can confirm this is the case because I gave it a try. Although I got through the “Add Host” wizard – the process does not complete and ends with “The host type is not supported, or was added to a cluster but does not support clustering”.

As result this currently means I am limited to managing the ESX3i host using the Vi Client that comes with ESX3i web-welcome-page.

Student Tip: Stopping WinSCP filepart errors

Monday, October 1st, 2007

Last week a student on my course gave me a tip. Personally, I perfer to use Veeam’s FastSCP for ESX Server when transferring files from my Windows Desktop to ESX 3. However, occasionally in the lab environments I work in I have to use WinSCP which is slower. One thing I have observed is if I copy a file such as an ISO to a VMFS volume, then WinSCP gives me an error. Basically, what happens is though the files get copied to the VMFS volume – and error occours when renaming the file from say – w2k3sp2.iso.filepart to w2k3sp2.iso. This is caused by the “Resume” feature in WinSCP which is intended to pickup an upload when it fails from where it failed, rather than starting the upload from the beginning. It appears as VMFS doesn’t support this functionality.

The solution to this problem is a work-around. To disable the “Resume” feature in the WinSCP software. I don’t mind doing this. Everything is gigabit in the lab environments I work in and very reliable so I don’t really need the resume feature. To disable the WinSCP “Resume” feature do the following:

In the menu choose, Options and Preferrences
Under Transfer, select Resume
Under “Enable transfer resume for”, select Disable
Under “Automatic Reconnect“, disable “Automatic reconnect session, if it breaks during transfer

Using ESXTOP to collect performance statistics

Monday, October 1st, 2007

RTFM Reader and regular contributor, Michael Knight has contacted me with some experiences and resources concerning gathering performance statistics using esxtop at the Service Console. It’s taken me sometime to blog about this, as I have been so busy with other work – Sorry about that Michael. Anyway, this is what Michael found:

“I was recently involved in trying to troubleshoot a VM that was performing badly. During the investigation I was experimenting with methods of capturing statistics of the Host and resident VMs both from VC and ESX. I was interested in capturing the %RDY time of a VM to determine if the VM was being hindered by others on the same host. For some reason VC reports a ready time in milliseconds and not a percentage like ESXTOP which was hard to interpret easily.
 
Whilst tinkering I discovered that by running ESXTOP in batch capture mode for a period I could stop the capture and then load the data file straight into Microsoft’s Perfmon tool and then manipulate the various counters I was interested in if as the data was from a Windows machine. Obviously the VI3 platform has different counters but it using a familiar tool it was easier to track the info.
 
I have created a spreadsheet listing the available Perfmon counters. Some are self explanatory others lack detail at this time.  The information captured looks more extensive than the interactive esxtop or VC performance data. ESXTOP batch mode can be invoked as   esxtop -b > /tmp/myesxtop.csv
 
Please note that depending on your sample rate these files can grow very large.”

You can download Michael’s XL spreedsheet from here



Podcast

LinkedIn

If you want to add Mike Laverick on LinkedIn, click on this button:

Mike Laverick

Categories

My Pages

Archives

Other VMware Bloggers