From: Joseph Glanville <joseph.glanville@orionvm.com.au>
To: John McMonagle <johnm@advocap.org>
Cc: xen-devel <xen-devel@lists.xensource.com>, xen-users@lists.xensource.com
Subject: Re: xl block-list error.
Date: Fri, 13 May 2011 22:21:44 +1000 [thread overview]
Message-ID: <BANLkTin-wDm__APdeLij0tZ=OGjMOPm=uA@mail.gmail.com> (raw)
In-Reply-To: <201105121501.44252.johnm@advocap.org>
Hi,
Issues with the xl stack should be fowarded to Ian Jackson and the
xen-devel list. I have cc'd in the xen-devel list which should get the
issue attended to. Also I think this bug may already be fixed, which
someone will be able to confirm.
Joseph.
On 13 May 2011 06:01, John McMonagle <johnm@advocap.org> wrote:
> Noticed if I started domain with xl it works.
> Even if that is required a Segmentation fault seems extreme.
>
> John
>
>
> On Thursday, May 12, 2011 09:01:18 am John McMonagle wrote:
>> Experimenting with the xl interface and get and error with the block-list
>> command.
>>
>> root@fdlxen1:~# xm block-list sq64
>> Vdev BE handle state evt-ch ring-ref BE-path
>> 51714 0 0 4 8 768 /local/domain/0/backend/vbd/2/51714
>> 51713 0 0 4 9 769 /local/domain/0/backend/vbd/2/51713
>>
>> root@fdlxen1:~# xl block-list sq64
>> Vdev BE handle state evt-ch ring-ref BE-path
>> Segmentation fault
>>
>> in dmesg have:
>> xl[11282]: segfault at 0 ip 00007f5164b7f6d2 sp 00007fff2150df50 error 4 in
>> libc-2.11.2.so[7f5164b48000+158000]
>>
>> Tried on 3 servers with the same result.
>>
>> All are Debian squeeze with Debian kernel and xen 4.1.0 built from source.
>>
>> John
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xensource.com
>> http://lists.xensource.com/xen-users
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
--
Kind regards,
Joseph.
Founder | Director
Orion Virtualisation Solutions | www.orionvm.com.au | Phone: 1300 56
99 52 | Mobile: 0428 754 846
parent reply other threads:[~2011-05-13 12:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <201105121501.44252.johnm@advocap.org>]
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='BANLkTin-wDm__APdeLij0tZ=OGjMOPm=uA@mail.gmail.com' \
--to=joseph.glanville@orionvm.com.au \
--cc=johnm@advocap.org \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@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).