Everything, Everything

2024: January February March
2023: J F M A M J J A S O N D
2022: J F M A M J J A S O N D
2021: J F M A M J J A S O N D
2020: J F M A M J J A S O N D
2019: J F M A M J J A S O N D
2018: J F M A M J J A S O N D
2017: J F M A M J J A S O N D
2016: J F M A M J J A S O N D
2015: J F M A M J J A S O N D
2014: J F M A M J J A S O N D
2013: J F M A M J J A S O N D
2012: J F M A M J J A S O N D
2011: J F M A M J J A S O N D
2010: J F M A M J J A S O N D
2009: J F M A M J J A S O N D
2008: J F M A M J J A S O N D
2007: J F M A M J J A S O N D
2006: J F M A M J J A S O N D
2005: J F M A M J J A S O N D
2004: J F M A M J J A S O N D
Hyper-V
Wednesday 14th April, 2010 16:34 Comments: 0
My first experience with Hyper-V didn't go very well, but in hindsight that was either down to network card drivers (possibly) or the fact I only had one network interface (probably the cause of my issues) when they recommend at least one interface is not used by Hyper-V.

But today's experience (with a server that has 2 NICs) was fantasic. Everything works. I even managed (after a bit of searching with Google to discover a VMC to Hyper-V import tool) to migrate a Windows 2003 SP2 VM created/running under Virtual Server 2005 SP1 to run under Hyper-V (it turns out that pre-SP2 is trickier to get up and running).

Quite happy :)
© Robert Nicholls 2002-2024
The views and opinions expressed on this site do not represent the views of my employer.
HTML5 / CSS3