From: "Roger Pau Monné" <roger.pau@citrix.com>
To: "Yuzhou (C)" <vitas.yuzhou@huawei.com>,
"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>,
"JBeulich@suse.com" <JBeulich@suse.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: "Zhangleiqiang (Trump)" <zhangleiqiang@huawei.com>,
"Xiaoding (B)" <xiaoding1@huawei.com>,
"Luohao (brian)" <brian.luohao@huawei.com>,
Zhuangyuxin <zhuangyuxin@huawei.com>
Subject: Re: xen4.5 dom0pvh test failed
Date: Tue, 27 Jan 2015 09:12:58 +0100 [thread overview]
Message-ID: <54C7488A.3040608@citrix.com> (raw)
In-Reply-To: <47498F109986134D9A5B42B82F405EBB7EDE5833@SZXEMA502-MBX.china.huawei.com>
El 27/01/15 a les 3.27, Yuzhou (C) ha escrit:
> Hi all,
>
>
>
> I want to test xen 4.5.0 + linux 3.17.4+ dom0pvh=1, but boot failed.
>
>
>
> I add dom0_mem=max:2GB dom0pvh=1 to xen boot params.
>
>
>
> I find some mails about dom0 as pvh mode, however I do not find the useful answer that solve this problem.
>
>
>
> And, I have tested xen 4.5.0 + linux 3.18.3+ dom0pvh=1, but also boot failed.
>
>
>
> Have anybody test this feature?
Yes, I've successfully tested Xen 4.5.0 and Linux 3.18.0. Can you please
provide more information, the attached screenshot doesn't even show the
actual cause of the panic. At least the Linux kernel config used to
compile the kernel and the full boot log are needed.
Please see http://wiki.xenproject.org/wiki/Reporting_Bugs_against_Xen.
Roger.
next prev parent reply other threads:[~2015-01-27 8:12 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é [this message]
2015-01-27 10:35 ` Yuzhou (C)
2015-01-27 10:52 ` Roger Pau Monné
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=54C7488A.3040608@citrix.com \
--to=roger.pau@citrix.com \
--cc=JBeulich@suse.com \
--cc=brian.luohao@huawei.com \
--cc=konrad.wilk@oracle.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.