similar to: problems with USB and PCI passthrough on Debian Lenny

Hi all, I have a problem with pci passthrough in xen 3.4.0 (Debian Lenny). I need to pass the audio board (which is 00:1b.0) to the domU, so I do the following: - Put pciback.permissive pciback.hide=(00:1b.0) in dom0 kernel boot options - Put swiotlb=force in domU kernel boot options - Put pci = [ ''00:1b.0'' ] in domU config file - reboot the machine I can see in dmesg the

Florian, I read already here and there that you shall not use shared interrupts in different PV DomUs, although I never found a written statement. But behaviour is exactly as you described, thus I took care that cards that share an IRQ are in the same DomU/Dom0. I also selected my motherboards accordingly. When I lately discussed lately with someone about MSI, I had the hope this could help,

Hi Xenners, I have tried to upgrade to kernel 3.5 and experienced the USB/PCI passthrough problem. This has not been "fixed" in 3.6 either. I do not know if this is qemu, xen or kernel related. I am using Xen 4.2 final and Xen 4.3-unstable to test. DomU is Windows 7 64 bit or Linux Fedora 17. In Windows, I get the little yellow triangle with Code 10 (I know this means nothing...

Hi, I''m currently working on the latest version of xen with debian (lenny), and I have done 2 PCI passthrough, the fisrt one is with eth1 and i got no probleme with this one, but the second one is with a infiniband adapter=> It''s not working I got this message with dmesg on my DomU : [ 4.111023] ib_mthca: Mellanox InfiniBand HCA driver v1.0 (April 4, 2008) [ 4.111047]

Hello, I have been using Xen on a Debian Lenny server for quite some time. I decided to build a new Dom0 using identical hardware, but newest version of Xen from repositories with Debian Squeeze. I attempting to create a new DomU on the new host which is similar to an existing DomU running on the older Lenny host. The DomU is a three NIC firewall. Two of the NICs are virtualized. One NIC is a

Hello, I''m seeing problems with Xen and IRQ-sharing PCI cards which are passed through to a Xen DomU. As I''m not sure whether this is a problem with Xen or with the Debian Xen Kernel (2.6.26-13 from lenny) I''m using, I''d like to ask here before posting a bug. Reproducing the problem goes as follows: 1. Put a PCI card in the machine and make sure it shares

Dear all, I have a reproducible issue with centos54 dom0 and debian lenny domU using pygrub. As far as I enter "shutdown -r now" in the running Debian Lenny DomU the whole system hangs. Keyboard is dead, network is dead and no more logging. Ending up in a hardware reset of the box. I was able to reproduce this 3 times. Restarting with xm reboot debian50 works without problems. Is there

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

Hi list, The crux of my setup is given in the Subject: field. I''m using Xen 3.0.3 (release) on a VIA Nehemiah chipset with Linux 2.6.16.29 in both dom0 and domU. Because the documentation on PCI passthrough is a bit sparse, I''m turning to the mailing list.. hopefully you guys have some input. My goal is to set up a system where: * 1 domU VM runs at a time. * The VM can be

Fixed : Double amount of memory from 128 to 256 and iommu works it out fine. RTFEM (read the fucking error message) : [ 0.872160] Kernel panic - not syncing: Out of memory and no killable processes... ________________________________________________________________________________________________________________ Frédéric Abel| RTS France BeNeLux | Quantum Corporation

Hi, to make transitions more convenient, I've done this by using uuid instead of device names. If you ls -l /dev/disk/by-uuid inside your domU, you'll see something like lrwxrwxrwx 1 root root 10 5. Mai 07:38 39a2a64b-0716-47ad-92f4-a7437cac54ee -> ../../sda2 lrwxrwxrwx 1 root root 10 5. Mai 07:38 e8b97b59-a790-417c-8231-fe8da8b6e6ee -> ../../sda1 In /etc/fstab inside the domU,

Package: src:linux Version: 3.2.41-2 Severity: important Hello, I just discovered a strange bug with serial passthrough in xen 4.1 on Debian Wheezy. The Dom0 has a GSM modem connected to serial port. The serial port is passed through to a DomU with options 'irq = [ 4 ]' and 'ioports = [ '3f8-3ff ]'. This worked as expected on Debian Squeeze with Xen 4.0 and Linux kernel

Hello, I''m experimenting with Xen. I managed to get running Windows8 Enterprise Evaluation in domU and passed through an ExpressCard34 USB3.0 controller to which I connect things. I have an external USB sound card working in domU just fine but when I''m trying to connect another USB sound capable device I get that error. If I open properties of the faulty device in Windows Device

On 5/10/2021 1:33 PM, Chuck Zmudzinski wrote: > Package: src:linux > Version: 5.10.28-1 > Severity: normal > Tags: upstream > > Dear Maintainer, > > I have been using Xen's PCI and VGA passthrough feature since wheezy and jessie were the stable versions, and back then both Windows HVMs and Linux HVMs would function with the Intel Integrated Graphics Device (IGD), the

I am having trouble getting PCI Passthrough to work from Dom0 running CentOS 7 to DomU runnning Debian 8 I am using Xen 4.6 with CentOS kernel 3.18.34-20.el7.x86_64 on a Dell Poweredge T430. I think I have set it all up correctly, but I see no message when putting a USB device into any of the USB slots on the DomU There are three other DomUs running, but I have no need of PCI Passthrough set up

Hi, I have a perfectly running Xen 3.0.4 installation with kernel 2.6.16-42 with PCI passthrough for my internet interface (ethernet). But with I boot my 2.6.19 xen kernel on dom0, I''m unable to have the NIC working in domU. I can see the NIC both in domU and dom0 with lspci. All other network interfaces are working correctly (ethernet in dom0 and bridges). Here is my entry in grub

Dear George please find attached the three files as requested. I have used iommu=soft in the grub command line for the kernel in the domU as explained before. many thanks Francis From: "George Dunlap" <dunlapg at umich.edu> To: "francis" <francis at choughs.net>, "centos-virt" <centos-virt at centos.org> Sent: Monday, 16 May, 2016 10:29:09

Hi, I have used this http://wiki.centos.org/HowTos/Xen/Xen4QuickStart and everything works like a charm then I installed a VM using http://wiki.centos.org/HowTos/Xen/Xen4QuickStart/Xen4Libvirt only to realize later that I don't want NAT. I would want to use PCI passthrough and so i used virsh net-destroy default virsh net-undefine default and net-create /home/kartik/passthrough.xml

Hi all, I recently upgraded my Xen 3.2.1 to 3.3.1 on Centos 5.2. Everything seems to have gone pretty smoothly except I have a few issues. My system specs are: 4GB RAM Q6600 quad core Intel CPU P5E-VM DO Q35 Intel mobo (VT-d enabled) Skystar2 DVB PCI card passed through to HVM DomU HVM Windows XP SP3 DomU 1. When I restart my DomU, it shuts down and turns into Domain-Unnamed but

I am setting up a DomU Debian on Xen on an LVM. Step 1  Debian Dom0 which has a Volume Group named virtualization. I edited /etc/xen-tools/xen-tools.conf and with some appropriate changes I  to create image I executed xen-create-image --hostname=vignettes --size=150Gb --swap=4Gb --ip=172.21.100.151 --force --memory=2Gb --arch=amd64 --role=udev Step 2. Now things go smoothly until I get