Henrik Persson E wrote:
Are there any plans to include possibility to configure bridged networks
in libvirt?
I see the need to be able to actually be able create vlans on physical
devices and the bridge the vlan, which I guess is a very normal case for
isolating network traffic between
On Mon, 2008-12-08 at 10:00 +0100, Chris Lalancette wrote:
Henrik Persson E wrote:
Are there any plans to include possibility to configure bridged networks
in libvirt?
I see the need to be able to actually be able create vlans on physical
devices and the bridge the vlan, which I guess is
Daniel Veillard [EMAIL PROTECTED] wrote:
Here are the induced help changes:
[code diffs coming in separate messages]
Looks fine to me, all those diffs seems to fix errors in synopsis
or rename the arguments to be more coherent. I don't think breaking
the unspecified -h behaviour is a
Daniel P. Berrange [EMAIL PROTECTED] wrote:
On Fri, Dec 05, 2008 at 07:24:31PM +0100, Jim Meyering wrote:
This started when I noticed that a lot of virsh help output was
out of date. Dan Berrange suggested to generate the SYNTAX line
automatically based on existing option descriptions, since
On Fri, Dec 05, 2008 at 07:24:53PM +0100, Jim Meyering wrote:
* src/virsh.c: Now, every command must have a desc string,
even if it has zero length. Mark these, so they'll be filled in.
sure, +1
Daniel
--
Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/
[EMAIL
On Fri, Dec 05, 2008 at 07:24:31PM +0100, Jim Meyering wrote:
This started when I noticed that a lot of virsh help output was
out of date. Dan Berrange suggested to generate the SYNTAX line
automatically based on existing option descriptions, since they tell us
what arguments/types each
On Mon, Dec 08, 2008 at 11:16:32AM +, Mark McLoughlin wrote:
On Mon, 2008-12-08 at 10:00 +0100, Chris Lalancette wrote:
Henrik Persson E wrote:
Are there any plans to include possibility to configure bridged networks
in libvirt?
I see the need to be able to actually be able create
I do have older versions (for chroot purposes) mounted in non-standard paths...
I don't know why it would pick it up in /data:
$ locate libgnutls.so.13
/data/f9root/usr/lib64/libgnutls.so.13
/data/f9root/usr/lib64/libgnutls.so.13.9.1
The strange part is, that it looks like it is linking
On Fri, Dec 05, 2008 at 07:25:02PM +0100, Jim Meyering wrote:
* src/virsh.c: ... now that it's generated.
---
FYI, I made this change with the following one-liner:
perl -ni -e '/syntax,/ or print' src/virsh.c
I still don't understand perl ( or print ???) but patch is trivial,
+1
On Thu, Dec 04, 2008 at 03:29:09PM -0500, Hugh O. Brock wrote:
On Thu, Dec 04, 2008 at 07:42:51PM +, Daniel P. Berrange wrote:
On Wed, Dec 03, 2008 at 05:47:11PM -0500, Itamar Heim wrote:
Thanks for the tips.
Next batch of issues...
1. while still trying to build manually...
On Fri, Dec 05, 2008 at 05:24:18PM +0100, Gerd v. Egidy wrote:
dbus_watch_get_unix_fd() was added in dbus = 1.1.1, it deprecate
dbus_watch_get_fd(), so we should use the later if compiling against
the old stuff,
hmm, somehow this problem and the solutions seems familiar to me:
On Fri, Dec 05, 2008 at 03:24:31PM -0500, Ben Guthro wrote:
So...I decided to make the leap, and upgraded to F10 (from F9)
After my upgrade, I decided to build the libvirt rpm from source, and install
it.
So far, so good...everything built, and installs nicely.
However, when I run virsh,
On Fri, Dec 05, 2008 at 07:25:12PM +0100, Jim Meyering wrote:
* src/virsh.c: Adjust some vshCmdOptDef command option flags
to improve auto-generated help command syntax.
---
Right, in general it's better to use a description of the argument
than the type used, and document internally if
On Fri, Dec 05, 2008 at 07:24:31PM +0100, Jim Meyering wrote:
This started when I noticed that a lot of virsh help output was
out of date. Dan Berrange suggested to generate the SYNTAX line
automatically based on existing option descriptions, since they tell us
what arguments/types each
On Mon, Dec 08, 2008 at 11:35:03AM +0100, Daniel Veillard wrote:
On Fri, Dec 05, 2008 at 07:25:02PM +0100, Jim Meyering wrote:
* src/virsh.c: ... now that it's generated.
---
FYI, I made this change with the following one-liner:
perl -ni -e '/syntax,/ or print' src/virsh.c
On Mon, Dec 08, 2008 at 07:53:10AM -0500, Ben Guthro wrote:
I do have older versions (for chroot purposes) mounted in non-standard
paths...
I don't know why it would pick it up in /data:
$ locate libgnutls.so.13
/data/f9root/usr/lib64/libgnutls.so.13
On Fri, Dec 05, 2008 at 07:24:44PM +0100, Jim Meyering wrote:
* src/virsh.c: Also, diagnose extra arguments after --help (-h).
---
src/virsh.c | 102 +-
1 files changed, 58 insertions(+), 44 deletions(-)
Patch looks fine, +1
FYI,
Itamar Heim noticed that the LIBVIRT_0_5_1 tag, while in CVS, was not
in the git repository (thanks, Itamar).
I have a vague recollection that git cvsimport creates certain tags lazily
(like only once there is something on a branch) but I have manually
applied and pushed this particular
On Sun, Dec 07, 2008 at 10:40:14AM -0500, Juan Miscaro wrote:
Quite new to libvirt (and kvm). I played with a few vm's with
libvirt/kvm and vnc/virsh/virt-manager. I would now like to implement
access control for my vm's (of any format: xen, kvm, etc) to a remote
backend (mysql/ldap/other).
Hi, guys.
During domain creation from xml like this:
domain type=openvz id=3005
name3005/name
memory131072/memory
currentMemory131072/currentMemory
vcpu1/vcpu
os
typeexe/type
20 matches
Mail list logo
