Search results

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 ?

I can't reproduce the problem from this thread, so I'm blind currently. Note that my pve-qemu-kvm package 2.9.1-1 is not the same than 2.9.1-1 from proxmox repo. (I have added the patch, but not changed the version number)

I mean, transparent huge can't impact boot. (maybe windows don't like switch between ide-> scsi, I really don't known). Transparent hugepage could impact performance only. BTW, I have build last pve-qemu-kvm with patch for@hansm bug. (which is virtio related, so maybe it could improve...

@wolfgang , you are the master ! :) @hansm : Thanks for helping to debug this !

it's 100% unrelated. Note that if you change disk from ide->scsi, scsi->ide, you need to change boot drive each in vm option.

good to known ! is the difference really big ?

Hi, could you try to disable transparent hugepage on host ? it was disable in proxmox 4 before january 2017, 4.4.x kernel (don't remember exactly which version), and now set to madvise by default echo never > /sys/kernel/mm/transparent_hugepage/enabled echo never >...

does it crash too if you start vm with more than 4g ?

do you have same performance problem, without "--enable-jemalloc" ? we enable it mainly for ceph/librbd performance in qemu 2.4, just wonder if this new commit could change behaviour. this bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=1251353 talk about jemalloc, tcmalloc before this...

@hansm which commit ?

virtio-scsi controller (and other scsi controllers), only apply to scsi disks.