On 07/07/2015 04:49 AM, Maxim Nestratov wrote:
It is better not to assume that newly created network should be connected to a bridge with same name, but specify it explicitly by PRL_USE_VNET_NAME_FOR_BRIDGE_NAME flag. Signed-off-by: Maxim Nestratov <mnestratov@xxxxxxxxxxxxx>
There is a typo in libvirt list name, but as I remember, there was an alias. Did it get there?
--- src/vz/vz_sdk.c | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/src/vz/vz_sdk.c b/src/vz/vz_sdk.c index 1b66958..1c56655 100644 --- a/src/vz/vz_sdk.c +++ b/src/vz/vz_sdk.c @@ -2834,7 +2834,9 @@ static int prlsdkAddNet(PRL_HANDLE sdkdom, pret = PrlVirtNet_SetNetworkType(vnet, PVN_BRIDGED_ETHERNET); prlsdkCheckRetGoto(pret, cleanup);- job = PrlSrv_AddVirtualNetwork(privconn->server, vnet, 0);+ job = PrlSrv_AddVirtualNetwork(privconn->server, + vnet, + PRL_USE_VNET_NAME_FOR_BRIDGE_NAME); if (PRL_FAILED(pret = waitJob(job))) goto cleanup;
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list