search for: kernl

...arger than 1024 bytes in size. It accomplishes this by returning the physical addresses of pages to the virtio-pci device. At present, the translation is usually a bit shift. However, that approach produces an invalid page address when we read/write to vmalloc buffers, such as those used for Linux kernle modules. This causes QEMU to die printing: qemu-system-x86_64: virtio: trying to map MMIO memory This patch enables 9p-virtio to correctly handle this case. This not only enables us to load Linux kernel modules off virtfs, but also enables ZFS file-based vdevs on virtfs to be used without killin...

...arger than 1024 bytes in size. It accomplishes this by returning the physical addresses of pages to the virtio-pci device. At present, the translation is usually a bit shift. However, that approach produces an invalid page address when we read/write to vmalloc buffers, such as those used for Linux kernle modules. This causes QEMU to die printing: qemu-system-x86_64: virtio: trying to map MMIO memory This patch enables 9p-virtio to correctly handle this case. This not only enables us to load Linux kernel modules off virtfs, but also enables ZFS file-based vdevs on virtfs to be used without killin...

...;m from HuaWei, China. We are looking for the candidate of virtualization platform among several vendors. Learned from Oracle people, the latest version of ocfs2 has integrated reflink feature which was commited to the the linux 2.6.32 kernel. But as we know, the sles11 integrated the linux 2.6.27 kernle, so the relink feature is not avaiable on the sles11 platform. We heared that the suse people plan to backport the latest ocfs2 into the sles11. Is there any more detaied information about that? Any response is appreciated. Thanks -------------- next part -------------- An HTML attachment was...

Hello, I'm playing with this issue several days and can't find why pxelinux boots kernels without problems and some doesn't start booting at all. It's not depend on kernel size or version, probably on kernel config or some magic. But there are kernels which boot anytime and kernles which boot never. How can i set debug/verbose mode in PXELINUX? This computer is based on dual pentium pro and PXE is used via 3com 3c905-TX-M, server is running debian stable with thttpd-hpa and i tried several versions of pxelinux. Thanks for your replies.

.../scsi_vhci/disk at g0100015c55fb40900002a00483e34c6 (sd9): disk has 3221225472 blocks, which is too large for a 32-bit kernel WARNING: /iscsi/disk at 0000iqn.1986-03.com.sun%3A02%3Aee2143f2-f5ce-6414-fcda-8035dacfc3730001,0 (sd10): disk has 3221225472 blocks, which is too large for a 32-bit kernl And it continues to do this on the other partition i had created. Ultimately coreadm:default fails bad and the server is stuck at svc.startd[7]: Lost repository event due to disconnection. I am on a Poweredge 2650 with 2xXeon Processors @2.8GHZ 1.5 GB Ram Running Opensolaris 2008.05 Anyideas,...

Hi, I am using linux kernle-2.6.15, iptables-1.4 and bridge-utils-1.4. Everything intslled without any issue and i am able to enable the bridge and traffic is also flowing without any issue. But i did not see any traffic on the iptables forward chain due to which i am not able to control the traffic. Do i requie enable any...

Hi, I am a masters student at IIIT Hyderabad, India. I am writing a GOSC proposal for CentOS organization. It's about delivering a custom installer ISO which delivers Xen 4.4 stack on CentOS 6. full proposal: http://www.google-melange.com/gsoc/proposal/public/google/gsoc2015/gautam_malu/5629499534213120 I want to port xapi on CentOS 6 as part of it. There has been some previous efforts to

...gt; Greetings. I read in a samba list that the quota support is 'broken' in > > so-called 'linus' kernels > 2.4.3 and that one is supposed to use a > > redhat or 'cox' kernel (what the hell is that supposed to mean . . . are > > we having different Linux kernle branches now??) > > In effect yes. > > The linus kernel and the Alan Cox kernel. Alan tests stuff and then > linus puts it in his kernel. More or less. Only the AC kernels have a > different VM and differen quota controls. > RedHat base their kernels off Alan Cox's tr...

