similar to: Xen4 / Intel DX58SO Mobo / VT-d not working

Hello, I''m having problems with VTD on this board. The board/cpu/bios all support vt-d and I think maybe I''m just missing something? Any feedback would be much appreciated :) Output below: root@vm:~# xm create /etc/xen/vm-nine.cfg Using config file "/etc/xen/vm-nine.cfg". Error: Failed to assign device to IOMMU (0000:05:00.0@100,msitranslate=1,power_mgmt=0)

Hello, I''m having problems with VTD on this board. The board/cpu/bios all support vt-d and I think maybe I''m just missing something? Any feedback would be much appreciated :) Output below: root@vm:~# xm create /etc/xen/vm-nine.cfg Using config file "/etc/xen/vm-nine.cfg". Error: Failed to assign device to IOMMU (0000:05:00.0@100,msitranslate=1,power_mgmt=0)

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, I did a git pull on pv_ops tree this morning and now get a crash when eth0 is started, here is the full boot log: Booting ''Xen 3.4 / Linux 2.6.29-rc6-tip'' root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /xen.gz com1=115200,8n1 console=com1,vga iommu=1 [Multiboot-elf, <0x100000:0x131748:0x8e8b8>, shtab=0x2c0078, entry=0x100000] module

Hello, I''m trying to compile Xen unstable on NetBSD, I''ve aplied the patches from http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/sysutils/xentools41/patches/?only_with_tag=MAIN and copied the blk files from http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/sysutils/xentools41/files/?only_with_tag=MAIN (I don''t know which of these patches have been applied to xen unstable, so

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:

Hi list, I have a problem with a new laptop (reproducable on other machines too) and the xen hypervisor. When the hypervisor gets booted with VESA mode 800x600 I see some messages and then the screen contents is switched into a pattern of vertical colored lines and never comes back. In text mode all works well, but later the pattern appears when the X servers starts. I disabled VTd in the bios

I try pci pci passthrough with xen 3.3.1 and CentOS 5.2(64bit) on a SUPERMICRO C7X58 board I see the following the error in my boot log. (XEN) [VT-D]dmar.c:372: RMRR is incorrect. This problem is caused by this condition in dmr.c:372. if ( rmrr->base_address >= rmrr->end_address ) { dprintk(XENLOG_ERR VTDPREFIX, "RMRR is incorrect.\n"); return -EFAULT; } As an

I try pci pci passthrough with xen 3.3.1 and CentOS 5.2(64bit) on a SUPERMICRO C7X58 board I see the following the error in my boot log. (XEN) [VT-D]dmar.c:372: RMRR is incorrect. This problem is caused by this condition in dmr.c:372. if ( rmrr->base_address >= rmrr->end_address ) { dprintk(XENLOG_ERR VTDPREFIX, "RMRR is incorrect.\n"); return -EFAULT; } As an

This patch supports basic gfx passthrough on QEMU: - disable emulated VGA adpater if there is passthroughed gfx - register/unregister legacy VGA I/O ports and MMIOs for passthroughed gfx Signed-off-by: Ben Lin <ben.y.lin@intel.com> Signed-off-by: Weidong Han <weidong.han@intel.com> _______________________________________________ Xen-devel mailing list

Hello, I''m also seeing this exact same problem. I''ve posted on xen-users, but did not get an answer. Venkat seems to be experiencing the same problem as me. I have the latest BIOS for my motherboard DQ35JO. (BIOS ver 933) I''m running a Q6600 as well. It hangs at "Brought up 4 CPUs." I''ve tried all sorts of combinations of Xen versions and kernels to

I do not seem to be able to get any where with the power management functions. I have had a look at the xenpm Wiki page, but it hasn''t helped. Its probably something completely obvious, but I can''t see it. I running Xen 3.4.0 on Centos 5.3 x86_64 using the gitco RPMs on an Intel S5000PSL motherboard with 2 x Xeon 5410s. Dom0 is running the latest Centos 5.3 kernel. My xm

This patch series restores the use of superpages when restoring or migrating a VM, while retaining efficient batching of 4k pages when superpages are not appropriate or available. Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Now that x86-64 has directly accessible percpu variables, it can also implement the direct versions of these operations, which operate on a vcpu_info structure directly embedded in the percpu area. In fact, the 64-bit versions are more or less identical, and so can be shared. The only two differences are: 1. xen_restore_fl_direct takes its argument in eax on 32-bit, and rdi on 64-bit.

I''ve a problem with managing power consumption on Intel Nehalem CPU. I''ve installed Xen 3.4 on our Dell PowerEdge T610 system on a Ubuntu 9.04 distribution. I recompiled the kernel 2.6.30rc5. Now I can see the c-states of the CPUs but no access to P-states information and the frequency scaling does not work. By the way, if I run the kernel 2.6.28.13 which is the last one

Hi all, I have searched the net and haven''t found a good answer so I hope perhaps someone here can help. I have an IBM x3850 (8863) that I am upgrading from SLES11SP1 to SLES11SP2, and at the same time XEN is being upgraded as part of the distro. The server is used as a Xen host for up to 6 guests. Anyway, the server boots fine with the SLES11SP2 default kernel, and the trace

Konrad, et al, I am seeing visual corruption (almost like an interlacing problem) with i915 under Xen on some platforms using linux-3.8. See attached file for an example of the visual corruption. This particular platform is an HP Elitebook 2540p The same kernel and ramdisk, when booted as native linux does not show this corruption. dmesg is attached, as well (out.txt) - but I did not see

>>> On 16.05.14 at 10:58, <ijc at hellion.org.uk> wrote: > So it seems like dom0 is unable to (correctly) bind to some hardware > interrupts. I wonder if these messages from Xen's dmesg are relevant. > (XEN) Not enabling x2APIC: depends on iommu_supports_eim. > (XEN) I/O virtualisation disabled > (XEN) Enabled directed EOI with ioapic_ack_old on! The last one

This fixes a bug in changeset 22526:7a5ee3800417, where the wrong value is read when deciding whether to flush the VTd tables. The effect is minor: in situations where the p2m entry is changed but the mfn is the same, the VTd tables will be unnecessarily flushed. old_entry is left untouched in the second case, since having a present old_entry will cause the an unnecessary check to be taken at

I obtain this error when booting (xen/stable-2.6.31.x|xen/master) on Xen 3.4.2 x86_64 xen_major : 3 xen_minor : 4 xen_extra : .2 I had no errors with the same kernel, version of the day 2010-03-03 To compile the kernel i use this configuration " http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.31.6-pvops-dom0-xen-master-x86_64 "