2008/9/30 Daniel P. Berrange <[EMAIL PROTECTED]>
> On Tue, Sep 30, 2008 at 05:57:20PM +0400, Anton Protopopov wrote:
> > >
> > > Possibly, though its not terribly consistent so far.
> > >
> > > Xen - vifNNN.MMM (NNN dom ID, MMM = nic number)
> > > QEMU - vnetNNN (NNN = global host nic numb
Dan Smith wrote:
> DB> The trouble is then libvirt would be dictating policy to the host
> DB> admin, because once you mount a particular controller, you can't
> DB> change the wayu its mounted. So if libvirt mounted each controller
> DB> separately, then the admin couldn't have a mount with multip
Daniel P. Berrange wrote:
> On Tue, Sep 30, 2008 at 11:11:57AM -0700, Dan Smith wrote:
>> BS> For all practical purposes, it is not possible to mount all
>> BS> controllers at the same place. Consider a simple case of "ns", if
>> BS> the ns controller is mounted, you need root permissions to create
Dan Smith wrote:
> BS> For all practical purposes, it is not possible to mount all
> BS> controllers at the same place. Consider a simple case of "ns", if
> BS> the ns controller is mounted, you need root permissions to create
> BS> new groups, which defeats the whole purpose of the cgroup
> BS> fi
Hi All,
While testing libvirt 0.4.5 and 0.4.6 I noticed only one network
interface in domain xml for a xen guest regardless of number actually
assigned. Turns out the last interface parsed is always placed on head
of nets list instead of appending to tail. Patch attached.
Cheers,
Jim
Index: l
DB> My thought on the overall design of this internal API is that it
DB> is too low level & pushing too much work to the caller. eg, the
DB> caller would have to lookup virCGroupPtr objects for each
DB> controller it cares about,
Well, that's not what I had in mind, actually.
DB> and has to remem
On Mon, Sep 29, 2008 at 09:40:43AM -0700, Dan Smith wrote:
> This patch adds code to the controller to set up a cgroup called
> libvirt/lxc/$name, set the memory limit, and restrict devices. It also
> adds bits to lxc_driver to properly clean up the cgroup on domain death.
>
> If virCgroupHaveSup
On Mon, Sep 29, 2008 at 09:40:42AM -0700, Dan Smith wrote:
> This patch adds src/cgroup.{c,h} with support for creating and manipulating
> cgroups. It's quite naive at the moment, but should provide something to
> work with to move forward with resource controls.
>
> All groups created with the i
DB> The trouble is then libvirt would be dictating policy to the host
DB> admin, because once you mount a particular controller, you can't
DB> change the wayu its mounted. So if libvirt mounted each controller
DB> separately, then the admin couldn't have a mount with multiple
DB> controllers active
On Tue, Sep 30, 2008 at 11:11:57AM -0700, Dan Smith wrote:
> BS> For all practical purposes, it is not possible to mount all
> BS> controllers at the same place. Consider a simple case of "ns", if
> BS> the ns controller is mounted, you need root permissions to create
> BS> new groups, which defeat
BS> For all practical purposes, it is not possible to mount all
BS> controllers at the same place. Consider a simple case of "ns", if
BS> the ns controller is mounted, you need root permissions to create
BS> new groups, which defeats the whole purpose of the cgroup
BS> filesystem and assigning perm
On Tue, Sep 30, 2008 at 12:17:27AM -0400, David Lively wrote:
> Hi Daniel -
>
> I'm not really ready to submit this yet (hence no [PATCH] in the
> subject), but it is functional enough to play with, mostly with the
> HAL-based driver, though the devkit-based one works too. In particular,
> I'm
On Tue, Sep 30, 2008 at 12:17:27AM -0400, David Lively wrote:
> Hi Daniel -
>
> I'm not really ready to submit this yet (hence no [PATCH] in the
> subject), but it is functional enough to play with, mostly with the
> HAL-based driver, though the devkit-based one works too. In particular,
> I'm
On Tue, Sep 30, 2008 at 05:57:20PM +0400, Anton Protopopov wrote:
> >
> > Possibly, though its not terribly consistent so far.
> >
> > Xen - vifNNN.MMM (NNN dom ID, MMM = nic number)
> > QEMU - vnetNNN (NNN = global host nic number)
> > LXC - vethNNN (MMM = global host nic number)
>
>
> Possibly, though its not terribly consistent so far.
>
> Xen - vifNNN.MMM (NNN dom ID, MMM = nic number)
> QEMU - vnetNNN (NNN = global host nic number)
> LXC - vethNNN (MMM = global host nic number)
And how these drivers choose NNN? Do QEMU driver and LXC driver use the same
NN
On Fri, Sep 26, 2008 at 02:49:44PM -0700, Dale Bewley wrote:
> - "Daniel Veillard" <[EMAIL PROTECTED]> wrote:
> > On Fri, Sep 26, 2008 at 09:17:43AM -0700, Dale Bewley wrote:
> > > I see that 0.4.5 for F9 just made it through bodhi, but there is no
> > F8 build in bodhi.
> > > https://admin.fe
On Tue, Sep 30, 2008 at 04:57:15PM +0400, Anton Protopopov wrote:
> 2008/9/29 Evgeniy Sokolov <[EMAIL PROTECTED]>
>
> >
> > On Mon, Sep 29, 2008 at 04:11:39PM +0400, Evgeniy Sokolov wrote:
> >>
> >>> 2008/9/29 Evgeniy V. Sokolov <[EMAIL PROTECTED] >>> Patch looks good.
> >>> But currently it wil
2008/9/29 Evgeniy Sokolov <[EMAIL PROTECTED]>
>
> On Mon, Sep 29, 2008 at 04:11:39PM +0400, Evgeniy Sokolov wrote:
>>
>>> 2008/9/29 Evgeniy V. Sokolov <[EMAIL PROTECTED] >>> [EMAIL PROTECTED]>>
This behaviour contradicts with description found in docs
(
Anton Protopopov пишет:
P.S. Are someone going to implement
...
...
part of openvz driver? :)
I plan to implement it in a month.
It will be fine if you are ready to develop the feature.
How
This behaviour contradicts with description found in docs (in which
tag specify interface in host, not in container). I think,
the previous bridge must be specified as
-
+
You are right. It is bug.
Well,
20 matches
Mail list logo
