From: "Jan Beulich" <JBeulich@novell.com>
To: Mukesh Rathor <mukesh.rathor@oracle.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Subject: Re: PV hybrid: vmlaunch failure help...
Date: Fri, 04 Mar 2011 09:37:33 +0000 [thread overview]
Message-ID: <4D70C0ED0200007800034E1B@vpn.id2.novell.com> (raw)
In-Reply-To: <20110303192123.01342340@mantra.us.oracle.com>
>>> On 04.03.11 at 04:21, Mukesh Rathor <mukesh.rathor@oracle.com> wrote:
> (XEN) ES: sel=0x0000, attr=0x00000, limit=0xffffffff,
> base=0x0000000000000000
> (XEN) FS: sel=0x0000, attr=0x00000, limit=0xffffffff,
> base=0x0000000000000000
> (XEN) GS: sel=0x0000, attr=0x00000, limit=0xffffffff,
> base=0x0000000000000000
Does it help either marking these unusable (attr=0x10000) or
giving them valid data segment attributes?
> (XEN) GDTR: limit=0xffffffff, base=0xffffffff81a4c490
Limit is restricted to 16 bits.
Jan
prev parent reply other threads:[~2011-03-04 9:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 3:21 PV hybrid: vmlaunch failure help Mukesh Rathor
2011-03-04 7:42 ` Keir Fraser
2011-03-05 2:29 ` Mukesh Rathor
2011-03-04 9:37 ` Jan Beulich [this message]
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=4D70C0ED0200007800034E1B@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=Xen-devel@lists.xensource.com \
--cc=mukesh.rathor@oracle.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).