similar to: Build failures (x86_64, IOMMU, Xen 3.0.0)

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 +++

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

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

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

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 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

The iommu is enabled by default when xen is booting and later disabled in iommu_setup() when no iommu is present. But under some circumstances iommu-code can be called before iommu_setup() is processed. If there is no iommu available xen crashes. This can happen for example when panic(...) is called that got introduced with patch "x86-64: detect processors subject to AMD erratum #121 and

The iommu is enabled by default when xen is booting and later disabled in iommu_setup() when no iommu is present. But under some circumstances iommu code can be called before iommu_setup() is processed. If there is no iommu available xen crashes. This can happen for example when panic(...) is called as introduced with the patch "x86-64: detect processors subject to AMD erratum #121 and

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.

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

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

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

Hi, Is the http://xenbits.xensource.com/linux-2.6-xen.hg tree still being updated? if not, what''s the preferred Linux tree to track that has all of the Xen bits? Thanks, Muli _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

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

Currently we assign devices with VT-d in Xend, this raises two issues: 1) assign devices regardless of they are hidden by pciback or not. If the device is not hidden, it results in the device doesn''t work in Dom0; 2) device is assigned one by one, if assign multiple devices, some devices may have been assigned when problem happens, it results in assigned devices don''t work in

Hi! I tried to pcipassthrough usb-controllers to domu to use it with a memory-stick. First xen complained that the driver needs write-access to its configuration space, so I added these to pci-quirks. Since it still didn''t work I also added the device to pci-permissive but I still get an errormessage with Oops (at the end of this email) when sticking in the memory-stick. I tried

Hi! I tried to pcipassthrough usb-controllers to domu to use it with a memory-stick. First xen complained that the driver needs write-access to its configuration space, so I added these to pci-quirks. Since it still didn''t work I also added the device to pci-permissive but I still get an errormessage with Oops (at the end of this email) when sticking in the memory-stick. I tried

On Mon, Apr 27, 2015 at 1:55 PM, Jan Kiszka <jan.kiszka at siemens.com> wrote: > Am 2015-04-27 um 14:35 schrieb Jan Kiszka: >> Am 2015-04-27 um 12:17 schrieb Stefan Hajnoczi: >>> On Sun, Apr 26, 2015 at 2:24 PM, Luke Gorrie <luke at snabb.co> wrote: >>>> On 24 April 2015 at 15:22, Stefan Hajnoczi <stefanha at gmail.com> wrote: >>>>>