From: Ian Campbell <Ian.Campbell@citrix.com>
To: Rishi Ranjan <rishi.rranjan@gmail.com>
Cc: xen-devel@lists.xensource.com, Anthony.Perard@citrix.comm,
qemu-devel@nongnu.org,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] [Xen-devel] bind interdomain ioctl error xen-kvm.c
Date: Tue, 6 Jan 2015 10:44:26 +0000 [thread overview]
Message-ID: <1420541066.28863.117.camel@citrix.com> (raw)
In-Reply-To: <CAGontdL3B9M+QZJDYqi4JuTv6QuayP8yTaK5bEfqbZSa=74y=w@mail.gmail.com>
On Mon, 2015-01-05 at 11:10 -0800, Rishi Ranjan wrote:
> Hi Stefano,
> Please find my answers inline.
>
>
> >>>> However Anthony (CC'ed) should have some patches for it.
>
> Anthony, can you please share any patch that can help me with this?
>
>
>
>
> >>>> Can you post the full output of the logs?
> I have attached the output of "sudo xl -v create /etc/xen/qemu-pv.cfg"
> as xl_create.txt. I have also enabled DEBUG_XEN_HVM in xen-hvm.c and
> pasted output of "sudo ./x86_64-softmmu/qemu-system-x86_64 -machine
> q35,accel=xen -cpu qemu64 -xen-domid 13" below:
Have you done anything which stops "xl create" from also launching a
qemu? The guest cfg file you posted earlier didn't suggest so. Running
two qemu's against the same domain doesn't seem likely to result in good
things...
> >>>>Did you execute the xencommons init script at boot time?
> On Ubuntu I don't see /etc/init.d/xencommon but there is
> a /etc/init.d/xen script which starts xenstored and xenconsoled.
Yes, Debian and Ubuntu don't use the upstream initscript but have their
own.
Ian.
next prev parent reply other threads:[~2015-01-06 10:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-30 23:35 [Qemu-devel] bind interdomain ioctl error xen-kvm.c Rishi Ranjan
2015-01-05 12:48 ` Stefano Stabellini
2015-01-05 19:10 ` Rishi Ranjan
2015-01-05 23:58 ` Don Slutz
2015-01-06 10:44 ` Ian Campbell [this message]
2015-01-06 11:11 ` Anthony PERARD
2015-01-06 11:32 ` Anthony PERARD
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=1420541066.28863.117.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Anthony.Perard@citrix.comm \
--cc=qemu-devel@nongnu.org \
--cc=rishi.rranjan@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).