> - If the user gives a URI with a vbox:/// prefix, we should always > handle it, unless a 'server' is set when we leave it to the remote > driver > - If an invalid path is given we must give back a real error code > - If after deciding the URI is for us, any initialization fails > we must raise an error. > - If the vbox glue layer is missing, we should still raise errors > for requested URIs, so user knows their URI is correct. > > To do this, I've taken the approach of registering a dummy vbox driver > if the glue layer is missing. This just parses the URI and always returns > an error for any vbox:// URIs that would otherwise work ACK. works fine for 2.2.* as well as internal 2.5* development versions. Regards, Pritesh -- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list