From: "Roger Pau Monné" <roger.pau@citrix.com>
To: "Yuzhou (C)" <vitas.yuzhou@huawei.com>
Cc: "Zhangleiqiang (Trump)" <zhangleiqiang@huawei.com>,
"Xiaoding (B)" <xiaoding1@huawei.com>,
"Luohao (brian)" <brian.luohao@huawei.com>,
Zhuangyuxin <zhuangyuxin@huawei.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: xen4.5 dom0pvh test failed
Date: Tue, 27 Jan 2015 11:52:39 +0100 [thread overview]
Message-ID: <54C76DF7.9050200@citrix.com> (raw)
In-Reply-To: <47498F109986134D9A5B42B82F405EBB7EDE5971@SZXEMA502-MBX.china.huawei.com>
Hello,
El 27/01/15 a les 11.35, Yuzhou (C) ha escrit:
> Hi Roger,
>
> Thanks.
>
> I only have the Linux kernel config (in the attachment), can not find any useful boot log up to now.
You need to setup a serial console in order to provide the boot log. The
following wiki page should contain all the information needed in order
to set it up:
http://wiki.xen.org/wiki/Xen_Serial_Console
> And I also seen a problem: If I only add dom0pvh=1 (not specify dom0_mem), error occurs in booting xen.
>
> I have two other questions:
>
> (1) for dom0pvh this feature, xen 4.5 have to go with linux kernel 3.18???
No, but the Xen PVH ABI is still not set in stone, so backwards/forwards
compatibility is not guaranteed. Either 3.17 or 3.18 should work fine.
> (2)for dom0pvh this feature, have you any reports about Performance improvements?
I don't have any performance figures yet. PVH is very experimental and
the focus right now is to make it stable and implement the missing features.
Roger.
next prev parent reply other threads:[~2015-01-27 10:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 2:27 xen4.5 dom0pvh test failed Yuzhou (C)
2015-01-27 8:12 ` Roger Pau Monné
2015-01-27 10:35 ` Yuzhou (C)
2015-01-27 10:52 ` Roger Pau Monné [this message]
2015-01-28 3:51 ` Yuzhou (C)
2015-01-28 9:19 ` Yuzhou (C)
2015-01-28 9:45 ` Jan Beulich
2015-01-28 9:32 ` Jan Beulich
2015-01-29 12:44 ` Yuzhou (C)
2015-01-29 15:36 ` Roger Pau Monné
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=54C76DF7.9050200@citrix.com \
--to=roger.pau@citrix.com \
--cc=brian.luohao@huawei.com \
--cc=vitas.yuzhou@huawei.com \
--cc=xen-devel@lists.xen.org \
--cc=xiaoding1@huawei.com \
--cc=zhangleiqiang@huawei.com \
--cc=zhuangyuxin@huawei.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.