similar to: Could not setup Speed and Duplex on CentOS 5.5

I come across some problem when using xen-4.1.1-rc1-pre from xen-4.1-testing tree and 2.6.32.36xen linux kernel from git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git. when I use ''xend restart'' , it hangs when kernel dmesg printing ''Bridge firewalling registered'' and the console show below messages: localhost# xend restart Nothing to flush. Cannot

Two problems I hope to solve: 1. The switch being used has autoneg off and has port set to 100 full duplex. 2. Many times NIC fails to come up properly during PXE boot: r8169: eth0: link down ADDRCONF(NETDEV_UP): eth0: link is not ready I can't use ethtool to disable autoneg because the nic driver is built into a bzImage. The root fs is currently being mounted via nfs during pxeboot at

I am having an extremely strange issue with a BL460c1 (G1) blade on a c7000 enclosure. I could not for the life of me get the machine to ping the gateway or any other blade on the same enclosure (yes, the subnet mask was correct & quadruple-checked); although pinging to the local IP works. I was almost convinced that it was a network or hardware issue; until I asked someone to try

We've just moved one a new server from our sever room, where I built it, to the datacenter. We want to force autoneg off, and tell it gigabit and full duplex. Using ethtool, I get no errors setting the speed or duplex. HOWEVER, autoneg on works... and autoneg off utterly refuses to work, and gives: ethtool -s eth0 autoneg off Cannot set new settings: Invalid argument not setting autoneg

When starting xend i see the following errors on the console. I''m running CentOS 5 as the operating system with kernel 2.6.32.18 from 4.0.1''s `make prep-kernels` Below is a log, the things i''m concerned with is the XENBUS errors and the deprecated iptables stuff. Any ideas whats going on here? ---------------------------------------------------- Bridge

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, I have Xen 3.0.3 installed on CentOS 5.5 with 2 paravirtualized domU''s configured to use the default bridge networking and am having networking issues. If I boot the computer fresh I am able to ping dom0 and can SSH into it and start the domU''s. The following ping snippet demonstrates the problem. The first group of "Destination Host Unreachable" is while the

Hello. I''ve just started with Xen and configuring Dom0. My hardware is Core2Duo based Xeon server and I installed Debian etch for amd64 architecture. The Xen related pachages installed are the following. linux-image-2.6.17-2-xen-amd64 linux-modules-2.6.17-2-xen-amd64 xen-hypervisor-3.0.3-1-amd64 xen-tools xen-utils-3.0.3-1 xen-utils-common My problem is that when xend is

Hi, I would like to ask concerning problems after installing xen 3.3 on Centos 5.2 I use 2.6.18.8-xen (xen3.3.1 testing - installing with mercurial). After done with make world and make install, I did mkinitrd and placing it in /boot changing the grub and reboot.. succeded I do not install libvirt and the domUs from the previous xen 3.0 (built-in Centos 5.2) are NOT able to start : [root@wing

Hi, after upgrading to 7.6, kernel 3.10.0-957.1.3.el7.x86_64, at boot instead of the GUI login screen I got two lines like this: IPv6: ADDRCONF(NETDEV_UP): em1: link is not ready IPv6: ADDRCONF(NETDEV_UP): em1: link is not ready The server is accessible via ssh on IPv4 Server: DELL PowerEdge T 110 II NIC: Broadcom, driver tg3, lspci -v: 04:00.0 Ethernet controller: Broadcom Inc. and

Hi all, I just noticed that my two nics that are bonded via mode 0 are showing the same mac addy in ifconfig. Is this normal? In syslog I keep getting; kernel: pbond0: received packet with own address as source address Some guidance is appreciated before I dive in and troubleshoot. If I don't list the mac addy in my ifcfg-th# files, only one of the 2 nic comes up during boot.

Objet : Xend start and after lose network Hi everybody : My configuration : Dapper 6.06 LTS with all updates Xen 3.0.2.2 My problem : After making ''xend start'', I lose network connections between my server and local network or internet. Nota : domU cas normally access to network I read about a similar problem in the bugtracker (N. 62) but it seems that this is normally

This problem still bites us. I've tried to play around with DHCP settings (rd.net.timeout.dhcp, rd.net.dhcp.retry) to no avail. I'm happy about /any/ hint. Cheers frank On 04/24/2017 11:57 PM, Frank Thommen wrote: > Hi, > > kickstarting fails due to problems with host resolution, even though the > network seems to be properly configured through DHCP. eno1 and eno2 are

Last problem I had involved changing one character in my configuration scripts. Really easy once someone showed me what was wrong. Well I think this issue is just the same. The moment I used apt to install the Xen kernal and tools I lost internet connectivity. I have been managing because I can restore connectivity be deleting the bridge mpower@dodtsair:~$ sudo ifdown eth0

Hello everybody, I have an odd problem with iptables using a Xen bridge setup. I don''t know if it would be better to post to netfilter Mailing-List. But I hope someone here know how to solve it. If it''s OT here, please let me know. I''ll try to do a little bit ASCII-Graphics to explain the topo better: _________ ________

Hello, I have installed CentOS 5 onto a server this afternoon using NFS. The NFS 'server' has a 100Mb/full-duplex interface, the server I installed CentOS on to has 4 x 100Mb interfaces. However, the installation was painfully slow to start with, and by using ctrl-alt-f2/f4/f5 I could see that contact with the NFS server was intermitently failing. Soon after some of the packages had

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

Command just times our for me virt-install --paravirt --vcpus=4 --name server1 --ram 4096 --file /opt/xen-images/hlcnwmmp01.img -x "ks=http://10.203.1.11/kickstart/ks-xen.cfg" --file-size 40 --location http://128.61.111.11/pub/centos/5.4/os/x86_64 -b peth0 Starting install... Retrieving file vmlinuz... | 1.9 MB 00:00 Retrieving file initrd.img...

Hi, kickstarting fails due to problems with host resolution, even though the network seems to be properly configured through DHCP. eno1 and eno2 are both attached to the network, but only eno1 gets an IP via DHCP. Still `curl` cannot resolve the mirror host and the kickstart host during dracut-initqueue: rdsosreport.txt ------------------------------------------------ [...] [ 14.780428]

I have a machine I just deployed w/ tg3 interfaces, I have setup bonding on this same line of server (HP DL380 G4) a million times. I saw there were changes recently to how you configure a bond and have my setup configured according to: http://kbase.redhat.com/faq/docs/DOC-7431 The HP switch has a LACP trunk defined on the two ports. Problem is, when rebooting, I need to issue a `service network