Regarding NAT configuration with KVM

Regarding NAT configuration with KVM

[Rajiv Rajaian]

Hi all,,
I have installed KVM by enabling KVM during Fedora core 8 OS installation.
I can able to create guest OS with qemu-system-x86_64.
Also I have configured guest OS with different subnet and I can reach
the guest OS from the host machine which is having different subnet
Now the problem is the guest OS is not reachable to the other hosts in
the network which are in the same subnet as that of the host machine
Is there any thing else to be configured to reach the VM. Please help
me to solve this issu

Re: Regarding NAT configuration with KVM

[Avi Kivity]

On 06/15/2010 02:40 PM, Rajiv Rajaian wrote:
> Hi all,,
> I have installed KVM by enabling KVM during Fedora core 8 OS installation.
> I can able to create guest OS with qemu-system-x86_64.
> Also I have configured guest OS with different subnet and I can reach
> the guest OS from the host machine which is having different subnet
> Now the problem is the guest OS is not reachable to the other hosts in
> the network which are in the same subnet as that of the host machine
> Is there any thing else to be configured to reach the VM. Please help
> me to solve this issu
>    

Fedora 8 is unsupported.  Try something newer, like Fedora 13.

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

Re: Regarding NAT configuration with KVM

[Rajiv Rajaian]

Hi Kivity..,
I have installed  Fedora 13  and enabled KVM. Still I can't reach the
virtual machine from the client machine with different subnet address
address.. But I can reach the virtual machine(kvmguest) from the host
machine (kvmcluster) in which the VM resides.

[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..



On Tue, Jun 15, 2010 at 5:37 PM, Avi Kivity <avi@redhat.com> wrote:
> On 06/15/2010 02:40 PM, Rajiv Rajaian wrote:
>>
>> Hi all,,
>> I have installed KVM by enabling KVM during Fedora core 8 OS installation.
>> I can able to create guest OS with qemu-system-x86_64.
>> Also I have configured guest OS with different subnet and I can reach
>> the guest OS from the host machine which is having different subnet
>> Now the problem is the guest OS is not reachable to the other hosts in
>> the network which are in the same subnet as that of the host machine
>> Is there any thing else to be configured to reach the VM. Please help
>> me to solve this issu
>>
>
> Fedora 8 is unsupported.  Try something newer, like Fedora 13.
>
> --
> error compiling committee.c: too many arguments to function
>
>

Re: Regarding NAT configuration with KVM

[Avi Kivity]

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

Re: Regarding NAT configuration with KVM

[Charles Duffy]

This is the libvirt default network configuration. Please see the 
libvirt documentation and mailing list for support.

As an aside -- you'll probably want to use a bridged configuration 
rather than the NATted one. If you really do want to stick with the NAT 
configuration, you'll need to make sure the routing tables on the other 
hosts guide packets destined for 192.168.122.0/24 back to the VM host.