I was not aware that you could not install WinXP SP2 or earlier versions as a VM on Microsoft’s Hyper-V servers. I haven’t had the opportunity to play with Hyper-V yet, so I I’ll attribute missing this fact to not having the need to know. I’m sure there are a bunch of administrators in the same stage of evaluation as me. Hopefully this post will not be old news to most. XP SP3 will become available for download this week as an optional update. Microsoft will begin pushing XP SP3 to everyone that has Windows Update set to Automatic in early June.
The problem with installing XP SP2 on Hyper-V is that you can not install Integration Services (also called VM Additions or VMtools by other vendors), and without Integration Services you do not have network adapters in the VM. Christian Saborío sums up the problem in his post titled How to Install Integration Services on a Virtual Machine without Windows XP SP3.
“The problem happened when importing a Virtual hard disk that I had that had Windows XP SP2. See, in order for a VM to take full advantage of Hyper-V, you need to have the Integration Services installed (these are the new Virtual Machine Additions, in Virtual Server lingo). In order to install the Integration Services, I needed to have Windows XP SP3 – which I could easily download; but the VM did not had network support. Why? Because it needed Integration Services…see where I am getting at here?”
Christian explains that he was able to slipstream an .iso of XP with SP3 and, after a new install he had a running VM.
Microsoft announced that XP SP3 will be generally available this week. I found the following useful info Continue reading
Anybody remember the buzz about Daylight Savings in 2007? Hopefully nobody will have issues this year, but in case someone needs it or just wants to reminisce here are some links from last year:
VMware’s KB article lists the ESX versions that comply with the new DST: Continue reading
One of the cool things about this blog is I am communicating with and learning from virtualization professionals all over the world. Recently I received an email from a reader in the UK, Mohammad, who notified me of a couple ESX 3.5 upgrade issues he has experienced. One of his issues, and the topic of this post, is a painful example of the need to understand the compatibility matrixes published by VMware before upgrading to VI3.5.
From Mohammad’s email:
It’s not as simple as in Windows VMs !
This guide is the combined instructions found from the guides at:
I started with a fresh install of Fedora 7. I used the LiveCD and installed it to the VM hard disk. I did not apply the 210 package updates or the security updates. (Who says Linux doesn’t have be patched as often as windows?)
Note: I was unable to get the shared folders or the fast network driver feature to work. I’ve never been able to get these features working properly, but I’ve never really needed them to. The VMtools will load without these features anyways. I assumed that the sections for fixing the vmxnet module would finally make this work, but it did not. I might have done something wrong so I kept those sections in these instructions in case someone else gets it to work.
After installing VMware tools in a Linux VM, if X windows will not start and you get an error similar to “undefined monitor vmware”, then you need to manually modify the xorg.conf file.
Do the following:
1. Edit the X config file
2. Add the lines
3. Restart X
[ad] Empty ad slot (#1)!