From: Avi Kivity <avi@redhat.com>
To: Brian Kelly <kelly.brianx@gmail.com>
Cc: Jim <jim@suresafe.co.uk>, "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: Nested Virtualization Of Hyper-V 2K8R2
Date: Tue, 18 Oct 2011 17:46:42 +0200 [thread overview]
Message-ID: <4E9D9F62.5080304@redhat.com> (raw)
In-Reply-To: <CAH-QgcacEPF_9QCsrmi-1bH_xC76nrUE8EPuDqSBhnDH6OQeaQ@mail.gmail.com>
On 10/18/2011 04:57 PM, Brian Kelly wrote:
> From msft - hyperv cpu requirements:
> *Processor *: x64 compatible processor with Intel VT or AMD-V
> technology enabled.
> Hardware Data Execution Prevention (DEP), specifically Intel XD bit
> (execute disable bit) or AMD NX bit (no execute bit), must be
> available and enabled.
>
> Are these enabled for guests when -enable-nesting is used?
>
Yes.
> On Tue, Oct 18, 2011 at 9:22 AM, Avi Kivity <avi@redhat.com
> <mailto:avi@redhat.com>> wrote:
>
> On 10/18/2011 02:00 PM, Jim wrote:
> > Hi Avi,
> >
> > There are 2 errors listed on the device manager.
> >
> > 1. Virtual Machine Bus : Windows cannot load the device driver for
> > this hardware. The driver may be corrupted or missing (Code 39)
> >
> > Driver details are listed as version 6.1.7601.17617, date 6/21/2006
> > signed by Microsoft
> >
> > 2. Virtualization Infrastructure Driver : Windows cannot load the
> > device driver for this hardware. The driver may be corrupted or
> > missing (Code 39)
> >
> > Driver details are listed as version 6.1.7601.17514, date 6/21/2006
> > signed by Microsoft
>
> Well, no idea. It will have to wait until someone takes the time to
> debug it.
>
> --
> error compiling committee.c: too many arguments to function
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> <mailto:majordomo@vger.kernel.org>
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
>
> --
> Email: kelly.brianx@gmail.com <mailto:kelly.brianx@gmail.com>
> Voice: (908) 514-8478
> Fax: (201) 221-8269
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-10-18 15:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 11:34 Nested Virtualization Of Hyper-V 2K8R2 Jim
2011-10-18 11:43 ` Avi Kivity
2011-10-18 12:00 ` Jim
2011-10-18 13:22 ` Avi Kivity
[not found] ` <CAH-QgcacEPF_9QCsrmi-1bH_xC76nrUE8EPuDqSBhnDH6OQeaQ@mail.gmail.com>
2011-10-18 15:46 ` Avi Kivity [this message]
2011-10-18 16:21 ` Jim
2011-10-18 16:34 ` Joerg Roedel
2011-10-18 18:28 ` Jim
2011-10-19 14:19 ` Joerg Roedel
[not found] ` <4E9EE787.30700@suresafe.co.uk>
2011-10-19 15:07 ` Jim
2011-10-24 11:13 ` Jim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E9D9F62.5080304@redhat.com \
--to=avi@redhat.com \
--cc=jim@suresafe.co.uk \
--cc=kelly.brianx@gmail.com \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.