similar to: Debian Squeeze hangs with kernel 2.6.32-5-xen-686

Hi, i have big trouble with a Debian Lenny dom0 and latest kernel 2.6.32.19 with xen-4.0.1rc5. Due some reason the system freezes from time to time. I used kernel 2.6.31.9 with xen-3.4.2 before. The machine doesn''t write anything to serial console so there are no errors or something like that. Perhaps there is something to see from the logs ... Hardware Board: Intel DQ45CB CPU:

Did a ''git pull'' a few minutes ago and tried to rebuild my kernel and was given this error: make CHK include/linux/version.h CHK include/linux/utsrelease.h SYMLINK include/asm -> include/asm-x86 CALL scripts/checksyscalls.sh CHK include/linux/compile.h CC drivers/acpi/acpica/hwsleep.o drivers/acpi/acpica/hwsleep.c: In function

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

Dear all, I have running a DOM-0 on debian squeeze with the most recent kernel: Linux 2.6.32-5-xen-amd64 #1 SMP On 30% of all reboots the system hangs and only a reset helps. acpi=off as an additional kernel parameter solves this problem, but the usb keyboard of the installed ip-kvm is not found then. with acpi=off Ican find a lot stuff like: [ 7.098747] uhci_hcd 0000:00:1d.2: UHCI Host

Hello, I tried out kernel 3.1.0-rc2 on my i386 Laptop with Xen 4.1.1. Booting hangs after these messages on the VGA console: pci 0000:02:09.0: address space collision: [mem 0x000da000-0x000dafff] conflicts with reserved [mem 0x0009f800-0x000fffff] reserve RAM buffer: 00000000 0009f000 - 00000000 0009ffff reserve RAM buffer: 00000000 38400000 - 00000000 3bffffff reserve RAM buffer: 00000001

Hello, I tried out kernel 3.1.0-rc2 on my i386 Laptop with Xen 4.1.1. Booting hangs after these messages on the VGA console: pci 0000:02:09.0: address space collision: [mem 0x000da000-0x000dafff] conflicts with reserved [mem 0x0009f800-0x000fffff] reserve RAM buffer: 00000000 0009f000 - 00000000 0009ffff reserve RAM buffer: 00000000 38400000 - 00000000 3bffffff reserve RAM buffer: 00000001

Hi, I'm not sure but I think I suffer under the same problem with a bit different setup with squeeze testing and xen 4.0rc5. In fact I'm using bridges in the dom0 and the connections to the domU get lost sporadically. In don't see where's a solution to the problem... Is it now a bug? When it's an iptables bug, where's the corresponding bug in the iptables bugtracker

Hi All, I am trying to get the pv_ops Xen dom0 kernel working with Xen 3.4 but with no success. I have been at this for 2 weeks now with different problems. Initially I could not get dom0 to boot when using LVM, so I reinstalled and didn''t use LVM. Now I am getting stack overran or currupted errors. Here is the boot log; From <IRQ 0> to the last line keeps on repeating until

Problem still not solved, or any idea whats wrong. here are some msgs: device vif1.0 entered promiscuous mode alloc irq_desc for 1246 on node 0 alloc kstat_irqs on node 0 brI: port 2(vif1.0) entering learning state device vif1.1 entered promiscuous mode brE: port 2(vif1.1) entering learning state physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for

Hello! I'm having problems getting PCI pass-through to work. This is on a AMD64 system, paravirtualized with xen-hypervisor-4.0-amd64 4.0.0-1~experimental.1, dom0: linux-image-2.6.32-5-xen-amd64 2.6.32-12. From IRC, earlier today: <tschwinge> waldi: Aren't the Debian xen domU-capable kernels supposed to contain the PCI frontend (needed for PCI pass-through)? I'm getting:

Hello! I'm having problems getting PCI pass-through to work. This is on a AMD64 system, paravirtualized with xen-hypervisor-4.0-amd64 4.0.0-1~experimental.1, dom0: linux-image-2.6.32-5-xen-amd64 2.6.32-12. From IRC, earlier today: <tschwinge> waldi: Aren't the Debian xen domU-capable kernels supposed to contain the PCI frontend (needed for PCI pass-through)? I'm getting:

Hi all, I recently bought a Intel D2500HN motherboard with Intel GMA 3600 video card. I want to install FreeBSD 9-Release on it via PXE, but after booting the system, it seems that video card driver doesn't work properly. Have a look at this picture: http://img703.imageshack.us/img703/5648/20120714393.jpg I've tried the # vidcontrol 80x25 but unfortunately it doesn't help. Do

Hi, another issue I''m seeing with 3.0-rc2 and Xen is that there is an unexpectedly high amount of kernel reserved memory. I suspect that Linux allocates page table entries and corresponding data structures for the whole 6GB areas of the provided ''physical RAM map'' even though it has rather big unusable holes in it. [ 0.000000] BIOS-provided physical RAM map: [

Konrad, et al, I am seeing visual corruption (almost like an interlacing problem) with i915 under Xen on some platforms using linux-3.8. See attached file for an example of the visual corruption. This particular platform is an HP Elitebook 2540p The same kernel and ramdisk, when booted as native linux does not show this corruption. dmesg is attached, as well (out.txt) - but I did not see

I''ve uploaded Beta 4. It corrects a bad bug involving exclusion in the hosts file. In addition, it contains the first release of a new Bridge/firewall implementation that uses the reduced-function physdev match found in kernel 3.6.20 and 3.6.21. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \

I''ve uploaded Beta 4. It corrects a bad bug involving exclusion in the hosts file. In addition, it contains the first release of a new Bridge/firewall implementation that uses the reduced-function physdev match found in kernel 3.6.20 and 3.6.21. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \

Hi, I have a suspicious problem with multiple uplinks configuration. First of all my configuration: 1) kernel 2.6.20.3 2) iptables 1.3.7 3) last iproute (for masked marks) All wan interfaces are bridged (stp disabled) in only one interface (wan0), all lan interfaces are bridged (stp enabled) in only one interface (zlan0). The wan0 bridge is to allow UPnP works. To allow related

Hi folks, in 2.4 kernels, device matching for bridged packets was done with iptables -i/-o. Since 2.6, I was used to use -m physdev here. In 2.6.18, This seems to be more complicated. At least the filter/INPUT chain now doesn't match with -m physdev --physdev-in anymore, but FORWARD and OUTPUT does. I also read the note that -m phydev is now deprecated for non-bridged traffic. Does this

Package: xen-utils-common Version: 3.4.2-2 Severity: important The network setup uses not longer supported iptables operations: | physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. -- Those who hate and fight must stop themselves -- otherwise it is not stopped. -- Spock, "Day of the Dove", stardate

Hello! Since i could not find any information on the internet about this subject, i'm going to try my luck on this list. I'm trying to setup network-filter on a routed setup. I have a root-server at Hetzner, a german hosting provider. Along with my server i ordered a (/28) subnet to be able to setup dedicated IPs for my virtual machines (KVM). My Server is running Ubuntu 12.04 with