Vista - Virtual PC 2007 SP1 64 bit on Windows Server 2008 standard 64 bit

I have a curious experience which i do not understand so thought I'd ask for
some assistance. Basically I get slow running guest OS in VPC 2007 SP1 64 bit
when running on Windows Server standard 2008 64 bit. The synopsis is as
follows:

I have a fresh install of Windows 2008 standard SP1 64 bit as I was going to
test out Hyper-V. I enabled hardware DEP and Virtualization Technologies in
the BIOS and Hyper-V runs lovely and with fast guests OS's. Good with server
guests but no sound support and only 16bit colour.

However, I have an XP Pro SP3 32 bit guest (that I've been using for
sometime in VPC 2007 on another host) that I want 32 bit colour and sound so
I thought I'd install Virtual PC 2007 SP1 64 bit and try it out on that, my
thinking was to use Hyper-V for server guests and VPC for client guests on
the same Win 2K8 host.

I noticed that VPC runs the guest but it is painfully slow and it does not
recognise 'Hardware Virtualization' in the VPC Options dialog - it i greyed
out (but I have it turned on in the BIOS). After some experiments, I found
that if I leave Hardware Visualization enabled in the BIOS but disable
Hardware DEP in the BIOS, then the VPC recognises Hardware Virtualisation and
the guest runs really fast (faster than expected in fact ). However,
without DEP, Hyper-V won't run.

My question is, how do I get Virtual PC 2007 SP1 64 bit to run on a
'Hardware DEP' enabled machine running Windows Server 2008 SP1 64 bit?

Note, I was running Vista Ultimate 32 bit on the same hardware before with
both Hardware DEP enabled and Hardware Virtualization enabled in the BIOS and
VPC 2007 SP1 worked brilliantly - suggesting that the hardware/BIOS is
working properly.

Note 2, Virtual Machine additions is installed in the guest OS.

Ideally I'd like to enable Hardware DEP and Hardware Visualization to run
both Hyper-V and VPC simultaneously.

Thanks in advance
Ian

>My question is, how do I get Virtual PC 2007 SP1 64 bit to run on aThe short answer is you can't if you're running Hyper-V too, the
hypervisor has control of the CPU and via virtualization, wont let
another higher level app even see that HW Virtualization is available.

Your speed problems really can't be helped and it's actually kind of a
miracle that VPC can run at all -- it just goes to show how hard the
virtualization team at Microsoft worked to get VM's so compatible with
real machines.

To get sound and 32-bit color in a VM is actually not all that hard in
Hyper-V anyway, just don' connect to the VM with Hyper-V's console,
use the normal RDP client instead, and have the VM's OS set to be able
to access the remote desktop. You can get odd screen resolutions that
way too where the Hyper-V console doesn't allow things like wide
screen. (1200x800 on my laptop) There's really no speed penalty for
using normal RDP either...

--
Bob Comer



On Wed, 11 Jun 2008 03:33:15 -0700, Ian Crisp
<IanCrisp@xxxxxx> wrote:

Thanks Robert

A sideways look at the problem!

I got RDP working to Hyper-V with sound and 24 bit color. cool

thanks again
Ian

"Robert Comer" wrote:

>Thanks Robert

You're quite welcome!
Sometimes that's best. <g>

--
Bob Comer <Microsoft MVP Windows - Virtual Machine>



On Wed, 11 Jun 2008 14:11:01 -0700, Ian Crisp
<IanCrisp@xxxxxx> wrote:

I'm experiencing a similar problem with my server where if i have both
Virtualization and DEP enabled in the BIOS, i get a Hyper-V launch failed. On
closer inspection virtualization is disabled (even though enabled in the
bios), en DEP enabled. I can however start Hyper-V if i disable Hardware
Virtualization and enable DEP, but this negatively affects my performance.

Does anyone have any advice? I'm running a DELL Poweredge 2900 with server
2008 enterprise. The only thing installed on it is Hyper-V and File Services
role

Thanks,
Hanno

"Robert Comer" wrote:

On Tue, 5 Aug 2008 11:58:00 -0700, Hanno
<Hanno@xxxxxx> wrote:
Do you have the most recent BIOS update from Dell?

--
Cheers,
Steve Jain, Virtual Machine MVP
http://vpc.essjae.com/
I do not work for Microsoft.

Yes, i have bios version 2.3.1 installed which is the latest

"Steve Jain" wrote: