Hyper-V Program Manager
Anyone who has installed Linux on Virtual PC / Virtual Server knows that while yes, Linux is supported on these platforms, and yes, it does run well after getting it setup - installation can be a downright pain. It is for this reason that I take great pride in the fact that installing Linux on the Hyper-V beta release is a breeze.
Installing Fedora Core 8 in a Hyper-V beta virtual machine involves:
As you can see there were no special options / kernel arguments / hardware configuration involved. All very straight forward.
How about the VM Additions, e.g. Heartbeat, TimeSync, Shutdown, etc? Do they "just work" out of the box as well?
Just a very quick correction, Fedora 8 is simply referred to as such. There is no 'Core' in 8. Apart from that, a good article.
All the best,
Red Hat, UK.
Have you tried to install and run any DOS games on Hyper-V?
it's more or less easier with virtualbox.
and it run on comodity hardware.
and it's free and even partly opensource
Fedora 8 is distribution that is fully LSB compliant. So it is the perfect choice for testing. Excellent job Ben.
First, a happy new year to everyone.
Secondly, I second Tom's question: is it necessary to install VMAdditions to increase guest performance?
I would think that heartbeat and shutdown probably won't work out of the box, since there would need to be some services running within the guest OS...
But I am looking forward to Ben's reply on that =)
Great article and good to hear that it is fairly easy to get up and running. Going to test this tonight.
One question... where can we get the VM Integration Components for Linux from? I ran across a posting that said they are on the Microsoft Connect site however I assume you have to part of the associated beta to get them.
Tom / tobi -
Integration components are not included by default with Linux - but you can download them from connect.microsoft.com.
You have to sign up to get them from connect.microsoft.com - but anyone can do this.
Chris Buckley -
I stand corrected :-)
Yes, I have - but that is a post for another day.
I guess I am little slow today however I can not figure out how to sign up for the Integration Components from the Connect site.
I logon using my normal ID like usual and am able to see the betas I am already participating in however there is nothing mentioned for the IC's that I can find.
Can you point me in the right direction?
Disregard my previous post.. I finally found the link. Thanks again for the help!
I'd like to ask a favor of you. When you reply to someone's post, especially when they have asked a question, could you please include the question, or at least a snippet of it in your response? I get the "New Content" email updates, and it would be nice to see the original question in the update. A good example of this would be your latest posts to Chris Buckley and Wesley. We have to go to the blog and backtrack through it to see what you were responding to. It would really be cool if all that info was in the email update.
Thanks again for running this, one of my top 5 favorite blogs!
Just curious, how is it that the dialogs in the post have an aero frame around them? Are they running on Vista or does Server 2008 support aero?
I'm having problems installing Linux on hyper-v.
Fedora 8 will just sit and tick over once I select install from the menu on a console screen that ends with a line about not detecting an AMD southbridge (will provide a screenshot link if needed).
CentOS 5.1 (my perfered distro) will install, but once it rebots and goes into the menu to edit security and firewall settings it will continue to dump lines of garbage to the screen. I can manage to exit from the menu and get to the console and the lines continue to dump only now they are text and report a DriveSeekCommand error. I tried storing the VHD on different drives in case it was corrupt as well as using both dynamic and fixed sizes, but an install on all scenarios gave the same error.
Ubuntu 7.1 Server - Once it gets to actually installing will get to around 75% and 'deciding on kernel' before erroring with the complaint it is unable to locate a kernel.
I'm hoping these are related issues.