From: Jim Fehlig <jfehlig@suse.com>
To: Ian Campbell <ian.campbell@citrix.com>, xen-devel@lists.xen.org
Cc: osstest service owner <osstest-admin@xenproject.org>
Subject: Re: [osstest test] 64958: regressions - trouble: broken/fail/pass
Date: Wed, 02 Dec 2015 18:33:14 -0700 [thread overview]
Message-ID: <565F9BDA.3030509@suse.com> (raw)
In-Reply-To: <1448465532.17688.122.camel@citrix.com>
On 11/25/2015 08:32 AM, Ian Campbell wrote:
> On Wed, 2015-11-25 at 14:37 +0000, Ian Campbell wrote:
>> 2015-11-21 23:06:44 Z executing ssh ... root@172.16.144.44 virsh domxml-from-native xen-xl /etc/xen/debian.jessie.guest.osstest.cfg > /etc/xen/debian.jessie.guest.osstest.cfg.xml
>> error: An error occurred, but the cause is unknown
> This turned out to be the check of vcpus vs MAX_VIRT_CPUS in
> xenParseCPUFeatures.
>
> MAX_VIRT_CPUS is defined (by libvirt) as XEN_LEGACY_MAX_VCPUS, which is
> mostly wrong on x86 (which supports more than that for guests using vcpu
> placement) but is very wrong on ARM where we insist on vcpu placement and
> XEN_LEGACY_MAX_VCPUS is therefore 1.
>
> This test was trying to create a 2 cpu guest.
>
> Since this check is in xen_common.c I think it might take a little
> unravelling to fix this, since it seems to have lead to various other
> assumptions to do with CPU masks fitting into an unsigned long in the
> libvirt code base.
Hi Ian,
Sorry for the delay. I'm still catching up on mail after some days away.
> /me rolls up sleeves.
I see that your toiling has produced some patches. I'm slowly making it through
patch reviews too, and will get to those soon.
Regards,
Jim
next prev parent reply other threads:[~2015-12-03 1:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <osstest-64958-mainreport@xen.org>
2015-11-25 14:37 ` [osstest test] 64958: regressions - trouble: broken/fail/pass Ian Campbell
2015-11-25 15:32 ` Ian Campbell
2015-12-03 1:33 ` Jim Fehlig [this message]
2015-12-03 9:31 ` Ian Campbell
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=565F9BDA.3030509@suse.com \
--to=jfehlig@suse.com \
--cc=ian.campbell@citrix.com \
--cc=osstest-admin@xenproject.org \
--cc=xen-devel@lists.xen.org \
/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.