Re: [Openstack] nova calls libvirt but failed:Operation not supported

2013-04-02 Thread Liu Wenmao 
I solve this problem by blacklist bridge module..

I refer this post http://dev.opennebula.org/issues/1688, which means I can
only use brcompat in ubuntu 12.04.

but the default bridge module is the built-in bridge module, so I
blacklist it and restart openvswitch, it works.


On Tue, Apr 2, 2013 at 2:46 PM, Liu Wenmao marvel...@gmail.com wrote:

 hi Aaron:

 thanks anyway..

 it's really a weird problem


 On Tue, Apr 2, 2013 at 2:29 PM, Aaron Rosen aro...@nicira.com wrote:

 I've not encountered these errors. If you didn't drop the list perhaps
 someone else could help you


 On Mon, Apr 1, 2013 at 11:15 PM, Liu Wenmao marvel...@gmail.com wrote:

 After I uncomment user and group in the qemu.conf, the error remains the
 same.

 My linux release is Ubuntu 12.04LTS:

 root@node1:~# dpkg -l|grep libvirt
 ii  libvirt-bin  0.9.8-2ubuntu17.7
programs for the libvirt library
 ii  libvirt0 0.9.8-2ubuntu17.7
library for interfacing with different virtualization
 systems
 ii  python-libvirt   0.9.8-2ubuntu17.7
libvirt Python bindings

 root@node1:~# tail /var/log/libvirt/libvirtd.log
 2013-04-02 03:47:59.159+: 12796: info : libvirt version: 0.9.8
 2013-04-02 03:47:59.159+: 12796: error : virNetDevBridgeAddPort:309
 : Unable to add bridge br-int port tapcc380352-8b: Operation not supported
 2013-04-02 03:49:26.103+: 12793: error : virNetDevBridgeAddPort:309
 : Unable to add bridge br-int port tapd941ef5a-f1: Operation not supported
 2013-04-02 05:01:12.223+: 30917: info : libvirt version: 0.9.8
 2013-04-02 05:01:12.223+: 30917: error : virNetSocketReadWire:996 :
 End of file while reading data: Input/output error
 2013-04-02 05:01:38.735+: 30921: error : virNetDevBridgeAddPort:309
 : Unable to add bridge br-int port tap8317bc2f-53: Operation not supported
 2013-04-02 05:03:08.780+: 30917: error : virNetSocketReadWire:996 :
 End of file while reading data: Input/output error
 2013-04-02 06:07:12.279+: 18978: info : libvirt version: 0.9.8
 2013-04-02 06:07:12.279+: 18978: error : virNetSocketReadWire:996 :
 End of file while reading data: Input/output error
 2013-04-02 06:07:42.519+: 18980: error : virNetDevBridgeAddPort:309
 : Unable to add bridge br-int port tapfcbc59a4-96: Operation not supported



 On Tue, Apr 2, 2013 at 1:05 PM, Aaron Rosen aro...@nicira.com wrote:

 I believe that with older versions of libvirt you need to uncomment the
 following lines in /etc/libvirt/qemu.conf

 # The user ID for QEMU processes run by the system instance.
 user = root

 # The group ID for QEMU processes run by the system instance.
 group = root


 I'd also check what's in /var/log/libvirt/libvirtd.log





___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] nova calls libvirt but failed:Operation not supported

2013-04-01 Thread Aaron Rosen 
Do you have the following line (bolded) in /etc/libvirt/qemu.conf  ?

cgroup_device_acl = [
/dev/null, /dev/full, /dev/zero,
/dev/random, /dev/urandom,
/dev/ptmx, /dev/kvm, /dev/kqemu,
/dev/rtc, /dev/hpet*,/dev/net/tun,*
]



