similar to: Bug#611278: linux-image-2.6.32-5-xen-amd64: boot fails when iommu is enabled in bios

Hi all, RMS would like to see more user friendly OpenSSH client error messages. Specifically, he would like to see the "permission denied" error messages easier to understand. If one tries to log into a machine that is configured to only accept publickey authentication and the key doesn't match, the client output is $ ssh user at server Permission denied (publickey). If the

Processing commands for control at bugs.debian.org: > reassign 611278 xen-hypervisor-4.0-amd64 4.0.1-1 Bug #611278 [linux-2.6] linux-image-2.6.32-5-xen-amd64: boot fails when iommu is enabled in bios Bug reassigned from package 'linux-2.6' to 'xen-hypervisor-4.0-amd64'. Bug No longer marked as found in versions 2.6.32-30. Bug #611278 [xen-hypervisor-4.0-amd64]

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-5.2 Severity: important Tags: patch I have a system based on a Supermicro X8DTH-i motherboard and a Xeon E5506 CPU. It was previously running Debian lenny with xen-hypervisor-3.2-1-amd64 / linux-image-2.6.26-2-xen-amd64 without incident. I upgraded it to Debian squeeze, with xen-hypervisor-4.0-amd64 / linux-image-2.6.32-5-xen-amd64 and now it does

Hi, I can''t get rid of an annoying domU machines hanging issue with Hyperthreading enabled in my BIOS. Hardware config: IBM x325 series 2 * CPUs Intel Xeon 3.06 Ghz Xen version: 3.0.0 Kernel version: 2.6.12.6 Linux distrib: Debian Sarge 3.1 r1 I run 1 domU machine on my dom0, here is my Xen config: . xen0: /etc/xen/xend-config.sxp : (dom0-num-cpus 0) .

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,

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:

Hello, We are also encountering this critical issue. I hope a solution will be found shortly. J?rg

Processing commands for control at bugs.debian.org: > severity 606589 important Bug #606589 [xen-linux-system-2.6.32-5-xen-amd64] xen-linux-system-2.6.32-5-xen-amd64 doesn't upgrade from xen-linux-system-2.6.26-2-xen-amd64 Severity set to 'important' from 'serious' > reassign 606589 xen-hypervisor-4.0-amd64 Bug #606589 [xen-linux-system-2.6.32-5-xen-amd64]

On 12/10/2010 11:37 PM, Ian Campbell wrote: > severity 606589 important > reassign 606589 xen-hypervisor-4.0-amd64 > merge 606590 606589 > thanks > > At the core this is the same issue as 606590. I think a single report is > enough to allow this to be fixed in the relevant place, if the kernel > ends up being the place to fix then the bug can be reassigned as >

Your message dated Sat, 14 Apr 2012 19:24:04 +0200 with message-id <20120414172403.GA25566 at wavehammer.waldi.eu.org> and subject line meta-packages available has caused the Debian Bug report #606589, regarding xen-linux-system-2.6.32-5-xen-amd64 doesn't upgrade from xen-linux-system-2.6.26-2-xen-amd64 to be marked as done. This means that you claim that the problem has been dealt

Following the ACPI spec. I improved the way the RSDP is found in the BIOS extension so that it will still be found if it ever moves. Also makes the code look better. Signed-off-by: Stefan Berger <stefanb@us.ibm.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Decided to try out lpxelinux on a couple of Dell R610s. Both versions 5.10 and 6.03 hung on a server with fairly up-to-date BIOS (6.1.0), but work fine on another R610 with old BIOS (1.2.6). Watching the TFTP log and running tcpdump on the PXE server, I see it download pxelinux.0 (renamed from lpxelinux.0), but it never even tries to transfer anything after that succeeds. It eventually (seems

This patch adds TCG BIOS extensions to the high memory area along with some often-used libc utility functions. The TCG extensions are described here: https://www.trustedcomputinggroup.org/specs/PCClient/TCG_PCClientImplementationforBIOS_1-20_1-00.pdf I have tried to keep the patching with rombios.c to a minimum, but some amount of code needs to be inserted at various locations. The code is

Dear WizaRds, My goal is to program the VS-KM algorithm by Brusco and Cradit 01 and I have come to a complete stop in my efforts. Maybe anybody is willing to follow my thoughts and offer some help. In a first step, I want to use a single variable for the partitioning process. As the center-matrix I use the objects that belong to the cluster I found with the hierarchial Ward algorithm. Then,

We appear to have some phantom DNS records on both our domain controllers. We can see the records using "dig", but not with samba-tool. We can't remove the records either. (v-ward and v-fief are the DCs, Hawaii and Alaska are old DCs which were demoted without errors, I'm trying to clean up some DNS records which don't seem to have been cleaned). All machines are

Processing commands for control at bugs.debian.org: > reassign 683170 linux-image-2.6.32-5-xen-amd64 Bug #683170 [xen-utils-4.0] Xend causing high CPU load - starting domU failing Bug reassigned from package 'xen-utils-4.0' to 'linux-image-2.6.32-5-xen-amd64'. No longer marked as found in versions xen/4.0.1-5.2. Ignoring request to alter fixed versions of bug #683170 to the

Your message dated Fri, 06 Sep 2013 09:09:48 +0100 with message-id <1378454988.3057.2.camel at dagon.hellion.org.uk> and subject line Re: [Pkg-xen-devel] Bug#710522: Problem found has caused the Debian Bug report #710522, regarding xen-hypervisor-4.1-amd64: Boot hang with Linux 3.2+Xen, works with linux 2.6.32+Xen or 3.2 raw to be marked as done. This means that you claim that the problem

Hello community! I need help with a problem I haven''t been solved with the network team. I manage a network that has over a thousand computers, and the most of the servers are virtualized over Debian / Xen by me. The specific issue arises when I try to set up a DomU HVM running Debian Squeeze, the VM doesn''''t recognize the network but it runs. It gives an error

Hey all, I have a problem with Xen 4.2 on Debian Squeeze with Kernel 2.6.32-5-xen-amd64. I rebuilded the source packages from Debian experimental trunk on Squeeze and installed them. Also I installed the Kernel 2.6.32-5-xen-amd64 from the Debian Squeeze trunk. Now it looks like that Xen can''t load the Dom0. After registering netback strange modprobe errors appear. In the attachment

Signed-off-by: Attilio Rao <attilio.rao@citrix.com> Acked-by: Ian Campbell <ian.campbell@citrix.com> --- Differences with previous revision: - Improvements to the manpage: * s/operated/made * s/compatbile/compatible * New paragraph for rombios, provided by Ian * s/force/request * redundant line removal in UEFI explanatory * Wrap of lines at 80 cols diff -r adcd6ab160fa