similar to: Strange XEN on CentOS HWaddr Address Issue

I've been noticing yum updates on several servers I manage over the last few weeks, which I know I didn't perform and could not explain until this morning. At first I suspect a break-in, but found no other evidence or reason an intruder would run the yum updates I was viewing. Yum updates are logged in /var/log/yum.log, which is what Logwatch scans. Seems that the format of the log

All, For a production environment, I'd like to setup CentOS XEN guests as lightweight as possible. I'd like the XEN guests to be able to send nightly email as all CentOS servers do, but there is no reason to run a mail server as the CentOS Dom0 already has an email server running that can act as an email smart host. The options that seem most appealing to me are either ssmtp or sendmail

Hi, I have been working with tinc network where one host will provide the IP addresses over DHCP to each connected node. Tinc runs in switch mode. It seems that the HWaddr of the tinc interface is regenerated every time when tinc is (re)started. As a result, DHCP server will assign a new IP for the host. Is there any configuration variable we could use to avoid HWaddr changing? Currently, I

Hi All, All of my systems are running 5.4 x64. The are all AMD x64 processors with at least 2gb of RAM in each. I am running SSH on a non standard port. When I SSH into ANY of my systems, I get prompted for my password right away, but after entering, it takes 30+ seconds to get logged in and get a prompt so I can work. I dont quite know what to look for here Does anyone have thoughts? -Jason

I am using Centos 5.2 as both my XEN host and guests. Both the XEN host and each XEN guest are up-to-date with the latest CentOS 5.2 updates. I've noticed over time that sometimes using init 6 (or init 0) in the guest works flawlessly and other times the guest will reach "Restarting System"/"System Halted" and hang. When this hang occurs the only way to finish the

I performed a test install of CentOS Beta 5 on a system with two ~60 GB drives. When installing CentOS 4 on this system, I normally work thru setting up Software RAID with identically sized partitions on each drive. For my test, the CentOS installer only presented a single drive. I took the default of letting it do what it wanted. After looking over the system I have verified that /boot is

Just prior to the time change, I made sure that ntpd and my timezone files were properly setup. Since this time, I've noticed the following errors: audit(1173310084.404:5): avc: denied { read } for pid=8634 comm="ntpd" name="unexpected.tdb" dev=md1 ino=147662 scontext=root:system_r:ntpd_t tcontext=root:object_r:samba_var_t tclass=file I've not successfully (so

Do people have wet underwear for nothing over XEN? See http://www.redhat.com/promo/qumranet/ <snip> Q: Will Red Hat continue to support and contribute to Xen? A: Yes. Red Hat will support Xen until at least 2014 (seven years after the release of Red Hat Enterprise Linux 5). We are committed to insulating our customers from changes in the infrastructure components and this is why we

Do people have wet underwear for nothing over XEN? See http://www.redhat.com/promo/qumranet/ <snip> Q: Will Red Hat continue to support and contribute to Xen? A: Yes. Red Hat will support Xen until at least 2014 (seven years after the release of Red Hat Enterprise Linux 5). We are committed to insulating our customers from changes in the infrastructure components and this is why we

All, I have a fresh CentOS 5.2 server that I am just starting to customize, it is very close to stock. This morning I ran yum update: ============================================================================= Installing: kernel-xen i686 2.6.18-92.1.6.el5 updates 15 M Updating: samba i386 3.0.28-1.el5_2.1 updates 16 M

Before starting xend (xen 3.0) these are my correct network interfaces: eth0 Link encap:Ethernet HWaddr 00:14:5E:0A:53:04 inet addr:192.168.1.51 Bcast:192.168.1.255 Mask:255.255.255.0 eth1 Link encap:Ethernet HWaddr 00:14:5E:0A:53:05 inet addr:192.168.1.52 Bcast:192.168.1.255 Mask:255.255.255.0 lo Link encap:Local Loopback inet

Hi all, I have a very strange situation, which I can''t explain. On a Core 2Quad server with 8GB RAM, we have 10 xen domU''s, as follows: vps.animalsaregreat.info login: root@zaxen01:[~]$ xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 512 4 r----- 232.2 actionco.vm

Greetings! I finally got the install done for a couple of gust OSs (Win 2003 server & Suse Enterprise 10) Bothe gusts are up and running, but - no networking. My setup: Hardware - AMD Athlon 4200+, ABIT Motherboard, 4 GB of DDR2 RAM, 2 onboard GB NICs Host OS- Suse Linux Enterprise server 10 Xen - 3.0.2_09749-0.4 Config file for Win 2003 server guest: # -*- mode: python; -*-

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Is there a way to prevent hwaddr/mac address spoofing between DomU''s? So in a way ''binding'' a mac-address on boot time with a virtual interface? (with something like ebtables/arptables/etc?) Stefan -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla -

Dear, I''ve attempted to upgrade a Xen box from 3.1.2 to 3.2.1. Unfortunately it has been a partial success only. At this point I''m really stuck with a network problem that affects my HVM machines (Linux PV run fine). The really odd thing is that everything seems to work properly, except that the "vif" network interfaces in dom0 seem to have only dropped TX packets for

Hi, I tried this post on the Xen list first with no answer. I have 4 machines and 3 of which (all different) have no network access when booted into Xen. I tried using Fedora Core 8 and it produced the same results. Is it normal for the virbr0 interface to take an arbitrary IP? How does it decide what to use? An ifconfig when booted into Xen shows the following: eth0 Link encap:Ethernet

Hi! I have a problem with my new Xen setup. I have installed Debian etch with netinstall and I''m using 2.6.18-6-xen-amd64 kernel in my dom0 and 3.0.3-0-4 version xen hypervisor. I''m using four network cards on my system and using three of them as xen bridges and dom0 is using the fourth one only for it''s own. So basicly both of my virtual servers use a network card

Hello. I need your help, DomU xen network diconnects randomly, how do you monitoring this? When I connect to vnc server in the hosts, DomU is running, then I open the DomU, after that guest network responds. DomU Debian 6.03 over Centos 5.7 and Xen 3.03. My network configuration: eth0 Link encap:Ethernet HWaddr 68:B5:99:78:AA:6D inet addr:192.168.5.230 Bcast:192.168.5.255

Hi, I''ve set up identical (what I think) machines using SLES 10 x86_64, but a new one of those is saying frequently in /var/log/messages: kernel: bond0: received packet with own address as source address A short summary of ifconfig looks like this: bond0 Link encap:Ethernet HWaddr 00:14:4F:2A:12:9C inet addr:132.199.176.78 Bcast:132.199.255.255 Mask:255.255.0.0 eth0

Well where do I start...I have a domU (ubuntu) booting and appears well but I don''t have an eth0 listed at all, dom) looks good. DomU: eth0 Link encap:Ethernet HWaddr 00:06:5B:15:C5:0B inet addr:10.99.99.5 Bcast:10.99.99.7 Mask:255.255.255.248 inet6 addr: fe80::206:5bff:fe15:c50b/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1