On Mon, Apr 1, 2013 at 8:42 PM, Liu Wenmao marvel...@gmail.com wrote:

 Hi all:

 I use github to install nova and quantum, but when I launch an instance,
 nova-compute fails:

 2013-04-02 11:00:15DEBUG [nova.openstack.common.lockutils] Released
 file lock iptables at /var/lock/nova/nova-iptables for method _apply...
 2013-04-02 11:00:17ERROR [nova.compute.manager] Instance failed to
 spawn
 Traceback (most recent call last):
   File
 /usr/local/lib/python2.7/dist-packages/nova-2013.2.a89.ge9912c6-py2.7.egg/nova/compute/manager.py,
 line 1069, in _spawn
 block_device_info)
   File
 /usr/local/lib/python2.7/dist-packages/nova-2013.2.a89.ge9912c6-py2.7.egg/nova/virt/libvirt/driver.py,
 line 1520, in spawn
 block_device_info)
   File
 /usr/local/lib/python2.7/dist-packages/nova-2013.2.a89.ge9912c6-py2.7.egg/nova/virt/libvirt/driver.py,
 line 2435, in _create_domain_and_network
 domain = self._create_domain(xml, instance=instance)
   File
 /usr/local/lib/python2.7/dist-packages/nova-2013.2.a89.ge9912c6-py2.7.egg/nova/virt/libvirt/driver.py,
 line 2396, in _create_domain
 domain.createWithFlags(launch_flags)
   File /usr/local/lib/python2.7/dist-packages/eventlet/tpool.py, line
 187, in doit
 result = proxy_call(self._autowrap, f, *args, **kwargs)
   File /usr/local/lib/python2.7/dist-packages/eventlet/tpool.py, line
 147, in proxy_call
 rv = execute(f,*args,**kwargs)
   File /usr/local/lib/python2.7/dist-packages/eventlet/tpool.py, line
 76, in tworker
 rv = meth(*args,**kwargs)
   File /usr/lib/python2.7/dist-packages/libvirt.py, line 581, in
 createWithFlags
 if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed',
 dom=self)
 libvirtError: Unable to add bridge br-int port tap89ed2dc0-2e: Operation
 not supported
 2013-04-02 11:00:17DEBUG [nova.openstack.common.lockutils] Got
 semaphore compute_resources for method abort...
 2013-04-02 11:00:17DEBUG [nova.compute.claims] Aborting claim: [Claim:
 512 MB memory, 0 GB disk, 1 VCPUS]

 Is it because user nova call libvirt to create a port so it has not enough
 permission?

 note1:I set up sudoer:
 root@node1:~# cat /etc/sudoers.d/nova_sudoers
 Defaults:nova !requiretty

 nova ALL = (root) NOPASSWD: /usr/local/bin/nova-rootwrap


 note2:I login as root, execute  ovs-vsctl add-port, and succeed.

 root@node1:~# ovs-vsctl add-port br-int  tap89ed2dc0-2e
 root@node1:~# ovs-vsctl show
 f3f4cdc0-1391-45fd-a535-1947d5aea488
 Bridge br0
 Port eth0
 Interface eth0
 Port br0
 Interface br0
 type: internal
 Bridge br-int
 Port br-int
 Interface br-int
 type: internal
 Port patch-tun
 Interface patch-tun
 type: patch
 options: {peer=patch-int}
 Port tap89ed2dc0-2e
 Interface tap89ed2dc0-2e
 Bridge br-tun
 Port patch-int
 Interface patch-int
 type: patch
 options: {peer=patch-tun}
 Port gre-1
 Interface gre-1
 type: gre
 options: {in_key=flow, out_key=flow,
 remote_ip=192.168.19.1}
 Port br-tun
 Interface br-tun
 type: internal
 ovs_version: 1.4.0+build0


 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] nova calls libvirt but failed:Operation not supported

2013-04-01 Thread Aaron Rosen 
I believe that with older versions of libvirt you need to uncomment the
following lines in /etc/libvirt/qemu.conf

# The user ID for QEMU processes run by the system instance.
user = root

# The group ID for QEMU processes run by the system instance.
group = root


I'd also check what's in /var/log/libvirt/libvirtd.log
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp