similar to: tg3 gigabit speed

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

Hi all! I want to assign a physical network card (e100) to a domU: I think Dom0 is ok but domU does not recognize the pci nic. into DomU I don''t know wath should I see: I have nothing in dmesg nor in messages... Into Dom0 I have this modules.conf: options pciback hide=(0000:03: 08.0) install e100 /sbin/modprobe pciback; /sbin/modprobe --ignore-install e100 This is dmesg: pciback

Hi, Thanks to everyone involved in the Xen project. I think it is great and can''t wait to get my hands dirty with it. In the meantime, I cannot boot Dom0 on an ibm x335 and I am not sure what the problem is. Any insights are welcome. Here is what my grub.conf file looks like: title Fedora Core (2.6.8-1.521) root (hd0,0) kernel /vmlinuz-2.6.8-1.521 ro root=/dev/sda9

Hi all, I am trying to configure a Dom U to act as a firewall and therefore I need to pass one of the two ethernet cards to the Dom-U. I configured the Xen kernel to build pciback as a module and I am passing the hide option via boot parameters. I boot the pv machine via pygrub and I am able to see the ethernet device in Dom U as follows: Dom-U#lspci 02:00.0 Ethernet controller: Broadcom

Group, My linux box, running with Centos-5.5, is showing up (??) a pseudo network interface for Eth0. On Switch where my Eth0 is connected, observed 2 MAC-Addresses. If a DHCP server present in LAN, the second pseudo interface is picking up a DHCP IP Address too. Furthermore you can ping both Eth0 ip and Psedo Eth0 IP from the switch. The intensity of the problem is more when port-security is

I have a strange problem on one machine where eth0 gets killed when I add a virtual interface. It's got something to do with the NIC ordering or with the xen network script having a problem with multiple NICs and virtual interfaces. I could need some help/comments on this. Some history: I added a NIC (chip identifies as Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit

Hi, I''m using CentOS 5.5 x86_64 xen 3.43 from gitco.de and I have an Openvox A1200P voip card and am passing it thru to another centos 5.5 DomU, when I 1st start the domain driver loads and everything seems quite nice and the device works, but after a reboor of the DomU, this is shown on my Dom0 dmesg Here''s Dom0 info [root@xen ~]# dmesg Bootdata ok (command line is ro

Hi, I''m using CentOS 5.5 x86_64 xen 3.43 from gitco.de and I have an Openvox A1200P voip card and am passing it thru to another centos 5.5 DomU, when I 1st start the domain driver loads and everything seems quite nice and the device works, but after a reboor of the DomU, this is shown on my Dom0 dmesg Here''s Dom0 info [root@xen ~]# dmesg Bootdata ok (command line is ro

On Wed, 2016-02-03 at 15:28 -0500, Konrad Rzeszutek Wilk wrote: > > > And I wonder if the XEN_DOMCTL_irq_permission aka, > > > xc_domain_irq_permission > > > had been called. I remember that at some point we missed it for > > > Xend.. > > > > > False alarm. > > It was all in Linux. Attached are four patches (the first two > are for

Greetings, I recently installed CentOS 5 on Dell PE 1750 server. I have noticed that the speed and duplex settings are 100 Half Duplex. I tried to change the duplex settings to full, but no success. I got the error message "Cannot get current device settings: Operation not supported". Does anyone else experience this issue?. Below is the error message and some more details about my box.

I''m at my wits end maybe someone out there can help me. Machine Shuttle AN51R Motherboard 1GB ram AMD-64 3000+ (2GHz) 20GB HD (western digital) with 1GB for minimal install, 500MB for swap, and the rest I had planned to use for LVM volumes for VMs. I''ve been running ubuntu 5.04 (hoary) happy as a clam for a while now no problems. Now I''ve started investigating Xen

I am unable to boot Dom0 on a machine with Reiser file systems. Reiser support is built into the xen0 kernel. I have similar setup with ext3 file systems working just fine, so I don''t think it is a setup problem. I have tried booting with and without and initrd file, booting with the original Linux distro initrd file, etc, but nothing seems to work. I recall seeing a thread about ReiserFS

(originally filed as a bug in Fedora's bugzilla, see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=171933) Greetings, Using Fedora Core 4 on a Dell PE 420sc. Malfunctioning kernel is smp-2.6.13-1.1532_FC4. Properly functioning kernels included smp-2.6.12-1.1456_FC4. Network performance is extremely poor when using bridged network interfaces. When not using brctl, the interface

I''m tracking performance on the machine I installed yesterday. mutt running on one Xen instance, accessing via imap to another instance, accessing via nfs the maildir in another instances, seems little laggy when moving up and down the message index list. Network latency seems low < 30ms on average. So I was tracking vmstat. On the mutt instances is seems reasonable: [nic@shell:~]

We have an HP DL360 server with dual on-board Tigon3 ethernet cards. We are using eth0, eth1 is unused at the moment. Sometimes when the network interface is under heavy load, for example moving large file transfers over rsync or NFS, the network interface stops working and we lose all connection to the server. The only solution at this point is to jump on the console and restart the network

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello All, I have had a problem detecting the network card on my notebook when ACPI is enabled for a year. The problem still exists in 7.1-RELEASE. with ACPI: ... bge0: <Broadcom NetLink Gigabit Ethernet Controller, ASIC rev. 0xb002> irq 17 at device 0.0 on pci8 bge0: 0x10000 bytes of rid 0x10 res 3 failed (0, 0xffffffff). bge0: couldn't

Source: xen Severity: normal Dear Maintainer, After an upgrade, my passthroughed NIC stopped working. I created a new jessie domU and tried to passthrough some PCI devices and found that both USB3 host controller and tg3 NIC generated these lines in domU dmesg: xen:events: Failed to obtain physical IRQ 31 xen:events: Failed to obtain physical IRQ 32 xen:events: Failed to obtain physical IRQ 33

My kernel crashes every time I shut down dom0 This crash was not happening before I installed the Xen hypervisor Any ideas? (XEN) Xen version 3.2-1 (Debian 3.2.1-2) (waldi at debian.org) (gcc version 4.3.1 (Debian 4.3.1-2) ) Sat Jun 28 09:32:18 UTC 2008 (XEN) Command line: com1=9600,8n1 console=com1 (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods:

Hi all I''m trying to get Xen running on a Tyan MB, having 3 NICs (1 e100 and 2 tg3''s). Using linux-2.6.hg on a dual Opteron. Compile was OK, and using the e100 as eth0 everything works as it should, great thing. when having one of the tg3''s as eth0, Dom0 works ok, but when starting a DomU, the network in as well Dom0 as DomU stop (as in ''completely

Hello listmates, As some of you may know we have been having a really bad problem with Realtek Semiconductor Co., Ltd. RTL-8169 cards. See here for details: http://forum.nginx.org/read.php?24,140124,140224 So now my question is, what PCI 1 Gbit/s Ethernet adapters should I use under CentOS? If you have had a consistent positive experience with any particular chipset/brand please speak up.