On Thu, Apr 08, 2010 at 11:27:46PM +0100, Antoine Martin wrote:
Hi,
I am moving this thread here as this seems more appropriate.
Sorry it has taken so long..
Here are 2 things that really get in the way of moving my existing
installations to libvirt:
* I tend to store much meta data with
On Thu, Apr 08, 2010 at 11:27:46PM +0100, Antoine Martin wrote:
Hi,
I am moving this thread here as this seems more appropriate.
Sorry it has taken so long..
Here are 2 things that really get in the way of moving my existing
installations to libvirt:
* I tend to store much meta data with
On Fri, Apr 09, 2010 at 09:49:51AM +0200, Daniel Veillard wrote:
On Thu, Apr 08, 2010 at 11:27:46PM +0100, Antoine Martin wrote:
Hi,
I am moving this thread here as this seems more appropriate.
Sorry it has taken so long..
Here are 2 things that really get in the way of moving my
[snip]
* not everything is exposed via libvirt:
virsh can retrieve vncdisplay
but libvirt (or at least the python bindings) does not. How come?
This happens to be one thing I need for writing a libvirt backend for my
virtual desktop software.
The 'virsh vncdisplay' command is simply
Daniel Veillard wrote:
On Thu, Apr 08, 2010 at 11:27:46PM +0100, Antoine Martin wrote:
Hi,
I am moving this thread here as this seems more appropriate.
Sorry it has taken so long..
Here are 2 things that really get in the way of moving my existing
installations to libvirt:
* I tend to
On Fri, Apr 09, 2010 at 03:31:37PM +0100, Antoine Martin wrote:
[snip]
* not everything is exposed via libvirt:
virsh can retrieve vncdisplay
but libvirt (or at least the python bindings) does not. How come?
This happens to be one thing I need for writing a libvirt backend for my
On 04/09/2010 10:31 AM, Antoine Martin wrote:
[snip]
* not everything is exposed via libvirt:
virsh can retrieve vncdisplay
but libvirt (or at least the python bindings) does not. How come?
This happens to be one thing I need for writing a libvirt backend for my
virtual desktop software.
On Fri, Apr 09, 2010 at 03:31:37PM +0100, Antoine Martin wrote:
[snip]
* not everything is exposed via libvirt:
virsh can retrieve vncdisplay
but libvirt (or at least the python bindings) does not. How come?
This happens to be one thing I need for writing a libvirt backend for my
Daniel P. Berrange wrote:
On Fri, Apr 09, 2010 at 03:31:37PM +0100, Antoine Martin wrote:
[snip]
* not everything is exposed via libvirt:
virsh can retrieve vncdisplay
but libvirt (or at least the python bindings) does not. How come?
This happens to be one thing I need for writing a libvirt
On Fri, Apr 09, 2010 at 03:53:37PM +0100, Antoine Martin wrote:
Daniel P. Berrange wrote:
On Fri, Apr 09, 2010 at 03:31:37PM +0100, Antoine Martin wrote:
[snip]
* not everything is exposed via libvirt:
virsh can retrieve vncdisplay
but libvirt (or at least the python bindings) does not.
On Fri, Apr 09, 2010 at 10:12:57AM -0400, Hugh O. Brock wrote:
On Fri, Apr 09, 2010 at 09:49:51AM +0200, Daniel Veillard wrote:
On Thu, Apr 08, 2010 at 11:27:46PM +0100, Antoine Martin wrote:
Hi,
I am moving this thread here as this seems more appropriate.
Sorry it has taken so
Daniel P. Berrange wrote:
On Fri, Apr 09, 2010 at 03:53:37PM +0100, Antoine Martin wrote:
Daniel P. Berrange wrote:
On Fri, Apr 09, 2010 at 03:31:37PM +0100, Antoine Martin wrote:
[snip]
* not everything is exposed via libvirt:
virsh can retrieve vncdisplay
but libvirt (or at least the
[snip]
I was thinking of something like:
domain.get_attribute(vncdisplay)
Because it's a shame to have to use virsh as a wrapper (or XML file
parsing) and re-do all the work that was done to get to the domain
object when all your really want is just an attribute..
You can already do that
Hi,
I am moving this thread here as this seems more appropriate.
Sorry it has taken so long..
Here are 2 things that really get in the way of moving my existing
installations to libvirt:
* I tend to store much meta data with each VM instance: it can be things
like ownership (contact details as
14 matches
Mail list logo
