similar to: xen 3.3.0 pv pci passthrough co-assigned problem

On Xen-3.3.0, domain0 Megaraid SAS (SAS 1068 controller) driver is not loading correctly if vtd support in Xen is enabled. It fails at the point of initializing firmware. I wasn''t seeing this error with Xen-3.2.2-rc3 (Unstable version), though with vtd disabled in Xen-3.3.0, it is working. Looks like a degrade problem. Any clues? Thx, Venkat

I have pulled a recent (today''s) clone of staging/xen-unstable.hg and I get a failure when trying to create a domain with xend/xm. The failure I get is: Error: (''<domain GUID>'', ''VM_metrics'') I have traced the problem down to where the pci = [ ''02:00.0'' ] parameter (which is the value in my case) from my configuration

The patch moves the struct IO_APIC_route_entry to a common place. This allows us to share the struct with iosapic. Thanks, -- Dexuan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I have successfully passed through a video card, network card, USB mouse, and USB keyboard to a MS Vista guest. That works well. I am trying to add another PCI device, such as a audio card or PCI USB hub, but I am running into a strange problem. When I plug the PCI audio (or USB card) to the motherboard. It makes it so that the PCI video card is no longer an "assignable device" (xm

In current xend, we can not assign co-assignment devices to different guests, even for pv guests. This patch loosens the policy for pv guest: if none of the co-assignment devices have been assigned to hvm guest, we can assign the devices to different pv guests. The patch also adds a detection: if a device has been assigned to guest, we can't try to "xm pci-attach" it to the same

Hi, I really need help. I spent 2 days already on this pci passthrough thing. I''m using Xen 3.2.1 with Centos 5.2 64 bits on intel VT. I''d like to use PCI passthrough and I don''t think I need VT-D functionality. I''m trying to pass PCI 12:01.0 to my domU guest. I got this error when I use "xm create /etc/xen/hvm_centos_2.cfg" Using config file

I am submitting the patch which supports more Capability Structures and Device Specific Registers for passthrough device. In Xen 3.3 unstable, qemu-dm supports Configuration Header, MSI Capability Structure, and MSI-X Capability Structure. But qemu-dm does not support PCI Express Capability Structure, Device Specific Registers, etc (writing them is ignored). To support various I/O devices, I

Hi: I am trying to understand the current pass-through device in Xen. To my understanding, Xen can hide a PCI device from Dom 0 and exclusively assign it to a guest OS (dom U), right? Does Xen support to assign one device to multiple guest OSes? Does current pass through require Intel -VT or AMD SVM? Where is the source file for the pass-through function? Is it in xen/drivers/passthrough? BTW:

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

Hi Jeff. I read that you use PCI Passthrough and works well, i was wonder if you can tell me how you do that ''cause i can''t find how to do it :( and i really need to. So if you can give some advice about how you do it would be really helpful. I appreciate your help Jeff. Regards Ivan ____________________________________________________________________________________

Dear David Techer, I have read through your article on Xen VGA passthrough on http://www.davidgis.fr. It appears that the following command on your blog doesn''t work. dmesg | grep 01:00.0 | grep BAR The above command shows nothing at all. Is there an alternative solution? Thank you very much. Yours sincerely, Teo En Ming (Zhang Enming)

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

Hi everyone, I am currently in the process of setting up a firewall/access point DomU and I would like to know if there is any way to run a linux kernel 2.4(.34) based system as a DomU. The primary reason for this is that I want to run IPCop on such a kernel, but also that I consider kernel 2.4 based systems to be more suitable for some applications, especially for use as a firewall.

Hi, I want to perform pass through I/O from my domU. I guess I would need an additional network card for the same. Is there any preference on the second network card I should get or any one is fine? I have a x86_64 machine with Cent OS 4.4 running. Are there any additional considerations that I cannot see - Kindly let me know. Thanks, Asim _______________________________________________

Dear Users, Debian Etch 2.6.18.8-xen from xensource.com with Xen 3.3.0 on AMD64: After i want to start the HVM i get: VmError: fail to assign device(1:0.0): maybe it has already been assigned to other domain, or maybe it doesn''t exist. [2008-10-25 19:59:30 2460] DEBUG (__init__:1072) XendDomainInfo.destroy: domid=5 [2008-10-25 19:59:30 2460] DEBUG (__init__:1072)

Hi, I''ve added some preliminary support for VT-d for paravirtualized guests. This must be enabled using an ''iommu_pv'' boot parameter (disabled by default). I''ve added some python bindigs to allow xend to assign PCI devices to IOMMU for PV guests. For HVM guests this is handled in ioemu. Not sure if it makes sense to handle both cases in one place. The

I'm trying to pass-through my VGA card to a guest session. I found: http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM - which is very frustrating because there's no date on the documentation. I suspect it's old. It does clearly say that you must have VT-d support for pci pass-through. It then goes on to say "Some work towards allowing this ["software

On 32e, we create one guest, then hotplug attach one NIC to guest, guest can not get IP address via dhcp, guest qemu log shows "libpci read error. No emulation ". Here is the bug entry: One 32e, hotplug attaching VT-d NIC to guest failed. http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1316. -- haicheng _______________________________________________ Xen-devel mailing list

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

Dear Sir, I am facing the same problem you were discussing here: https://www.redhat.com/archives/libvirt-users/2015-January/msg00070.html I am getting this error: Starting install... ERROR internal error: unable to execute QEMU command 'qom-list': The command qom-list has not been found Domain installation does not appear to have been successful. If it was, you can restart your domain