search for: neocleuse

Hi folks, this is my first post to the mailing list. I have a general question about the state of various efforts aimed at granting a domU physical access to a hardware device like a NIC, graphics card, etc. I generally understand the challenges this poses to a hypervisor in terms of interrupts and DMA. I am specifically wondering about what options are available when running non-Paravirtualized

Folks, I download the Neocleus 1:1 patch from following link: http://lists.xensource.com/archives/html/xen-devel/2007-05/msg01144.html Currently I want to add Neocleus 1:1 Patch to the xen-3.1.0 to make the HVM guest grab the device directly. When I add these patches and recompile and install the Xen source and try to start the HVM guest, the HVM guest can not start and the system hang.

This patch applies to c/s #15522. Nativedom 1:1 memory enabling - Done by "stealing" memory from Xen''s e820 at boot time. The pages are later being allocated to NativeDom using a special allocator. x86-64 ====== The 512KB-1MB region is remapped (because of the ROMs) to an address above 16MB. As far as NativeDom can see: 1. The 0-512KB

The following 5 patches are re-submissions of the vt-d patch. This set of patches has been tested against cs# 15080 and is now much more mature and tested against more environments than the original patch. Specifically, we have successfully tested the patch with following environements: - 32/64-bit Linux HVM guest - 32-bit Windows XP/Vista (64-bit should work but did not test) -

Userspace patches for the pci-passthrough functionality. The major updates since the last post are: - Loop to add passthrough devices in pc_init1 - Handle errors in read/write calls - Allow invocation without irq number for in-kernel irqchip Other than this, several small things were fixed according to review comments received last time.

Userspace patches for the pci-passthrough functionality. The major updates since the last post are: - Loop to add passthrough devices in pc_init1 - Handle errors in read/write calls - Allow invocation without irq number for in-kernel irqchip Other than this, several small things were fixed according to review comments received last time.

Hello everyone, just wondered after I read about devices passed through in HVM if the following if still true: (for Xen3.2.1) - a Domain running in HVM cannot get forwarded any other device than a USB device. - the USB device forwarding is not too stable - PCI forwarding is not possible without processor support and Xen support. - The GPLPV tools won''t change anything with that.

int.patch: - Supports only level-triggered interrupts. Edge interrupts support will be added shortly (should be fairly simple) - Change polarity trick: in order to reflect the external device''s assertion state, the ioapic pin gets its polarity changed whenever an interrupt occur. So an interrupt is generated when the _external_ line is asserted (then,

Hi, Maybe it''s a dumb question, but I''m actually trying to understand how the memory allocation works within Xen. I try to give 128MB to a domU and see if it increases for example when I "nano" a 500mb file, but the process just get killed when it reachs the 128MB memory limit. How do I configure the guests so they can ask for more memory until a limit is reached

Hi, Can anybody shed light on the Xen function map_domain_page (in xen/arch/x86/x86_32/domain_page.c)? What is it doing? Jinpeng Wei _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

libpci.patch: - A library to access the PCI config space, probe the bus for devices, etc. It is basically a copy & paste from the libpci app. - Uses the 0xcf8/0xcfc method to read the config. - PIO/MMIO low-level access functions. Signed-off-by: Alex Novik <alex@neocleus.com> _______________________________________________ Xen-devel mailing list

&nbsp;Hi! &nbsp;&nbsp;&nbsp;I&nbsp;want&nbsp;to make windows work&nbsp; with native graphics card on xen with no iommu (no vt-d) support. With many googling, I&nbsp;find that xen with Neocleuse 1:1 No-IOMMU passthough patches maybe can meet my requestment. &nbsp;&nbsp; I download and compile a copy of direct-io.hg source, and pass my graphics card to hvm windows domU.&nbsp;&nbsp;I hide the graphics card from dom0 linux with backpci.hide boot option, and&nbsp;allow dom0...

I know most of the motherboards based off of the Intel Q35 northbridge usually have VT-d options for it to be enabled or disabled in the BIOS.  I''ve heard the same for Intel 5400''s and Intel 3200/3210''s but been looking through manuals for various server boards and don''t see VT-d options in the BIOS. However, I was wondering if anyone had success stories or

It seems to me that Xen is full of stuff that aren''t beneficial for everybody, this includes NUMA, ACM and other stuff that certain companies try to introduce... In a better world, the Xen binary would have been more sleek and fast, and those extra features should be loaded via stating a Module boot line in Grub. This way, testing would be easy and it''s more elegant than using a

Platform : Nehalem, official Intel x58 with Core i7 920 (dx58so) Main (Console): Nvidia 9500 GT PCI Express Secondary: Nvidia 8800 GTS PCI Express Yes, I binned the ASUS P6T due to bad VT-d support in the BIOS. With the latest BIOS from Intel, the dx58so has enable/disable for VT-d, ICH FLR and Interrupt Mapping! Helped a lot with getting this working ... Dom0: 2.6.18-xen0 (built from

Hi all! I''m hoping someone here might be able to help. I''m familiar with several UNIX''es, though farily new to Linux... I''m running RHEL 5.2. I''ve got the RHEL kernel headers installed, etc, and compiled xen-3.3. Once that was built, I rebuilt libvirt, etc, the kernel, and all the modules. The whole mess boots and runs fine... mostly. My hardware

Ever since xen-unstable cset 14308 ("pci back: Fix registration of of filters on subsections of config space") I''ve been getting an MCA on the *2nd* boot of a driver domain using an e1000 NIC. Cset 14308 allowed the proper setup of the PM control registers, so the NIC is put in the D3 power state when the driver domain shuts down. Unfortunately, pci_set_power_state()

I am trying to get a pv_ops dom0 working for testing, but I am running into an elf_init error: (XEN) *** LOADING DOMAIN 0 *** (XEN) elf_init: not an ELF binary Full output attached. >From what I have read on the mailing lists, it seems that it is usually a problem with either grub or a corrupt dom0 kernel. Attached is my kernel config (2.6.28-rc6-tip). I followed the instructions on:

A character device for accessing (in user-space) pages that have been granted by other domains. Signed-off-by: Derek Murray <Derek.Murray@cl.cam.ac.uk> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I''m trying to use Splashy (splashy.alioth.debian.org) to display a .png splash screen while the kernel boots under Xen Dom0 (Debian Etch). Splashy dies with "Splashy ERROR: Couldn''t splashy_start_splashy(). Error -2", which seems to me to be a problem with the fb driver (all other fb apps die as well with: "map: vt01 => fb0 can handle only packed pixel frame