similar to: Working COMPAT_VDSO patch?

Hello, I am experimenting with Snort and other IDS and I would like to use Xen for these tests. This would require me to use port mirroring to sent a bunch of packets to a NIC located on my Xen machine. I don''t really know how Xen networking works, but is it possible to give a domU direct access to a NIC ? Or at least give it enough access so that it can see packets that are not for the

VMI is broken under COMPAT_VDSO, as Xen and other non hardware assisted hypervisors will be. I have been working on a fix for this which works for older glibcs that panic when the new relocatable VDSO is used. However, I believe at this time that the fix is going to be too radical to consider at this stage in the release of 2.6.21. We don't expect this config option to be turned on by

VMI is broken under COMPAT_VDSO, as Xen and other non hardware assisted hypervisors will be. I have been working on a fix for this which works for older glibcs that panic when the new relocatable VDSO is used. However, I believe at this time that the fix is going to be too radical to consider at this stage in the release of 2.6.21. We don't expect this config option to be turned on by

Paravirt-ops guests which move the fixmap also end up moving the syscall = VDSO. This fails if it is prelinked at a fixed address, which is why = COMPAT_VDSO is broken under CONFIG_VMI (and also under CONFIG_XEN). = Several options are available to try to address this. Jan had cooked up = a patch for Xen that used build magic to find the parts of the VDSO that = need relocation. I

Paravirt-ops guests which move the fixmap also end up moving the syscall = VDSO. This fails if it is prelinked at a fixed address, which is why = COMPAT_VDSO is broken under CONFIG_VMI (and also under CONFIG_XEN). = Several options are available to try to address this. Jan had cooked up = a patch for Xen that used build magic to find the parts of the VDSO that = need relocation. I

This adds support for CONFIG_COMPAT_VDSO. As this will certainly raise questions, I left in the code needed for an alternative approach (which requires mode C code, but less build script changes). Signed-off-by: Jan Beulich <jbeulich@novell.com> Index: head-2007-02-27/arch/i386/Kconfig =================================================================== ---

This adds support for CONFIG_COMPAT_VDSO. As this will certainly raise questions, I left in the code needed for an alternative approach (which requires mode C code, but less build script changes). Signed-off-by: Jan Beulich <jbeulich@novell.com> Index: head-2007-02-27/arch/i386/Kconfig =================================================================== ---

This adds support for CONFIG_COMPAT_VDSO. As this will certainly raise questions, I left in the code needed for an alternative approach (which requires mode C code, but less build script changes). Signed-off-by: Jan Beulich <jbeulich@novell.com> Index: head-2007-02-27/arch/i386/Kconfig =================================================================== ---

Dear developers! I''ve found that recent xen releases cannot be simly run on openSUSE! The script /etc/xen/scripts/xen-network-common.sh makes some incorrect assumptions on the SuSE ifup script. Bridged xen networking only works if the script executes this branch: preiftransfer() { true } ifup() { false } ifdown() { false } Otherwise the xen networking scripts fail to put the

Hi, I''ve successfully used VT-d on an ASUS P6T mainboard which is known to have really buggy RMRR tables. I tested passtrough with: - the onboard (fake-)raid-controller (no problems) - a pci card (no problems) - VGA cards (worked only partly - I''ll investigate that) I wrote a little patch to the code parsing the RMRR tables and enabled the following command line options:

Hi Andi, Four patches: - clean up asm/bugs.h, by moving all the C code into its own C file - split identify_cpu() into boot and secondary variants, so that boot-time setup functions can be marked __init - repost of the COMPAT_VDSO patches with a bit more robustness from unknown DT_tags, and functions marked __init, since all this is boot-time only setup. Thanks, J --

Hi Andi, Four patches: - clean up asm/bugs.h, by moving all the C code into its own C file - split identify_cpu() into boot and secondary variants, so that boot-time setup functions can be marked __init - repost of the COMPAT_VDSO patches with a bit more robustness from unknown DT_tags, and functions marked __init, since all this is boot-time only setup. Thanks, J --

Hello I do have problem using Linux with an external HP tape drive. The server platform is also an HP Server; the server is an HP ML350 G4, and the Tape drive is a HP Storage Works Ultrium 448 - 1U Rack-mountable. HP Ultrium documentation says two drivers should be automatically up, sym53c8xx for LSI SCSI interface "st" for tape and /proc/scsi/scsi should contain information about

Hello, After updating to 6.6 I've lost my connection to my tape library. Old log file (6.5): Sep 13 08:17:51 server1 kernel: scsi 1:2:0:0: Sequential-Access HP Ultrium 5-SCSI Z65W PQ: 0 ANSI: 6 Sep 13 08:17:51 server1 kernel: scsi 1:2:0:1: Medium Changer HP 1x8 G2 AUTOLDR 4.20 PQ: 0 ANSI: 5 New log file (6.6): Oct 28 18:15:06 server1 kernel: scsi1 : hpsa Oct 28 18:15:06

Hi, I've been reading up on how to create guests which will have a gpu. I found a technologie of nvidia called Grid K1 or Grid K2. It's a graphical PCIe card which can make virtual gpu's available. Only I think nvidia doesn't support qemu and it looks expensive (didn't ask for a quote yet) because these cards are created for 10 tot 20 users. I only need to support about 6

I have Centos 5.2 and am trying to set up my first tape loader, a Quantum SuperLoader 3. My "cat /proc/scsi/scsi" outputs the following: Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: transtec Model: PV610F16R1C Rev: 373I Type: Direct-Access ANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 01 Lun: 00 Vendor: HP Model: Ultrium

Hello all. I'm struggling to get Centos 4 to recognize my Dell Powervaul 132T tape changer. The system doesnt create a device node for it. [root at orion scotty]# cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 06 Lun: 00 Vendor: SEAGATE Model: DAT DAT72-052 Rev: A060 Type: Sequential-Access ANSI SCSI revision: 03 Host: scsi1 Channel: 00 Id: 01 Lun:

On Mon, 2007-03-05 at 13:06 +0100, Ingo Molnar wrote: > Subject: [patch] paravirt: VDSO page is essential > From: Ingo Molnar <mingo@elte.hu> > > commit 3bbf54725467d604698721384d858b5983b87e8f disables the VDSO for > CONFIG_PARAVIRT kernels. This #ifdeffery was a bad change: the VDSO is > an essential component of Linux, and this change forces all of them to > use

On Mon, 2007-03-05 at 13:06 +0100, Ingo Molnar wrote: > Subject: [patch] paravirt: VDSO page is essential > From: Ingo Molnar <mingo@elte.hu> > > commit 3bbf54725467d604698721384d858b5983b87e8f disables the VDSO for > CONFIG_PARAVIRT kernels. This #ifdeffery was a bad change: the VDSO is > an essential component of Linux, and this change forces all of them to > use

Guys Is it possible to passtrough iGPU from AMD A10-7870K to kvm virtual machine? If so then how please? Thank you David