I have attempted to add following methods to Domain class:
1. vcpus=
2. memory=
This is my first patch to libvirt-ruby, and I will appreciate your
feedback.
My next goal is to add binding for virDomainPinVcpu() method.
Sincerely,
Vadim
mychanges.hg
Description: Binary data
--
Libvir-list
On Thu, Mar 27, 2008 at 03:35:54PM -0500, Charles Duffy wrote:
> Daniel P. Berrange wrote:
> >Instead of having the separate ACCEPT rule I think it would be sufficient
> >to replace the 0.0.0.0/0 target with ! 192.168.65.0/24, eg
> >
> >iptables -t nat -A POSTROUTING
> >--source 1
Daniel Veillard wrote:
> On Wed, Mar 26, 2008 at 11:22:25PM -0700, Dave Leskovec wrote:
>> This patch contains the shutdown and destroy domain support for Linux
>> Containers.
>>
>> A shutdown of the container is requested by sending a SIGINT to the container
>> root process.
>> A container is des
On Thu, Mar 27, 2008 at 02:50:20PM -0700, Dave Leskovec wrote:
> Daniel Veillard wrote:
>
> >
> >> +static int lxcStartContainer(virConnectPtr conn,
> >> + lxc_driver_t* driver,
> >> + lxc_vm_t *vm)
> >> +{
> >> +int rc = -1;
> >> +i
Daniel Veillard wrote:
> On Wed, Mar 26, 2008 at 11:20:59PM -0700, Dave Leskovec wrote:
>> This is a repost of patch four in the last series I posted. It contains the
>> start container support. I've made some changes corresponding to Dan B's
>> patch
>> moving the lxc driver under libvirtd. I
Daniel Veillard wrote:
> On Wed, Mar 26, 2008 at 11:35:08PM -0700, Dave Leskovec wrote:
>> Sorry - I should have mentioned that the two lxc patches I just posted are
>> built
>> on Dan B's patch. The order is this:
>>
>> Dan's patch
>
> commited,
>
>> lxc_start.patch
>
> reviewed
>
>> lxc
On Thu, Mar 27, 2008 at 03:35:54PM -0500, Charles Duffy wrote:
> Daniel P. Berrange wrote:
> >Instead of having the separate ACCEPT rule I think it would be sufficient
> >to replace the 0.0.0.0/0 target with ! 192.168.65.0/24, eg
> >
> >iptables -t nat -A POSTROUTING
> >--source 1
Daniel P. Berrange wrote:
Instead of having the separate ACCEPT rule I think it would be sufficient
to replace the 0.0.0.0/0 target with ! 192.168.65.0/24, eg
iptables -t nat -A POSTROUTING
--source 192.168.65.0/24
--destination ! 192.168.65.0/24
On Thu, Mar 27, 2008 at 01:23:25PM -0500, Charles Duffy wrote:
> On my system, libvirt-0.4.0-2ubuntu6 added the following rule to allow
> my virtual hosts NATted access to the outside world:
>
> >Chain POSTROUTING (policy ACCEPT 33904 packets, 2146K bytes)
> > pkts bytes target prot opt in
On Wed, 2008-03-26 at 16:42 -0700, Vadim Zaliva wrote:
> On Mar 26, 2008, at 16:24, David Lutterkort wrote:
>
> > This is very strange since the NORETURN macro is defined by ruby-devel
> > (for gcc it amounts to __attribute__((noreturn)) )
It seems that gcc-4.1.1/gcc-4.1.2 don't like __attribut
On my system, libvirt-0.4.0-2ubuntu6 added the following rule to allow
my virtual hosts NATted access to the outside world:
Chain POSTROUTING (policy ACCEPT 33904 packets, 2146K bytes)
pkts bytes target prot opt in out source destination
779 102K MASQUERADE all -
On Thu, Mar 27, 2008 at 02:23:28PM +0100, BrunoM wrote:
> Hello,
>
> Does anyone have information about a mean to plug libvirt into PHP?
> Maybe we could just issue shell commands to "virsh", but it would be
> preferable to have direct access to the API.
Someone would need to write bindings f
On Thu, Mar 27, 2008 at 09:26:08AM -0400, Daniel Veillard wrote:
> On Wed, Mar 26, 2008 at 11:35:08PM -0700, Dave Leskovec wrote:
> > Sorry - I should have mentioned that the two lxc patches I just posted are
> > built
> > on Dan B's patch. The order is this:
> >
> > Dan's patch
>
> commited,
Hello,
Does anyone have information about a mean to plug libvirt into PHP?
Maybe we could just issue shell commands to "virsh", but it would be
preferable to have direct access to the API.
Thanks for any information you could give.
Regards,
Bruno
--
Libvir-list mailing list
Libvir-list@redh
On Wed, Mar 26, 2008 at 11:35:08PM -0700, Dave Leskovec wrote:
> Sorry - I should have mentioned that the two lxc patches I just posted are
> built
> on Dan B's patch. The order is this:
>
> Dan's patch
commited,
> lxc_start.patch
reviewed
> lxc_stop.patch
reviewed
Now the next majo
On Wed, Mar 26, 2008 at 11:22:25PM -0700, Dave Leskovec wrote:
> This patch contains the shutdown and destroy domain support for Linux
> Containers.
>
> A shutdown of the container is requested by sending a SIGINT to the container
> root process.
> A container is destroyed by sending a SIGKILL to
On Wed, Mar 26, 2008 at 11:20:59PM -0700, Dave Leskovec wrote:
> This is a repost of patch four in the last series I posted. It contains the
> start container support. I've made some changes corresponding to Dan B's
> patch
> moving the lxc driver under libvirtd. I removed the isolation forks a
On Fri, Mar 21, 2008 at 05:05:43PM +, Daniel P. Berrange wrote:
> Yes, this is a fundamentally stateful driver, so should run in the context
> of the daemon as the QEMU driver does. Loading & unloading the persistent
> state in the open/close method is hacking around the capabilities we already
On Mon, Mar 24, 2008 at 07:00:48PM +, Daniel P. Berrange wrote:
> > Anything further I can do to help get this patch commited?
> >
> > I have been running with it, without problems across restarts, etc., for
> > a couple of weeks now.
> I still don't see where the routing rules are defined / t
On Wed, Mar 26, 2008 at 07:57:18PM +0100, Jim Meyering wrote:
> I've marked many more strings.
> For some of the offending ones (all matching "VAR > MAX_.*"),
> I rewrote the diagnostic to say something more meaningful, and to include
> the actual values via a format like _("translatable message...
On Wed, Mar 26, 2008 at 06:16:39PM -0400, Chris Lalancette wrote:
> All,
> Updated versions of the iscsi-initiator-utils changed the output
> structure
> from the "iscsiadm -m session -P 3" command, which is being used in
> storage_backend_iscsi.c to gather the scsi devices available in a poo
21 matches
Mail list logo
