Prev: WinVPC and XP Mode general availability
Next: Virtual PC wants a Product ID, but it's a free download
From: VanguardLH on 24 Oct 2009 04:24
moondaddy wrote:

> VanguardLH wrote ...
>
>> moondaddy wrote:
>>
>>> Is it possible to install windows 7 virtual PC on a hyper-v windows 7 vm?
>>
>> Isn't the point of Hyper-V to let you run multiple guests (VMs)? Why
>> would you load one instance of Windows 7 in a VM under Hyper-V to then
>> try to load in that instance of Windows another VM? Why not create
>> another VM under Hyper-V and run that one as the 2nd instance of Win7
>> (assuming you actually have the 2nd license)?
>
> Because I'm wanting to do away with the windows 2008 r2 OS and use windows 7
> instead

Hyper-V is its own OS. You install it. You then configure VMs that
*it* loads (much like IBM's VM operating system in which you can run
VSE, MVS, other CICS, or whatever it supports for guests). Windows 2008
isn't involved. Just install Hyper-V and then add whatever guests (VMs)
you want it to manage (which can all be running concurrently but which
might mean you need to ensure you have the licenses for those concurrent
instances).

Or is the Windows 2008 server that you are trying to get rid of the
Hyper-V Server 2008? That means you are trying to instead use Windows 7
as the host OS and then run other instances of Windows 7 as guests (if
you have the licenses for them). Just install Windows 7 in the same
partition where was Hyper-V installed (select to format the partition
when you install Windows 7) and the format wipes away Hyper-V in that
partition.

Hyper-V is designed to load first and by the hypervisor for each guest
OS that you run atop of it. You don't need to load an OS to then load
the hypervisor to load the guest. You just load the hypervisor which
loads the guests.

VirtualPC:
Load Windows -> Load VPC -> Load guests

Hyper-V
Load Hyper-V -> Load guests

Here is a diagram showing hierachy:

http://en.wikipedia.org/wiki/File:Viridian_Architecture.svg

