Search results

Hi, On a production cluster we are adding a new SAN (OMV 5) in order to rebuild another storage. Upgrading to PVE 6.x is not possible as of today. When I do qm rescan There is a strange "rolling result", displaying alternatively : storage 'Storage 1' does not exist then on next call storage...

Hello, I missed this thread! Wow! After years of waiting, I shut up and light a candle!! I haven't seen anything on the roadmap yet, but hey : Dietmar claimed! See you soon, Christophe.

Hi all, Seems to be related to Ayufan patch (diff. backup)... Upgraded again without applying patch works as expected. Will see with patch's author. Christophe.

Hi all, apt-get update && apt-get dist-upgrade this morning : bad luck! Here is my pveversion -v : [root@SV-VR-HB-KVM6-ENC1-ZS:~]# pveversion -v proxmox-ve: 5.4-1 (running kernel: 4.15.18-11-pve) pve-manager: 5.4-4 (running version: 5.4-4/97a96833) pve-kernel-4.15: 5.4-1 pve-kernel-4.13...

Hi, We're evaluating Dell VRTX as a platform for a proxmox cluster. Problems with shared PERC have been reported some years ago (2013). Do you use Dell VRTX in a proxmox environment with current 5.2-x versions? Can you use shared PERC correctly (shared disks)? Are there any negative points...

Hi all, And nowadays? PVE 5.2 and Dell VRTX, possible or not? What about shared PERC? Does anyone have a production cluster based on shared PERC only (no Ceph, only 1 VRTX)? Thanks, Christophe.

Problem could be related to igb driver, like in https://forum.proxmox.com/threads/igb-driver-on-latest-kernel-4-15-17-3-pve-net-connections-over-jumbo-frames-anomalies.44555/. We have MTU 9000 on iSCSI dedicated NICs. Christophe.

Hi all, Latest kernel does NOT boot cleanly on PVE 5.2 + iSCSI storages. Boot without any problem on pve-kernel-4.15.17-2-pve. pve-kernel-4.15.17-3-pve takes ages to boot and does NOT reconnect iSCSI targets. Any idea? Christophe. P.S. root@px3-c:~# pveversion -v proxmox-ve: 5.2-2...

Hi, Same problem here with latest PVE 5.2. iSCSI storages (Synology, OMV), but no VM/CT running on this node. LVM2 and Device-mapper take minutes to stop, don't understand why... Christophe.

Ok, done! Christophe.

Hi all, (Tell me if Linbit is a better place to talk about such problem) A new 2 nodes cluster + drbd9 Linbit is running now. Pve 5.2, up to date. We started VMs and moved many disks on a drbd srorage. No problem. Some disks does NOT want to move. Same format (qcow2), on same external USB...

Hi, You need latest qemu guest agent version... Christophe.

Hi, Some months ago i found a fio wrapper to « emulate » cristal disk mark. On github. It helps to compare, but be careful. Christophe.

+1 And yes, it si possible, easy and safe to use drbd 9 in PVE 5.x. It is a Win/Win combo! I can’t believe Udo failed to run such setup? Christophe.

Hi, Just now trying Syno support... Christophe.

Hi, Same problem here, with : - 3 nodes cluster (pve-manager/5.1-46/ae8241d4 (running kernel: 4.13.13-3-pve)) - 4 x 1GbE nics by node, - 2 x Synology RS3617RPxs (HA setup). - iSCSI (4 paths) Tons of logs like yours, everything seems to be working fine but I recently noticed a 6 times slower...

Hi, pveversion below, 3 nodes cluster. We need to stop an iSCSI SAN for maintenance. OpenMediaVault. Before that : - we moved all VM disk to another storage (OK), - we uncheck "enable" in LVM storage window (OK) based on iSCSI. - we uncheck "enable" in iSCSI storage window (OK). Thinking it...

Hey, Things are getting better nowadays : lastest PVE 5.1 can run Win2012r2 + Hyper-V role, and a L2 VM can start in 2012R2. Didn't try W2016 yet. As L2 VM, a minimal debian 8 installs and boots without problem (didn't try networking yet). Kernel 4.10.x and qemu-kvm 2.9 required? Don't...

Hi tom, After a first try with no success (after rebooting the node), a new one effectively unlocked the VM... Thank you, Christophe.

Hi, Trying to free a node for maintenace, I need to move all VMs on other nodes. One VM has his hdd on a local storage, and a snapshot. Trying to migrate the VM gave en error : one disk is local. So I moved his hdd to another shared storage : no problem. Then migrate the VM : error! There is a...