search for: kernles

The 9p-virtio transport does zero copy on things larger 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:

The 9p-virtio transport does zero copy on things larger 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:

Hellow, everyone I'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

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.

Not sure where to put this but I am cc''ing the ZFS - discussion board. I was successfull in creating iscsi shares using ZFS set shareiscsi=on with 2 thin provisioned partitions of 1TB each (zfs create -s -V 1tb idrive/d1). Access to the shares with an iscsi initiator was successful, all was smooth, until the reboot. Upon reboot, the console reports the following errors. WARNING:

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 anything more to make the traffic pass through iptables forward chain.

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

On Tue, Nov 20, 2001 at 10:54:41AM +1100, Matthew Geier wrote: > Frank Joerdens wrote: > > > > 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

On Wed, Dec 04, 2013 at 08:43:18PM +0000, Richard Yao wrote: > The 9p-virtio transport does zero copy on things larger 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

Thanks Jon, it worked, I was able to build all the packages for xenserver on CentOS 6.6 final version. Here is the package list: https://gist.github.com/gautammaloo/7616cccbe8f5c85c196e I was wondering what packages would be necessary to use Xen with xapi, I already have xen with xl installed. Could we have a package like http://packages.ubuntu.com/precise/xcp-xe with which we can have

On 12/06/2013 06:14 AM, Will Deacon wrote: > On Wed, Dec 04, 2013 at 08:43:18PM +0000, Richard Yao wrote: >> The 9p-virtio transport does zero copy on things larger 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,

On 12/06/2013 06:14 AM, Will Deacon wrote: > On Wed, Dec 04, 2013 at 08:43:18PM +0000, Richard Yao wrote: >> The 9p-virtio transport does zero copy on things larger 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,

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

Hi, we''re running 4 xen servers on our network with multiple network cards. During HighLoad we experince degeneration of inbound network traffic through our loadbalancer. I might found a reason for it, in Dom0 dmesg output looks as follows: [1157421.975910] eth0: received packet with own address as source address [1157421.975957] eth0: received packet with own address as source

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:

This attempts to implement the idea proposed in https://www.redhat.com/archives/libguestfs/2010-April/msg00087.html The idea is that an externally managed QEMU (manual, or via libvirt) can boot the appliance kernel/initrd. libguestfs can then be just told of the UNIX domain socket associated with the guest daemon. An example based on guestfish. 1. Step one, find the appliance kernel/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,