On Thu, Jul 25, 2013 at 08:10:46AM +0200, Ján Tomko wrote:
On 07/24/2013 10:06 PM, John Ferlan wrote:
> On 07/24/2013 05:57 AM, Daniel P. Berrange wrote:
>>> On Wed, Jul 24, 2013 at 10:25:06AM +0200, Ján Tomko wrote:
> <...snip...>
>>>
>>> Both secret and qemu drivers are registered after the storage driver on
>>> libvirtd startup, so autostarting these pools will only work on storage
driver
>>> reload. On libvirtd startup it fails with:
>>> qemuConnectOpen:1033 : internal error qemu state driver is not active
>>>
>>> (And it seems nwfilter only opens the qemu:// connection on reload)
>>
>> Oh damn, yes, that pretty much dooms us. We can't change the order of
>> the drivers either, because autostarting of QEMU guests, requires that
>> the storage pools be autostarted already.
>>
>> To fix this would require that we split virStateInitialize into two
>> parts, virStateInitialize() and virStateAutoStart(). That's too big
>> a change todo for this release, but we could do it for next release
>> without too much trouble.
>>
>>
>> Daniel
>>
>
>
> Could we just do it for storage driver? It seems you are indicating
> that the following would suffice, right? Or does this problem go deeper?
>
Doing it only for the storage driver would move the pool autostart after QEMU
guests autostart and the guests wouldn't be able to use the pools.
Yep, we'd need todo it for all the drivers at once to preseve the ordering.
Daniel
--
|:
http://berrange.com -o-
http://www.flickr.com/photos/dberrange/ :|
|:
http://libvirt.org -o-
http://virt-manager.org :|
|:
http://autobuild.org -o-
http://search.cpan.org/~danberr/ :|
|:
http://entangle-photo.org -o-
http://live.gnome.org/gtk-vnc :|