Sankamesh wrote:
Hello,
I am using Scientific Linux 5.4 and xen. I want to deploy a sample
ttyimage by creating a domain using virsh create.
My configuration file is :
-
?xml version=1.0
Hello
Thanks for the reply. Now I use virsh -c xen:/// define
libvirt-ttylinux.xml (domain is created) and virsh start ttyimage the image
starts and shuts down immediately. This time I can view the domain even after
the shut down.
So is there any reason for the image being shutdown
On Thu, Apr 08, 2010 at 09:33:38PM -0400, Stefan Berger wrote:
This patch adds a couple more nwfilter test cases for the XML parser tests.
Signed-off-by: Stefan Berger stef...@us.ibm.com
More tests is good :-)
ACK,
Daniel
--
Daniel Veillard | libxml Gnome XML XSLT toolkit
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 04:11:32PM -0400, David Allan wrote:
Dan Kenigsberg requested that we add an option to explicitly request enospace
as the disk error policy.
Well, to be more exact, I asked if leaving it out was intentional ;-)
(But I do think that alowing explicity here is a good
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
Hello,
at http://libvirt.org/formatdomain.html#elementsNICS there are three
examples of interfaces with a particular MAC address specified. I
understand the provided mac address is more a placeholder than a real
value; but since '11:22:33:44:55:66' seems to be a multicast address[1],
I would
On Fri, Apr 09, 2010 at 11:44:30AM +0300, Dan Kenigsberg wrote:
On Thu, Apr 08, 2010 at 04:11:32PM -0400, David Allan wrote:
Dan Kenigsberg requested that we add an option to explicitly request
enospace as the disk error policy.
Well, to be more exact, I asked if leaving it out was
On Thu, Apr 08, 2010 at 10:33:53PM +0200, Daniel Veillard wrote:
On Thu, Apr 08, 2010 at 04:11:33PM -0400, David Allan wrote:
* Dan Kenigsberg requested explicit support for the qemu default disk error
policy which is enospace
---
docs/schemas/domain.rng|
In a couple of cases typos meant we were firing the wrong type
of event. In the python code my previous commit accidentally
missed some chunks of the code.
* python/libvirt-override-virConnect.py: Add missing python glue
accidentally left out of previous commit
* src/conf/domain_event.c,
Daniel P. Berrange berra...@redhat.com wrote on 04/08/2010 09:07:39
AM:
Due to licensing complexity we can't distribute pre-built guest images
directly with the TCK. So I think what we'd want todo is to write a
kickstart file that installs a bare minimum Fedora guest OS, with a
pre-set
On Fri, Apr 09, 2010 at 11:51:46AM +0100, Daniel P. Berrange wrote:
In a couple of cases typos meant we were firing the wrong type
of event. In the python code my previous commit accidentally
missed some chunks of the code.
* python/libvirt-override-virConnect.py: Add missing python glue
On Fri, Apr 09, 2010 at 11:46:20AM +0200, redsh...@gmx.com wrote:
Hello,
at http://libvirt.org/formatdomain.html#elementsNICS there are three
examples of interfaces with a particular MAC address specified. I
understand the provided mac address is more a placeholder than a real
value; but
On Wed, Mar 31, 2010 at 12:22:50PM -0500, Ryan Harper wrote:
Currently when we attempt to change the cdrom in a qemu VM the monitor
doesn't generate an error if the target filename doesn't exist. I've
submitted a patch[1] for this. This patch is the libvirt qemu-driver
side which catches the
Hello,
In response to a lot of the talk of qemud lately on qemu-devel, the
libvirt community would like to put forward a proposal to help enable
debug/advanced options when using various hypervisors. The goals of
this API are:
1) To enable more rapid access to hypervisor features before
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
Eric Blake ebl...@redhat.com wrote on 03/30/2010 05:24:56 PM:
On 03/30/2010 02:52 PM, Stefan Berger wrote:
Trivial fix for the cp error in the nwfilter test driver.
Signed-off-by: Stefan Berger stef...@us.ibm.com
Index: libvirt-acl/src/test/test_driver.c
[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
On Fri, Apr 09, 2010 at 09:41:39AM -0400, Chris Lalancette wrote:
Hello,
In response to a lot of the talk of qemud lately on qemu-devel, the
libvirt community would like to put forward a proposal to help enable
debug/advanced options when using various hypervisors. The goals of
this API
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
The idea is that every API implementation in driver which has flags
parameter should first call virCheckFlags() macro to check the function
was called with supported flags:
virCheckFlags(VIR_SUPPORTED_FLAG_1 |
VIR_SUPPORTED_FLAG_2 |
I think we need a simple and consistent way of checking whether flags passed
to API entry points in drivers are valid/supported or not. So far some entry
points don't check flags at all and some checks for 0 when no flags are
expected/supported.
The first patch introduces a macro which can be
---
src/esx/esx_driver.c | 44 -
src/nwfilter/nwfilter_driver.c |5 ++-
src/qemu/qemu_driver.c | 69 +++-
src/storage/storage_driver.c |7 +---
src/vbox/vbox_tmpl.c | 42
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
On 04/09/2010 10:27 AM, Daniel P. Berrange wrote:
The concept of command line monitor is something that is QEMU specific
and thus is not suitable for the primary XML schema. IMHO, this needs to be
done as a separate schema, linked in via an XML namespace. For example
domain type='kvm'
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
I mistakenly took the op field in the DHCP message as the DHCP_OFFER
type. Rather than basing the decision to read the VM's IP address on
that field, process the appended DHCP options where option 53 indicates
the actual type of the packet. I am also reading the broadcast address
of the VM, but
Two small issues I found while testing libvirt under QMP, there is also
a third I won't fix today: dommemstat doesn't work under QMP.
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
It's not needed and is just discarded by the Server.
Signed-off-by: Luiz Capitulino lcapitul...@redhat.com
---
src/qemu/qemu_monitor_json.c | 34 --
1 files changed, 0 insertions(+), 34 deletions(-)
diff --git a/src/qemu/qemu_monitor_json.c
- Two missing 's'
- 'dominfo' is duplicated
Signed-off-by: Luiz Capitulino lcapitul...@redhat.com
---
tools/virsh.pod |8 ++--
1 files changed, 2 insertions(+), 6 deletions(-)
diff --git a/tools/virsh.pod b/tools/virsh.pod
index 1b5c1d6..46ba813 100644
--- a/tools/virsh.pod
+++
On Fri, Apr 09, 2010 at 02:57:43PM -0400, Stefan Berger wrote:
I mistakenly took the op field in the DHCP message as the DHCP_OFFER
type. Rather than basing the decision to read the VM's IP address on
that field, process the appended DHCP options where option 53 indicates
the actual type of
[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
On Wed, 2010-04-07 at 10:43 +0100, Daniel P. Berrange wrote:
On Tue, Apr 06, 2010 at 08:00:01PM +0100, Paul Jenner wrote:
On Fri, 2010-04-02 at 21:46 -0400, Chris Lalancette wrote:
snip
@@ -8288,6 +8731,14 @@ static const vshCmdDef commands[] = {
{vcpupin, cmdVcpupin, opts_vcpupin,
On 04/09/2010 07:41 AM, Chris Lalancette wrote:
Caveats:
3) Application developers will be strongly discouraged from using
this API because of the above 2 issues. To help in this, the
API's will be in a separate library that developers will explicitly
have to link to, and it will have a
Daniel P. Berrange wrote:
I think this alteration of existing args is fr too complex fragile,
and way overkill.
Would it not be simpler, for the target audience, for the config to
contain a one-line shell script to transform particular matched
arguments in any way that's wanted?
If the
On 04/09/2010 03:06 PM, Jamie Lokier wrote:
Daniel P. Berrange wrote:
I think this alteration of existing args is fr too complex fragile,
and way overkill.
Would it not be simpler, for the target audience, for the config to
contain a one-line shell script to transform particular
41 matches
Mail list logo
