[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-API] Private network and gre tunnel problem

  • To: Jan Škoda <lefty@xxxxxxxxxxxx>
  • From: Rob Hoes <Rob.Hoes@xxxxxxxxxx>
  • Date: Sun, 23 Jun 2013 09:31:09 +0000
  • Accept-language: en-GB, en-US
  • Cc: "xen-api@xxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxx>
  • Delivery-date: Sun, 23 Jun 2013 09:31:29 +0000
  • List-id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
  • Thread-index: AQHOb4BkM0aGIt9rT0iosE4CsCcfB5lC+QCA
  • Thread-topic: [Xen-API] Private network and gre tunnel problem

Hello Jan,

A "private network" is a network without any PIFs on it, and is restricted to a 
single host. You can create such a network by calling only 'xe network-create', 
as you would have done. Xapi raises the exception you saw, because it assumed 
that your two VMs are supposed to be on the same network, but there is no 
physical network connection between the two hosts (no PIFs on the network).

You can fix this by using the 'xe tunnel-create' command on both hosts to 
create a link between your private network and your PIFs. This tells xapi that 
there is a tunnel connection between the two hosts. Xapi does not create the 
actual GRE tunnel for you, so you still need to manually create actual GRE 
tunnel ports on the OVS, but it looks like you already know how to do that.

Hope this helps.


On 22 Jun 2013, at 20:36, Jan Škoda <lefty@xxxxxxxxxxxx> wrote:

> Hello,
> I have XCP pool with 2 hosts, 2 public IPs using openvswitch back-end.
> VMs are connected to private network using ovs bridge (xapi0) and I want
> to connect them with gre. However, I cannot start any vm on second XCP
> because of error:
>> You attempted to run a VM on a host which doesn't have a PIF on a Network 
>> needed by the VM. The VM has at least one VIF attached to the Network.
> Network params:
>> uuid ( RO)                    : 1fff1405-cb84-4db3-4d0e-e5c4cde6e21b
>>              name-label ( RW): Internal shared
>>        name-description ( RW): 
>>               VIF-uuids (SRO): ..many..
>>               PIF-uuids (SRO): 
>>                     MTU ( RW): 1500
>>                  bridge ( RO): xapi0
>>            other-config (MRW): automatic: true
>>                   blobs ( RO): 
>>                    tags (SRW): 
>>    default-locking-mode ( RW): unlocked
> xapi0 on first XCP gets created after first VM starts. I tried to create
> it on second server using ovs-vsctl, set up gre tunnel (which works) and
> then start a vm, but with no luck, xapi probably looks into some kind of
> database, but I don't know, why is it's content different on those 2
> servers.
> Do you know about any possibility do debug this behaviour?
> Thanks!
> Jan Škoda
> _______________________________________________
> Xen-api mailing list
> Xen-api@xxxxxxxxxxxxx
> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

Xen-api mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.