...size. It accomplishes this by returning the physical addresses of > pages to the virtio-pci device. At present, the translation is usually a > bit shift. > > However, that approach produces an invalid page address when we > read/write to vmalloc buffers, such as those used for Linux kernle > modules. This causes QEMU to die printing: > > qemu-system-x86_64: virtio: trying to map MMIO memory > > This patch enables 9p-virtio to correctly handle this case. This not > only enables us to load Linux kernel modules off virtfs, but also > enables ZFS file-based vdevs...

...trix.com> wrote: > On Tue, Mar 24, 2015 at 11:28:51PM +0530, Gautam Malu wrote: > > I tried out building https://github.com/xenserver/buildroot on CentOS > 6.6 > > > > > > It builds around 300 packages and then it just gets stuck while building > > ocaml-core-kernl-111.28.00-1.el6 . > > build log: https://gist.github.com/gautammaloo/92a6199ee4ed100b1b92 > > > > Hi Gautam, > > From the log it looks like it ran out of space - this could be the disk > being > full, but it could also be that it might be building in a tmpfs environmen...

...es this by returning the physical addresses of >> pages to the virtio-pci device. At present, the translation is usually a >> bit shift. >> >> However, that approach produces an invalid page address when we >> read/write to vmalloc buffers, such as those used for Linux kernle >> modules. This causes QEMU to die printing: >> >> qemu-system-x86_64: virtio: trying to map MMIO memory >> >> This patch enables 9p-virtio to correctly handle this case. This not >> only enables us to load Linux kernel modules off virtfs, but also >> ena...

...es this by returning the physical addresses of >> pages to the virtio-pci device. At present, the translation is usually a >> bit shift. >> >> However, that approach produces an invalid page address when we >> read/write to vmalloc buffers, such as those used for Linux kernle >> modules. This causes QEMU to die printing: >> >> qemu-system-x86_64: virtio: trying to map MMIO memory >> >> This patch enables 9p-virtio to correctly handle this case. This not >> only enables us to load Linux kernel modules off virtfs, but also >> ena...

Hello, I just setup a few virtual systems, and I came into some limitations using XEN. I''d like to share these, just to know if the limitations are in the system or in the user :) I am using a standard Debian 4.0 (etch) GNU/Linux distribiution. The system is an Intel Core 2 duo with virtualization inside. I use the amd64 flavour. Thus my kernel is

...also found a side that suggests to turn off arp entirely for your xenbr0. Enclosed is my network configuration and the output for my bridges. As you see I''m not reseting my Mac address of the physical interface to FE:FF:FF:FF:FF:FF or turn arp off. I''m using Debian Lenny with kernl 2.6.26-2-xen-amd64 =================================== # The loopback network interface auto lo eth0 eth1 eth2 eth3 iface lo inet loopback # xenbr0 -> eth0 auto xenbr0 iface xenbr0 inet static address 192.168.0.78 netmask 255.255.255.0 network 192.168.0.0 bro...

http://bugs.freedesktop.org/show_bug.cgi?id=24370 Summary: nouveau and xorg-server-1.7 does not work without NoAccel Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at

http://bugs.freedesktop.org/show_bug.cgi?id=15481 Summary: Nouveau on nVidia Corporation G71 [GeForce 7950 GT]: works but lockup for 6 min at shutdown Product: xorg Version: 7.3 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: high Component:

...cally deleted when the guestfs handle is closed. Instead of using 'find-appliance' an app can manually invoke the febootstrap-supermin-helper to build the initrd/kernel but is a fragile coupling to libguestfs internals. Thus it is preferable to let libguestfs locate & inform you of the kernl and initrd

The first patch really isn''t as much of a follow-up than what triggered the security issues to be noticed in the first place. 1: x86: preserve FPU selectors for 32-bit guest code 2: x86: fix XCR0 handling 3: x86/xsave: adjust state management 4: x86/fxsave: bring in line with recent xsave adjustments The first two I would see as candidates for 4.3 (as well as subsequent backporting,