[Ovirt-devel] [PATCH] Fix so libvirt does not start default network interface on developer/bundled
Perry N. Myers
pmyers at redhat.com
Mon May 26 15:42:41 UTC 2008
Alan Pevec wrote:
>>> No, no, no and no. To disable it use virsh
>>>
>>> virsh destroy default
>>> virsh autostart --disable default
>>
>> I'll commit it with:
>>
>> + virsh net-destroy default
>> + virsh net-undefine default
>>
>> net-undefine removes autostart link too
>
> Correction: virsh needs running libvirtd and ovirt-wui-first-run start
> priority is 96 while libvirtd is 97.
> I'll change ovirt-wui-first-run to 98.
This may not be an issue, since on first boot none of the init scripts for
the oVirt daemons are active anyhow...
The oVirt daemons are all runlevel 97. If you set ovirt-wui-first-run to
98 it'll be after the ovirt daemons, which conceptually is confusing.
The other thing that needs to change is libvirtd -must- be set to start in
the kickstart. Right now it's off by default. So make sure you update
the ks file.
Perry
More information about the ovirt-devel
mailing list