similar to: Running Xen domU hangs until service xend is restarted

Hello, running xen 3.0.4_1 I find the following messages in /var/log/messages: kernel: peth0: received packet with own address as source address Is this something to worry about? The tcpdump shows the following pakets during that time: 14:58:05.546043 fe:ff:ff:ff:ff:ff (oui Unknown) > 09:00:2b:00:00:0f (oui Unknown), ethertype LAT (0x6004), length 81: 0x0000: 2808 0505 0502 131f

Hi, since I, just hours ago, followed http://wiki.centos.org/HowTos/JavaOnCentOS (Sun's JDK) I thought I'd confirm and update the "A less simple approach" with information that's a bit newer than jdk 1.4. Registered WIKI account: MikaelFridh Furthermore, I'd like to ask you if anyone know what was meant by the comment on the wiki: > *This HowTo is not complete

First run of puppet performs a configsync and an attempt to load the downloaded plugins, the provider fails to be found by puppet in this first run, another re-run of puppet is needed for the provider to work, see debug output below. Is this a bug or am I missing something you think? The error in short: err: /Stage[main]/Ibe::Slave/Logical_volume[mysql]: Could not evaluate: No ability to

Facter 2.0.0rc1 is a feature release candidate with bug fixes, features and other improvements. Facter 2.0 is designed to accompany the upcoming Puppet 3.0 release and has breaking changes from Facter 1.6.x. Facter 2.0 is not backwards compatible with Puppet 2.6 or 2.7. It includes contributions from the following people: Chris Price, Daniel Black, Daniel Pittman, Garrett Honeycutt, Gary Larizza,

Hi again. I'm pleased to say that my experimentation with ocfs2 has been very successful and I'm considering doing some real work with it. My current question is related to virt-manager and the use of kickstart to install paravirtualised domU's. I'm happily doing fully-virtualised installs with this tool but due to poor network performance I thought it time to do some

Respecting cloning vm guests, I see in /etc/ssh the following: ssh_host_dsa_key ssh_host_dsa_key.pub ssh_host_key ssh_host_key.pub ssh_host_rsa_key ssh_host_rsa_key.pub Is there a simple script somewhere to regenerate all the server host keys for the new guest after cloning? -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB at

Respecting cloning vm guests, I see in /etc/ssh the following: ssh_host_dsa_key ssh_host_dsa_key.pub ssh_host_key ssh_host_key.pub ssh_host_rsa_key ssh_host_rsa_key.pub Is there a simple script somewhere to regenerate all the server host keys for the new guest after cloning? -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB at

Hi.. I know this isn't a centos/rhel/fedora issue... but i'm hopeful that someone might have an answer!!! thanks VVVVVVVVVV Got a bit of an issue here, that I can't seem to resolve. I have a test domain on a dynamic service (dyndns.org). the test domain is foo.gotdns.com, which i have pointing to my external cable/dsl address. Here's my issue, I would really like to be able to

Hi all, The CentOS community is pretty limited in what we can do to the core distribution. Since our mantra is "aiming to be 100% compatible with Red Hat Enterprise Linux" we cannot fix bugs or improve the CentOS core without waiting for Red Hat to make those modifications first. We have limited leverage and a 6-month release cycle against us. But that is not the complete truth,

In an email yesterday evening, Perry Nguyen expressed concern about the moving of the ''restarted'' file from /var/lib/shorewall to $STATEDIR (STATEDIR is set in your shorewall.conf file and defaults to /var/state/shorewall). I''m afraid I was a bit short with Perry for which I apologize. Here''s the story: 1. What is the ''restarted'' file

Hi, I got a problem with PRI that I'm not sure how to solve. Asterisk sits between PABX and PRI. PRI is span 1 and PABX is span 2. After every single call (no matter in what direction) I get "pri_fixup_principle: Call specified, but not found?" and "pri_dchannel: Hangup on bad channel" messages and the channel in question is restarted. As far as I can see, all

Hello everyone, LLVM buildmaster will be updated and restarted after 7 PM Pacific time. Thanks Galina -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170921/cb7017e7/attachment.html>

Hello everyone, LLVM buildmaster will be updated and restarted after 6PM Pacific time today. Thanks Galina -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180404/d611ddf1/attachment.html>

Hello everyone, LLVM buildmaster will be restarted after 6PM Pacific time today. Thanks Galina -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180409/7b28c2e0/attachment.html>

Hello everyone, LLVM buildmaster will be updated and restarted after 6 PM Pacific time today. Thanks Galina -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180202/7d56a5ea/attachment.html>

Hello everyone, LLVM buildmaster will be updated and restarted after 8PM Pacific time today. Thanks Galina -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180212/38e63bf8/attachment.html>

Hello everyone, LLVM buildmaster will be updated and restarted after 6PM Pacific time today. Thanks Galina -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180223/4661d153/attachment.html>

Hello everyone, LLVM buildmaster will be updated and restarted after 6 PM Pacific time today. Thanks Galina -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180110/20130ff4/attachment.html>

Good Morning, We will be restarting Green Dragon at 10:00PST today in order to apply security updates. Thank you for your patience and cooperation. Hope you all have a nice day. Respectfully, Mike Edwards -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180128/91e2630f/attachment.html>

Hello everyone, LLVM buildmaster will be updated and restarted after 6 PM Pacific time today. Thanks Galina -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180129/555e74a9/attachment.html>