similar to: dom0 bootup -- Device eth0 has differet mac address than expected

>> I think he''s having problems with Dom0 changing >> Mac address, rather than the domU (is that right?) Yes, you are correct. It''s dom0 that seems to be getting a random MAC and because of that Xen can''t t find the NIC and won''t load eth0 because the MAC is different than what is expected. I''ve seen others with the same problem and their

Hi, I''m a newbie to Xen and I need some help. I saw user ''datto'' had a similar problem but changed to FC4 to resolve it. I''m currently running FC3 and Xen2.0.7. I did the usual ''make install'' and I can boot into Xen dom0. However, my network card is not working. The driver is found in the linux-2.6.11.12-xen0 tree but not selected. I

Hi Everyone: I installed CentOS 4.4 on a new Dell 2950 using the server cd. No errors during the installation and no errors on bootup when loading the Eth0 or Eth1 interfaces. I currently have iptables stopped and selinux disabled. The interfaces have been given a static ip (192.168.1.x). the subnet is 255.255.255.0 and the gateway is 192.168.1.1. I can not ping any device on my network

I have 5 VMs on my host. The first four are setup to start on boot. But only the first three end up running. The fourth has to be started manually. "Start virtual machine on host bootup" is checked on all four VMs but the fourth VM does not get started on host bootup. After the host boots up, the VM is "Shutdown" state. If I go into "virt-manager" and click

I''ve been using Puppet now for a month or so and I''ve come to a problem that may warrant an additional Puppet metaparameter. I''m advocating the addition of a metaparameter called "preaction" (or something like that), which will perform some arbitrary action before the resource is modified. There may be a way to do this within Puppet already (with some

I am running RH6.1 on an x86 with 2.0.6 installed with an RPM. I am confused as to getting smb to start at bootup. It works fine if I start it manually (/etc/rc.d/init.d/smb start). I swear, the 5.2 installation had smb start at bootup, but I can't find the difference between the two. Is the answer 1 - edit the /etc/inetd.conf file (swat needed a line uncommented) 2 - edit the

Hi, got a very severe problem. I have two hard drives in my RS server and I am getting the secondary drive removed. Here's the problem. After the secondary drive is removed, the server fails to bootup completely, crashing at fsck. The server boots up fine when the secondary drive is put back in however. Has anyone ever encountered this problem before? Could the problem be to references to

This is an x86_64 system that I just updated from 4.2 to 4.3 (including the csgfs stuff). When I watch the bootup on the console, I see an error: lvm.static: symbol lookup error: /usr/lib64/liblvm2clusterlock.so: undefined symbol: lvm_snprintf This error comes immediately after the "Activating VGs" line, so it appears to be triggered by the vgchange command in the clvmd startup

I am running SUSE 12.0 I have had this problem on another machine months ago, but never solved it. I have done many searches, but have come up empty. When booted, port 139 is not open on IPv4. There os no 0.0.0.0:139listening. HOWEVER: :::139 is listening. SO I know it is open on IPv6. When I try to gain remote access through a share, the machine is not found. When I try to telnet to port

I have an x86_64 box. I have a program I need to compile with the 32 bit compiler and linker. Are there directions explaining how to do that somplace? Or can someone provide details. THanks, Jerry -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20051230/224e5a7d/attachment-0001.html>

Dear Xen Community, today we tried to upgrade our base server from a Xeon E5430 to a Xeon X5570 (Nehalem). This worked fine so far, but our DomUs with Kernel 2.6.27 no longer boot - they start up until the following message appears: [..] Mount-cache hash table entries: 256 Initializing cgroup subsys ns Initializing cgroup subsys cpuacct Initializing cgroup subsys memory Initializing cgroup

Hi all, I have an odd problem, for which I couldn't find any suggestions on google. A CentOS 5.7x64 gives me a blank screen on bootup, both to the 17" LCD monitor connected to the VGA port, and to the KVMOVIP device built-into the server, I can see the GRUB boot loader, and everything booting up, upto the point where it says "Waiting for driver initialization.", then it goes

I have nic bonding (mode=802.3ad) setup on 2 servers, both running Centos 5.5 In the "Active Aggregator Info", on one reports 4 ports - which is correct - but the other only reports 3 ports. It''s always eth0 that shows a different aggregator ID. Changing the cables around so it hits a different port on the switch makes no difference. The switch is correctly configured for the

Hi, I was wondering if anyone had a good dhcpd.conf and /tftpboot files for a EPIA-M motherboard with RedHat 9.0.... Or maybe just a configuration that works with the EPIA-M (doesn't matter which type of linux). I'm trying to boot the system from the network and it seems to be getting to downloading pxelinux.0 but then nothing happens after that.... I'm using ISC dhcpd V3.0pl2,

Hello, I created a CentOS 5.0 x86_64 guest under Debian Etch with Xen 3.0.3 and it boots fine except for one re-occuring problem - whenever it boots the /etc/sysconfig/network-scripts/ifcfg-eth0 script gets renamed to .bak and doesn''t configure the ethernet device. Here is the content of this file: TYPE=Ethernet DEVICE=eth0 BOOTPROTO=static ONBOOT=yes IPADDR=192.168.0.247

Hi there! Im using a dovecot system in combination with postfix(with dovecot lda) and ldap. Till today it ran well, but before switching to live, i did some system updates and at the reboot following message occured: Starting IMAP/POP3 mail server: dovecoUnexpected first line <localhost: timed out, nothing received> (First it says: "Starting IMAP/POP3 mail server: dovecot ",

Hi, I've done my fair share of CentOS 7 installations, but this is the first time I have this kind of weird problem. Here goes. In my office I have a battered Dell Optiplex 320 PC with two NICs that I'm using as a bare metal sandbox server for testing purposes. The CentOS 7 installer sees the connected network card as eth0. But after the first reboot, the interface comes up as eth1.

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 am new to CentOS (coming from Fedora) and I really like it! I am having difficulty getting one of my machines to boot and assign the same designation of eth0 and eth1 to the same nics consistantly. I have an MSI motherboard with 2 nics on the board. Strangely enough both nics report the same MAC address. This is not an issue since I use the computer to route between two different subnets so

All, I've got a machine running CentOS 5.3 and this machine has got 2 - built-in 1 Gig NICs and a expansion card with 4 - 100 Meg NICs. For whatever reason at install time, it made the expansion card eth0 through eth3 and the internal ports eth4 and eth5. And by default the 'machine' is known on the network by the eth0 NIC, so my throughput is limited to 100 Mb. How can I force