[ovirt-devel] Service vdsmd can't get start again and The bridge name in virsh and ovs are not the same after click 'Sync All Networks' on the vdsm
Michael Burman
mburman at redhat.com
Tue Aug 2 09:39:39 UTC 2016
Hi Mark,
Just to be clear about it, we currently not supporting ovs on 4.0.2.
This is still not working as you saw and the upgrade cluster isn't really
working.
We still reporting linux bridge as well as the ovs..
Dan, correct me if i'm wrong..
On Tue, Aug 2, 2016 at 12:33 PM, lifuqiong <lifuqiong at cncloudsec.com> wrote:
> Hi Michael,
>
> As described above, I create a ovs-based cluster, and added a
> Host, and created a VM successfully.
>
>
>
> I click the ‘Sync All Networks’ Tab, and “ovs-vsctl show” can get
> some seems correct result as follows: (The port ‘p3p1’ is my physical
> NIC, my vdsm server have 3 physical NICs, the other two NICs was disabled
> by me)
>
> ovs-vsctl show
>
> 931582d5-9318-48c6-a1d6-8ec486582eb8
>
> Bridge vdsmbr_vfMUcNKp
>
> Port vdsmbr_vfMUcNKp
>
> Interface vdsmbr_vfMUcNKp
>
> type: internal
>
> Port ovirtmgmt
>
> Interface ovirtmgmt
>
> type: internal
>
> Port "p3p1"
>
> Interface "p3p1"
>
> ovs_version: "2.5.0"
>
>
>
> At the same time ‘brctl show’ can still get ovirtmgmt information. And
> then, the network can not work from vdsm using the Ip binding to p3p1 or
> ovirtmgmt; I enable one of the other two NICs and the network is still not
> work for new enabled NIC.
>
>
>
> I have to reboot the vdsm. After reboot, the vdsm was not abled controlled
> by ovirt engine anymore.
>
>
>
> Here is some information: (The bridge name in virsh and ovs are not the
> same, why? Is this cause the error?)
>
>
>
> Ifconfig
>
> ovirtmgmt: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
>
> inet 192.168.0.117 netmask 255.255.255.0 broadcast 0.0.0.0
>
> inet6 fe80::f8e5:c3ff:fe74:5c59 prefixlen 64 scopeid 0x20<link>
>
> ether fa:e5:c3:74:5c:59 txqueuelen 0 (Ethernet)
>
> RX packets 8389 bytes 1528498 (1.4 MiB)
>
> RX errors 0 dropped 0 overruns 0 frame 0
>
> TX packets 22 bytes 3740 (3.6 KiB)
>
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
>
>
> ovs-vsctl show
>
> 931582d5-9318-48c6-a1d6-8ec486582eb8
>
> Bridge vdsmbr_vfMUcNKp
>
> Port vdsmbr_vfMUcNKp
>
> Interface vdsmbr_vfMUcNKp
>
> type: internal
>
> Port ovirtmgmt
>
> Interface ovirtmgmt
>
> type: internal
>
> Port "p3p1"
>
> Interface "p3p1"
>
> ovs_version: "2.5.0"
>
>
>
> vi /etc/libvirt/qemu/networks/vdsm-ovirtmgmt.xml
>
> <network>
>
> <name>vdsm-ovirtmgmt</name>
>
> <uuid>09e92e82-2510-450e-bff7-72252e37b1b8</uuid>
>
> <forward mode='bridge'/>
>
> <bridge name='ovirtmgmt'/>
>
> </network>
>
>
>
> I can’t find anything about VM because ‘virsh list --all’ show nothing.
>
>
>
> [root at server117 vdsm]# service vdsmd status -l
>
> Redirecting to /bin/systemctl status -l vdsmd.service
>
> â— vdsmd.service - Virtual Desktop Server Manager
>
> Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor
> preset: enabled)
>
> Active: inactive (dead)
>
>
>
> Aug 02 04:37:50 server117 systemd[1]: Dependency failed for Virtual
> Desktop Server Manager.
>
> Aug 02 04:37:50 server117 systemd[1]: Job vdsmd.service/start failed with
> result 'dependency'.
>
> [root at server117 vdsm]# service vdsmd start
>
> Redirecting to /bin/systemctl start vdsmd.service
>
> A dependency job for vdsmd.service failed. See 'journalctl -xe' for
> details.
>
> [root at server117 vdsm]# service vdsmd status -l
>
> Redirecting to /bin/systemctl status -l vdsmd.service
>
> â— vdsmd.service - Virtual Desktop Server Manager
>
> Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor
> preset: enabled)
>
> Active: inactive (dead)
>
>
>
> Aug 02 04:37:50 server117 systemd[1]: Dependency failed for Virtual
> Desktop Server Manager.
>
> Aug 02 04:37:50 server117 systemd[1]: Job vdsmd.service/start failed with
> result 'dependency'.
>
> Aug 02 05:28:58 server117 systemd[1]: Dependency failed for Virtual
> Desktop Server Manager.
>
> Aug 02 05:28:58 server117 systemd[1]: Job vdsmd.service/start failed with
> result 'dependency'.
>
>
>
>
>
> I think I already got mad now. ^_^
>
>
>
>
>
> Hope get help from you as soon as possible.
>
> Thank you
>
> Mark
>
>
>
> *发件人:* Michael Burman [mailto:mburman at redhat.com]
> *发送时间:* 2016年8月2日 16:01
> *收件人:* Meni Yakove
> *抄送:* lifuqiong; Dan Kenigsberg; Petr Horacek; users
> *主题:* Re: [ovirt-users] [ovirt-devel] How to add ovs-based VM in version
> 4.0.2? Thank you
>
>
>
> Hi ,
>
> Did you synced network/s after you moved the host to the ovs type cluster?
>
> It seems like you didn't..)
>
> Go to 'Hosts' main tab' and choose the host, go to 'Network Interfaces'
> sub tab and press the 'Sync All Networks' , now the networks should be
> synced to host as ovs switch type.
>
> Run the vm and check the xml.
>
> It should look something like this:
>
> <source bridge='vdsmbr_nRL3asDq'/>
> <virtualport type='openvswitch'>
>
> thanks
>
>
>
>
>
> On Tue, Aug 2, 2016 at 9:37 AM, Meni Yakove <myakove at redhat.com> wrote:
>
>
>
>
>
> On Tue, Aug 2, 2016 at 7:12 AM, lifuqiong <lifuqiong at cncloudsec.com>
> wrote:
>
> I create a cluster which already enabled ovs network as you mentioned ,
> but when I create vm in this cluster, I can only using ovirtmgmt/ovirtmgmt
> vNIC profile, which is still a Linux bridge.
>
> I found no way to add a OVS vNIC profile, I have to chose
> ovirtmgmt/ovirtmgmt vNIC to setup a VM. After VM is started, the vm is
> still using Linux bridge to communicate with outside, not the ovs.
>
>
>
> Need I to create a ovs bridge or vport and bind it to physical NIC in vdsm
> manually?
>
>
>
> Hope your reply as soon as possible.
>
> Thank you
>
> Mark
>
>
>
> *发件人:* users-bounces at ovirt.org [mailto:users-bounces at ovirt.org] *代表 *Meni
> Yakove
> *发送时间:* 2016年8月1日 16:42
> *收件人:* Dan Kenigsberg
> *主题:* Re: [ovirt-users] [ovirt-devel] How to add ovs-based VM in version
> 4.0.2? Thank you
>
>
>
> On Mon, Aug 1, 2016 at 11:07 AM, Dan Kenigsberg <danken at redhat.com> wrote:
>
> On Mon, Aug 01, 2016 at 02:02:52PM +0800, lifuqiong wrote:
> > Hi, I upgrade my ovirt to version 4.0.2.2, how to using ovs in this
> version?
> > Is there any instruction? Thank you
>
> Please note and note well: OVS is not production-grade yet. It is only a
> preliminary tech preview, under active development.
>
> However, we'd be very happy to get your help in testing it (and possibly
> fixing it, too).
>
> When defining a new cluster, you should see a check box, letting you
> select OVS for that cluster.
>
>
>
> To be precise, this is not a check box. In the Edit Cluster dialog, look
> at the "switch
>
> type" option, and change "LEGACY" to "OVS".
>
>
>
>
>
>
>
> After being checked, each VM network that
> is defined in your cluster would be implemented with OVS instead of
> Linux bridge.
>
> As aluded before, there are plenty of known definciencies (e.g., no
> persistence of ip config on VM network, no live migration, not all bond
> modes, etc etc). But do not hesitate to raise other issues with the
> devel mailing list.
>
> Happy testing!
>
> Dan.
> _______________________________________________
> Devel mailing list
> Devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
>
>
>
>
>
>
>
> --
>
> Michael Burman
> RedHat Israel, RHEV-M QE Network Team
>
> Mobile: 054-5355725
> IRC: mburman
>
--
Michael Burman
RedHat Israel, RHEV-M QE Network Team
Mobile: 054-5355725
IRC: mburman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20160802/e8205261/attachment-0001.html>
More information about the Devel
mailing list