similar to: Xen 3.2.1, Intel DQ35JO, VT-d not working with Windows 2003

I thought I''d pass along a few tips for getting the Intel DQ35JO motherboard to play nice with Xen: 1. The dom0 kernel won''t boot with CONFIG_PCI_MMCONFIG enabled. If you get a hang during boot after seeing this message: ACPI: PCI Root Bridge [PCI0] (0000:00) ...then MMCONFIG is your problem. Some kernels seem to support a pci=nommconfig option, but my Gentoo 2.6.21 Xen

hi, This is what I get on the Intel DQ35JO. Is it critical? (XEN) Brought up 2 CPUs (XEN) [VT-D]iommu.c:1700: Queued Invalidation hardware not found (XEN) [VT-D]iommu.c:1700: Queued Invalidation hardware not found (XEN) [VT-D]iommu.c:1700: Queued Invalidation hardware not found (XEN) [VT-D]iommu.c:1700: Queued Invalidation hardware not found (XEN) [VT-D]iommu.c:1708: Interrupt Remapping hardware

Purchased DQ35JO on Vt-d/PCI passthrough wiki''s recommendations. Built latest xen-unstable and am getting the following via ''xm dmesg'': (XEN) [VT-D]dmar.c:374: RMRR error: base_addr d0000000 end_address cfffffff (XEN) Failed to parse ACPI DMAR. Disabling VT-d. My grub.conf looks like this: kernel /xen.gz vga=mode-0x0317 vtd=1 iommu=1

Hello, I have been working sometime now on getting a HVM accepting a PCI card from the host. As was said in the VT-D wiki I bought an ASUS P5E VM DO motherboard (rel 0803) which has the VT-D option in the bios. I want to pass a Hauppauge PVR 500 card to a virtual machine running LinuxMCE. After first trying XEN 3.2.1 which did not enable the "VT-D virtualisation" bit in xm dmesg, i

Hi there, I have a question regarding PCI passthrough on the Citrix XenServer 5.6 (Xen 3.4.2). I already managed to get some soundcard passed through to a Windows guest. So I think my knowledge about that topic isn''t _that_ low. But I cannot seem to pass through a SATA/PATA controller to a Linux guest. I have some additional CD/DVD burner (PATA) attached to a SATA/PATA controller

server:~# dmesg|grep pciback [ 0.000000] Kernel command line: root=/dev/hda1 ro console=tty0 pciback.permissive pciback.hide=(00:1d.00)(00:1d.01)(00:1d.07) [ 0.000000] Unknown boot option `pciback.permissive'': ignoring [ 1.210945] pciback 0000:00:1d.0: seizing device [ 1.211082] pciback 0000:00:1d.1: seizing device [ 1.211215] pciback 0000:00:1d.7: seizing device [

Sorry to duplicate my issues onto the list - I thought I had looked through this thread before and seen a different error, but apparently Adam and I are running into much the same thing. I'm seeing exactly the same "Failed to assign device to IOMMU" along with the "Device not owned by PCI Back End or pci-stub" in these scenarios. I have not gone back to previous versions,

Hello all, I'm looking at buying an intel dq35jo mother board. From what I've read on the net other's have been using the board to one degree or another for a year now. My main concern is that I can install CentOS 5 over a network. Any comments? -- Milton Calnek BSc, A/Slt(Ret.) milton at calnek.com 306-717-8737 -- This message has been scanned for viruses and dangerous

(lspci-output added at the end of this mail!) Hi specialists, I''m trying to pass an HP Surestore USB-drive to a domU. I''m hiding the pci-device in the dom0, and capturing it in the domU. Although this works fine I receive the following lines in /var/log/syslog of the dom0 after a reboot ======================================================================= Aug 8

How does one do this? For example: # lspci | grep USB 00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 02) 00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 02) 00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 02) 00:1a.7 USB Controller: Intel Corporation 82801I (ICH9

I have begun to see these messages in my morning reports: WARNING: Kernel Errors Present pciehp 0000:00:1c.0:pcie04: Link Training Error occurs ...: 146 Time(s) pciehp 0ng Error occurs ...: 1 Time(s) pcieport 0000:00:1c.0: bridge window [mem 0xd0a000000.0 failed with error -22 ...: 1 Time(s) r8168: probe of 0000:01:00.0 failed with error -22 ...: 702 Time(s) r8168:

im trying to do pcipassthrough to a hvm domain on xen 3.4.2 with jeremy''s pv_ops dom0 kernel 2.6.31.6 on debian lenny. dom0 kernel indicates that pciback cmdline options are unknown, but config shows CONFIG_XEN_PCIDEV_BACKEND=y is compiled in. is pciback broken on this kernel or something? all relevant information i can think is here, let me know if theres anything else you''d

Hello, I FINALLY got Xen working with VT-d. I compiled Xen-unstable (3.3) from Mercurial on CentOS 5.2, but compiled my own kernel-xen from the latest CentOS SRPM. (Made sure pciback was built-in and not a module, as the stock kernel-xen has it as a module.) I''m probably going to write a how-to soon, so stay tuned! I have a JMicron SATA/PATA PCI Express controller with a DQ35JO

Hello, I FINALLY got Xen working with VT-d. I compiled Xen-unstable (3.3) from Mercurial on CentOS 5.2, but compiled my own kernel-xen from the latest CentOS SRPM. (Made sure pciback was built-in and not a module, as the stock kernel-xen has it as a module.) I''m probably going to write a how-to soon, so stay tuned! I have a JMicron SATA/PATA PCI Express controller with a DQ35JO

Thanks to the kind person(s) who worked on this. I am using PCI passthrough right now and it works. I hope support is added for VT domains too; That would be extremely useful. So far I have tried a NIC, USB, and PCI Video. The NIC works flawlessly. USB works as long as the devices are present at the time the domain is started. Hotplugging USB devices seems not to work. If I open

Hi xen-users, I install xen, on gentoo linux. Install was ok, but i have an issue that i can''t solve. When booting in xen-linux, whereis no eth0 interface. When i boot non-xen kernel all is ok, eth0 is present. I use 2.6.18-xen kernel version. lspci show me: 00:00.0 Host bridge: Intel Corporation 82P965/G965 Memory Controller Hub (rev 02) 00:01.0 PCI bridge: Intel Corporation

Hello, In real life I use xen 3.3.1 successfully on servers Fujitsu-Siemens RX100. Now I to see how working xen-3.4-rc3 on the same server, but unfortunately is a problem with loading a module to handle the disk (mptsas) . I use debian lenny 5.0.1 and kernel version 2.6.26-2-xen-686. Someone managed to compile 3.4 xen kernel with this version? xen:~# lspci 00:00.0 Host bridge: Intel

These are new boxes. http://www.supermicro.com/products/system/1U/5015/SYS-5015B-MT.cfm core 2 Q6600 CPU 8Gb 667 RAM Boxes were memtested from Fri-Mon okay. 6.3-RELEASE (amd64) installs fine. Build cycle okay. Running (no load) for a week or so. However, when I try to configure gmirror they hang on boot. After some fiddling it appears issuing #kldload geom_mirror hangs the boxes very hard.

Hi, I using on all server (FSC RX100S5) xen 3.3.1 and kernel 2.6.26-1 or 2.6.26-2,evrything it works good. Now I try using xen 3.4.0 with the same kernel but the system not up only go to the initramfs. I suspect that the kernel did not load the driver for the controller. The question just why it works on a Xen 3.3.1 does not work on 3.4 with the same versions of the kernel . Below I put

Hi, Here it is... 00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 0c) 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) 00:02.1 Display controller [0380]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary)