On 08/24/2015 11:26 PM, Michal Privoznik wrote:
> On 23.08.2015 07:20, chenhongz...@zhicloud.com wrote:
>> Hi, All!
>>
>> I found a bug!
>> When I start the default network, I got a error shown as below:
>>
>> [root@localhost ~]# virsh net-start default
>> error: Failed to start network default
>>
On 23.08.2015 07:20, chenhongz...@zhicloud.com wrote:
> Hi, All!
>
> I found a bug!
> When I start the default network, I got a error shown as below:
>
> [root@localhost ~]# virsh net-start default
> error: Failed to start network default
> error: error creating bridge interface virbr0: Operation
On 23.08.2015 10:42, Amit Aviram wrote:
> Hi all.
> In libvirt documentation it is written that virDomainDetachDeviceFlags is
> an asynchronous call:
> http://libvirt.org/html/libvirt-libvirt-domain.html#virDomainDetachDeviceFlags
>
> Does that mean that also virDomainDetachDevice is asynchronous?
I filed a bug about this at:
https://bugzilla.redhat.com/show_bug.cgi?id=1252780
Dropping back to libvirt-1.2.2 fixed it for me, but there was no answer to the
bug report.
Sent from my Sony Xperia™ smartphone
chenhongz...@zhicloud.com wrote
>_
Hi all.
In libvirt documentation it is written that virDomainDetachDeviceFlags is
an asynchronous call:
http://libvirt.org/html/libvirt-libvirt-domain.html#virDomainDetachDeviceFlags
Does that mean that also virDomainDetachDevice is asynchronous? the reasons
mentioned in the above seems relevant f
Hi all!,
I have a setup in which I want to NAT several Virtual Machines from the host
based on ports all of them running CentOS 7.1.
The idea is I have several different services running in different VMs and all
of them are accessible from the host using different ports that are forwarded
to t
