This bug was fixed in the package xen - 4.1.1-2ubuntu4.1
---
xen (4.1.1-2ubuntu4.1) oneiric-proposed; urgency=low
* debian/patches/xen-pirq-resubmit-irq.patch: Retrigger
pirq events when asserted while processing. Thanks to Stefan Bader
(LP: #854829)
-- Chuck ShortMon,
This bug was fixed in the package xen - 4.1.1-2ubuntu4.1
---
xen (4.1.1-2ubuntu4.1) oneiric-proposed; urgency=low
* debian/patches/xen-pirq-resubmit-irq.patch: Retrigger
pirq events when asserted while processing. Thanks to Stefan Bader
(LP: #854829)
-- Chuck ShortMon,
Tested the proposed package and it does give a working 8139cp connection
in HVM mode.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Hello Stefan, or anyone else affected,
Accepted xen into oneiric-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
**
** Changed in: xen (Ubuntu)
Status: Confirmed => Triaged
** Changed in: xen (Ubuntu)
Assignee: Stefan Bader (stefan-bader-canonical) => Chuck Short (zulcss)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
For completeness this is the backported version of the Xen 4.2 patch.
But since it is more complex, the recommendation would be to go with the
first (simpler) patch.
** Patch added: "Backport version of upstream patch"
https://bugs.launchpad.net/ubuntu/+source/xen/+bug/854829/+attachment/25175
The attachment "Minimal fix against Xen 4.1.1" of this bug report has
been identified as being a patch. The ubuntu-reviewers team has been
subscribed to the bug report so that they can review the patch. In the
event that this is in fact not a patch you can resolve this situation by
removing the t
This is the (tested) minimal fix for the xen 4.1.1 hypervisor. The
problem with the more complete patch against 4.2 is that it needs to
keep the number of "lost" interrupts per pirq. It does that by adding an
element to the pirq struct (which does not exist in 4.1.1). So for the
backport of that on
Stefano Stabellini replied:
Thanks for the very detailed analysis. It seems to me that the problem is that
if the interrupt is a level
triggered interrupt when the guest issues an EOI we should be reinjecting the
interrupt again if it has been issued a second time in the meantime. However
this
The patch needed some changes because the code we use in Oneiric is
4.1.1 and is different here. Tested the adapted patch and did not see
the network stalls anymore.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Replicating some information that was sent to the mailing list:
It took quite a bit of time but at least I got some hopefully useful information
now. So in general, whenever an interrupt is asserted,
the hypervisor runs through this:
__hvm_pci_intx_assert:
when assert count was 0 before increme
** Tags added: server-o-ro
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/854829
Title:
[Oneiric] Xen HVM: transmit timeouts on emulated 8139cp device
To manage notifications about this bug go to:
h
Testing various emulated devices shows:
- ne2k_pci gets the tx problems almost immediatly
- 8139cp on any slightly higher traffic
- e1000 seems to work
When pirq's are not used, 8139cp also works again. So there seems to be
a subtle bug in the delivery of those.
--
You received this bug notifica
13 matches
Mail list logo
