On 11/08/2008, at 8:42 PM, Daniel P. Berrange wrote:
On Mon, Aug 11, 2008 at 09:18:19AM +0100, Richard W.M. Jones wrote:
On Mon, Aug 11, 2008 at 07:39:34PM +1200, james wrote:
This is what libvirt gives you (and lots more, eg. secure remote
access to hypervisors, bindings to Perl many other
On 12/08/2008, at 10:30 PM, Daniel P. Berrange wrote:
Oh, that means the version of libvirt you are using is too old - it
predates us adding support for the -drive argument, which is required
in order to use SCSI disks. THis was added in libvirt 0.4.3
Regards,
Daniel
Ah - the penny drops.
On Mon, Aug 11, 2008 at 07:39:34PM +1200, james wrote:
This is what libvirt gives you (and lots more, eg. secure remote
access to hypervisors, bindings to Perl many other languages, etc.).
Can you be more specfic about what you couldn't do with libvirt?
I can give you such an example
On Sun, Aug 10, 2008 at 11:07:32AM +0100, Richard W.M. Jones wrote:
Libvirt deliberately doesn't expose the full
feature set of any one hypervisor which it supports, but instead
exposes common features.
Judging by one private reply I got, I don't want this to be
misinterpreted. Libvirt
On Thu, Aug 07, 2008 at 11:47:39AM +0100, Daniel P. Berrange wrote:
On Thu, Aug 07, 2008 at 07:40:58PM +0900, Jun Koi wrote:
One of the problem is that these tools work via libvirt, so on a VM is
not managed by libvirt, these tools no longer work.
That's not a problem - that's a reason to
