It looks like this exactly could be the problem. I don't know how the node installation works, but when you install normal system it shouldn't start any services until you specify that. Of course this is another story when installing one-purpose system, so I won't be able to tell you exactly, but vdsm should definitely make sure libvirtd loads its config (re/starts *after* the config is modified)
I'm glad it works for you now. Martin On 07/31/2012 01:42 PM, T-Sinjon wrote: > yeah, everything went ok after restart libvirtd > > I have do a test : > Install a new node, the problem always there (any possible that > "dynamic_ownership=0 # by vdsm" has done after libvirtd starting??) > _______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
