similar to: Passthrough support ?

Hello, I am desperately trying to get pci-passthrough to working. I want to pass a tg3 nic to domU. when booting domU I get a lot of messages: pcifront pci-0: pciback not responding!!! in domU, "ifconfig eth... adress up" hangs for 2 minutes, finally ifconfig -a shows a correct setting with no data transmitted rx/tx The IP Adress is being assigned, but there is no data transmission

On Wed, Jan 27, 2016 at 7:30 PM, Konrad Rzeszutek Wilk < konrad.wilk at oracle.com> wrote: > On Sat, Jan 23, 2016 at 05:12:04PM +0100, Tommi Airikka wrote: > > Xen developers, > > > > After an upgrade of my Debian Jessie dom0 and domUs, my passthroughed > > NIC stopped working. > > This bug was probably introduced in Debian Jessie sometime > > between

Hi experts I use xen-4.0.0 and dom0 is 2.6.33 and domU is 2.6.34 #lspci ............... 01:00.0 Ethernet controller: Intel Corporation Unknown device 10a7 (rev 02) 01:00.1 Ethernet controller: Intel Corporation Unknown device 10a7 (rev 02) 05:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06) 05:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit

Dear all, i''m having problems passing a Hauppage Nova-S2 card to my DomU (Mythtv Backend). Hardware is: HP XW8200 2x 3.0GHz Xeon 8Gb ECC Ram 1x TT3200-S2 card 1x DVBWordl S2 card 1x Nova-S2 card [many other card for other domUs...] Dom0 is Ubuntu 8.04 server LTS. Xen 3.2 from repo. DomU (Mythtv) is a 8.04 (using LVM) both using 2.6.24-23-xen kernels Dom0 configs: lspci: ... 02:01.0

This patch enables PCI passthrough with stub domain. PCI passthrough with stub domain has failed in the past. The primary reason is that hypercalls from qemu in stub domain are rejected. This patch allows qemu in stub domain to call the hypercalls which is needed for PCI passthrough. For security, if target domain of hypercall is different from that of stub domain, it rejects hypercall. To use

I am running debian lenny, with the standard Xen 3.2 packages, with the 2.6.18-6-xen-686 kernel as dom0, and 2.6.24-1-xen-686 as domU. Everything is working fine apart from the console and the PCI passthrough. I am getting these errors in the domU on startup: XENBUS: Device with no driver: device/pci/0 XENBUS: Device with no driver: device/console/0 Does this mean the modules are missing?

Hello I am new in XEN and Linux. I am trying the VGA passthru. I can xen-pciback.hide EtherNet, Serial Com port. But when I xen-pciback.hide my VGA. I can no longer login to the Linux(Fedora 12). Then how can I xm create a XP DomU guest? Can anyone help? I am using Intel Q35 MB with Intel Core2 CPU. _______________________________________________ Xen-users mailing list

On Wed, Jun 22, 2016 at 11:49 AM, Francis Greaves <francis at choughs.net> wrote: > More information... > I have pcifront showing as a module in the DomU and the usb shows in dmesg > as: > [ 3.167543] usbcore: registered new interface driver usbfs > [ 3.167563] usbcore: registered new interface driver hub > [ 3.167585] usbcore: registered new device driver usb >

Hello, The topic is self-explanatory: how to ensure that a PV driver domain correctly prepares its PCI devices for S3 sleep? If I do "pm-suspend" in dom0, and the driver domain has active network interfaces, suspend hangs the system. Yes, in case of this particular machine, suspend works fine when there is no driver domain. It is possible to manually invoke scripts from

Hi all, I have a problem when from domU I need to configure a network interface. My system configuration is the next: dom0: xen 3.4.3 with 2.6.18-238.9.1.el5xen kernel, making pci back from a network card. All ok. This is the result from "lspci -v -s 09:00.0" 09:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12) Subsystem: Broadcom

I''m using Xen 4.3, installed from source on Ubuntu 13.04. I''ve successfully installed a Windows 8 guest, and had Xen pass it an AMD FirePro W7000 GPU (technically 2 PCI devices - the second is for the sound), as well as the virtualised graphics adapter. Windows finds the card fine, and I''ve installed AMD''s drivers. Device Manager says that the card cannot

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 _______________________________________________

Hi : I am trying to do PCIe passthrough on HVM domu. I have window XP as a HVM domu and xen-4.0. dom0 and domU (without device assign) works fine. I have more than one NIC card. I want to passthrough 03:00.0 to domu here are the list of my nic cards: lspci | grep -i eth 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)

testing, uname -ri 2.6.33-rc5-4-xen x86_64 rpm -qa | grep -i Xen-4 xen-4.0.0_20873_01-29.1.x86_64 cat test.cfg name = ''test'' builder = ''linux'' bootloader = ''/usr/lib/xen/boot/domUloader.py'' bootargs = ''--entry=xvda1:vmlinuz-xen,/boot/initrd-xen'' disk = [

Hi all!. First of all sorry about my English it''s not very fluid. I have a small server based upon Supermicro X7DBN (Chipset Intel® 5000P) motherboard and Intel Xeon E5320 (1,83Ghz) with 4Gb of FB-DIMM RAM. The OS is Debian Lenny in dom0 (2.6.26-2-xen-amd64) and Debian Lenny in domU (2.6.26-2-xen-amd64). Xen is 3.4.2 compiled from sources. The problem comes when I need to passthrough

Hi! As dom0 I''m running Ubuntu Hardy withe xen 3.3 from backports. Reason to using xen 3.3 is that I could get Intrepid stock kernel to work as domu with xen 3.2. Now the problem I have is that I can''t passthrough PCI-devices to my domu. If I run lspci in the domu nothing is returned. I''ve tried to use the kernel from Hardy (2.6.24-21-xen) and stock kernel from

Hello, on a Supermicro H8DGU server with the latest BIOS PCI passtrough fails. I tried to give a two igbvf devices to the domU. pciback is configured and everything locks good until igbvf tries to initialize the PCI device. I have the same error with XEN 4.3, 4.3.1 and the current 4.4-unstable, linux kernel 3.12.0, 3.12.1, 3.9. DomU config: kernel = "/boot/gentoo-DomU" memory =

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 all, I have been having an issue for over a year with several Xen installations and have not been able to find out if this is just something I am missing. Basically I am trying to configure a firewall with two ethernet cards in a domU using pci passthrough. I am hiding the Ethernet cards at boot time via the pciback.hide kernel option. Right now I am running Xen 3.3.0 and the two Ethernet

Dear List, I need to make an Aladdin eToken Pro visible in a Linux guest HVM, but I cannot assign the device to any domU, while it''s being blocked by the dom0. To avoid this trouble I would like to pass the whole USB bus to the domU directly, via PCI passthrough. Now I use xen 3.3.0 from xensource and xen kernel from Ubuntu 8.04 2.6.24-19-xen, because the xensource xen kernel