Hyper-V Program Manager
Over on the Windows Blog, Scott Woodgate has given us a brief glance of Windows Virtual PC, which will be part of Windows 7. One of the most exciting features is the new “Windows XP mode” which is designed to help people with Windows XP applications as they move to Windows 7:
You can read about it here. Stay tuned for more details soon.
It would be nice if Aero Snaps worked with windows that come out of a virtual pc.
I also can't install Virtual PC 2007 SP1 on Windows 7 RC, are there any solutions for this problem?
I downloaded Virtual PC 7 (XPM) form technet (not Virtual PC 2007).
I tested it with a old virtual machine (Server 2008, which contains a base vhd and a diff vhd). I create a new VM in VPC7 and configured it to use an existing vhd. (Before i copied the 2 vhd´s to a new location.) If i tried to start the VM i get an error message. I find out that the link to the parrent vhd is wrong cause i copied it to a diffend location.
In Virtual PC 2007 there was a message box which asked me for the localtion of the base vhd. In VPC 7 there is only a error message.
I had to edit the diff disk with a Hex-Editor an set the path to the base vhd. After that i can start the VM.
How can i change the path to base vhd without using an Hex-Editor? Is there a official way to fix that problem?
(sorry for my bad english.)
I tested Virtual XP and got it running. It works well with an application installed in the virtual machine.
But what to do with an application which does not need to be installed? How do you get this application to the Windows 7 Desktop?
I create a VPC using Windows Virtual PC and try to run it on VPS2007 on a Vista box and it crashed. I hope there will be a fix to this because I could be creating VPC images for other machines not running W7 (ie. training). Now it seems like Windows Virtual PC and VPC2007 are 2 different unrelated products.
Already got it working.
Just add the application to the Virtual Windows XPs start menu.
Can we expect a full GUI console where the virtual machines can be managed ?
1. When i delete the virtual machine entry it does not remove all its related files
2. When i boot a virtual machine, we don't see the full OS boot process.
Hope you guys start talking soon. Personally, I found the new design somewhat disappointing.
A chance to hear the thought process would either give an alternate point of view a chance to be heard or at least be the launching point for a lively public discussion.
Starting points :
1. I miss the host key for things like c-a-d and full-screen mode toggle. Any chance it will come back?
2. Why was dragging in to and out of the VPC was dropped?
Then we can eventually get to XP mode. I get why it is the way it is now, but there are definite some huge issues with its current design that will likely result in the product dying a quick and ugly death instead realizing its full potential.
Will this new version of Windows Virtual PC and Windows XP Mode play nicely with VMware Workstation? I would like to use Windows XP Mode to run our legacy Windows XP programs but I need VMware to run my development environment so that I can test the effects of clustering. Can all three run on the same machine without any issues?
I had a hard time installing Virtual PC Beta. After re-booting I inevitably got SOD. Finally after careful reading of the blue screen content I realized that the source of the fault was vpcnfltr.sys. Disabled 2-nd network adapter and installation completed successfully. Then I enabled it back and could use as a shareable adapter for guest OS (XP).
Though I had more problems with networking. I installed non-windows guest (QNX, installed very good), but couldn't get connection (it worked fine on VPC 2007). Network adapter reported as DECchipset 21041, but was incompatible with it. I understand that running other OSs on VPC is not the main issue for Micrsoft, but I don't see reason it shouldn't work if it worked in previous release.
BTW, IMHO UI is confusing.
I am so disappointed there's still no x64 guest support :( I was hoping to play around with x64 Exchange 2010 on my Windows 7 workstation while leaving my Hyper-V Exchange 2007 installation alone.
Guess I'll have to use VMWare for that now...
With Windows Virtual PC, Microsoft took Desktop Virtualization one step forward and two steps backwards!
Ben, please take a look in this post:
I hope you can know our comment and help us to get 64bit guest OS support on Desktop OS.
Scott Bussinger -
A lot of work has gone into trying to get these sort of problems solved. And yes, it can be used to run 16-bit applications on 64-bit platforms.
Tarek Majdalani -
Now that the beta is available - please try it out and provide us with your feedback. We have done a lot of work to try and make this as simple as possible for non-tech savvy users.
Claus Valca -
Windows 7 only.
You are absolutely correct that most people do not want to virtualize 20 machines on their desktop. Windows Virtual PC is primarly targetted at providing a single virtual machine for application compatibility. You can - of course - run more if you want to.
Leith Bade -
Sorry, I cannot comment on that.
Can you try changing the power management profile to "high performance"?
No, only 32-bit guest operating systems are supported. You can run on 64-bit host operating systems.
Blake Coverett -
Yes, with Win7 on Win7 you should get full Aero / glass supported.
We are looking at what we can do here, but I cannot comment on our plans.
Richard Wu -
Unfortunately this is jsut a cae of prioritization of resources and features. Providing a top-notch XP application compaibility story for Windows 7 is more important than providing 64-bit virtual machines on the desktop today.
I agree, but that does not work :-)
Thanks for the feedback. I will get a bug logged against this.
Alex Verboon -
What more are you looking for beyond the current window / console? Also - hit "shift + esc" when the VM is booting to see the boot process.
I agree with the two points you make. Unfortunately both are the result of moving to using RDP technology for our integration features.
Laurence Rooks -
Unfortunately only one program can use processor hardware virtualization at a time, so you will not be able to run all three at once. I do not know what will happen if you try to run them at seperate times.
I am not sure why you think there are two steps back here. Windows Virtual PC adds a lot of cool new features over Virtual PC 2007.
I will post there.
Ben, I appreciate the responses to the respondees, but I'm not sure you understood the point of my message.
If application compatibility is all WVPC was targetting, that's fair enough, and no big leap of innovation. I personally think it could have been done much more simply and with far far far less overhead as a virtual application approach - so in that regard I consider it a poor solution, even if it is sufficient for the task. I can't imagine companies spending the time and money to roll out XPM except in the most gruesome of cases where they have no other choice. I could be wrong, but I sure can't see looking someone in the face and telling them to buy Windows 7 and still manage XPM as a step in the right direction. I will reserve final judgement on that, but I sure can't make a good justification for it at the moment.
What I was hoping from WVPC was a competitor to VMWare workstation or VirtualBox, which are targetted toward actual desktop virtualization. VirtualBox may be the first to offer a true virtual machine experience at their current pace, as their next installment (2.5) integrates directx support and vSMP (though how many cores is still a big question).
Does microsoft not view this as a worthwhile segment for a product? It would seem to me that they would want IT professionals and higher end users to use similar tools on the desktop as in their server environment. Having a Hyper-V desktop variant would go a long way to selling Hyper-V on the server side.
WVPC is certainly no "Hyper-V workstation"
and XPM/MED-V/APP-V are no ThinApp (though I have a little hope for App-V).
Anyways, just thought I would clarify...