xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Lingfei Kong <lkong@redhat.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xen.org
Subject: Re: Is: Xen 4.4 and 'cpus="X-Y" command line parsing borked Was:Re: drjones@redhat.com, vkuznets@redhat.com, leiwang@redhat.com, wshi@redhat.com
Date: Tue, 22 Apr 2014 09:33:44 +0800	[thread overview]
Message-ID: <5355C6F8.4040403@redhat.com> (raw)
In-Reply-To: <20140421130253.GB3425@phenom.dumpdata.com>

On 04/21/2014 09:02 PM, Konrad Rzeszutek Wilk wrote:
> On Thu, Apr 17, 2014 at 09:40:46PM -0400, Lingfei Kong wrote:
>> Hello,
>> When i create a guest with option 'cpus="0-3"' on the command line, xl can not parse the config. But it works well when i specify 'cpus=1' on the command line. I read the man page xl.cfg, learned that xl support the following format:
>> "0-3,5,^1"
>> so  it would be very nice if xl can support this format on the command line too.
>>
>> Also i have file a bug on bugzilla: Bug 1886 - option `cpus="0-3"` works well when you specify it in a configure file, but it give a error feadback when you add it to the command line
>>
> 
> On what bugzilla system?
> 

I follow the steps descripted in xl command's man page. Here is the link
of this bug:  http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1886

>>
>>
>> The following are the  details:
>>
>> Description of problem:
>> option `cpus="0-3"` works well when you specify it in a configure file, but it give a error feadback when you add it to the command line.
>>
>> Version-Release number of selected component (if applicable):
>>
>> How reproducible:
>> 100%
>>
>> Steps to Reproduce:
>> 1. Install a host with xen4
> 
> How did you install that? Did you use the Xen RPMs?

Yes. Here are my steps
1. Install Fedora20
2. Install xen packages
#yum -y install xen
3. Configure grub2.cfg, Set 'Fedora, with Xen hypervisor' as the default
menuentry and reboot the host
4. Use option `cpus="0-3"` on the command line to create the guest

> 
>> 2. Create a guest, add option 'cpus="0-3"' on the command line
>> # xl -v create hvm-7.0-64-1.cfg cpus="0-3"
>> Parsing config from hvm-7.0-64-1.cfg
> 
> Does it work if you have the 'cpus="0-3"' in the guest config file
> (from hvm-7.0-64-1.cfg)
> 

When I specify it in t he guest config file, it works well.

>> hvm-7.0-64-1.cfg:28: config parsing error near `-3': lexical error
>> warning: Config file looks like it contains Python code.
>> warning:  Arbitrary Python is no longer supported.
>> warning:  See http://wiki.xen.org/wiki/PythonInXlConfig
>> Failed to parse config: Invalid argument
>>
>>
>> Actual results:
>> Failed to create the guest
>>
>> Expected results:
>> Guest can be created successfully.
>>
>> Additional info:
>> # xl info
>> host                   : hp-z220-02.qe.lab.eng.nay.redhat.com
>> release                : 3.11.10-301.fc20.x86_64
>> version                : #1 SMP Thu Dec 5 14:01:17 UTC 2013
>> machine                : x86_64
>> nr_cpus                : 8
>> max_cpu_id             : 7
>> nr_nodes               : 1
>> cores_per_socket       : 4
>> threads_per_core       : 2
>> cpu_mhz                : 3392
>> hw_caps                : bfebfbff:28100800:00000000:00007f00:77bae3ff:00000000:00000001:00000281
>> virt_caps              : hvm hvm_directio
>> total_memory           : 16258
>> free_memory            : 10185
>> sharing_freed_memory   : 0
>> sharing_used_memory    : 0
>> outstanding_claims     : 0
>> free_cpus              : 0
>> xen_major              : 4
>> xen_minor              : 3
>> xen_extra              : .2
>> xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 
>> xen_scheduler          : credit
>> xen_pagesize           : 4096
>> platform_params        : virt_start=0xffff800000000000
>> xen_changeset          : 
>> xen_commandline        : placeholder
>> cc_compiler            : gcc (GCC) 4.8.2 20131212 (Red Hat 4.8.2-7)
>> cc_compile_by          : mockbuild
>> cc_compile_domain      : [unknown]
>> cc_compile_date        : Wed Mar 26 20:46:37 UTC 2014
>> xend_config_format     : 4
>>
>>
>> The attachment is the log file /var/log/xen/xl-${DOMNAME}.log 
>>
>> Best Regards
>> Lingfei Kong
> 
>> Waiting for domain hvm-7.0-64-1 (domid 5) to die [pid 16670]
>> Domain 5 has been destroyed.
> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel
> 


Thanks and Best Regards
Lingfei Kong

  reply	other threads:[~2014-04-22  1:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <648058658.7316781.1397784467480.JavaMail.zimbra@redhat.com>
2014-04-18  1:40 ` drjones@redhat.com, vkuznets@redhat.com, leiwang@redhat.com, wshi@redhat.com Lingfei Kong
2014-04-21 13:02   ` Is: Xen 4.4 and 'cpus="X-Y" command line parsing borked Was:Re: " Konrad Rzeszutek Wilk
2014-04-22  1:33     ` Lingfei Kong [this message]
2014-04-22 10:59   ` George Dunlap
2014-04-23  0:56     ` Lingfei Kong
2014-04-23 10:58       ` George Dunlap
2014-04-24  0:14         ` Lingfei Kong
2014-04-24  8:44           ` Ian Campbell
2014-04-24  9:01             ` George Dunlap
2014-04-24  9:32               ` Ian Campbell
2014-04-24 11:27                 ` George Dunlap
2014-04-24 11:33                   ` 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=5355C6F8.4040403@redhat.com \
    --to=lkong@redhat.com \
    --cc=konrad.wilk@oracle.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).