WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

RE: [Xen-users] Virtual machine not found by network

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] Virtual machine not found by network
From: "Lippert, Kenneth B." <Kenneth.Lippert@xxxxxxxxx>
Date: Thu, 27 May 2010 13:16:49 -0400
Delivery-date: Thu, 27 May 2010 10:18:00 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <814F64744F74804890E12C0C48221C9D08D2619D@xxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <814F64744F74804890E12C0C48221C9D08D26089@xxxxxxxxxxxxxxxxxxxxxxxxxx><20100527145116.GS7148@xxxxxxxxxxxxxx><814F64744F74804890E12C0C48221C9D08D26154@xxxxxxxxxxxxxxxxxxxxxxxxxx> <814F64744F74804890E12C0C48221C9D08D2619D@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acr9rC7cAHb9sH0sT5e9Htc2cUWZbgAAdxywAAGXobAAAvC6gA==
Thread-topic: [Xen-users] Virtual machine not found by network
Crap.

Disabling AppArmor didn't help, still broken.  Put external machine's
crontab ping to every minute.  We'll see what happens now.

Sorry for the many messages.  

-k

-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Lippert,
Kenneth B.
Sent: Thursday, May 27, 2010 11:53 AM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] Virtual machine not found by network

Another update.....

Novell's AppArmor WAS enabled on the domU.   I disabled it, stopped all
the pinging cron jobs, and have not had a failure since.  

Could that have been the problem?

Thanks,
-k

-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Lippert,
Kenneth B.
Sent: Thursday, May 27, 2010 11:13 AM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] Virtual machine not found by network

Rainer,

Thank you for your reply.

No, no firewall running on the domU.

No other machine with same IP (although there USED to be, we did some IP
switching when this domU went to production mode several days ago).  The
domU's old IP is now the dom0's (and vice versa).  We did this so that
outside clients that attached to 123.456.8.2 wouldn't have to change
anything in their /etc/hosts, etc.).

Update on my original email.  The pinging from the domU to the outside
didn't actually help.  What DOES help is another machine on the same
LOCAL net pinging the domU every 5 minutes.  I have not had a failure
since that started.

Are there XEN bridge settings that define how to respond to
"arp-who-has" requests?  Certainly sounds like that is the problem.

-k


-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Rainer
Sokoll
Sent: Thursday, May 27, 2010 10:51 AM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Virtual machine not found by network

On Thu, May 27, 2010 at 09:48:06AM -0400, Lippert, Kenneth B. wrote:

> The gateway is defined in both to be 123.456.8.254.
> 
> My virtual machine builds fine, and all seems well, but if the domU is
> inactive for a period of several minutes, with no network traffic, it
> seems the gateway forgets how to get to it.   This is manifested by
> other machines on the local 123.456.8.* network being able to ping and
> get to the domU, but machines OUTSIDE the local net cannot.  It is not
a
> DNS problem , pings from 123.456.22.1 (for instance) fail even if the
IP
> of the domU is specified (not just its name).

Sounds like the gateway 123.456.8.254 forgot the mac address of your
domU.
Do you have some weired firewall running on your domU blocking
arp-who-has?
Another machine with the same IP in the same broadcast domain?

Rainer

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>