Hyper-V is a role provided by Windows 2008 Server. Actually, as of Oct
2008, Hyper-V is a separate variant of Windows Server 2008 (it isn't a
full Windows 2008 Server so now it's called "Hyper-V Server 2008"); see
http://www.microsoft.com/hyper-v-server/en/us/default.aspx. Similarly,
Windows XP Professional x64 is built on Windows 2003 Server but it isn't
the full blown Windows 2003 Server product with a Windows XP skin. If
you don't want Windows 2008 Server then you also don't want Hyper-V. So
asking anything about Hyper-V is irrelevant if you are looking to leave
Windows 2008 Server and instead load Windows (some supported host OS
version) and then load VPC atop of that and finally get around to
loading your guests.

If you have the hardware needed to run Hyper-V (and the disk space and
memory for the guests, I would think Hyper-V would be the better
solution.

If using Hyper-V, there's no point in using VirtualPC. You question
packs way too many terms together without any boundaries to discern just
WHAT you are asking.

"Is it possible to install windows 7 virtual PC on a hyper-v windows 7
vm?"

Does that mean:
- Can you run Windows 7 as a guest on Hyper-V? Yes.
- Can you run Hyper-V as a guest on Windows 7? No.
- Can you run Hyper-V as a guest of VPC running in Windows 7? No.
- Why is Windows 7 mentioned TWICE in your question? There is no such
thing as "Hyper-V Windows 7".
- Does "windows 7 virtual pc" (without the proper capitalization) refer
to the Windows XP compatibility mode in Windows 7 (if you have the
requisite hardware to support it)? Or do you intend to run VirtualPC
2007 on Windows 7?

Your question is so garbled that no one know what you meant to ask.
From: moondaddy on 24 Oct 2009 13:45
OK thanks. My goal was to get rid of using WnSrvr 2008 R2 (as a work
station) because of 3rd party software licensing issues and
incompatibilities. I used WnSrvr 08 R2 so I could get Hyper-V (which I'm
now seeing as a poor understanding of Hyper-V on my part).

Vanguard's email helps to clarify things as well. My goal is to have the
ability to run Windows 7 as my normal workstation OS where I work all day
long. From this Windows 7 OS I will have a 3rd party backup utility which I
will be able to do bare metal backups as well as differential backups of my
OS and data drives (which includes backing up the various VM files).
Additionally, I need to have the ability to have many different VMs to test
the software I develop.

Therefore, based on Vanguard's and your response, installing Hyper-V first
on a clean partition sounds like the way to go except for one caveat: I don't
have a good backup solution which would need to run from the Hyper-V OS so
it could backup 'everything'.

Thanks to the both of you for your input. I will have to think this through
some more.



"Steve Jain [MVP]" <noreply.-@-.essjae.com> wrote in message
news:j794e5dk52423d022f8mvaf2rerbga4ddg(a)4ax.com...
> On Fri, 23 Oct 2009 16:16:05 -0500, "moondaddy"
> <moondaddy(a)newsgroup.nospam> wrote:
>
>>Because I'm wanting to do away with the windows 2008 r2 OS and use windows
>>7
>>instead
>>
>
> That still doesn't make sense. Hyper-V is a VM solution, so why do
> you need to run another VM program inside of it?
>
> Hyper-V doesn't require an OS, it works outside the OS, its a
> hypervisor.
>
> the Hyper-V product is designed for a different use than VPC.
>
> --
> Cheers,
> Steve Jain, Virtual Machine MVP
> http://vpc.essjae.com/
> http://smudj.wordpress.com/

From: moondaddy on 24 Oct 2009 13:46
Thanks for the good info. The confusion comes from my poor understanding of
Hyper-V and how things can be configured. Please see my response above to
Steve.

"VanguardLH" <V(a)nguard.LH> wrote in message
news:hbudk8$vee$1(a)news.albasani.net...
> moondaddy wrote:
>
>> VanguardLH wrote ...
>>
>>> moondaddy wrote:
>>>
>>>> Is it possible to install windows 7 virtual PC on a hyper-v windows 7
>>>> vm?
>>>
>>> Isn't the point of Hyper-V to let you run multiple guests (VMs)? Why
>>> would you load one instance of Windows 7 in a VM under Hyper-V to then
>>> try to load in that instance of Windows another VM? Why not create
>>> another VM under Hyper-V and run that one as the 2nd instance of Win7
>>> (assuming you actually have the 2nd license)?
>>
>> Because I'm wanting to do away with the windows 2008 r2 OS and use
>> windows 7
>> instead
>
> Hyper-V is its own OS. You install it. You then configure VMs that
> *it* loads (much like IBM's VM operating system in which you can run
> VSE, MVS, other CICS, or whatever it supports for guests). Windows 2008
> isn't involved. Just install Hyper-V and then add whatever guests (VMs)
> you want it to manage (which can all be running concurrently but which
> might mean you need to ensure you have the licenses for those concurrent
> instances).
>
> Or is the Windows 2008 server that you are trying to get rid of the
> Hyper-V Server 2008? That means you are trying to instead use Windows 7
> as the host OS and then run other instances of Windows 7 as guests (if
> you have the licenses for them). Just install Windows 7 in the same
> partition where was Hyper-V installed (select to format the partition
> when you install Windows 7) and the format wipes away Hyper-V in that
> partition.
>
> Hyper-V is designed to load first and by the hypervisor for each guest
> OS that you run atop of it. You don't need to load an OS to then load
> the hypervisor to load the guest. You just load the hypervisor which
> loads the guests.
>
> VirtualPC:
> Load Windows -> Load VPC -> Load guests
>
> Hyper-V
> Load Hyper-V -> Load guests
>
> Here is a diagram showing hierachy:
>
> http://en.wikipedia.org/wiki/File:Viridian_Architecture.svg
>
> Hyper-V is a role provided by Windows 2008 Server. Actually, as of Oct
> 2008, Hyper-V is a separate variant of Windows Server 2008 (it isn't a
> full Windows 2008 Server so now it's called "Hyper-V Server 2008"); see
> http://www.microsoft.com/hyper-v-server/en/us/default.aspx. Similarly,
> Windows XP Professional x64 is built on Windows 2003 Server but it isn't
> the full blown Windows 2003 Server product with a Windows XP skin. If
> you don't want Windows 2008 Server then you also don't want Hyper-V. So
> asking anything about Hyper-V is irrelevant if you are looking to leave
> Windows 2008 Server and instead load Windows (some supported host OS
> version) and then load VPC atop of that and finally get around to
> loading your guests.
>
> If you have the hardware needed to run Hyper-V (and the disk space and
> memory for the guests, I would think Hyper-V would be the better
> solution.
>
> If using Hyper-V, there's no point in using VirtualPC. You question
> packs way too many terms together without any boundaries to discern just
> WHAT you are asking.
>
> "Is it possible to install windows 7 virtual PC on a hyper-v windows 7
> vm?"
>
> Does that mean:
> - Can you run Windows 7 as a guest on Hyper-V? Yes.
> - Can you run Hyper-V as a guest on Windows 7? No.
> - Can you run Hyper-V as a guest of VPC running in Windows 7? No.
> - Why is Windows 7 mentioned TWICE in your question? There is no such
> thing as "Hyper-V Windows 7".
> - Does "windows 7 virtual pc" (without the proper capitalization) refer
> to the Windows XP compatibility mode in Windows 7 (if you have the
> requisite hardware to support it)? Or do you intend to run VirtualPC
> 2007 on Windows 7?
>
> Your question is so garbled that no one know what you meant to ask.

From: Bill Grant on 18 Nov 2009 22:43


"Steve" <Steve(a)discussions.microsoft.com> wrote in message
news:5CB20EE6-E59E-49D8-9F05-5476DE81B35E(a)microsoft.com...
> My 2 cents:
>
> The reason I would like to run Virtual PC in Win7 on HyperV is for XP
> mode.
> I want to virtualize my instance of Win7 on HyperV but I also have some
> software that I need to run in XP mode. For instance I want to run the
> Exchange 2003 management pack but it won't run on Win7.
>
> I really wish they would have made Virtual PC more versatile.
>
>
>
Windows VPC for windows 7 requires that the host machine supports
hardware virtualization (just as Hyper-V does). An instance of Windows 7
running in a virtual machine under Hyper-V cannot possibly do that, since it
is running on a virtual machine, not a physical machine with hardware
virtualization.


First  |  Prev  | 
Pages: 1 2
Prev: WinVPC and XP Mode general availability
Next: Virtual PC wants a Product ID, but it's a free download