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: Mon, 21 May 2012 12:26:34 +0200	[thread overview]
Message-ID: <4FBA185A.3080306@amd.com> (raw)
In-Reply-To: <1337356698.22316.138.camel@zakaz.uk.xensource.com>

On 05/18/12 17:58, Ian Campbell wrote:

> 
>> In libxl__build_post() I check the return value
>> of libxl__sched_set_params().
> 
> The mesages about scheduler params are a known and benign issue.
> 
>> 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
> 
> Is your device model dying for some reason? Anything
> in /var/log/xen/*guest*.log about it?


The guest logfile doesn't exist. Does that mean the errors happens
before device model has been started at all?

> 
> You could try "xl -vvv cr ..." too, not sure what it will say.


libxl: debug: libxl_device.c:183:libxl__device_disk_set_backend: Disk
vdev=hda spec.backend=unknown
libxl: debug: libxl_device.c:219:libxl__device_disk_set_backend: Disk
vdev=hda, using backend phy
xc: detail: elf_parse_binary: phdr: paddr=0x100000 memsz=0x9bd04
xc: detail: elf_parse_binary: memory: 0x100000 -> 0x19bd04
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
xc: detail: elf_load_binary: phdr 0 at 0x0x7f7ff7f42000 -> 0x0x7f7ff7fd4b74
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 2
xc: debug: hypercall buffer: total allocations:1251 total releases:1251
xc: debug: hypercall buffer: current allocations:0 maximum allocations:2
xc: debug: hypercall buffer: cache current size:2
xc: debug: hypercall buffer: cache hits:1248 misses:2 toobig: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-21 10:26 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
2012-05-18 15:58       ` Ian Campbell
2012-05-21 10:26         ` Christoph Egger [this message]
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=4FBA185A.3080306@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).