Dom0: 192.168.100.251DomU: 192.168.100.238
nova.conf http://pastebin.com/B0PVVWivifconfig (dom0 and domU): 
http://pastebin.com/iCLX91RSnova network table: http://pastebin.com/k5XcXHee
Please, explain me how to take others informations if you want, i think i have 
been taken all information.
Thank you.
From: john.garb...@citrix.com
To: alex_...@live.com; openstack@lists.launchpad.net
Date: Mon, 2 Apr 2012 16:05:15 +0100
Subject: RE: [Openstack] [OpenStack] Xen Hypervisor

Just double checking, but about the other machine you have put on the same 
network as your VMs, is the interface configured in the same subnet as the VMs? 
Also, Just to be clear, not sure anyone has ever tried the sort of setup you 
are wanting (Single interface, with no VLANs). I have seen many setups using a 
single interface and VLANs, and many setups using different physical 
interfaces, and some combinations of the two, but I haven’t seen anyone try 
collapsing everything onto a single physical interface. It might not work due 
to the way nova network in flatDHCP works (i.e. adds a DHCP server onto your 
network). Just checking, but you are using FlatDHCP networking, I presume? If 
you haven’t assigned a floating ip and you are using some kind of flat 
networking, the public network configuration should be largely unimportant. I 
think you want these settings:flat_networking_bridge=xenbr0flat_interface=eth0 
What is the state of your VM, does it seem to have the correct IP address from 
the nova network DHCP? I think you are close with your flags now, but I can’t 
be specific with the help without more information:·         a list of your 
flags in nova.conf·         networking info (ifconfig or otherwise) from both 
Dom0 and DomU (with compute running) and the VM·         networking config from 
XenServer (networks, DomU VIFs and VM VIFs)·         a copy (in text form) of 
the network related tables in your DB (or all the values from your “nova-manage 
network create” and related calls) More general advice is: To make sure all the 
new network settings get applied, I would recommend:·         stop all nova 
services·         reset your nova DBo   delete the old DBo   Create the DB, do 
DB migration again, etc.o   Add in your network again, (please tell us what 
values you use for that)·         start all nova services It might be worth 
adding a second VIF on the same network, calling that eth1 in the Nova domU and 
then using that as the flat_interface. Normally it is not recommended that you 
configure an IP address on the interface that nova-network uses for the guest 
networking. Not sure what you are trying will work. Thanks,John From: 
openstack-bounces+john.garbutt=eu.citrix....@lists.launchpad.net 
[mailto:openstack-bounces+john.garbutt=eu.citrix....@lists.launchpad.net] On 
Behalf Of Alexandre Leites
Sent: 02 April 2012 14:53
To: openstack@lists.launchpad.net
Subject: Re: [Openstack] [OpenStack] Xen Hypervisor I tried the last thing 
about changing public interface to eth0... but it still doesn't work. I still 
with erro of can't ping anything outside of VM (created by nova on xen).> From: 
todd.desh...@xen.org
> Date: Mon, 2 Apr 2012 09:15:52 -0400
> Subject: Re: [Openstack] [OpenStack] Xen Hypervisor
> To: alex_...@live.com
> CC: openstack@lists.launchpad.net
> 
> On Mon, Apr 2, 2012 at 8:49 AM, Alexandre Leites <alex_...@live.com> wrote:
> > Ok, anyway i tested it and didn't worked. Any other solution?
> >
> 
> You should be more specific.
> 
> You should explain the specific flags you tried and then post the
> relevant logs files.
> 
> Thanks,
> Todd
> 
> 
> -- 
> Todd Deshane
> http://www.linkedin.com/in/deshantm
> http://blog.xen.org/
> http://wiki.xen.org/                                    
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Reply via email to