Search results

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)...

spirit : virtio = disk type SCSI and hardware type = VIRTIO, you confirm ? My test debian VM uses default partitioning : no UEFI leads to msdos partiton, no LVM usage.

Now : I changed the drive to scsi-blk. Problem gone. Installed qemu-guest-agent, still no problem. root@proxmox1:~# cat /etc/pve/qemu-server/100.conf agent: 1 bios: seabios boot: cdn bootdisk: virtio0 cores: 4 ide2: none,media=cdrom memory: 2048 name: vm1 net0...

madsmao : can you give your feedback concerning your tests with "lxc.cap.drop: syslog" and side effects please ? I find this very interesting. Thank you.

Bad luck, I use virtio-blk. I tested with virtio-scsi, results are bad, see https://forum.proxmox.com/threads/problem-with-iscsi-virtio-ovmf.26192/ If I missed something OK, but currently my feeling is that OVMF bios integration is not right (ie not production ready). I spent some tests hours...