DB> I don't. The API should be hypervisor agnostic. Needing to pass DB> HV specific attributes to make it works shows we have failed.
In that case, haven't we already failed with virDomainCreate() since it takes hypervisor-specific XML? Doesn't the presence of VIR_DEVICE_RW_FORCE imply knowledge of Xen-specific behavior? How would you handle someone wanting to use tcp:// or ssh:// with qemu? -- Dan Smith IBM Linux Technology Center Open Hypervisor Team email: [EMAIL PROTECTED]
pgpsRaQZEZG6G.pgp
Description: PGP signature
-- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
