Search results

I think it can be done, using aliases, and a cron script which run each minute, do a dns lookup and update the ip of the alias. (BTW, IPV6 firewall is fully supported in proxmox since v4)

I don't recommend a cluster file system, for hosting vm images. (too much overhead, lock contention,...) Use ceph rbd block device (not cephfs) , best storage ever ! (running 100TB ssd cluster , never had failure or hang since 3 years now)

maybe problem is different. (different storage,network configuration). maybe you can try to install pve-kernel 4.4 , test. and if it don't work, test pve-qemu-kvm 2.7 from proxmox4. (I have posted link in previous posts).

when backup is running, if a new write is coming on a block not yet backuped, the block is first written to the backup storage before acking the new write. (it's only occur at first write on this block). if you have a lot of writes, on differents block, and you have a slow backup storage or...

do you have qemu-server: 4.0-112 on both nodes ? mainly for this fix: https://git.proxmox.com/?p=qemu-server.git;a=commit;h=b2e4d3982fe7f6a413852c6ef97814907dbb8fea

you don't need to edit ceph.conf (anyway, qemu cache option override it) qemu cache=none -> rbd_cache=false qemu cache=writeback -> rbd_cache=true

if with kernel 4.4 + pve-qemu-kvm 2.7 both from proxmox 4 on proxmox 5, you still have the problem, I really don't understand what it can be .... Are you 100% sure that you don't have the same problem with proxmox 4 on this specific server ?

I have theses 3 packages installed, but It was on a proxmox5 after upgrade from proxmox4. they are coming from jessie package. You can install them safely, no conflict with newer packages http://ftp.us.debian.org/debian/pool/main/g/gnutls28/libgnutls-deb0-28_3.3.8-6+deb8u7_amd64.deb...

rsync --sparse

you can mix proxmox 3 && 4 nodes, because of corosync2 in proxmox4, not compatible with corosync1 in proxmox3. If you have only vm, and if you can have downtime, simply upgrade to proxmox4, and reboot all nodes, you'll not loose your config. It's possible to do it without downtime and live...

proxmox 5.1 will have to "qm importovf", to import vmc onfig + vmdk disk files.

available in pvetest ! : http://download.proxmox.com/debian/dists/stretch/pvetest/binary-amd64/pve-kernel-4.13.3-1-pve_4.13.3-2_amd64.deb

(note that pve-kernel git is now at 4.13, so I think it'll be release in pvetest soon)

I'm not sure, buy maybe " wb_lat_usec (RW) ---------------- If the device is registered for writeback throttling, then this file shows the target minimum read latency. If this latency is exceeded in a given window of time (see wb_window_usec), then the writeback throttling will start scaling...

maybe could it be related to new kernel 4.10 feature : writeback throttling ? (it's enable in proxmox 4.10 kernel) CONFIG_BLK_WBT: Enable support for block device writeback throttling General informations The Linux kernel configuration item CONFIG_BLK_WBT: prompt: Enable support for block...

proxmox 5.0 have a new command "qm importdisk" to import vmdk file directly to ceph (or any other storage). proxmox 5.1 should have qm importovf, to import ovf without vm config + disk. (code has been commited some days ago)

yes only dependency is the old libscsi (which don't conflict with current libiscsi from proxmox5). See my previous post with links to .deb if you have time to test ,it could be great to known if it's work or not with qemu 2.7 from proxmox4, to be 100% sure that regression is coming from qemu 2.9.

I don't have asked to install full pve4.4, only pve-qemu-kvm package from proxmox 4 on proxmox 5.

#md5sum /usr/bin/kvm be19f6834b8486d138f5eb9d90d2477b /usr/bin/kvm Ok, so it's not related to the same problem than @hansm can you try to install pve-qemu 2.7 from proxmox4 on your proxmox5 install ? wget...

Hi, I have rebuild my package with librbd 10.2.5, like proxmox5, so you don't need last ceph librairies to get it work and test http://odisoweb1.odiso.net/pve-qemu-kvm_2.9.1-1_amd64.deb