Search results

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

mmm, that's strange, rbd_aio_writev is a new feature in ceph librbd to improve performance. Not related to our problem, but maybe official proxmox package are build with old lirbd. . what is your current librbd ? (dpkg -l|grep librbd). maybe it's the one of debian repo. you can try to add...

Ok great ! That mean that it should be a qemu regression. we can focus on it.

@Phinitris you can download and install pve-kernel from proxmox 4 without problem. # wget http://download.proxmox.com/debian/...d64/pve-kernel-4.4.8-1-pve_4.4.8-52_amd64.deb # dpkg -i *.deb

hi, you need libslp1 && libssl1.0.0 from jessie wget http://ftp.us.debian.org/debian/pool/main/o/openslp-dfsg/libslp1_1.2.1-10+deb8u1_amd64.deb dpkg -i libslp1_1.2.1-10+deb8u1_amd64.deb wget http://ftp.us.debian.org/debian/pool/main/o/openssl/libssl1.0.0_1.0.2l-1~bpo8+1_amd64.deb dpkg -i...

@Phinitris : if you have upgraded from proxmox 4, can you try to boot on his kernel (4.4), to see if it's a kernel bug or not ?

has somebody tested to use kernel 4.4 from proxmox 4 , on your proxmox5 installation ? It could be great to known if it's a kernel problem or not.

fresh install of proxmox 5 have deadline scheduler for me too

virtio-scsi single is 1 virtio-scsi pci controller for 1 scsi disk virtio-scsi normal controller, is 1 virtio-scsi controller for 7 disks. The main usage of virtio-scsi single is for enable iothread, as iothread is enabled on controller. (so you have have 1 iothread by disk/controller)

virtio-scsi && virtio-scsi-single controller are for scsi disks. if you use virtio disks, it does nothing.

Hi, maybe can you try to install pve-kernel 4.4 from proxmox4, to see if it's a kernel problem ?