From: Rick Gonzalez <rcgneo@us.ibm.com>
To: Xen Developers <xen-devel@lists.xensource.com>
Subject: Xen-HVM Build: cs11268: xmtest broken
Date: Wed, 30 Aug 2006 15:24:29 -0500 [thread overview]
Message-ID: <44F5F3FD.9080109@us.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]
changeset: 11286:5acf10969b1d
tag: tip
user: Ewan Mellor <ewan@xensource.com>
date: Tue Aug 29 19:20:01 2006 +0100
summary: Added an entry to arch._types for x86_64.
Hardware: x460
******************** x86_32(no PAE): ***************************
* dom0: SLES10 GM
* dom0 boots fine
--- Linux HVM domain status: ---
* Xm-test FAILS in sanity check. This is because the shadow memory
parameter in the config file is missing in xmtest config file.
* I'm looking into fixing the problem soon.
I'm opening a bug to fix it. Just to track it.
********************** x86_64: *********************************
* dom0: SLES10 GM
* dom0 boots fine
--- Linux HVM domain status: ---
* Xm-test FAILS in Sanity checks. This is because the shadow memory
parameter in the config file is missing in xmtest config file.
* I'm looking into fixing the problem soon.
NOTE: Contact me if you would like to see all the output files.
regards,
------------------------
Rick Gonzalez
Linux Technology Center
IBM Corporation
Phone#: 512-838-0623
[-- Attachment #2: rcgneo.vcf --]
[-- Type: text/x-vcard, Size: 255 bytes --]
begin:vcard
fn:Rick Gonzalez
n:Gonzalez;Rick
org:;LTC Test Development
adr:;;11501 Burnet Rd;Austin;TX;78758;USA
email;internet:rcgneo@us.ibm.com
title:Staff Engineer
tel;work:512-838-0623
tel;fax:512-838-8858
tel;home:512-873-2286
version:2.1
end:vcard
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
reply other threads:[~2006-08-30 20:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=44F5F3FD.9080109@us.ibm.com \
--to=rcgneo@us.ibm.com \
--cc=xen-devel@lists.xensource.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 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.