similar to: IPv6: ADDRCONF(NETDEV_UP): link is not ready after upgrading to 7.6

On 12/25/18 11:54 PM, Luigi Rosa wrote: > 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: The output you see is probably unrelated to the problem.? Check the output of "systemctl status gdm" and /var/log/Xorg.0.log

When i do #xm create name.cfg i''ve ADDRCONF(NETDEV_UP): vif2.0: link is not ready My DomU was created but can''t access to network.... What do think about it? I use xen 3.0.4 HVM. Thanks! -- Benjamin HENRION Elève de 4eme année de l'' EXIA (Nancy) Ecole supérieure d''informatique Spé Réseaux _______________________________________________ Xen-users mailing

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'm trying to autoinstall a DELL 9030 desktop with CentOS7 using PXE and Kikstart. I fall in a strange problem (I have several other laptop or desktop using this install process without any problem, kernel and initrd are from a Centos 7.4 iso) - PXE boot start and the desktop load the kernel and the inirtd file - the kernel is booted and at this time the led of the network switch goes down

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

I use bonding under CENTOS4.5 x32_62. I have these weird messages when I'm restarting network. Do you have any ideas how to fix this? (there is similar bug for centos5 http://bugs.centos.org/view.php?id=2404, but the author says that it worked for him in centos4...) Thanks Vitaly Dec 17 08:34:21 3_10 kernel: bonding: Warning: the permanent HWaddr of eth0 - 00:1A:64:0A:DC:9C - is still in

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

Le 18/02/2019 ? 18:58, Tru Huynh a ?crit?: > On Mon, Feb 18, 2019 at 06:36:10PM +0100, Patrick B?gou wrote: > ... >> - PXE boot start and the desktop load the kernel and the inirtd file >> >> - the kernel is booted and at this time the led of the network switch >> goes down for the port used by the desktop. >> >> - then I have a message "no carrier

On Mon, Feb 18, 2019 at 06:36:10PM +0100, Patrick B?gou wrote: ... > > - PXE boot start and the desktop load the kernel and the inirtd file > > - the kernel is booted and at this time the led of the network switch > goes down for the port used by the desktop. > > - then I have a message "no carrier detected on interface em1" > > - followed by " IPv6

I'm observing double the amount of "recv" bytes in latest Centos v6.8 with ixgbe 4.2.1-k. Anybody seeing the same? $ ethtool -i em1 driver: ixgbe version: 4.2.1-k $ uname -an Linux chndcdmid01.rd.ph.cox.net 2.6.32-642.4.2.el6.x86_64 #1 SMP Tue Aug 23 19:58:13 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Doing comparison on 2 days at same hour just to show the difference. This is an

Shorewall 4.5.15 3 Interface setup em1 p3p1 p4p4 ppp0 Hi, Since changing to NetworkManger on Fedora 18 I can no longer connect to the DSL Modem, which is connected to Interface em1. When the NetworkManger brings up the interfaces and ppp0, it no longer assigns an IP to em1. If I have ppp0 disabled and NetworkManger brings up the interfaces, em1 gets an IP of 192.168.1.2. Then when I get

I am running NOX controller with a python script that prints out the destination mac and the source mac for each packet arriving at the now controller and then floods it out. So here's what happening: With em1 connected, all the packets that arrive at em1 are coming to the controller and printing out the details. However, without em1 connected to the OVS, when I have the following setup:

Hey, I have KVM installed on my Fedora 17 box. I added the network interfaces of the virtual machines to the openvswitch bridge as follows: ____ ____ / VM1\______br0_______/ em1\ \____/ | \____/ | _|_ /VM2\ \____/ virbr0 is the virtual network switch VM1 and VM2 are on the same subnet having tap interfaces vnet0 and vnet1 respectively. em1 is the default

Once upon a time, Lists <lists at benjamindsmith.com> said: > I understand that it's possible to allow the 4 VM guest systems to each have a > "direct" fixed IP address and access the addresses \via the host network > adapter, while the host retains its fixed IP. If you are running NetworkManager (the default), it's not too hard. Here's an example

Since RHV 3.6.10, the default network name is 'ovirtmgmt' instead of 'rhvm'. This is just a documentation change. --- p2v/virt-p2v.pod | 10 +++++----- v2v/cmdline.ml | 2 +- v2v/virt-v2v.pod | 12 ++++++------ 3 files changed, 12 insertions(+), 12 deletions(-) diff --git a/p2v/virt-p2v.pod b/p2v/virt-p2v.pod index ea685be..4a5f587 100644 --- a/p2v/virt-p2v.pod +++

Hi, I am using opensuse as my dome and I tried to make a NIC card work in PCI passthrough. pciback is installed as a module in this kernel. I unbound all the NIC''s from dom0 driver and bound them to PCI back. I then modified the domU config file to include the pci device. When the system started booting up, I NICs were recognized however they failed to attach. This is the message I got,

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

We just got DELL R920 and installed Centos 6.5 on it.? After installation, network not function.? We manually enter IP address, gateway and netmark on "em1".? we also do following: 1. startup NetworkManager 2. /etc/sysconfig/network-scripts/ifcfg-em1? ==> NM_CONTROOLED=yes I tried to startup network and get error message: Bring up interface em1: connection activation failed