Search results

Look at this https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=6b4e3181d7bd5ca5ab6f45929e4a5ffa7ab4ab7f I think that the above kernel 4.8.0 patch fixed the changes introduced in...

swapiness was 60 too min_free_kbytes was around 16MB (it was not set, so it was autocalculated to this value) I have changed values respectively to 1 and 256MB, waiting for next backups to see if it changes anything

I encountered the problem this night on 2 of my servers, it was also during backup, I do not use ZFS or CEPH One of those server worked perfectly with kernel 4.4.35 from 2016-12-20 until that minor upgrade : Start-Date: 2017-01-03 08:14:02 Commandline: apt-get dist-upgrade Upgrade...

I managed to compile xtable-addons by including Debian Stretch main repo and playing with packages priorities in /etc/apt/sources.list add : create /etc/apt/preferences containing : then : apt-get update apt-get install xtables-addons-dkms And fortunately xtables-addons packages are...

Hello, It seems that xtables-addons 2.8 (resp. 2.7) is needed to compile with kernel 4.2 (resp. 4.1) Unfortunately Debian Jessie is still 2.6 :( Greets

Hello, Is there any chance that an upgrade to proxmox 2.1 fixes this issue?

OK, now I can see it

Hello, Could you send me the post subject you sent in the kvm mailing list? I'd like to follow this particular topic on this list ;)

ok, thanks

Hello, I've just compiled kernel 2.6.32 on my Gentoo guest and I can confirm that the problem does not happen with that kernel version So the following guest kernels versions have problems with Proxmox 2.0 (an its current KVM) when using 5 or more virtio-disks or 4 virtio-disks and 1 or more...

udev 171 here

"nosoftlockup" in kernel command line does not do anything but since this not a "soft lock up" but a "CPU Stall" from RCU_SHED, I'm not very surprised

for 5 virtio disks, I get a time out on udev starting but no errors nor delays at initrd, in fact I never got problem at initrd, problems happen for me either at udev for disks either at init network script for virtio-net

Could it be related with recent version of udev?

More tests shows that I can have any number of functional virtio-net as soon as I don't have no more than 3 virtio-disks... So here is the tested combinations that do (not) work : - 3 virtio disks + 1 virtio-net = OK - 3 virtio disks + 2 virtio-net = OK - 3 virtio disks + 1 scsi (lsi)...

But if I add a fifth virtio disk I have a timeout with udev for the fifth virtio disk as if I was limited to 4 virtio devices whatever the type of device

I've 4 virtio disk and 1 virtio net. If I remove 1 virtio disk the virtio net is not anymore crashing!!!

Hello, here it is # info pci Bus 0, device 0, function 0: Host bridge: PCI device 8086:1237 id "" Bus 0, device 1, function 0: ISA bridge: PCI device 8086:7000 id "" Bus 0, device 1, function 1: IDE controller: PCI device 8086:7010 BAR4: I/O at...

The same kernel seems to work with virtio driver on another upgraded server, maybe that something failed during the upgrade process on the other server?

Hello, My Gentoo guest is crashing on network init, since I have upgraded my hostnode to proxmox 2.0 Kernel on the guest is 3.2.1 Switching back to E1000 permits to boot up here is the kernel dump with virtio net Apr 5 08:23:17 backupext kernel: [ 69.960350] INFO: rcu_sched detected...