similar to: Traditional network interface naming scheme vs. persistent naming

Hi, I have a LAN server running CentOS 5.11 with two NICs eth0 and eth1. I'd like to swap the interface names, but I don't know how to go about that under CentOS. Here's what I would do on a Slackware server (I have one next to me in my office). Open /etc/udev/rules.d/70-persistent-net.rules and edit it: # PCI device 0x8086:/sys/devices/pci0000:00/0000:00:04.0/0000:03:00.0 (e1000e)

Le 04/02/2015 18:48, m.roth at 5-cent.us a ?crit : > That directory, and that file, exist in CentOS, also, since 6. And the new > naming... it's*so* much easier to deal with... yeah, right, I'll run the > install, and wait till it hangs, so I can see that the NIC is named, what > was it, on that HP last month, oh, yeah, I need to use ip -f inet link, > far simpler than

Control: tag -1 +moreinfo On Tue, 2014-05-13 at 08:55 -0700, Mike Egglestone wrote: > After booting into kernel 3.13 dom0, the keyboard no longer works. > All other aspects work, ssh is needed to login to the system to > start working with the domU's. > They keyboard works at the grub menu just fine, and > works normal when booting into the non xen kernel. I think at a minimum

Hallo, I need the device eth0 for one tool using centos 7.6. Using this tutorial https://www.certdepot.net/rhel7-restore-old-network-interface-name/ doesn t work. Thanks for a hint. Ralf

Nicolas Kovacs wrote: > Hi, > > I have a LAN server running CentOS 5.11 with two NICs eth0 and eth1. I'd > like to swap the interface names, but I don't know how to go about that > under CentOS. > > Here's what I would do on a Slackware server (I have one next to me in > my office). > > Open /etc/udev/rules.d/70-persistent-net.rules and edit it: > >

Hey all I''m new to Linux and Virtualizing. I''m trying to dedicate my nic''s to each virtual server. For instance, virt server A would use nic1 and virt server B would use nic2 and so on. I''ve been reading some stuff for this list and to tell you the truth I''m a bit overwhelmed. We are going to run SLES10.1 and Xen. I would appreciate any assistance.

> Hello everyone. I try to connect four PowerMust 2000 ups's via usb to one > computer using megatec_usb driver. But megatec_usb completly ignores port > directive in ups.conf, I even try port = /dev/null and megatec_usb founds > ups and it works. The 'port' is not used for USB connected devices, it's only needed for compatibility reasons. > Problem is that

Hi, I have just installed Slackware64 13.0 Linux as a HVM guest with Xen 3.5-unstable changeset 20143 pv-ops dom0 kernel 2.6.31.4. For more details, please refer to the following link: http://enmingteo.wordpress.com/2009/11/01/picture-tutorial-how-to-setup-slackware64-13-0-hvm-domu-with-xen-3-5-unstable-pv-ops-dom0-kernel-2-6-31-4-in-fedora-11-x86-64-dom0/ There are 83 screenshots so far at

Hi, I have just installed Slackware64 13.0 Linux as a HVM guest with Xen 3.5-unstable changeset 20143 pv-ops dom0 kernel 2.6.31.4. For more details, please refer to the following link: http://enmingteo.wordpress.com/2009/11/01/picture-tutorial-how-to-setup-slackware64-13-0-hvm-domu-with-xen-3-5-unstable-pv-ops-dom0-kernel-2-6-31-4-in-fedora-11-x86-64-dom0/ There are 83 screenshots so far at

https://bugs.freedesktop.org/show_bug.cgi?id=103351 Bug ID: 103351 Summary: Nouveau fails when booting with a screen connected to displayport since 13a86519202c5d119d83640d6f781f3181205d2c Product: Mesa Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW

Hi! As dom0 I''m running Ubuntu Hardy withe xen 3.3 from backports. Reason to using xen 3.3 is that I could get Intrepid stock kernel to work as domu with xen 3.2. Now the problem I have is that I can''t passthrough PCI-devices to my domu. If I run lspci in the domu nothing is returned. I''ve tried to use the kernel from Hardy (2.6.24-21-xen) and stock kernel from

Hey all, Just downloaded the new Xen 4.0 and ran Make xen Make tools Make stubdom Copied the new files from dist/install Im already running pv_ops 2.6.31.6 kernel. When I boot i get (XEN) Panic on CPU 0: (XEN) IO-APIC + timer doesn''t work! I have tried booting with noapic boot option but makes no difference. The system worked fine on 3.4.2 CPU is AMD.

Hi, I am having problems with the nouveau driver from Debian. Can I get help here? Cheers

On Tue, Apr 11, 2017 at 08:09:01AM -0400, Pete Orrall wrote: > > And *why* random NIC names? Quick, you've got servers from 5 > > manufacturers, of different ages... what's the NIC going to be called? Do > > names like enp5s0 offer any convenience to *anyone* not a hardware > > engineer? > > As someone else had stated, it's not related to SystemD but >

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

https://bugs.freedesktop.org/show_bug.cgi?id=76818 Priority: medium Bug ID: 76818 Assignee: nouveau at lists.freedesktop.org Summary: Xorg EQ overflowing lock up QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: All Reporter: max.snow at 4mation.com.au

Hi, I encountered a problem when creating a VLAN interface according to the Red_Hat_Enterprise_Linux-7-Networking_Guide. I configuered the parent interface ifcfg-eno1 as follows: DEVICE=eno1 TYPE=Ethernet BOOTPROTO=none ONBOOT=yes And I created a new file named ifcfg-eno1.5, the content is: DEVICE=eno1.5 BOOTPROTO=none ONBOOT=yes IPADDR=192.168.81.3 PREFIX=24

Hello List, I'm trying to get libvirt to work on slackware64-current (slackware64-14.2 beta) and while it compiles just fine, it refuses to run because of an undefined symbol: 2016-03-01 20:09:26.822+0000: 27849: error : virDriverLoadModule:73 : failed to load module /usr/lib64/libvirt/connection-driver/libvirt_driver_storage.so /usr/lib64/../lib64/libfl.so.2: undefined symbol: yylex

On 13 February 2017 at 16:17, peter.winterflood <peter.winterflood at ossi.co.uk> wrote: > > > > there's a really good solution to this. > > yum remove NetworkManager* > > chkconfig network on > > service network start > > and yes thats all under fedora 25, and centos 7. > > works like a charm. > > sometimes removing NM leaves resolv.conf

centos 5 had modprobe.conf entries for eth0 and if present eth1. something like: alias eth0 forcedeth alias eth1 e1000e For the new centos 6 (I have the rhel 6 client installed on my laptop) the modprobe.conf file is gone. Which is fine. I understand files can be created in /etc/modprobe.d and server the same purpose. My question is I dont see (doing a grep) any eth0 alias's in the files in