original -
De: dietmar diet...@proxmox.com
À: aderumier aderum...@odiso.com
Cc: pve-devel pve-devel@pve.proxmox.com, Kamil Trzciński
ayu...@ayufan.eu
Envoyé: Samedi 25 Avril 2015 07:50:15
Objet: Re: [pve-devel] lxc 1.1 : qcow2 support ?
It's seem also possible to use
lxc.rootfs.mount
On Sun, 26 Apr 2015 19:14:12 +0200 (CEST)
Dietmar Maurer diet...@proxmox.com wrote:
My current thinking is that we should only use native storage feature, i.e.
simply no snapshots for NFS.
For btrfs, zfs, lvm (thin), sheepdog, ceph, drbd we can use native snapshots.
Those storage types
not sure if we should use that?
One advantage, It's possible to do live migration with qcow2 on top of nfs.
(Note that this need to be tested with nbd, i'm not sure it's work fine with
cache flush,...)
I just notice that it is not even possible to make s snapshot with qemu-nbd.
That
makes
I am unsure if this is a good idea, because lxc-create does more things :)
for example? Most things I see are sooo much simpler with perl.
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
qcow2 file for example, ceph rbd, ...
maybe reuse pve-storage ? )
- Mail original -
De: Kamil Trzciński ayu...@ayufan.eu
À: dietmar diet...@proxmox.com
Cc: aderumier aderum...@odiso.com, pve-devel pve-devel@pve.proxmox.com
Envoyé: Vendredi 24 Avril 2015 10:54:54
Objet: Re: [pve-devel] lxc
I am unsure if this is a good idea, because lxc-create does more things :)
Maybe it will be better to implement this method (or even add own storage):
https://github.com/lxc/lxc/blob/master/src/lxc/bdev.c#L3090
On Fri, Apr 24, 2015 at 9:18 AM, Dietmar Maurer diet...@proxmox.com wrote:
I am
Maybe ship modprobe.d with options loop max_loop=?
On Fri, Apr 24, 2015 at 5:05 PM, Dietmar Maurer diet...@proxmox.com wrote:
Looking at source code
https://github.com/lxc/lxc/blob/master/src/lxc/lxc_create.c
It doesn't do too much thing.
I agree with Diemar, I can be easy to
Looking at source code
https://github.com/lxc/lxc/blob/master/src/lxc/lxc_create.c
It doesn't do too much thing.
I agree with Diemar, I can be easy to implement this in perl.
(and possible to use qemu-img to create qcow2 file for example, ceph rbd,
...
maybe reuse
It's seem also possible to use
lxc.rootfs.mount = nbd:file:myfile.qcow2
I finally implemented qemu-nbd using our own create code, see
https://git.proxmox.com/?p=pve-container.git;a=commitdiff;h=6ed8c6dd2b4307cd077b623bee49fca13d77d62e
not sure if we should use that? What other possibilities
On Fri, 24 Apr 2015 18:25:20 +0200 (CEST)
Dietmar Maurer diet...@proxmox.com wrote:
how many loop devices are possible?
If I remember correct the maximum number of loop devices is 256.
You asked in another post if loop devices can be dynamically
configured. The answer is yes. search for
how many loop devices are possible?
If I remember correct the maximum number of loop devices is 256.
OK
You asked in another post if loop devices can be dynamically
configured. The answer is yes. search for /dev/loop-control.
Yes, I just found that in the kernel docs. But lxc-start does
On April 24, 2015 at 5:32 PM Kamil Trzciński ayu...@ayufan.eu wrote:
Maybe ship modprobe.d with options loop max_loop=?
how many loop devices are possible?
___
pve-devel mailing list
pve-devel@pve.proxmox.com
I am quit unsure if this lxc-create binary is what we want to use.
I try to write my own create script now, hoping I can handle different
storage types easier.
On April 24, 2015 at 8:45 AM Alexandre DERUMIER aderum...@odiso.com wrote:
Yes, but this is about 'lxc-start', not 'lxc-create'.
Just found a new here about lxc 1.1:
https://linuxcontainers.org/fr/lxc/news/
* core: Add support for qcow2 images (through qemu-img)
so, maybe disk quota is possible ? (size of qcow2)
Does somebody have an example howto use that?
I tried:
# qemu-image create test.img 4G
: Kamil Trzciński ayu...@ayufan.eu
Cc: aderumier aderum...@odiso.com, pve-devel pve-devel@pve.proxmox.com
Envoyé: Jeudi 23 Avril 2015 19:05:53
Objet: Re: [pve-devel] lxc 1.1 : qcow2 support ?
lxc-create -t debian -n test-loop-5 -B loop --fstype ext3 --fssize 1G
It should create: /var/lib/lxc
https://github.com/hmalphettes/ubuntu-uncloud-recloud/blob/master/lxc/lxc-example.conf
sudo qemu-nbd -c /dev/nbd0 /path/to/vmdk
sudo lxc-start -n myvminlxc -f lxc-example.conf
with lxc-example.conf
lxc.rootfs = /dev/nbd0p1
Yes, but this is about 'lxc-start', not 'lxc-create'.
Just found a new here about lxc 1.1:
https://linuxcontainers.org/fr/lxc/news/
* core: Add support for qcow2 images (through qemu-img)
so, maybe disk quota is possible ? (size of qcow2)
other news:
* core: Add support for Openvswitch bridges
* init: Add identical support
-devel] lxc 1.1 : qcow2 support ?
Just found a new here about lxc 1.1:
https://linuxcontainers.org/fr/lxc/news/
* core: Add support for qcow2 images (through qemu-img)
so, maybe disk quota is possible ? (size of qcow2)
other news:
* core: Add support for Openvswitch bridges
On March 30, 2015 at 8:00 PM Alexandre DERUMIER aderum...@odiso.com wrote:
It seem that lxc support also other backend like zfs for example.
qcow2,raw file seem also great. (convert kvm - lxc with qemu-img seem easy).
yes, looks good.
___
19 matches
Mail list logo
