similar to: Kernel panic with 2.6.32-30 under network activity

Hi, I''m trying to install Debian Squeeze as DomU on an openSUSE 11.4 Xen host but fail all the time. I''ve also searched Google and Debian as well as openSUSE resources but haven''t found any hint about my issue :-( First I''ve tried to install it as a paravirtualized guest but when the Debian installer tries to detect the disks I get this: [ 173.233735]

Hello, kernels 2.6.35.5 and 2.6.32.22 xen domU panics at the very begining of the boot process. I have bisected it to a single commit, and the first bad commit is: [fb412a178502dc498430723b082a932f797e4763] xen: use percpu interrupts for IPIs and VIRQs kernel v2.6.35.5 with reverted this commit works for me. Here are the kernel configs I was using:

Hello, kernels 2.6.35.5 and 2.6.32.22 xen domU panics at the very begining of the boot process. I have bisected it to a single commit, and the first bad commit is: [fb412a178502dc498430723b082a932f797e4763] xen: use percpu interrupts for IPIs and VIRQs kernel v2.6.35.5 with reverted this commit works for me. Here are the kernel configs I was using:

Hi experts I use xen-4.0.0 and dom0 is 2.6.33 and domU is 2.6.34 #lspci ............... 01:00.0 Ethernet controller: Intel Corporation Unknown device 10a7 (rev 02) 01:00.1 Ethernet controller: Intel Corporation Unknown device 10a7 (rev 02) 05:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06) 05:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit

Use PM_FREEZE, PM_THAW and PM_RESTORE power events for suspend/resume/checkpoint functionality, instead of PM_SUSPEND and PM_RESUME. Use of these pm events fixes the Xen Guest hangup when taking checkpoints. When a suspend event is cancelled (while taking checkpoints once/continuously), we use PM_THAW instead of PM_RESUME. PM_RESTORE is used when suspend is not cancelled. See

https://bugzilla.netfilter.org/show_bug.cgi?id=852 Summary: IPv6 TEE target sends packets to original IP address on wrong network device Product: netfilter/iptables Version: unspecified Platform: x86_64 OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: unknown

Package: xen-hypervisor-3.4-amd64 and linux-image-2.6.32-5-xen-amd64 Version: 3.4.3-1 and 2.6.32-15 Hello all, GRUB-PC does not automatically populate Xen related parameters in /boot/grub/grub.cfg so I added them manually (see below). All the packages involved on my Dell PowerEdge R710 running Debian GNU/Linux Squeeze AMD64 are from the Squeeze repository. There are four (4) 1TB SATA HDD

[This email is either empty or too large to be displayed at this time]

1.if xen.4.0.tar and kernel/arch/xen is all code? thansk _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

hi, I tried to make huge page request in Fedora x86_64 PV guest using xen 4.1 unstable and it crashed(crash info given below) I had enabled superpages in config file I had also set hugepages parameter at boot time for the PV Dom U By excuting # cat /proc/mem_info | grep Huge gave me that there are 10 free huge pages available , still the domain crashed. [ 86.403654] BUG: unable to handle

Hi! We have a problem that the dom0 very often does not boot and hangs in the hypervisor - see screenshot. The last message is: (XEN) Dom0 has maximum 16 VCPUs (afterwards xen should overwrite the memory) We are using the xen kernel from kernel.org git. Kernel is 2.6.32.24-xen with Xen 4.0.1 Hardware is HP DL380. Is this a known problem? Any hints what could be the problem and how we can

Hi! We have a problem that the dom0 very often does not boot and hangs in the hypervisor - see screenshot. The last message is: (XEN) Dom0 has maximum 16 VCPUs (afterwards xen should overwrite the memory) We are using the xen kernel from kernel.org git. Kernel is 2.6.32.24-xen with Xen 4.0.1 Hardware is HP DL380. Is this a known problem? Any hints what could be the problem and how we can

On Fri, 2013-06-28 at 12:17 +0800, Joe Jin wrote: > Find a similar issue http://www.gossamer-threads.com/lists/xen/devel/265611 > So copied to Xen developer as well. > > On 06/27/13 13:31, Eric Dumazet wrote: > > On Thu, 2013-06-27 at 10:58 +0800, Joe Jin wrote: > >> Hi, > >> > >> When we do fail over test with iscsi + multipath by reset the switches

Anybody have any issues running tdmoe on kernel 2.6+? I've got Suse 9.1 + 9.2 running 2.6.5 and 2.6.8 respectively, and when I enable dynamic spans between them, both boxes dump something similar to: Badness in local_bh_enable at kernel/softirq.c:141 [<c0120768>] local_bh_enable+0x48/0x60 [<c02952b0>] dev_queue_xmit+0x230/0x240 [<c02a0980>] eth_header+0x0/0x140

Hello, I'm having a problem, I've seen other people with the same problem, but with USB. Some people solved this with the pciback.permissive option, but in my case it's ignored. I'm using CentOS 5.2 - 2.6.18-92.1.10.el5.centos.plusxen The error return from the console starting the domU is below. I've tried swiotlb=force, pciback.permissive like I said. My configs are:

Get blktap2 running on pvops. This mainly adds eventfd support to the userland code. Based on some prior cleanup to tapdisk-queue and the server object. We had most of that in XenServer for a while, so I kept it stacked. 1. Clean up IPC and AIO init in tapdisk-server. [I think tapdisk-ipc in blktap2 is basically obsolete. Pending a later patch to remove it?] 2. Split tapdisk-queue into

I have the exact same issue on several Sunfire v20z (hardware LSI RAID controler). Under high IO load, the raid controler starts complaining with disk errors : [163442.483878] mptbase: ioc0: LogInfo(0x11070000): F/W: DMA Error [163445.172333] sd 2:0:0:0: [sda] Unhandled error code [163445.172338] sd 2:0:0:0: [sda] Result: hostbyte=DID_SOFT_ERROR driverbyte=DRIVER_OK [163445.172345] sd 2:0:0:0:

Previous 2.6.31-rc8 kernel was built on F11 and installed with modules on F12. Current kernel has been built on F12 (2.6.31-0.204.rc9.fc12.x86_64) and installed on F12 before loading under Xen 3.4.1. Dmesg log looks similar to Michael Yuong''s ''rc7.git4''  kernel for F12. Boris. --- On Tue, 9/8/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: From: Boris

I''m getting this: blktap_validate_params: aio:/dev/vg_lilith-raid/xen-f13-64: capacity: 20971520, sector-size: 512 blktap_validate_params: aio:/dev/vg_lilith-raid/xen-f13-64: capacity: 20971520, sector-size: 512 blktap_device_create: minor 0 sectors 20971520 sector-size 512 blktap_device_create: creation of 253:0: 0 INFO: trying to register non-static key. the code is fine but needs

what does it mean? i never seen that before xen4 on debian squeeze 2.6.32-5-xen-amd64 [22077.208077] BUG: soft lockup - CPU#7 stuck for 61s! [udisks-dm-expor:11772] [22077.208139] Modules linked in: ext4 jbd2 crc16 xfs exportfs xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack xt_physdev bridge stp ip6table_filter ip6_tables iptable_filter ip_tables x_tables xen_evtchn xenfs fuse