xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Sven Köhler" <sven.koehler@gmail.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Re: xl vs. xm, possible bug in xl
Date: Fri, 09 Sep 2011 14:43:30 +0200	[thread overview]
Message-ID: <4E6A09F2.4040405@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1109091254590.12963@kaball-desktop>


[-- Attachment #1.1: Type: text/plain, Size: 1699 bytes --]

Am 09.09.2011 14:05, schrieb Stefano Stabellini:
> On Fri, 9 Sep 2011, Sven Köhler wrote:
>> Am 09.09.2011 13:27, schrieb Stefano Stabellini:
>>>> Any clue, that the second problem is about?
>>>>> # xl create /etc/xen/xen-sk1
>>>>> Parsing config file /etc/xen/xen-sk1
>>>>> libxl: error: libxl_device.c:476:libxl__wait_for_device_model Device Model not ready
>>>>> xl: fatal error: libxl_create.c:535, rc=-1: libxl__confirm_device_model_startup
>>>
>>> That means that qemu failed to start. Could you please cat
>>> /var/log/xen/qemu-dm-domainname.log?
>>
>> There is no such file (my domain config lacks a name="something" line).
>> However qemu-dm-test.log does exist and is of recent date, and it says
>> that qemu cannot be started. This is very plausible, since qemu is not
>> even installed. This machine is supposed to start paravirt guests only.
>> And xen has been compiled without support for hvm guests. (Not sure
>> right now, what the gentoo people do to disable support support for hvm
>> guests).
>>
>> Does my config file for the domain (see one of my previous emails in
>> this thread) indicate, that the machine is a hvm domain? How can I tell
>> xl that this a paravirt domain, and qemu is not needed and should not be
>> used?
> 
> I think I have found the issue: if blktap2 is not enabled xl is going to
> start qemu (to provide a disk backend) even if it is not actually needed
> because the user wants to use blkback.
> 
> We have a patch upstream to fix this issue but it hasn't been backported
> to 4.1:

Thanks, sounds like this will fix my problem.

Is there any chance that this is going to be in 4.1.2 final?


Regards,
  Sven


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  parent reply	other threads:[~2011-09-09 12:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-08 16:42 xl vs. xm, possible bug in xl Sven Köhler
2011-09-08 17:07 ` Konrad Rzeszutek Wilk
2011-09-08 17:44   ` David Vrabel
2011-09-08 22:53   ` Sven Köhler
2011-09-09 11:27     ` Stefano Stabellini
2011-09-09 11:27       ` Sven Köhler
2011-09-09 12:05         ` Stefano Stabellini
2011-09-09 12:06           ` Stefano Stabellini
2011-09-09 12:43           ` Sven Köhler [this message]
2011-09-09 12:54             ` Stefano Stabellini
2011-09-09 14:16               ` Ian Campbell
     [not found]                 ` <alpine.DEB.2.00.1109091307080.12963@kaball-desktop>
2011-09-21 16:13                   ` Re: xl vs. xm, possible bug in xl (fwd) [and 1 more messages] Ian Jackson

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=4E6A09F2.4040405@gmail.com \
    --to=sven.koehler@gmail.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.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 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).