search for: config_security_capability

I have a strange problem. I can't get lisa to run because named will not run. In the kernel 2.6.5-7.108, I see CONFIG_SECURITY_CAPABILITY = m. So that should work. Still I get the message: Starting name server BIND 9 named: capset failed: Operation not permitted startproc: exit status of parent of /usr/sbin/named: 1 failed Can someone help me? Henk

Hello, On my x86_64 box, when compiling the xen-3.0.4-rc1, if CONFIG_HOTPLUG_CPU is not set it produces an undefined reference to ''remove_siblinginfo'' that is used in arch/x86_64/kernel/smpboot.c drivers/built-in.o: In function `__cpu_up'': (.text+0x54c10): undefined reference to `remove_siblinginfo'' If CONFIG_HOTPLUG_CPU is set the compilation works fine.

Hi, At the time of writing this mail, a few days ago, I couldn''t access the lists, so my apologies if this mail is received duplicate. I recently bought a new server with a 3Ware 8006-2LP controller to run Xen on a Debian linux distribution: - Server: ASUS RS120-E4/PA4 - Debian Release: etch - Architecture: 32bit / 686 - Memory: 8 GB - Disks: 2x Hitachi HDT725050VLA360 - Controller:

Hi List, I encountered some problems with PCI pass to PVM using 2.6.18.8 kernel. When I try to pass an USB bus I get: usbcore: registered new driver usbfs usbcore: registered new driver hub USB Universal Host Controller Interface driver v3.0 PCI: Enabling device 0000:00:1d.1 (0000 -> 0001) uhci_hcd 0000:00:1d.1: UHCI Host Controller uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus

Hi List, I encountered some problems with PCI pass to PVM using 2.6.18.8 kernel. When I try to pass an USB bus I get: usbcore: registered new driver usbfs usbcore: registered new driver hub USB Universal Host Controller Interface driver v3.0 PCI: Enabling device 0000:00:1d.1 (0000 -> 0001) uhci_hcd 0000:00:1d.1: UHCI Host Controller uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus

Hi I just tried to install Xen (3.0.4) from source. The Installation process finished without any errors. Then after booting the XEN-Image (without initrd) I got a Kernel Panic. My machine said it was unuable to mount root fs from Sda1 or unknown-block(0,0) After some research on google, I built the SCSI and SATA drivers in the XEN-kernel and now this kernel Panic occurs: Kernel Panic-not

Wanted to pass this error by you and get your feedback ... I tried building a debug kernel with spinlock related debug info. The tree was pulled when the Xen-305 first rc was announced (and has not been updated since) make -C /root/src/mercurial/xen-3.0.5-testing.hg/linux-2.6.18-xen O=/root/src/mercurial/xen-3.0.5-testing.hg/build-linux-2.6.18-xen_x86_64 vmlinuz Using

Hello, I got this message when exiting qemu: [11266.262154] EXT3-fs error (device hda): ext3_free_blocks_sb: bit already cleared for block 318015 [11266.276897] Aborting journal on device hda. [11266.283815] EXT3-fs error (device hda): ext3_free_blocks_sb: bit already cleared for block 318016 [11266.293567] EXT3-fs error (device hda): ext3_free_blocks_sb: bit already cleared for block 318017

On Mon, Nov 26, 2007 at 01:06:16PM -0500, Miles Lane wrote: > arch/x86/xen/enlighten.c: In function ''xen_flush_tlb_others'': > arch/x86/xen/enlighten.c:591: error: ''TLB_FLUSH_ALL'' undeclared (first > use in this function) > arch/x86/xen/enlighten.c:591: error: (Each undeclared identifier is > reported only once > arch/x86/xen/enlighten.c:591:

Hi, Kernel crash when i tried to mount btrfs: -- Machine: HP Proliant DL 380 G4 -- Ubuntu 8.04 Hardy Server root at btrfs:/home/trey# uname -a Linux btrfs 2.6.24-16-server #1 SMP Thu Apr 10 13:15:38 UTC 2008 x86_64 GNU/Linux -- root at btrfs:/home/trey# fdisk -l Disk /dev/cciss/c0d0: 146.8 GB, 146807930880 bytes 255 heads, 63 sectors/track, 17848 cylinders Units = cylinders of 16065 *

Hi guys I gave these patches a try (on top of 2.6.23-rc9 plus the previously submitted 2.6.24 patch set). The last two seem to cause Badness on my system, whereby if I start a guest (using the same bzImage as the host, as before) it seems to boot OK, and the host system still superficially looks stable (my X session is OK and I can interact with existing processes) but if I attempt to launch any

Hi guys I gave these patches a try (on top of 2.6.23-rc9 plus the previously submitted 2.6.24 patch set). The last two seem to cause Badness on my system, whereby if I start a guest (using the same bzImage as the host, as before) it seems to boot OK, and the host system still superficially looks stable (my X session is OK and I can interact with existing processes) but if I attempt to launch any