All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
To: gerryw-dHy0zPTSVEVBDgjK7y7TUQ@public.gmane.org
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: libqemu => libkvm?
Date: Tue, 04 Sep 2007 08:55:23 -0500	[thread overview]
Message-ID: <1188914123.19454.0.camel@squirrel> (raw)
In-Reply-To: <OF71DCD0E8.065585B8-ON8625734B.00804A16-8625734B.0082D8AE-Ojamyiewz+ICx7yrEBmKXg@public.gmane.org>


On Mon, 2007-09-03 at 18:49 -0500, gerryw-dHy0zPTSVEVBDgjK7y7TUQ@public.gmane.org wrote:
> 
> Hi Folks, 
> 
> I've been spending some time playing around with KVM and I am starting
> to become interested in making a contribution to the project. I'm
> considering the idea of writing a library interface to libqemu in a
> KVM context.

What do you mean by libqemu?  The libqemu in the QEMU project is a
library for the CPU translation.  It actually doesn't really serve a
purpose in the context of KVM.  It is not the sort of thing you'd write
a GUI tool around.

Regards,

Anthony Liguori

>  I am aware of libvirt, but that isn't what I'm thinking here. This
> lib would be very specific to KVM. I have been poking around in the
> source a bit and it seems like it would be possible. Before I go
> further, I thought I would ask a few questions. I would also
> appreciate any and all opinions on the subject. 
> 
> 1. Is anyone already thinking about , or actually doing this? 
> 2. Does this sound useful? 
> 3. Is the libqemu API stable enough at this point to write code
> against? 
> 4. Can anyone see any immediate road blocks to doing this? 
> 
> This would probably also include a cross platform GUI interface at
> some point. This interface would be specific to KVM and the subtle
> nuances that make it unique. I've been looking for a good excuse to
> use FLTK on a project anyway ;-) 
> 
> Thanks for your consideration, 
> -G 
> 
> 
> 
> 
> 
> 
> 
> 
>  
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________ kvm-devel mailing list kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org https://lists.sourceforge.net/lists/listinfo/kvm-devel


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

  parent reply	other threads:[~2007-09-04 13:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-03 23:49 libqemu => libkvm? gerryw-dHy0zPTSVEVBDgjK7y7TUQ
     [not found] ` <OF71DCD0E8.065585B8-ON8625734B.00804A16-8625734B.0082D8AE-Ojamyiewz+ICx7yrEBmKXg@public.gmane.org>
2007-09-04  7:38   ` Dor Laor
     [not found]     ` <64F9B87B6B770947A9F8391472E032160D7065D7-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-09-04  9:35       ` gerryw-dHy0zPTSVEVBDgjK7y7TUQ
     [not found]         ` <OF011A2D66.C01A5229-ON8625734C.0032D27A-8625734C.00361C57-Ojamyiewz+ICx7yrEBmKXg@public.gmane.org>
2007-09-04 12:15           ` Dor Laor
     [not found]             ` <64F9B87B6B770947A9F8391472E032160D7066AE-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-09-04 12:42               ` Daniel Veillard
2007-09-04 13:55   ` Anthony Liguori [this message]
2007-09-04 14:16     ` gerryw-dHy0zPTSVEVBDgjK7y7TUQ
  -- strict thread matches above, loose matches on Subject: below --
2007-09-04 13:23 gerryw-dHy0zPTSVEVBDgjK7y7TUQ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1188914123.19454.0.camel@squirrel \
    --to=anthony-rdkfgonbjusknkdkm+me6a@public.gmane.org \
    --cc=gerryw-dHy0zPTSVEVBDgjK7y7TUQ@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.