similar to: domU does not see the pci nic - pci passthrough

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

I just managed to get xen 3.2 up and running in Centos 5.1. I installed the rpms from xen.org (first the xen 3.1 then 3.2 rpms) my grub setting in dom0 is title CentOS (2.6.18-xen_3.2.0) root (hd0,5) kernel /boot/xen.gz-3.2 module /boot/vmlinuz-2.6-xen ro root=LABEL=/ rhgb quiet module /boot/initrd-2.6-xen.img where vmlinuz-2.6-xen is a symlink to

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''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, Is virsh able to access the VMX config of a virtual machine running on a esxi host? I would like to take backups of my virtual machine configs and the doku section "Converting from VMware VMX config to domain XML config" (http://libvirt.org/drvesx.html) comes close to this - but does not tell how to get access to the vmx file. I would prefer a solution where ssh access to the

So I just finished doing a fresh install of CentOS 6.3. The machine has three ethernet ports in it: one on the motherboard (VIA Rhine), and two add-on cards, an Intel Pro100 and an old SMC1255TX. When CentOS comes up, this is what I see in the dmesg output: # dmesg | grep eth e100 0000:00:08.0: eth0: addr 0xf6043000, irq 16, MAC addr 00:02:b3:be:02:87 eth1: ADMtek Comet rev 17

Hi, next step, # dmesg | grep pciback Bootdata ok (command line is root=/dev/sda2 ro console=tty0 pciback.hide=(0000:02:05.0)(0000:02:06.0)(0000:02:07.0)(0000:02:08.0)(0000:02:09.0) ) Kernel command line: root=/dev/sda2 ro console=tty0 pciback.hide=(0000:02:05.0)(0000:02:06.0)(0000:02:07.0)(0000:02:08.0)(0000:02:09.0) Unknown boot option

Or how to delegate special PCI devices from domain-0 to dom(u) Hi, I tried to manage some pci devices for dom(u) domains, using the fedora core 5 (xen0/u) and 6-test2 (xen) i686 kernel-xen and kernel-xen-devel rpms: In domain-0 lspci shows the pci device 00:04.01 which should be delegated to dom(u) In dom(u) lspci does not show any information (this seems to be ok) lsmod in dom(u) gives:

Dear all, I followed the steps described in the wiki in order to get an Arnadle board running Xen, but I''m having trouble in starting a domU. Let me describe you the steps I followed. Sorry for such a long mail, but I think that a verbose description is necessary so you can point me what I''m doing wrong. I couldn''t boot properly over the network. This is why I

I had test the command virsh blockcommit, but it failed, with the libvirt version 1.1.0, and qemu version 1.6.0. Is this feature being developing? Thanks root at cvk-31:/vms/images# virsh -v 1.1.0 root at cvk-31:/vms/images# qemu-img -V qemu-img version 1.6.0, Copyright (c) 2004-2008 Fabrice Bellard usage: qemu-img command [command options] root at cvk-31:/vms/images# virsh blockcommit Vmtest

Hi All, This might be a stupid question, but I have two PCI devices that I want to pass-thru to a PV domU. I can pass one of them, but not both. I''m sure it''s a stupid syntax issue within my configuration file. When I do a "lspci" in the domU, (CentOS 5.1), only one of the devices shows up. (e.g.) 00:00.0 Multimedia video controller: Internext Compression Inc

Could the problem be that the e100 can do IP receive checksumming on the board, but the eepro driver doesn't enable it. When the board is doing checksum offload, then the csum field isn't set. Please try disabling receive checksumming on the e100 driver modprobe e100 XsumRX=0 If this is the problem, it exists both 2.4 and 2.6. On Wed, 27 Aug 2003 18:24:57 +0200 Hannes Schulz

Hello! I'm having problems getting PCI pass-through to work. This is on a AMD64 system, paravirtualized with xen-hypervisor-4.0-amd64 4.0.0-1~experimental.1, dom0: linux-image-2.6.32-5-xen-amd64 2.6.32-12. From IRC, earlier today: <tschwinge> waldi: Aren't the Debian xen domU-capable kernels supposed to contain the PCI frontend (needed for PCI pass-through)? I'm getting:

Hello! I'm having problems getting PCI pass-through to work. This is on a AMD64 system, paravirtualized with xen-hypervisor-4.0-amd64 4.0.0-1~experimental.1, dom0: linux-image-2.6.32-5-xen-amd64 2.6.32-12. From IRC, earlier today: <tschwinge> waldi: Aren't the Debian xen domU-capable kernels supposed to contain the PCI frontend (needed for PCI pass-through)? I'm getting:

Hi, I have another question, when I do the blockcommit command and get the result " Top image as the active layer is currently unsupported ", is it being developed? root@cvk-31:/vms/images# virsh blockcommit Vmtest /vms/images/Vmtest1;echo $? error: internal error unable to execute QEMU command 'block-commit': Top image as the active layer is currently unsupported 1 But as I

Hi All, For my issue, first thanks to ALL, I have some idea of it. Also Thank Peter for his kind remind, I would become one good guy in this list. Most mentioned MTU, but how I assure that the problem is just MTU, how I debug it? Here is my bridge configuration: Internet | | Gateway | | eth0 Ethernet Bridge | eth1 | H u b ( one normal hub

I have a hardware here with 9 NICs (8 of them on-board) and I want to set up 8 NICs as real network interfaces, one for each xen domain. The 9th NIC should be Domain-0 which is working well. Currently I have only set up one domain which is running in bridged mode at the moment. I am currently trying to set up a second domain which uses eth2 but I didn''t succeed. I want to get the

Hi, I have been receiving messages on a new DomU''s kern.log. I''ve done a lot of googling, but haven''t came up with anything very useful, at least not in a Xen context. I was wondering if anyone had any suggestions about what could be wrong. From everything I have read, there should be a stack trace included, but I am not seeing one. Thanks in advance, Ian. on

I four nodes setup to do active-backup bonding and the drivers loaded for the bonded network interfaces vary between tg3 and e100. All interfaces with the e100 driver loaded report errors much like what you see here: bonding: bond0: link status definitely down for interface eth2, disabling it e100: eth2: e100_watchdog: link up, 100Mbps, full-duplex bonding: bond0: link status definitely up for

>From: "Shawn Wright" <swright@sls.bc.ca> >Subject: [Shorewall-users] Finally making some progress >I *think* we are finally making some progress in tracking our elusive >performance problems. After employing a second 10Mb link from our ISP, >along with another firewall box and proxy, we were able to determine the >problem *is* our firewall. We don''t