Regards _Sugesh
> -----Original Message----- > From: Vivek Gupta [mailto:vive...@hcl.com] > Sent: Friday, April 29, 2016 7:09 AM > To: Chandran, Sugesh <sugesh.chand...@intel.com>; > discuss@openvswitch.org > Subject: RE: [ovs-discuss] Unable to add bridge ovsbr0 port vnet0: Operation > not supported > > Hi > > thanks for your reply. I will proceed as suggested. > > But right now I am facing problem in VM creation. Due to "Unable to add > bridge ovsbr0 port vnet0: Operation not supported" error I moved to QEMU > 2.2.0 from QEMU 2.0.. [Sugesh] If you are adding the vhost-user port as I suggested in the earlier mail, you wont see this error. > > I did custom installation of QEMU2.2.0 in homedirectory/qemu2.2.0 and > made the softlink from earlier qemu-system-x86_64 as > > ln -s homedirectory/qemu2.2.0/softmmu/qemu-system-x86_64 qemu- > stsem-x86_64 > > and whenever I try to create a VM by virtinstall I get error message as > > "internal error: process exited while connecting to monitor: /usr/bin/kvm- > spice: 2: exec: qemu-system-x86_64: Permission denied" > I have made all in complain mode in apparmor but no success. > [Sugesh] This error has nothing to do with OVS. It looks to me that the issue is in the qemu configuration. > Please suggest. > > Thanks & Regards > Vivek > ________________________________________ > From: Chandran, Sugesh [sugesh.chand...@intel.com] > Sent: Thursday, April 28, 2016 10:16 PM > To: Vivek Gupta; discuss@openvswitch.org > Subject: RE: [ovs-discuss] Unable to add bridge ovsbr0 port vnet0: Operation > not supported > > Regards > _Sugesh > > > > -----Original Message----- > > From: discuss [mailto:discuss-boun...@openvswitch.org] On Behalf Of > > Vivek Gupta > > Sent: Thursday, April 28, 2016 8:12 AM > > To: discuss@openvswitch.org > > Subject: [ovs-discuss] Unable to add bridge ovsbr0 port vnet0: > > Operation not supported > > > > Hi > > > > I am trying to create a VM using OVS bridge but I am getting error as > > below- > > ------------------------------------- > > Starting install... > > ERROR Unable to add bridge ovsbr0 port vnet0: Operation not supported > > Domain installation does not appear to have been successful. > > If it was, you can restart your domain by running: > > virsh --connect qemu:///system start y otherwise, please restart > > your installation. > > -------------------------------------------- > > > > > > Created the bridge as below > > $OVS_DIR/utilities/ovs-vsctl -- > > db=unix:/usr/local/var/run/openvswitch/db.sock --no-wait add-br ovsbr0 > > -- set Bridge ovsbr0 datapath_type=netdev > > > > Bridge detail is as below- > > ovs-vsctl show > > 781cb2cb-f595-436c-b356-9df62ef2fcfa > > Bridge "ovsbr0" > > Port "dpdk0" > > Interface "dpdk0" > > type: dpdk > > Port "dpdk2" > > Interface "dpdk2" > > type: dpdk > > Port "ovsbr0" > > Interface "ovsbr0" > > type: internal > > > > As of now, I have not binded any port of host machine to OVS bridge > > interface. > > VM creation is as below- > > virt-install > > --connect qemu:///system -n VMImage -r 2048 -- > > file=/var/lib/libvirt/images/VMImage.img --file-size=16 -- > > cdrom=/cdrom/ubuntu-14.04.3-desktop-amd64.iso --vcpus=2 --network > > bridge=ovsbr0 --os-type=linux --os-variant=ubuntutrusty --cpu host -- > > prompt > > > > > > Please suggest how to solve it > > Do i need to do entry for OVS bridge into /etc/network/interface file > > (In Ubuntu Machine)? > > I am not able to understand what is vnet0 in error message. > > > [Sugesh] Use vhost-user interface to connect VM to the OVS. > Refer INSTALL.DPDK.md for more details about adding a vhost-user port. > start the VM using the created vhost-user port socket. > You asked the same question again in another mail, I feel this will answer > your questions. > > > > Thanks & Regards > > Vivek > > > > > > > > > > > > > > > > ::DISCLAIMER:: > > ---------------------------------------------------------------------- > > ------------------------ > > ------------------------------------------------------ > > > > The contents of this e-mail and any attachment(s) are confidential and > > intended for the named recipient(s) only. > > E-mail transmission is not guaranteed to be secure or error-free as > > information could be intercepted, corrupted, lost, destroyed, arrive > > late or incomplete, or may contain viruses in transmission. The e mail > > and its contents (with or without referred errors) shall therefore not > > attach any liability on the originator or HCL or its affiliates. > > Views or opinions, if any, presented in this email are solely those of > > the author and may not necessarily reflect the views or opinions of > > HCL or its affiliates. Any form of reproduction, dissemination, > > copying, disclosure, modification, distribution and / or publication > > of this message without the prior written consent of authorized > > representative of HCL is strictly prohibited. If you have received > > this email in error please delete it and notify the sender immediately. > > Before opening any email and/or attachments, please check them for > > viruses and other defects. > > > > ---------------------------------------------------------------------- > > ------------------------ > > ------------------------------------------------------ > > > > _______________________________________________ > > discuss mailing list > > discuss@openvswitch.org > > http://openvswitch.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
