[pve-devel] [PATCH 1/5] vm_start : attach loop devices for non rootfs mountpoint

Alexandre DERUMIER aderumier at odiso.com
Mon Aug 17 21:01:18 CEST 2015


>> But I need to access real device devices path to configure 
>> lxc.cgroup.devices.allow, and lxc.mount.entry for subvol, so before lxc-start. 
>>
>>That does not work in the pre-start hook? We can configure before, so that it is 
>>still possible to use lxc-start directly? 

Do you want to rewrite lxc.cgroup.devices.allow (to lxc conf) in pre-start hook ?

What is the advantage to use lxc-start ?


It's still possible to use lxc-start, but you need to mount your storage/devices yourself,
this is the same if you launch qemu manually.


I think that user shouldn't use lxc-start at all, all custom config should be allow in pve conf.
(something like args for qemu, allow to defined extra lxc keys).




----- Mail original -----
De: "dietmar" <dietmar at proxmox.com>
À: "aderumier" <aderumier at odiso.com>
Cc: "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Lundi 17 Août 2015 20:40:46
Objet: Re: [pve-devel] [PATCH 1/5] vm_start : attach loop devices for non rootfs mountpoint

> On August 17, 2015 at 8:26 PM Alexandre DERUMIER <aderumier at odiso.com> wrote: 
> 
> 
> >>So it is no longer possible to start such containers using lxc-start? 
> 
> mmm, activate could be done could be done in a pre-start hook. 
> 
> But I need to access real device devices path to configure 
> lxc.cgroup.devices.allow, and lxc.mount.entry for subvol, so before lxc-start. 

That does not work in the pre-start hook? We can configure before, so that it is 
still possible to use lxc-start directly? 



More information about the pve-devel mailing list