http://jeremywaldrop.wordpress.com/2008/10/28/how-to-build-a-windows-2008-vmware-esx-vm-template/
Excellent. I think some of the decisions are little odd (turn off the firewall?!?), but this covers a lot of ground.
The bits of the IT world that apply to me right now. Blogged in the hope that someone (even me) will find them useful.
Showing posts with label qemu. Show all posts
Showing posts with label qemu. Show all posts
Monday, June 20, 2011
How to build a (modern) Windows Server
Labels:
2008,
appliances,
esx,
esxi,
qemu,
rPath,
virtualisation,
virtualization,
Vista,
vmware,
win2k8,
windows
Friday, June 06, 2008
Vista and VMWare network irritation
I've been working with VMWare a bit recently, on my machines. As both the machines I use are relatively new, they came with Vista. Vista has been irritating, but less so than a downgrade.
Vista wants to describe and categorize all the network interfaces. Unfortunately, that includes the virtual network adapters that VMWare sets up (and probably the same for Windows qemu users fiddling with openvpn for its TAP implementation); and it gets its knickers in a twist because they don't seem to lead anywhere. The solution for Vista (pre-SP1) was to take advantage of a bug and add bogus default gateways to the virtual interfaces. The solution for Vista SP1 is more involved, but at least seems more "proper".
Essentially, you need to hack the Windows registry and tell Vista that these interfaces aren't leading anywhere. This seems a bit odd, as there may be an extensive network infrastructure of VMs; but that's it.
Use the registry editor of your choice and follow this:
http://communities.vmware.com/message/916766#916766
Vista wants to describe and categorize all the network interfaces. Unfortunately, that includes the virtual network adapters that VMWare sets up (and probably the same for Windows qemu users fiddling with openvpn for its TAP implementation); and it gets its knickers in a twist because they don't seem to lead anywhere. The solution for Vista (pre-SP1) was to take advantage of a bug and add bogus default gateways to the virtual interfaces. The solution for Vista SP1 is more involved, but at least seems more "proper".
Essentially, you need to hack the Windows registry and tell Vista that these interfaces aren't leading anywhere. This seems a bit odd, as there may be an extensive network infrastructure of VMs; but that's it.
Use the registry editor of your choice and follow this:
http://communities.vmware.com/message/916766#916766
Subscribe to:
Posts (Atom)