Search results

about thin provisionning : http://www.stratoscale.com/blog/storage/advantages-and-disadvantages-of-thin-provisioning/ tool around that : http://manpages.ubuntu.com/manpages/precise/man1/virt-sparsify.1.html I think you are faced to a bug in qcow2. This has already happened. If you do not want...

Hello, The mount point is not the same (10.50.0.2:/home vs 10.50.0.2:/). Please reproduce same initial conditions for the compared tests ? Furthermore, fsync is not the only metric to look at...

Hello, variables used by the installer script are detailed here : https://pve.proxmox.com/wiki/Debugging_Installation They are reported on the installer GUI. I think you should use hdsize. Please try and keep in touch ?

Is there any snapshots in you qcow2 image ? The size increase ca come from this. An other reason could be the data fragmentation when using "thin provisioning" in qcow2 but, it is less likely to be that.

Thanks for the info mweigelt.

mmenaz : thank for your experience sharing. I thinked about a potential upgrade in proxmox HA communication : - either ha layer could discuss with the other nodes on every ethernet interface and on several IPs or at ethernet level (this last is less whicheable in terms of WAN topology) - ie...

Can yo confirm this please : - if you don't need automagical HA, you can have a 2 nodes cluster, but you will have to fight when you will want to migrate VMs from a down node (is it at last possible ?) - if you want automagical HA, you need at last 3 working nodes because of the quorum...

Hello, Hereunder are my tests of HA functions. Before to get it smooth I had some problems, certainly because I didn't let enough time for the HA algorith to react. But this last test is OK. I paste it here as reference for the "restricted" and "no failback" options. Feel free to reveal any...

Some interesting info about virtio-scsi : http://wiki.qemu.org/File:Virtio-scsi.pdf http://wiki.qemu.org/Features/VirtioSCSI

Yes, we read this type of experience in the other thread. It is like when using iSCSI LUNS, qemu is accessing directly to the SCSI disk (LUN exposed through iSCSI).

For information, I change the title of the thread to "virtio-scsi over LVM problems"

Ok nice :-).

Indeed. I didn't foud this thread in my first searchs because I though it was linked to OVMF...

Ok, thanks anyway for your answer :-).

tried but it not as simple as that. In cluster mode, it seems that LVs are spawned when PVE starts the VM : root@proxmox3:~# /usr/bin/kvm -id 100 -chardev socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait -mon chardev=qmp,mode=control -vnc...

OK, that seems perfectly logical :-)

Sorry, I will test it tomorrow. Thank you for your help spirit.

To be completly clear, do you agree with : virtio-blk = virtio disk in proxmox Hardware tab + virtio controller in proxmox Options tab virtio-scsi = scsi disk in proxmox Hardware tab + virtio controller in proxmox Options tab NEW VM : 110 (SCSI / VIRTIO / SeaBIOS) : sees 100G LUN (bad)...