Tuesday, October 7, 2008
Wednesday, October 1, 2008
Tuesday, September 30, 2008
Well, the role installs, and I can create Hyper-V virtual machines, but I can't start them:
Note that I have two VMs running. The main VM in the screen shot is my Server 2008 Enterprise Full Domain Controller while the Server 2008 x64 Enterprise Core Hyper-V server. I made the same modification to the Core VMX as I did for the ESXi-3 VM from my earlier post. The Hyper-V role installed and updated fine. As you can see from the screen shot, I was able to manage Hyper-V remotely and create a VM. When I connect to the VM to start it, it displays the error message that it cannot create the partition because of an unspecified error 0x80004005. There aren't many search results about this error with Hyper-V other than two forum posts (one of which I posted an updated error message). There are some results about the error code.
I attempted the same thing in a Full installation and the Hyper-V installation was prevented by ServerManager. Is possible that ocsetup, the utility which installs Hyper-V in CORE does not properly detect VT and DEP capabilities and thus allows installation on non-Hyper-V supported hardware? I ran ocsetup on the Full installation, and the role installs just fine....
An error occurs upon attempting to start the VMbus:
John Howard mentions that this could happen if resources are scarce. In my instance, I confirm that it is unsupported hardware with no driver:
Looks like Hyper-V isn't actually running. Apparently ocsetup doesn't prevent installation of Hyper-V as ServerManager does...
I stumbled upon a post about running ESX inside of VMware Workstation. While I'm not sure of the practicality behind recursive virtualization, I want to see this working. This post is a walkthrough of my ESXinsideWS process.
Saturday, September 27, 2008
Tuesday, September 16, 2008
Microsoft says, "You can create a custom content provider for cases where the default provider is not sufficient (for example when using Transport Server to deploy an operating system from inside a .vhd image). See the Windows Server 2008 SDK for guidelines and samples for authoring and registering the provider." I'm going to investigate custom content providers for the purposes of transmitting a template repository version and talk about custom content providers in future post.