similar to: Systemd spends 6 min. to startup a host

On Tue, Oct 6, 2015 at 6:53 AM, Gordon Messmer <gordon.messmer at gmail.com> wrote: > On 10/03/2015 09:47 AM, C.L. Martinez wrote: >> >> All works well, except when I reboot this server. Systemd spends 6 min. >> to startup this host!!! .. It stops with: "A start job is running for LSB: >> Raise network ...". > > >

On 10/5/2015 2:36 AM, C.L. Martinez wrote: > On 10/05/2015 08:43 AM, Eero Volotinen wrote: >> This looks like modifications broke network configuration and it may >> affect >> startup speed. >> >> Please try standard network configuration first. >> > > Are you referring to use NetworkManager?? I can't. I need to use > openvswitches in this host

On 10/5/2015 11:53 PM, C. L. Martinez wrote: > Uhmm ... but I need to startup openvswitches at boot ... I only see > one option: start openvswitches when libvirtd starts ... my suggestion was to help isolate the cause of this boot delay. if removing the openvswitch from your network configuration took out the delay, then you'd KNOW thats the problem, and you could work to further

This looks like modifications broke network configuration and it may affect startup speed. Please try standard network configuration first. -- Eero 2015-10-05 11:38 GMT+03:00 Mihamina Rakotomandimby < mihamina.rakotomandimby at rktmb.org>: > On 10/03/2015 07:47 PM, C.L. Martinez wrote: > >> Hi all, [...] >> >> Are not supposed that systemd startups hosts more

On 10/06/2015 06:14 PM, Gordon Messmer wrote: > On 10/05/2015 11:58 PM, C. L. Martinez wrote: >> Yes, my problem is very similar as described in Debian's bugtracker. > > The problem might be a bug. Ask the openvswitch people. > > It looks like the problem is probably: > /etc/sysconfig/network-scripts/ifup-ovs calls "systemctl start >

On 10/03/2015 09:47 AM, C.L. Martinez wrote: > All works well, except when I reboot this server. Systemd spends 6 > min. to startup this host!!! .. It stops with: "A start job is running > for LSB: Raise network ...". https://www.google.com/search?q=systemd+lsb+raise+network&ie=utf-8&oe=utf-8 If your problem is similar to the first few google hits, then some part

On Mon, Oct 5, 2015 at 3:11 PM, John R Pierce <pierce at hogranch.com> wrote: > On 10/5/2015 2:36 AM, C.L. Martinez wrote: >> >> On 10/05/2015 08:43 AM, Eero Volotinen wrote: >>> >>> This looks like modifications broke network configuration and it may >>> affect >>> startup speed. >>> >>> Please try standard network

On 10/05/2015 11:58 PM, C. L. Martinez wrote: > Yes, my problem is very similar as described in Debian's bugtracker. The problem might be a bug. Ask the openvswitch people. It looks like the problem is probably: /etc/sysconfig/network-scripts/ifup-ovs calls "systemctl start openvswitch-nonetwork.service" openvswitch-nonetwork.service "Wants" openvswitch.service

On 10/05/2015 08:43 AM, Eero Volotinen wrote: > This looks like modifications broke network configuration and it may affect > startup speed. > > Please try standard network configuration first. > Are you referring to use NetworkManager?? I can't. I need to use openvswitches in this host ...

On 10/03/2015 04:47 PM, C.L. Martinez wrote: > Hi all, > > I have a strange behavior with a CentOS7 host (fully patched). I have > configured nics as old style format: ifcfg- ... due to I need to use > openvswitch for my vms. > > All works well, except when I reboot this server. Systemd spends 6 > min. to startup this host!!! .. It stops with: "A start job is

Em 03-10-2015 13:47, C.L. Martinez escreveu: > Hi all, > > I have a strange behavior with a CentOS7 host (fully patched). I have > configured nics as old style format: ifcfg- ... due to I need to use > openvswitch for my vms. > > All works well, except when I reboot this server. Systemd spends 6 > min. to startup this host!!! .. It stops with: "A start job is

Hi, I have an existing OVS bridge, that I can see in ovs-vsctl and use for other purposes. I've edited the machine's XML as instructed in http://docs.openvswitch.org/en/latest/howto/libvirt/ When I try to start the VM, i get error: Cannot get interface MTU on 'ovsbr': No such device Any ideas? (Note: I can't see the ovs switch in brctl show or any other regular kernel tool,

Hello! How can i operate with openvswitch without root rights? For example - i can add my user to kvm group and create vm from libvirt with my own user, but now i'm failed with creating port. errors in logs: Mar 06 14:04:46 selfip.ru ovs-vsctl[19065]: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port Mar 06 14:04:46 selfip.ru ovs-vsctl[19065]:

On 10/03/2015 07:47 PM, C.L. Martinez wrote: > Hi all, [...] > > Are not supposed that systemd startups hosts more faster?? > ts.centos.org/mailman/listinfo/centos I think you misunderstand: systemd has a dependency management between services, that could make the boot faster. Speeding up the boot was not the goal, it's an effect.

Hi. I'd like to use Openvswitch while running libvirt as an unprivileged user (qemu:///session). As expected, system session works just fine with OVS. When I try to start the domain from user session, with the relevant network part of the domain xml edited to use openvswitch, like this --- <interface type='bridge'> <mac address='52:54:00:4a:ef:bb'/>

hi guys I have a qemu guest and openvswitch bridge and the guest fails to start: $ virsh start work8 error: Failed to start domain work8-vm-win2016 error: Cannot get interface MTU on 'ovsbr0': No such device LXC guest which uses the same source network starts just fine. I'm on Centos 7 with openvswitch-2.9.0-3.el7.x86_64 from centos-openstack-pike repo and

Hey folks, I'm working on setting up a Cuckoo sandbox malware lab at home, and can't seem to get openvswitch and libvirt to work together as-documented. I'm not subscribed to the list, so please reply-all. Thanks in advance! I've debugged this, and I think the interfaceid stuff in network XML isn't doing much besides setting a custom interfaceid in an OpenVSwitch table that

Based on Waldi''s RFC at http://lists.xen.org/archives/html/xen-devel/2012-09/msg00943.html To use it set vif.default.script="vif-openvswitch" in /etc/xen/xl.conf or use script=vif-openvswitch in the vif configuration. Appears to do the right thing for PV and HVM guests (including tap devices) and with stubdomains. In order to support VLAN tagging and trunking the

I have installed OVS from sources using the installation steps mentioned on this link: http://docs.openvswitch.org/en/latest/intro/install/general/ I had installed libvrt, KVM, QEMU and all the necessary packages using apt-get. My KVM-QEMU hypervisor has been running well. To add a VM with the port attached to OVS bridge I changed the XML domain file as per the instructions on this page:

hi all , i use ubuntu 12.04 with xcp , all config run very well except vlan i use xe network-create and xe vlan-create to build vlan 3000 then startup a vm in this network, xapi0 fakebridge and vif1.0 all looks well, use ovs-vsctl list port i can see xapi0 and vif1.0 have beed taged with 3000 but i can not access the internent~~~ somebody can help me with this? thanks.