From: David Vrabel <david.vrabel@citrix.com>
To: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
<netdev@vger.kernel.org>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: [Xen-devel] xen-netfront crash when detaching network while some network activity
Date: Fri, 22 May 2015 17:58:41 +0100 [thread overview]
Message-ID: <555F6041.7000203@citrix.com> (raw)
In-Reply-To: <20150522164246.GE957@mail-itl>
On 22/05/15 17:42, Marek Marczykowski-Górecki wrote:
> On Fri, May 22, 2015 at 05:25:44PM +0100, David Vrabel wrote:
>> On 22/05/15 12:49, Marek Marczykowski-Górecki wrote:
>>> Hi all,
>>>
>>> I'm experiencing xen-netfront crash when doing xl network-detach while
>>> some network activity is going on at the same time. It happens only when
>>> domU has more than one vcpu. Not sure if this matters, but the backend
>>> is in another domU (not dom0). I'm using Xen 4.2.2. It happens on kernel
>>> 3.9.4 and 4.1-rc1 as well.
>>>
>>> Steps to reproduce:
>>> 1. Start the domU with some network interface
>>> 2. Call there 'ping -f some-IP'
>>> 3. Call 'xl network-detach NAME 0'
>>
>> I tried this about 10 times without a crash. How reproducible is it?
>>
>> I used a 4.1-rc4 frontend and a 4.0 backend.
>
> It happens every time for me... Do you have at least two vcpus in that
> domU? With one vcpu it doesn't crash. The IP for ping I've used one in
> backend domU, but it shouldn't matter.
>
> Backend is 3.19.6 here. I don't see any changes there between rc1 and
> rc4, so stayed with rc1. With 4.1-rc1 backend it also crashes for me.
Doesn't repro for me with 4 VCPU PV or PVHVM guests. Is your guest
kernel vanilla or does it have some qubes specific patches on top?
David
next prev parent reply other threads:[~2015-05-22 16:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 11:49 xen-netfront crash when detaching network while some network activity Marek Marczykowski-Górecki
2015-05-22 16:25 ` David Vrabel
2015-05-22 16:25 ` [Xen-devel] " David Vrabel
2015-05-22 16:42 ` Marek Marczykowski-Górecki
2015-05-22 16:58 ` David Vrabel [this message]
2015-05-22 17:13 ` Marek Marczykowski-Górecki
2015-05-22 17:13 ` [Xen-devel] " Marek Marczykowski-Górecki
2015-05-22 16:58 ` David Vrabel
2015-05-22 16:42 ` Marek Marczykowski-Górecki
2015-05-26 10:56 ` David Vrabel
2015-05-26 22:03 ` Marek Marczykowski-Górecki
2015-05-26 22:03 ` Marek Marczykowski-Górecki
2015-10-21 18:57 ` Marek Marczykowski-Górecki
2015-11-17 2:45 ` Marek Marczykowski-Górecki
2015-12-01 22:00 ` Konrad Rzeszutek Wilk
2015-12-01 22:32 ` Marek Marczykowski-Górecki
2016-01-20 21:59 ` Konrad Rzeszutek Wilk
2016-01-21 12:30 ` Joao Martins
2016-01-22 19:23 ` Marek Marczykowski-Górecki
2016-01-22 19:23 ` Marek Marczykowski-Górecki
2016-01-21 12:30 ` Joao Martins
2015-12-01 22:32 ` Marek Marczykowski-Górecki
2015-11-17 2:45 ` Marek Marczykowski-Górecki
2015-11-17 11:59 ` [Xen-devel] " David Vrabel
2015-11-17 11:59 ` David Vrabel
2015-10-21 18:57 ` Marek Marczykowski-Górecki
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=555F6041.7000203@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=marmarek@invisiblethingslab.com \
--cc=netdev@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.