similar to: [PATCH] fix mkelf32 when cross compiling on i386 for x86-64

The linux-2.6-xen tree has a typo in the Kconfig file for i386 that disables building swiotlb. This patch fixes it in the same manner that x86-64 does it. Cheers, Muli Signed-Off-By: Muli Ben-Yehuda <mulix@mulix.org> diff -r c1c170a55fe0e97156379d10870aed024ed0012a arch/i386/Kconfig --- a/arch/i386/Kconfig Thu Dec 8 20:50:02 2005 -0700 +++ b/arch/i386/Kconfig Tue Dec 13 20:07:34 2005

check_hotplug fails on one of my machines running ubunto 4.10 "Warty Warhog", due to misparsing the udevinfo version string. The problem is caused by an old version of sed that does not appreciate the regexp. This patch fixes it, and also works on debian unstable and SLES9SP2. Please apply... Signed-Off-By: Muli Ben-Yehuda <mulix@mulix.org> Signed-Off-By: Orna Agmon

On Wed, Jan 25, 2006 at 03:12:08PM +0000, Xen patchbot -unstable wrote: > # HG changeset patch > # User kaf24@firebug.cl.cam.ac.uk > # Node ID 709bce2f08d6024c2efb2938e564915da1ca51f2 > # Parent aad2b2da3c8beda24bc62ca6e92b28c28def0849 > Export Xen driver util function symbols so that Xen drivers > can build as modules. > > Signed-off-by: Keir Fraser

From: Ian Campbell <ian.campbell@citrix.com> The zImage compatible binary is the useful one on real hardware. The relocated ELF thing is only really useful when booting directly on Fast Models. The customary suffix for that case is .axf so provide that as a target. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Cc: Wookey <wookey@linaro.org> --- xen/arch/arm/Makefile |

On 2018/11/3 ??12:07, Vitaly Mayatskikh wrote: > Hi, > > I stumbled across poor performance of virtio-blk while working on a > high-performance network storage protocol. Moving virtio-blk's host > side to kernel did increase single queue IOPS, but multiqueue disk > still was not scaling well. It turned out that vhost handles events > from all virtio queues in one helper

I'm currently playing with Wine on Cygwin on Windows 2000 on VirtualBox. Just to see what happens. Also to see how feasible Wine on Windows is from here. I've been updating the http://wiki.winehq.org/CygwinSupport page accordingly. With the 1.1.11 source tarball, I'm getting a compile error: internettransport.c:348: error:

After fuzzing 'qemu-img info' I found that certain files can cause the command to use lots of memory and time. Modify the command mini-library to allow us to place resource limits on subprocesses, and use these to limit the amount of space and time used by 'qemu-img info'. --- configure.ac | 3 +++ src/command.c | 53

The attached patch makes xenconsole send and receive console messages over a remote connection, instead of via stdin/stdout - if given the --remote switch. It is useful for proxy''ing real console message or other protocol messages (such as gdb) between dom0 and a remote host. We''re currently using it for proxying gdb between gdbstub in a partition that talks gdb over the console

Dear List I am trying to draw a heatmap using ggplot2. In this heatmap I have faceted my data by 'infection' of which I have four. These four infections break down into two types and I would like to reorder the 'infection' column of my data to reflect this. Toy example below: library(ggplot2) # test data for ggplot reordering genes <- (rep (c(rep('a',4),

Hi, I have successfully installed Xen unstable binary on SuSE 9.3. I am trying to do a source install and I got the following error. Will be glad for any help or guidance. In file included from include/asm-xen/asm/processor.h:18, from include/asm/thread_info.h:17, from include/linux/thread_info.h:21, from include/linux/spinlock.h:12, from include/linux/capability.h:45, from

Hi! This is the third and last patch. This patch makes the xen kernel buildable on OpenBSD by adding support for ProPolice. ProPolice has been added to standard GCC in version 4.1.x under the name Stack Smashing Protection (SSP). Cheers Christoph _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Does anyone have experience installing Xen on IBM eSeries (I have an x336), specifically with getting all the drivers to work? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

On Fri, 2005-10-21 at 18:54 +0000, Xen patchbot -unstable wrote: > # HG changeset patch > # User kaf24@firebug.cl.cam.ac.uk > # Node ID 8eaaa622db81393ef0eae497090c34c04adf4212 > # Parent 3eee5653f08b01a310e0a9172a6c0149f16217df > Tweak to pygrub build config detection. > Signed-off-by: Jeremy Katz <katzj@redhat.com> Applying both patches for this is overkill.... ;)

Hi experts,'' I build xen on my 64 bit redhat with "make xen", I got the image xen-4.0.0.gz then $gunzip xen-4.0.0.gz $file xen-4.0.0 it tells me it''s 32 bit,but I saw it link the 64 bit lib Thanks Lei -- "We learn from failure, not from success!" _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Hi experts,'' I build xen on my 64 bit redhat with "make xen", I got the image xen-4.0.0.gz then $gunzip xen-4.0.0.gz $file xen-4.0.0 it tells me it''s 32 bit,but I saw it link the 64 bit lib Thanks Lei -- "We learn from failure, not from success!" _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Here is the usage for Fedora usage: mkinitrd [--version] [-v] [-f] [--preload <module>] [--omit-scsi-modules] [--omit-raid-modules] [--omit-lvm-modules] [--with=<module>] [--image-version] [--fstab=<fstab>] [--nocompress] [--builtin=<module>] [--nopivot] <initrd-image> <kernel-version> (ex: mkinitrd /boot/initrd-2.2.5-15.img

This patch enables tracing VMEXIT/ENTRY for 64-bit systems (are there any 32-bit VT enabled systems out there?) Signed-off by Himanshu Raj (rhim.list@nosuchaddr.com) -- ------------------------------------------------------------------------- Himanshu Raj PhD Student, GaTech (www.cc.gatech.edu/~rhim) I prefer to receive attachments in an open, non-proprietary format.

Does Xen 3.0.0 actually support the IOMMU on x86_64? I''ve tried building with a couple of different configurations, and it always fails if I''ve enabled CONFIG_GART_IOMMU. The problems center around undefined references to functions such as dma_alloc_coherent, dma_free_coherent, iommu_setup, iommu_hole_init, force_iommu, iommu_aperture_allowed, and so on. In all cases, changing

When making the "unstable" version I got an in "tools". There was a complaint about "cc.has_function" in the following code area in tools/pygrub/setup.py if cc.has_function("ext2fs_open"): ext2defines.append( ("HAVE_EXT2FS_OPEN2", None) ) else : sys.stderr.write ("Warning: older veriosn of e2fsprogs installed ...")

The paravirtualized guests are offered wallclock time referenced to UTC only, while fully virtualized guests are given the option via the config file (localtime parameter) of starting with UTC time or local time. What would it take to optionally provide localtime to the paravirtualized guests as well? For a guest that launches assuming localtime as its time basis, then later deriving UTC from it