Closed rsampaio closed 8 years ago
This fix the driver initialization caused by d.connectionString not being initialized when the Driver is created, this will make subsequent calls use qemu:///session instead of qemu:///system and network.Create will fail with this message.
d.connectionString
(local-kvm) DBG | Reactivating private network: %!s(<nil>) Error creating machine: Error with pre-create check: [Code-38] [Domain-0] error creating bridge interface virbr0: Operation not permitted
Also changed the function signature to match with what is used in other driver, not related to the issue though.
I just hit the same error.
Thanks! - I've resolved the merge conflict and pushed this to master.
This fix the driver initialization caused by
d.connectionString
not being initialized when the Driver is created, this will make subsequent calls use qemu:///session instead of qemu:///system and network.Create will fail with this message.Also changed the function signature to match with what is used in other driver, not related to the issue though.