public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Rajiv Rajaian <rajiv.grid@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: Regarding NAT configuration with KVM
Date: Sun, 20 Jun 2010 11:22:37 +0300	[thread overview]
Message-ID: <4C1DCFCD.3000609@redhat.com> (raw)
In-Reply-To: <AANLkTikwb06n_a93MX5Y_sKr2wQ0NhPWrkOK5Hyl62Nw@mail.gmail.com>

On 06/18/2010 04:33 PM, Rajiv Rajaian wrote:
> [root@kvmcluster ~]# ping 144.68.100.1
> PING 144.68.100.1 (144.68.100.1) 56(84) bytes of data.
> 64 bytes from 144.68.100.1: icmp_seq=1 ttl=64 time=2.59 ms
>
>
> Heres the IP configuration Details:
>
> Host machine 10.2.0.20 (Kvmcluster)
> Virtual machine : 144.68.100.1 (kvmguest)
> Client Machine: 10.2.0.25 (xencluster)
>
> Routing table of the client machine (xencluster) looks like this
>
> [root@xencluster ~]# route -n
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> 10.2.0.0        0.0.0.0         255.255.255.0   U     0      0        0 eth0
> 192.168.122.0   0.0.0.0         255.255.255.0   U     0      0        0 virbr0
> 144.68.100.0    10.2.0.40       255.255.255.0   UG    0      0        0 eth0
> 169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth0
> 0.0.0.0         10.2.0.40       0.0.0.0         UG    0      0        0 eth0
>
> Please help me to solve this issue..
>    

Check your firewall rules?

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2010-06-20  8:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-15 11:40 Regarding NAT configuration with KVM Rajiv Rajaian
2010-06-15 12:07 ` Avi Kivity
2010-06-18 13:33   ` Rajiv Rajaian
2010-06-20  8:22     ` Avi Kivity [this message]
2010-06-21 14:17     ` Charles Duffy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C1DCFCD.3000609@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=rajiv.grid@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox