similar to: Simple Query on PCI passthrough I/O

Hi , I have been trying to understand PCI -passthrough support. Please correct me if I am wrong in my following inferences. 1. Device emulation and pass through are both implemented using split drivers. 2. But, in case of emulation drivers of dom0 are used where as in case of passthrough ( as the name suggests ) native drivers in domU are used . 3. dom0 provides a virtual PCI device { an

Hi , I have been trying to understand PCI -passthrough support. Please correct me if I am wrong in my following inferences. 1. Device emulation and pass through are both implemented using split drivers. 2. But, in case of emulation drivers of dom0 are used where as in case of passthrough ( as the name suggests ) native drivers in domU are used . 3. dom0 provides a virtual PCI device { an

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

Hello Everyone. Well i want to write some information (not a complete backup) from my Virtual Machine to the tape drive, but the VM can''t read it. I guess i need to attach this device to the VM so it can read and write the tape driver but i don''t know how to do that, i found something similar but with a cd: # xm block-list <vm-id> –long # xm block-detach 1 5632 -f # xm

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

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?

Some question. Can I install Xen-3.2.1 with 2.6.18-xen kernel... to my Dom0 and without HVM, starting a debian(DomU) with kernel 2.6.25 from kernel src and compiled with all XEN port / features ? or i need to use the vmlinuz-2.6.18-xen to all my DomU ?? Thanks Crazy _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Newbie here. My hardware supports HVM (full virtualization), but I only need to run Linux on it. I initially tried to create a HVM domU, but couldn''t get pciback to work with a telephony card I need for use with Asterisk. However everything seems to be working fine under a paravirtualized guest as long as I use permissive mode on the card. (Knock on wood-I''ve had some weird

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 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

Hello everyone, just wondered after I read about devices passed through in HVM if the following if still true: (for Xen3.2.1) - a Domain running in HVM cannot get forwarded any other device than a USB device. - the USB device forwarding is not too stable - PCI forwarding is not possible without processor support and Xen support. - The GPLPV tools won''t change anything with that.

Hello all I tried to enable PCI Passthrough in my Debian Squeeze installation. Unfortunately, it didnt work. The following bug showed up (excerpt from dmesg): [ 10.148612] uhci_hcd 0000:00:14.2: PCI INT D -> Link[LNKD] -> GSI 11 (level, low) -> IRQ 11 [ 4.678352] Failed to setup GSI :11, err_code:-22 [ 4.678480] dmfe 0000:00:0e.0: PCI INT A -> Link[LNKB] -> GSI 11 (level, low)

Hello All, I have been having a very difficult time getting any template to work on xen. Here is what I am running root@personal:/etc/xen-tools# xm info host : personal release : 2.6.22-14-xen version : #1 SMP Tue Feb 12 09:27:26 UTC 2008 machine : i686 nr_cpus : 2 nr_nodes : 1 sockets_per_node : 1

Further to my messages back in May I have at last got round to trying to get my DomU to recognise USB devices. I am using Xen 4.6 with CentOS kernel 3.18.34-20.el7.x86_64. I have to manually make the port available before creating the DomU by issuing the command: xl pci-assignable-add 00:1a.0 otherwise nothing shows in: xl pci-assignable-list I have added this to my .cfg file as per the

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

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

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

Hi Konrad, Due to a 2.6.37-merge-window kernel now being able to boot under Xen i was able to test my xhci controller under dom0 which i previously couldn''t. The results: A) 2.6.37-merge-window kernel baremetal: Videograbbing while doing 20 iterations of make -j6 of kernel works. B) Xen + 2.6.37-merge-window kernel as Dom0: Videograbbing while doing 20 iterations of make -j6 of kernel

All, I''m posting to the Xen-devel list and the OSDL fastboot list. There are a number of Xen folks who''ll want to look at the code. For the fastboot folks, this is mostly intended as an announcement of the port. Please limit your replies to the list(s) that they applies to, thanks :-) A number of people have expressed interest in kexec support for Xen guests. In

Hello, i have been looking over inet for an answer to a problem iam unable to resolve, and after not being able to find a solution, i hope to get an aswer in the list. I have been trying to reach my /home (Dom0) from one of my virtual machines (i''m runnning them in debian etch) and i''m unable to do it, what i''m trying to do is to catch a file from the /home of my Dom0,