similar to: [PATCH RESEND] enable swiotlb on i386 in linux-2.6-xen tree

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

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

Use strtoull to parse the final_exec_addr value from the command line. Whe cross compiling on i386 for x86-64 unsigned long is 32 bit, which leads to final_exec_addr being truncated to 32 bits by strtoul, which leads to grub refusing to load the resulting image. Please apply. Signed-Off-By: Muli Ben-Yehuda <mulix@mulix.org> diff -r 86eba2e17a39 -r ef4fe9970b03 xen/arch/x86/boot/mkelf32.c

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.... ;)

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 ...")

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

These are the diffs against the pristine versions of arch/x86_64/kernel/[aperture.c,pci-gart.c] to better show the changes necessary to adapt those files to Xen. They were included with the patch and should not be applied again. -Mark Langsdorf AMD, Inc. --- pristine-linux-2.6.12/arch/x86_64/kernel/aperture.c 2005-06-17 12:48:29.000000000 -0700 +++

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

This patch proposes to remove the XEN_PRIVILEGED_GUEST kernel configuration parameter defined in arch/x86/xen/Kconfig, but used nowhere in the makefiles and source code. This dummy parameter was added 3 years back, and it may make sense to remove it now, as the reasons to use it were not very clear. Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com> ---

This patch proposes to remove the XEN_PRIVILEGED_GUEST kernel configuration parameter defined in arch/x86/xen/Kconfig, but used nowhere in the makefiles and source code. This dummy parameter was added 3 years back, and it may make sense to remove it now, as the reasons to use it were not very clear. Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com> ---

This patch proposes to remove the XEN_PRIVILEGED_GUEST kernel configuration parameter defined in arch/x86/xen/Kconfig, but used nowhere in the makefiles and source code. This dummy parameter was added 3 years back, and it may make sense to remove it now, as the reasons to use it were not very clear. Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com> ---

0) The Kconfig symbol XEN_PRIVILEGED_GUEST got added to the mainline Linux repository in v2.6.37. It has never been used. It has always been a nop. 1) Its Kconfig entry is preceded with this comment: # Dummy symbol since people have come to rely on the PRIVILEGED_GUEST # name in tools. What does that mean? 2) On a related note: can anyone please explain commit

0) The Kconfig symbol XEN_PRIVILEGED_GUEST got added to the mainline Linux repository in v2.6.37. It has never been used. It has always been a nop. 1) Its Kconfig entry is preceded with this comment: # Dummy symbol since people have come to rely on the PRIVILEGED_GUEST # name in tools. What does that mean? 2) On a related note: can anyone please explain commit

XEN_DOM0 is a silent option that has been automatically selected when CONFIG_XEN is selected since 6b0661a5e6fbf. If this option was changed to a menu configurable option then it would only give users the ability to compile out about 100 kbytes of code. As that option makes little sense to choose, and the option isn''t menu selectable anyway, then we can clean up some code by simply

XEN_DOM0 is a silent option that has been automatically selected when CONFIG_XEN is selected since 6b0661a5e6fbf. If this option was changed to a menu configurable option then it would only give users the ability to compile out about 100 kbytes of code. As that option makes little sense to choose, and the option isn''t menu selectable anyway, then we can clean up some code by simply

XEN_DOM0 is a silent option that has been automatically selected when CONFIG_XEN is selected since 6b0661a5e6fbf. If this option was changed to a menu configurable option then it would only give users the ability to compile out about 100 kbytes of code. As that option makes little sense to choose, and the option isn''t menu selectable anyway, then we can clean up some code by simply