similar to: Bug#701744: We see the same with Debian wheezy.

Displaying 10 results from an estimated 10 matches similar to: "Bug#701744: We see the same with Debian wheezy."

2013 Mar 29
0
Bug#701744: [xen] Update to hypervisor 4.0.1-5.6 or linux-image-2.6.32-5-xen-amd64 2.6.32-48 causes networking (VIF) failures
Hello, I was also hit by this problem. Perhaps it is related to the xen-netback module in the dom0 kernel? Have a look at: http://www.gossamer-threads.com/lists/xen/devel/275548 -- greetings eMHa -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL:
2013 Apr 11
0
Bug#701744: xen-hypervisor-4.0-amd64: also seeing this problem on 4.0.1-5.8
Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-5.8 Severity: critical We're seeing this too on 4.0.1-5.8, and it's causing major problems. Xen on Debian Squeeze is basically unusable with the latest packages. Is a fixed package in sight? Thanks, Ward. -- System Information: Debian Release: 6.0.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500,
2013 Apr 22
0
Bug#701744: Possible workaround.
It might help to disable TSO and GSO inside the Linux PV guest with ethtool. ethtool -K eth0 tso off gso off
2013 May 24
0
Bug#701744: [xen] Update to hypervisor 4.0.1-5.6 or linux-image-2.6.32-5-xen-amd64 2.6.32-48 causes networking (VIF) failures
Hello, We are also encountering this critical issue. I hope a solution will be found shortly. J?rg
2013 Feb 26
1
Bug#701744: [xen] Update to hypervisor 4.0.1-5.6 or linux-image-2.6.32-5-xen-amd64 2.6.32-48 causes networking (VIF) failures
Package: xen Version: 4.0.1-5.5 Severity: critical --- Please enter the report below this line. --- Hi! Since the update last weekind in stable/squeeze I'm experiencing problems with running Xen on amd64 and multiple domUs losing their network connection/VIFs. From http://blog.windfluechter.net/content/blog/2013/02/26/1597-xen-problems-vms-2632-5-xen-amd64 Unfortunately this update
2013 Jul 17
4
[xen-unstable] FATAL PAGE FAULT when shutting down guest with pci passthrough using MSI interrupts
Hi Jan, It seems the last changes to xen-unstable to implement multi-msi-irq''s cause some trouble. The guest starts and works fine. But it causes a xen crash when shutting the guest down. (xen_changeset: Thu Jul 4 16:01:06 2013 +0100 git:d4435fe) If you need more info than given below in the serial log snippet, just say so .. -- Sander (XEN) [2013-07-17 19:10:09] AMD-Vi: Share p2m
2018 Aug 03
0
[net-next, v6, 6/7] net-sysfs: Add interface for Rx queue(s) map per Tx queue
On Fri, Aug 03, 2018 at 12:06:51PM -0700, Andrei Vagin wrote: > On Fri, Aug 03, 2018 at 12:08:05AM +0300, Michael S. Tsirkin wrote: > > On Thu, Aug 02, 2018 at 02:04:12PM -0700, Nambiar, Amritha wrote: > > > On 8/1/2018 5:11 PM, Andrei Vagin wrote: > > > > On Tue, Jul 10, 2018 at 07:28:49PM -0700, Nambiar, Amritha wrote: > > > >> With this patch series,
2013 Feb 01
45
netback Oops then xenwatch stuck in D state
We''ve been hitting the following issue on a variety of hosts and recent Xen/dom0 version combinations. Here''s an excerpt from our latest: Xen: 4.1.4 (xenbits @ 23432) Dom0: 3.7.1-x86_64 BUG: unable to handle kernel NULL pointer dereference at 000000000000001c IP: [<ffffffff8141a301>] evtchn_from_irq+0x11/0x40 PGD 0 Oops: 0000 [#1] SMP Modules linked in: ebt_comment
2008 Jun 16
1
3.2.1 HVM network packets dropped
Dear, I''ve attempted to upgrade a Xen box from 3.1.2 to 3.2.1. Unfortunately it has been a partial success only. At this point I''m really stuck with a network problem that affects my HVM machines (Linux PV run fine). The really odd thing is that everything seems to work properly, except that the "vif" network interfaces in dom0 seem to have only dropped TX packets for
2013 Apr 30
13
WARNING: at fs/btrfs/free-space-cache.c:921 __btrfs_write_out_cache+0x6b9/0x9a0 [btrfs]()
Hello On my HP Compaq dc5800 with Ubuntu 13.04 and their 3.8.0-19-lowlatency kernel, I''ve got quite some kernel traces in the syslog. You can find them below or at http://pastebin.com/bLXPBX67 (to avoid line breaks…). These kernel traces all begin with: WARNING: at fs/btrfs/free-space-cache.c:921 __btrfs_write_out_cache+0x6b9/0x9a0 [btrfs]() Most of the time, it starts with: Call