similar to: VTd - PCI Passthrough - VMError: fail to assign device

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: normal After giving xen a shoot with the fresh lenny packages, an annoying bug comes up right after trying to boot into the new system. I'll provide further informations if needed. Please see serial debug output below and here http://plzk.de/xen-lenny (maxlines got extended for comfortable reading) XEN) Xen version 3.2-1

I''m having trouble actually seeing a PCI device in my VMs. I''ve resolved several of my issues using previous posts and using the VTdHowTo wiki page. I have both VT and VTd BIOS options enabled. I have pciback hiding the devices and xm can list and assign the devices to VMs. I don''t see the PCI devices in my VMs though. I have tried a windows and a Linux vm, without

Hello, I''ve done an update from xen 3.2 to 3.3. Since 3.3 I can not use my TV-Card anymore. The error message is "Error: pci: 0000:10:0a.0: non-page-aligned MMIO BAR found." lspci shows the card as 10:0a.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) Any hints ? Thanks in advance Christoph xm dmesg: (XEN) Xen version 3.3.1-rc1-pre (root@artus.own) (gcc

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

Hi, I have some problems to configure the xen I''ve installed (3.3.1). The computer is a Intel Core 2 Duo, I''m using Ubuntu 8.10 and have linux in my dom0 and winxp pro in my domU. I have two cores and I''d like to set the affinity of dom0 to cpu0 and domU to cpu1 but I haven''t find the way of making this permanent. I''ve set cpus=1 in the domU config

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

I keep on getting the following entries in the xend.log file and it''s drowning out the important messages: [2007-07-23 14:58:28 2931] ERROR (XendConfig:909) dumping sxp from device controllers Traceback (most recent call last): File "/usr/lib64/python2.5/site-packages/xen/xend/XendConfig.py", line 895, in to_sxp configs = controller.configurations(txn) File

Hi, I tested xm block-attach command with a wrong parameter(file:). Naturally a command error occurred. Then I retested xm block-attach command with a correct parameter(phy:). But a command error occurred again. The second command error occurred because Xend did not remove device information from self.info when the first command error occurred. # xm block-attach vm1 file:/dev/hda4 hdb1 w

Hi I have configured few VMs with RHEL5,32 bit, but some VMs after successful stop/restart few times, suddenly they start giving following error from "xm create vm1.cfg" startup. ---- Error: (''c618d493-a696-7637-333d-bd891fa41ac2'', ''VM_metrics'') ---- If i replace system.img, they starts working again. This is what i see in xend.log file. This happens

Hello List, i am trying to get xen 3.3.1+ linux kernel 2.6.18 +drbd 8.3.0 working. Here is my config: ---------------------------------------------- kernel = ''/boot/vmlinuz-2.6.18.8-xenU'' memory = ''128'' root = ''/dev/sda2 ro'' disk = [ ''drbd:pgone-disk,sda2,w'' ] name

Hello Xen refuses to create domU VM. I have posted some info about my system. Please suggest a solution. gate xen # xm info host : gate release : 2.6.25.5-1.1dom0 version : #24 SMP Sun Aug 31 16:55:27 EEST 2008 machine : x86_64 nr_cpus : 2 nr_nodes : 1 cores_per_socket : 2 threads_per_core : 1 cpu_mhz : 1999 hw_caps : 178bf3ff:e3d3fbff:00000000:00000010:00000001:00000000:00000003:00000000

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3 Severity: grave Justification: causes non-serious data loss -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash

I have an IBM System x 3250 that successfully boots using the standard kernel (2.6.18-8.1.10.el5) but fails to boot with the xen kernel. The kernel appears to fail when it attempts to initialize the driver for the onboard SAS controller (LSI Logic / Symbios Logic SAS1064E PCI-Express Fusion-MPT SAS). Can anyone provide any advice? Here's the relevant info. Please let me know if any other

I''m newbie Xen-4.1.1 I''m trying to boot DomU with the following configuration. Sometime DomU boot, but sometime boot failed I''m not sure what is the problem. I can attach that image with tap-ctl on Dom0. Does anybody advice me about this problem?? Sincerely * Environment OS : Scientific Linux 6.1 x86_64 Kernel : 2.6.32.43

Hi everyone, I generated my own DomU guest using opensuse''s yast dirinstall and stored it on a seperate iscsi target. I created it as a DomU on my Domain0 (2.6.25.16-0.1-xen kernel) successfully, using the following configuration: name = "vm01-opensuse11-base-LAMP" memory = 256 kernel = "/boot/vmlinuz-xen" ramdisk = "/boot/initrd-xen" root =

Hi, I have a problem booting the Xen hypervisor on my brand new Lenovo Thinkpad T400 2765D2G (Core2 Duo P8600 CPU, 2.40GHz. 4GB RAM). I''m running Debian 5.0 (Lenny) and I use the Debian-provided xen-hypervisor-3.2-1-amd64 package. The Dom0 kernel seems to be the Xen patches ported to a 2.6.26 kernel: linux-image-2.6.26-1-xen-amd64 I can boot the hypervisor only very unrealiably: Out of

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: important The Xen hypervisor very unreliably boots on my 4GB Lenovo Thinkpad T400 2765D2G. Right after installation it booted the DomO kernel from linux-image-2.6.26-1-xen-amd64 without any problems, but every subsequent restart failed completely. Once I had a XEN "early fatal page fault" error message, on every other of

When booting a recently compiled Xen 4.2 on Ubuntu 12.04, dom0 crashes. I''ve included a serial console log below. I''ve used: Xen 4.2 unstable rev. 25483, compiled on the same machine. I had to apply the AT_EMPTY_PATH patch from http://lists.gnu.org/archive/html/qemu-devel/2012-02/msg03460.html to get it to compile. Linux 3.2.0-25, which is the default kernel in Ubuntu''s

Hey guys, I am posting this again....because i didnt get any replay. Please I am doing my thesis and I am stack installing a guest machine from Yocto, a unix like machine. It boots successfully on the same host without xen. thank you again, Nas On Tue, Jun 4, 2013 at 5:37 PM, nesredin mahmud <nasmitlinux@gmail.com>wrote: > hello everyone, > > I am experiencing DomU booting

Hi Everyone! I've been trying to get my Nvidia 9800m GT working with the latest nouveau drivers with no luck so far. First of all I'd like to mention that this is a weird card as it is an SLI in one piece of hardware (not 2 separated cards). It came with my Dell XPS M1730 laptop. I know SLI is not currently supported and _I don't want_ to use SLI, I just would like to use one of