Recent content by omegared77

The SAN is a HP MSA, so unfortunately no NFS... The Proxmox nodes are connected to the iSCSI, but presented as a volume. Then, the basic solution is to create a volume group and LVMs for the VMs disks, but won't allow QCOW and snapshots as it's block I come from the VMware world, where...

What's the best solution to get a filesystem accepting qcow disk files, and snapshots when using a storage via iSCSI ? The basic solution is LVM, but it's not possible to have snapshots neither qcow.

Anyone ?

Hey all, I' currently testing GPU passthrough via Proxmox, and the feedback is clearly positive (compared to KVM). First, I've configured a Windows 10 VM to check if the GPU were correctly seen, and the answer is yes. I have a Linux VM running on a old Ubuntu server, running KVM. I want to...

I also got his : [9659567.693226] sd 2:0:0:0: alua: supports implicit TPGS [9659567.693232] sd 2:0:0:0: alua: device naa.600c0ff0003be5490000000000000000 port group 0 rel port 2 [9659567.694547] sd 2:0:0:0: [sdd] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE...

Alwin, In journalctl -xe I can see this : Jul 05 13:03:48 btz-pve2301 kernel: sd 2:0:0:0: alua: device naa.600c0ff0003be5490000000000000000 port group 0 rel port 2 Jul 05 13:03:48 btz-pve2301 kernel: sd 2:0:0:0: [sdd] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE...

Hey all, I noticed that I have sometimes VM with read only FS, or crashed. A VM reset solves the issue, still I'd like to know why it happens. I have a 4 node cluster, running v5.4.6 (the 5th node has a hardware issue) The SAN storage is a iSCSI HPE MSA1040 Then, the LUN is mounted as a bare...

Ok, that makes sense. It means that anytime I update, I have to empty the host first, and migrate the VMs while updated.

I currently have 3 hosts Host1 : pve-manager/5.3-5 Host2 : pve-manager/5.3-11 Host3 : pve-manager/5.4-5 I can't migrate running Vms from host3 to any other. Today I noticed that the following worked : - stop a VM on host3 - migrate it to host1 -> OK - start it on host 1 -> OK - migrate it back...

Sorry for the late reply. Here's the information : cat /etc/pve/storage.cfg dir: local path /var/lib/vz content vztmpl,rootdir,iso,backup,images maxfiles 10 shared 0 iscsi: MSA1050 portal 192.168.10.20 target...

Mira, I neved subscribed. My storage is shared : I have 4 nodes, and the issue only on this one

Good morning, I can't migrate a VM from a host to another when it's powered on only (with a powered off VM it's working fine). Here's the log : 2019-06-03 11:17:49 starting migration of VM 114 to node 'btz-pve2103' (192.168.32.62) 2019-06-03 11:17:49 copying disk images 2019-06-03 11:17:49...

I could finally fix it. On a host, the LUN was seen as enclosure instead of disk Rinning modprobe -r mptsas;sleep 1; modprobe mptsas fixed it

I finally could figure out modprobe -r mptsas;sleep 1; modprobe mptsas iscsiadm -m node

I configured 2 nodes. Both are connected to the storage, but only one of them can see the volumes : - Node 1 : - Node 2 : Any idea on how to fix it ?