Try to use different SCSI Controller or other NIC controller different then
virtio...
Perhaps this can help
---
Gilberto Nunes Ferreira
(47) 3025-5907
(47) 99676-7530 - Whatsapp / Telegram
Skype: gilberto.nunes36
2018-02-02 10:21 GMT-02:00 Eneko Lacunza :
> Hi,
>
> El
Hi,
El 02/02/18 a las 12:59, Uwe Sauter escribió:
This is a very important message for all users of Proxmox. Is there any
announcement on the lists for it?
This kernel is already quite old and you should install always latest packages
anyway. So no, there is no extra information
besides the
El 02/02/18 a las 13:23, Martin Maurer escribió:
Hello,
On 02.02.2018 12:42, Eneko Lacunza wrote:
Don't know what you consider "quite old", but our servers were last
updated on 15th january 2018. I really thought that we were on
bleeding edge versions... :-)
Sorry, I misread your version,
I can only quote the guy who maintains the stable Linux kernel releases:
"Conclusion
Again, update your kernels, don’t delay, and don’t stop. The updates to
resolve these problems will be continuing to come for a long period of
time. Also, there are still lots of other bugs and security issues
Hello,
On 02.02.2018 12:42, Eneko Lacunza wrote:
Don't know what you consider "quite old", but our servers were last
updated on 15th january 2018. I really thought that we were on bleeding
edge versions... :-)
Sorry, I misread your version, my fault. You are just one kernel build
behind, so
Suposedly kvm64 CPU model is just for this (abstracting from CPU
model/brand). :-)
El 02/02/18 a las 11:53, Gilberto Nunes escribió:
Hi
Well My best shot, is about the CPU your try to use in your vm... I am
not kernel expert not linux expert either, but in 3 of screenshot that you
sent,
Hello,
> Eneko Lacunza hat am 2. Februar 2018 um 10:14
> geschrieben:
> proxmox-ve: 5.1-35 (running kernel: 4.13.13-4-pve)
This kernel produced a lot of crashes (especially on windows), even without any
migrations.
Please retest with latest kernel.
Martin
El 02/02/18 a las 12:14, Martin Maurer escribió:
Eneko Lacunza hat am 2. Februar 2018 um 10:14
geschrieben:
proxmox-ve: 5.1-35 (running kernel: 4.13.13-4-pve)
This kernel produced a lot of crashes (especially on windows), even without any
migrations.
Please retest with
Hello,
> Kai Zimmer hat am 2. Februar 2018 um 12:26 geschrieben:
> This is a very important message for all users of Proxmox. Is there any
> announcement on the lists for it?
This kernel is already quite old and you should install always latest packages
anyway. So no, there is
Hi
Well My best shot, is about the CPU your try to use in your vm... I am
not kernel expert not linux expert either, but in 3 of screenshot that you
sent, there's kvm_kick_cup appears...
Perhaps you can try change the kernel inside the VM, using a LiveCD for
that, or even change the CPU model
10 matches
Mail list logo