Hi Anthony,
> Ok, let's debug that further. Once the VM have booted, can you check the
> state of the network interface by running the following command?
>
> ip link
> brctl show
The output is below:
root@hp3:~# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: p3p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system
state UP mode DEFAULT group default qlen 1000
link/ether e4:11:5b:9b:51:30 brd ff:ff:ff:ff:ff:ff
3: p3p2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000
link/ether e4:11:5b:9b:51:31 brd ff:ff:ff:ff:ff:ff
4: em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000
link/ether ac:16:2d:b3:be:10 brd ff:ff:ff:ff:ff:ff
5: em2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000
link/ether ac:16:2d:b3:be:14 brd ff:ff:ff:ff:ff:ff
6: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode
DEFAULT group default
link/ether 62:58:aa:78:c1:03 brd ff:ff:ff:ff:ff:ff
7: br-eth1: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN mode
DEFAULT group default
link/ether 12:44:5f:df:92:44 brd ff:ff:ff:ff:ff:ff
8: br-ex: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN mode
DEFAULT group default
link/ether e4:11:5b:9b:51:30 brd ff:ff:ff:ff:ff:ff
10: br-int: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN mode
DEFAULT group default
link/ether aa:b3:cb:98:c9:47 brd ff:ff:ff:ff:ff:ff
13: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state
DOWN mode DEFAULT group default
link/ether ea:29:40:f2:dd:92 brd ff:ff:ff:ff:ff:ff
21: qbr66ad9f38-2c: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UP mode DEFAULT group default
link/ether 1e:ac:e8:c2:67:62 brd ff:ff:ff:ff:ff:ff
22: qvo66ad9f38-2c: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc
pfifo_fast master ovs-system state UP mode DEFAULT group default qlen 1000
link/ether 4a:25:02:4c:67:f6 brd ff:ff:ff:ff:ff:ff
23: qvb66ad9f38-2c: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc
pfifo_fast master qbr66ad9f38-2c state UP mode DEFAULT group default qlen 1000
link/ether 1e:ac:e8:c2:67:62 brd ff:ff:ff:ff:ff:ff
24: vif2.0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UP mode DEFAULT group default qlen 32
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
root@hp3:~# brctl show
bridge name bridge id STP enabled interfaces
qbr66ad9f38-2c 8000.1eace8c26762 no qvb66ad9f38-2c
virbr0 8000.000000000000 yes
> But you can access the console through other mean, via libvirt.
Thank you for this, I was able to connect to the console. There I can see that
the VM has ethic, but it does not have an IP.
> Yes, all in one. I've enable those neutron services via devstack:
> q-agt q-dhcp q-lbaas q-meta q-metering q-svc q-vpn q-l3 q-fwaas
Okay thanks for verifying. I should note that in this system, I
deployed openstack module by module instead of devstack, as per:
http://docs.openstack.org/juno/install-guide/install/apt/content/
Thanks,
Geoffrey
----- Original Message -----
> From: "Anthony PERARD" <anthony.per...@citrix.com>
> To: "Geoffrey Tran" <gt...@isi.edu>
> Cc: openstack@lists.openstack.org
> Sent: Thursday, July 23, 2015 12:40:59 AM
> Subject: Re: [Openstack] Spawning Issue with Juno, Neutron, Xen and Libvirt
>
> On Wed, Jul 22, 2015 at 06:21:31PM -0400, Geoffrey Tran wrote:
> > Hi Anthony,
> >
> > Thank you for your help.
> >
> > > I don't know much of what Neutron is doing with the network interface but
> > > we can maybe try to work arround this issue.
> > > Could you add "exit 0" at the begin of the /etc/xen/scripts/vif-bridge
> > > script? Then check if you've got network access to the guest.
> >
> > I tried as you suggested. Now, the VM does boot, but unfortunately there
> > is no network access (I cannot ping the associated floating IP).
>
> Ok, let's debug that further. Once the VM have booted, can you check the
> state of the network interface by running the following command?
>
> ip link
> brctl show
>
> > Furthermore, I am unable to view the console through horizon.
>
> That expected, unfortunatly, there are bugs which are been fixed in later
> version of libvirt, from libvirt 1.2.15.
> What we are using for the Xen Project CI loop can be found at this address:
> http://wiki.xenproject.org/wiki/OpenStack_CI_Loop_for_Xen-Libvirt#Baseline
>
> But you can access the console through other mean, via libvirt.
>
> Start virsh, find the running instance and connect to it:
> (There are two prompts, shell prompt and virsh prompt)
>
> sh$ virsh -c xen:
> virsh# list
> Id Name State
> ----------------------------------------------------
> 193 instance-0000008e running
> virsh# console instance-0000008e
> // here will be the console of the VM
> // to quit, ctr+]
>
>
> > Do you have any other ideas? That is interesting that the master doesn't
> > have the issue. Just to verify, are you running this all on one node?
>
> Yes, all in one. I've enable those neutron services via devstack:
> q-agt q-dhcp q-lbaas q-meta q-metering q-svc q-vpn q-l3 q-fwaas
>
> --
> Anthony PERARD
>
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
