similar to: Bug#399073: xen-hypervisor-3.0.3-1-i386: dom0 crashes with a domU that define more than 6 vdb

Hi all, I'm experiencing a systematic crash with icecast2 when I goes in this case (tested with debian 2.3.1-5 2.3.1-6 and latest trunk) When there is more than ~1400 clients connected and a mountpoint that was not relaying goes online it crash. Without this I can go up to 5000 clients without problems. Changing the number of threadpool does'nt change anything. here is the term log:

I hate intermittent problems ... Most of the time, my domUs launch just fine. But, occasionally I get a failure to connect a vdb or vif and the domU fails to completely launch ("xm list" shows it is present but no console activity either through "xm create -c" or through "xm console"). The log shows a stack trace in DevController.py in the area of waiting for

I hate intermittent problems ... Most of the time, my domUs launch just fine. But, occasionally I get a failure to connect a vdb or vif and the domU fails to completely launch ("xm list" shows it is present but no console activity either through "xm create -c" or through "xm console"). The log shows a stack trace in DevController.py in the area of waiting for

Hello, I''m testing Btrfs RAID1 feature on 3 disks of ~10GB. Last one is not exactly 10GB (would be too easy). About the test machine, it''s a kvm vm running an up-to-date archlinux with linux 3.7 and btrfs-progs 0.19.20121005. #uname -a Linux seblu-btrfs-1 3.7.0-1-ARCH #1 SMP PREEMPT Tue Dec 11 15:05:50 CET 2012 x86_64 GNU/Linux Filesystem was created with : # mkfs.btrfs -L

Package: xen-hypervisor-3.0.3-1-amd64 Version: 3.0.3-0-2 Severity: important On a machine with 2 dual-core Opterons and 16GB of memory, only about 3GB is detected by the hypervisor. Transcript: root at thismachine:~# xm dmesg Xen version 3.0.3-1 (Debian 3.0.3-0-2) (ultrotter at debian.org) (gcc version 4.1.2 20061028 (prerelease) (Debian 4.1.1-19)) Fri Nov 3 00:21:27 CET 2006 Latest

http://bugs.freedesktop.org/show_bug.cgi?id=13815 Summary: Wrong url for http get Product: swfdec Version: git Platform: Other URL: http://www.betterworldbooks.com/Flash/output.swf OS/Version: All Status: NEW Severity: normal Priority: medium Component: library AssignedTo: swfdec at

Package: xen-hypervisor-4.3-amd64 Version: 4.3.0-3+b1 Severity: normal Dear Maintainer, After booting into kernel 3.13 dom0, the keyboard no longer works. All other aspects work, ssh is needed to login to the system to start working with the domU's. They keyboard works at the grub menu just fine, and works normal when booting into the non xen kernel. -- System Information: Debian Release:

Package: xen-hypervisor-3.2-1-i386 Version: 3.2-1 Severity: critical Tags: security Justification: DoS of entire system regardless of privilege When running the exploit listed in bug 464953 [1], Xen's memory state becomes corrupted and the hypervisor eventually crashes, taking all of the domU's with it. As such, this breaks operational behaviour, so I have marked this as critical. [1]

Package: xen-hypervisor-4.0-i386 Version: 4.0.1~rc6-1 Severity: important --- Please enter the report below this line. --- Booting up the Xen Dom0 fails with an error in "i387.c:159" --- System information. --- Architecture: i386 Kernel: Linux 2.6.32-5-686-bigmem Kernel: Linux 2.6.32-5-xen-686 Debian Release: squeeze/sid 500 testing security.debian.org 500

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3+deb7u1 Severity: important Dear Maintainer, Just upgraded a Supermicro server (X9SCM-F motherboard) from Squeeze to Wheezy. And now the IPMI serial console no longer work as it used to. It hangs like this: [...] (XEN) Enabled directed EOI with ioapic_ack_old on! (XEN) ENABLING IO-APIC IRQs (XEN) -> Using old ACK method (XEN) Platform timer

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-1 Severity: grave Tags: squeeze sid Justification: causes non-serious data loss Live migration of a guest (running CentOS 5.5, Paravirtualized) crashes the target-host (Hardware: Dell R610, 2x Xeon 5620, 16Gb RAM, Perc/700-Raid) (XEN) ----[ Xen-4.0.1 x86_64 debug=n Not tainted ]---- (XEN) CPU: 9 (XEN) RIP: e008:[<ffff82c4801151f6>]

Package: xen-hypervisor-3.0.3-1-amd64 Version: 3.0.3-0-2 Severity: important about every 1 in 10 boots I am getting the following error: (XEN) ************************************ (XEN) CPU0 FATAL TRAP 6 (invalid opcode), ERROR_CODE 0000, IN INTERRUPT CONTEXT. (XEN) System shutting down -- need manual reset. (XEN) ************************************ This seems to happen in the CPU detection

Package: xen-hypervisor-4.3-amd64 Version: 4.3.0-3+b1 Severity: critical File: xen-hypervisor-4.3-amd Justification: breaks the whole system Dear Maintainer, Installation is a minimal system designed only to get dom0 working. The following are the uncommented GRUB commands GRUB_DEFAULT=0 GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`

Package: src:xen Version: 4.14.1+11-gb0b734a8b3-1 Severity: critical Justification: causes serious data loss X-Debbugs-Cc: debianbts at virtualzone.hu Dear Maintainer, after a clean install of bullseye/testing the xen dmesg shows the following message: (XEN) AMD-Vi: IO_PAGE_FAULT: 0000:01:00.1 d0 addr fffffffdf8000000 flags 0x8 I this is the sata device: 01:00.1 SATA controller: Advanced Micro

Package: xen-hypervisor-4.0-i386 Version: 4.0.1-4 This is the same machine referenced in http://bugs.debian.org/665413. It is an HP d530 SFF workstation (model DG784A) with 4GiB of RAM. It has run for years on the lenny xen + linux stack. If my notes are correct, it also ran smoothly for about a year with the lenny hypervisor + kernel and the squeeze userland. Rebooting into squeeze xen +

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9+deb8u1 Severity: critical Justification: breaks the whole system Dear Maintainer, -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8,

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9+deb8u4 Severity: important Dear Maintainer, I installed a fresh Debian Jessie amd64 on our new server with Intel Xeon E3-1270 v5 Skylake CPU and EFI. Linux without Xen boots flawlessly and shows 8 CPU cores. I then tried all combinations of Xen 4.4 (with xsave=off for Skylake support), Xen 4.6 (crashes after a few seconds during boot) and

Hello, I work for the company Smartjog (http://smatjog.com/) where we use a modified version of Icecast. We would like to contribute back those patchs, and hopefully have them merged in the official repository. I have posted them on the patch tracker, so feel free to leave a comment on them. Some of those patch are based on the work done by Niv Sardi (see

Hello, I work at SmarctJog.com, we have here some patches on IceCast for performance and reliability, these are mostly client/connection/source cleanups (a slave merge is underway, and some more good stuff (c)), but we'd like this to be merged in before the list gets any longer. Please find attached a list of our patches with a short desc: This one is actually not from us/me, it was found

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-2 Severity: important the xen-utils packages lack xfrd, which is required for live domain migrations using xm migrate. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-1-686 Locale: