similar to: Maybe a bug of xen

I want to check the speed like features of my Ethernet in dom0 and domUs. But in virtualized environment it gives strange output why is that so? how to check it otherwise? Non-virtualized FC11 [root@fasiha home]# ethtool eth0 Settings for eth0:     Supported ports: [ TP ]     Supported link modes:   10baseT/Half 10baseT/Full                             100baseT/Half 100baseT/Full    

I want to check the speed like features of my Ethernet in dom0 and domUs. But in virtualized environment it gives strange output why is that so? how to check it otherwise? Non-virtualized FC11 [root@fasiha home]# ethtool eth0 Settings for eth0:     Supported ports: [ TP ]     Supported link modes:   10baseT/Half 10baseT/Full                             100baseT/Half 100baseT/Full    

On 10/10/2016 09:31 PM, John R Pierce wrote: > > oh. Yeah, the entire "net-tools" package is deprecated. I tend to forget which of the two (ethtool or mii-tool) is in that set. # Avoid using any of these: $ rpm -ql net-tools

I''m trying to build out a test cloud using XCP 1.0.0 beta with 3 machines of 18 cores total (Phenom II 1090s). I''ve built three machines, installed XCP 1.0.0 beta on them and they all three have the same problem - the Realtek network cards don''t work. The following is the output from lspci 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI

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

CentOS 6.2......... Why do the physical interfaces report (correctly) that they're negotiated at 1000Mb/s, but when I `cat /proc/net/bonding/bond0` I get 100Mbps for the member interfaces, and when I ` mii-tool bond0` I get 10Mbps for the bond? ----------------------------------------------------------------------------------------- ethtool em1 Settings for em1: Supported ports: [

My system is: Intel CC820 motherboard (which supports PME# wake up for wake on LAN) 3com 3C905C which also supports wake on LAN via PME# Linux 5.5 The motherboard BIOS is later than one that reports an issue with WOL and this particular network card was fixed. But when I turn off the PC (shutdown or poweroff commands or front panel button), it cannot be restarted via WOL. The network light on

I've got a pair of identical CentOS 6.7 servers, with SuperMicro X8DTE-F motherboards, these have 2 each Intel 82574L ethernet ports. The eth0 ports are plugged in with 10' runs of brand new cat 5e cable to a Cisco Nexxus 9000 switch (provided by the data center). These servers keep coming up at 100baseT rather than gigE. I've swapped ports and cables with a different server,

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

in dom0, how does one get and set the link information for a NIC? In a non-xen kernel, we could get this info by simply running: # ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supports auto-negotiation: Yes Advertised link modes:

Hi. I am trying to setup my firewall in DomU. However, I have got a little problem. My pon dsl-provider exits with following message. Nov 18 09:44:40 alsfw01 pppd[1723]: Plugin rp-pppoe.so loaded. Nov 18 09:44:40 alsfw01 pppd[1723]: Linux kernel does not support PPPoE -- are you running 2.4.x? Nov 18 09:44:40 alsfw01 pppd[1723]: Exit. I am running xen out of the box on Debian Stable. My

Hello, Just did a fresh install of xen-4.0 and using the 2.6.31.13 dom0 kernel. I have 6 linux debian guests running, and on my host console i am getting these errors rolling pretty constantly. "Attempting to checksum a non-TCP/UDP packet, dropping a protocol 1 packet" I tried doing the ethtool -K eth0 tx off and same thing on peth0, using bridged mode for network config. Any tips?

Hello, Just did a fresh install of xen-4.0 and using the 2.6.31.13 dom0 kernel. I have 6 linux debian guests running, and on my host console i am getting these errors rolling pretty constantly. "Attempting to checksum a non-TCP/UDP packet, dropping a protocol 1 packet" I tried doing the ethtool -K eth0 tx off and same thing on peth0, using bridged mode for network config. Any tips?

Hi, I have been playing this weekend with bonding on PCI netcards and found that all of netcards I have, but old 3com, do not support MII. So bonding is not going to happen with them. Do you have some pci netcards supporting MII successfully running on bonging? Thanks, David Hrb??

anyone know how to force network cards talk at gig speeds when all it wants to do is establish a connection at 100mbits root at host1 [/backup/cpbackup/daily]# mii-tool eth0: negotiated 100baseTx-FD, link ok eth1: negotiated 100baseTx-FD flow-control, link ok 01:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express (rev 11) Subsystem: Broadcom

Tested on identical hardware (Dell SC1425) with a non-xen kernel, it wroks fine. However under Xen, this is what happens: xen1 ~ # ethtool eth0 Settings for eth0: No data available xen1 ~ # mii-tool eth0 SIOCGMIIPHY on ''eth0'' failed: Operation not supported Any ideas? Thanks, -- Ian P. Christian ~ http://pookey.co.uk _______________________________________________

Hi folks on debian stable I've a default samba file sharing config. Everything works perfectly (almost...) - samba version 3.6.6 >From linux and windows clients (wired and wifi too) when I (i.e. listen musics) often (one time every 4/5 minutes) networks suddenly collapse (for less one second) and immediately goes up. So I've an interrupt of broadcast (this happens also if I use rsync

Problem still not solved, or any idea whats wrong. here are some msgs: device vif1.0 entered promiscuous mode alloc irq_desc for 1246 on node 0 alloc kstat_irqs on node 0 brI: port 2(vif1.0) entering learning state device vif1.1 entered promiscuous mode brE: port 2(vif1.1) entering learning state physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for

When I start xen dom0 I get that same dhcp address for eth0 and for xen-br0, dom0 can talk to the world. If I start each of my 3 domU''s mannually, each guest gets a xen-br0 vif with a dhcp address and all 3 can talk to the outside world and each other (my "flat network"). What I want is a tiered network with the first domU acting as a firewall with 3 nics vif = [