xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Egger <Christoph.Egger@amd.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: libxl: cannot start guest
Date: Fri, 18 May 2012 17:51:09 +0200	[thread overview]
Message-ID: <4FB66FED.5080704@amd.com> (raw)
In-Reply-To: <4FB65B61.7000902@amd.com>

On 05/18/12 16:23, Christoph Egger wrote:

> On 05/18/12 15:30, Ian Campbell wrote:
> 
>> On Fri, 2012-05-18 at 14:17 +0100, Christoph Egger wrote:
>>> Hi,
>>>
>>> I am currently using c/s 25371:e9058654ca08.
>>> When I try to start a HVM guest I get this failure:
>>>
>>>
>>> xc: info: VIRTUAL MEMORY ARRANGEMENT:
>>>   Loader:        0000000000100000->000000000019bd04
>>>   TOTAL:         0000000000000000->00000000ff800000
>>>   ENTRY ADDRESS: 0000000000100000
>>> xc: info: PHYSICAL MEMORY ALLOCATION:
>>>   4KB PAGES: 0x0000000000000200
>>>   2MB PAGES: 0x00000000000003fb
>>>   1GB PAGES: 0x0000000000000002
>>> libxl: error: libxl.c:3208:libxl_sched_credit_domain_set: Cpu weight out
>>> of range, valid values are within range from 1 to 65535
>>> libxl: error: libxl_xshelp.c:102:libxl__xs_get_dompath: failed to get
>>> dompath for 1: Bad file descriptor
>>
>> This is on NetBSD?
> 
> 
> Yes.
> 
>>
>> These sorts of symptoms are similar to those fixed by 25364:8dce7a4121b9
>> but you've already got that. It might be worth doing a full clean and
>> rebuild, just in case.
> 
> 
> This is a clean build.
> 
>  
>> What does your guest config look like?
> 
> 
> builder='hvm'
> memory=4096
> nestedhvm=1
> name="guest"
> vcpus=4
> cpuid="host,page1gb=k,hypervisor=0"
> acpi=1
> apic=1
> vif = [ 'type=ioemu, bridge=bridge0, model=e1000' ]
> disk = [ 'file:/hvm-guest/guest.img,ioemu:hda,w' ]
> serial='pty'
> vnc=1
> sdl=0
> 
>> What is your command line?
> 
> xl create -c guest.conf
> 
>  
>> Do you know when it last worked?
> 
> 
> Changeset 24462 worked. I need to bisect the exact
> changeset.
> 
>  
>> The places which close ctx->xsh are very few -- might be worth
>> annotating any call to xs_daemon_close() with a printf. 
> 
> 
> ok.

In libxl__build_post() I check the return value
of libxl__sched_set_params().
Now trying to start a guest results in this failure:

xc: info: VIRTUAL MEMORY ARRANGEMENT:
  Loader:        0000000000100000->000000000019bd04
  TOTAL:         0000000000000000->00000000ff800000
  ENTRY ADDRESS: 0000000000100000
xc: info: PHYSICAL MEMORY ALLOCATION:
  4KB PAGES: 0x0000000000000200
  2MB PAGES: 0x00000000000003fb
  1GB PAGES: 0x0000000000000002
libxl: error: libxl.c:3211:libxl_sched_credit_domain_set: Cpu weight out
of range, valid values are within range from 1 to 65535
libxl: error: libxl_create.c:694:domcreate_bootloader_done: cannot
(re-)build domain: -6
libxl: error: libxl_dm.c:1104:libxl__destroy_device_model: Couldn't find
device model's pid: No such file or directory
libxl: error: libxl.c:1162:libxl_domain_destroy:
libxl__destroy_device_model failed for 1
libxl: error: libxl.c:155:libxl_ctx_free: libxl_ctx_free: call
xs_daemon_close  <-- the printf annotation


Christoph


-- 
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Einsteinring 24, 85689 Dornach b. Muenchen
Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632

  reply	other threads:[~2012-05-18 15:51 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-18 13:17 libxl: cannot start guest Christoph Egger
2012-05-18 13:30 ` Ian Campbell
2012-05-18 14:23   ` Christoph Egger
2012-05-18 15:51     ` Christoph Egger [this message]
2012-05-18 15:58       ` Ian Campbell
2012-05-21 10:26         ` Christoph Egger
2012-05-21 12:15           ` Ian Campbell
2012-05-21 13:10             ` Christoph Egger
2012-05-21 13:49               ` Ian Campbell
2012-05-21 15:43                 ` Christoph Egger
2012-05-21 15:44                 ` Christoph Egger
2012-05-21 15:57                   ` Ian Campbell
2012-05-21 16:11                     ` Ian Jackson
2012-05-22 12:35                     ` Christoph Egger
2012-05-22 12:53                       ` Ian Campbell
2012-05-22 13:17                         ` Christoph Egger
2012-05-22 13:18                         ` Christoph Egger
2012-05-22 13:21                           ` Ian Campbell
2012-05-22 14:03                             ` Christoph Egger
2012-05-22 14:20                               ` Ian Campbell
2012-05-22 15:16                                 ` Christoph Egger
2012-05-22 15:21                                   ` Ian Campbell
2012-05-22 15:32                                     ` Christoph Egger
2012-05-23 10:11                                       ` Ian Campbell
2012-05-24  9:44                                         ` Christoph Egger
2012-05-25 14:56                                           ` Roger Pau Monne
2012-05-25 15:42                                             ` Ian Campbell
2012-05-29 10:02                                         ` Ian Jackson
2012-05-29 10:13                                           ` Ian Campbell
2012-05-22 13:21                           ` Christoph Egger

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=4FB66FED.5080704@amd.com \
    --to=christoph.egger@amd.com \
    --cc=Ian.Campbell@citrix.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).