From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: "Hao, Xudong" <xudong.hao@intel.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Failure to boot HVM guest with more than 32 VCPUS
Date: Thu, 13 Aug 2015 10:20:11 +0200 [thread overview]
Message-ID: <874mk3fvlw.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <B8376D2DEA074F45BA033984477C453EC44E72@shsmsx102.ccr.corp.intel.com> (Xudong Hao's message of "Thu, 13 Aug 2015 00:48:23 +0000")
"Hao, Xudong" <xudong.hao@intel.com> writes:
>> -----Original Message-----
>> From: Vitaly Kuznetsov [mailto:vkuznets@redhat.com]
>> Sent: Wednesday, August 12, 2015 5:40 PM
>> To: Hao, Xudong
>> Cc: xen-devel@lists.xen.org
>> Subject: Re: [Xen-devel] Failure to boot HVM guest with more than 32
>> VCPUS
>>
>> "Hao, Xudong" <xudong.hao@intel.com> writes:
>>
>> > Hi,
>> >
>> > In X86_64 platform, we noticed an issue that Xen boot a RHEL6u6 or
>> > Fedora22 guest, when configure the VCPU more than 32, the guest will
>> > fail to boot up.
>>
>> The issue is well-known for RHEL6.6 (and is fixed in 6.7 and in 6.6.z)
>> but Fedora22 should boot. The log below is from RHEL6.6, can you please
>> provide one from Fedora?
>>
>
> Vitaly,
>
> Thanks for quick response. Is the fix in guest pv driver?
The fix is in RHEL6 kernel, prior to it there is no support for
vcpu_info outside of shared_info and so only 32 vcpus are supported.
> Will catch Fedora22 log.
Please do, this is probably a different issue.
--
Vitaly
next prev parent reply other threads:[~2015-08-13 8:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 9:02 Failure to boot HVM guest with more than 32 VCPUS Hao, Xudong
2015-08-12 9:39 ` Vitaly Kuznetsov
2015-08-13 0:48 ` Hao, Xudong
2015-08-13 8:20 ` Vitaly Kuznetsov [this message]
2015-08-13 8:37 ` Hao, Xudong
2015-08-13 9:20 ` Vitaly Kuznetsov
2015-08-13 11:45 ` Konrad Rzeszutek Wilk
2015-08-13 12:58 ` Vitaly Kuznetsov
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=874mk3fvlw.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=xen-devel@lists.xen.org \
--cc=xudong.hao@intel.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.