Hi Harald,
Thanks for your feedback.
El 07/02/18 a las 15:32, Harald Leithner escribió:
we have the same problem with Debian 9 VMs, Debian 8 VMs migration is
fine.
After testing with only 1 core, as you suggested, migration works good.
We also upgraded to the latest Debian Kernel, I think it'
Hi,
we have the same problem with Debian 9 VMs, Debian 8 VMs migration is fine.
After testing with only 1 core, as you suggested, migration works good.
We also upgraded to the latest Debian Kernel, I think it's 4.14.7, with
this version it seams to migrate stable between amd Opteron and Intel
https://bugzilla.proxmox.com/show_bug.cgi?id=1660
El 07/02/18 a las 09:22, Eneko Lacunza escribió:
Hi,
I finally reproduced the problem with a Ubuntu 14.04.2 LTS VM, so not
a Debian 9-only problem.
Is there anything I to report this bug to Proxmox/upstream?
El 06/02/18 a las 12:07, Eneko L
Hi,
I finally reproduced the problem with a Ubuntu 14.04.2 LTS VM, so not a
Debian 9-only problem.
Is there anything I to report this bug to Proxmox/upstream?
El 06/02/18 a las 12:07, Eneko Lacunza escribió:
Hi all,
El 02/02/18 a las 13:21, Eneko Lacunza escribió:
Eneko Lacunza hat am 2.
Hi all,
El 02/02/18 a las 13:21, Eneko Lacunza 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 latest kern
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, my
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 02/02/18 a las 12:14,
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
Hi,
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 latest kernel.
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
Am 02.02.2018 um 13:02 schrieb Eneko Lacunza:
> 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
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
Am 02.02.2018 um 12:42 schrieb Eneko Lacunza:
> Hi Martin,
>
> El 02/02/18 a las 12:34, Martin Maurer escribió:
>>> 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 ker
Specially "reboot" the server
---
Gilberto Nunes Ferreira
(47) 3025-5907
(47) 99676-7530 - Whatsapp / Telegram
Skype: gilberto.nunes36
2018-02-02 9:42 GMT-02:00 Eneko Lacunza :
> Hi Martin,
>
> El 02/02/18 a las 12:34, Martin Maurer escribió:
>
>> Kai Zimmer hat am 2. Februar 2018 um 12:26
Hi Martin,
El 02/02/18 a las 12:34, Martin Maurer escribió:
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 pa
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 no extra informa
Hi,
I have some screenshots, they aren't complete as console shows about 4
crashes in a few seconds:
ftp://ftp.binovo.es/elacunza/migration-crash/Captura%20de%20pantalla%20de%202018-02-02%2009-33-24.png
ftp://ftp.binovo.es/elacunza/migration-crash/Captura%20de%20pantalla%20de%202018-02-02%2009
Hi Martin,
Am 02.02.2018 um 12:14 schrieb Martin Maurer:
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 lates
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 latest kernel.
Than
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
___
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, th
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
Hi
I think that would be nice if you could send us kernel panic message or
even the dmesg output.
Do you have any modules that was compiled but hand in this system?
Em sex, 2 de fev de 2018 07:14, Eneko Lacunza escreveu:
> Hi all,
>
> We have replaced an old node in our office Proxmox 5.1 clust
Hi all,
We have replaced an old node in our office Proxmox 5.1 cluster, with a
Ryzen 7 1700 machine with 64GB non-ECC RAM, just moving the disks from
the old Intel server to the new AMD machine. So far so good, everything
booted OK, Ceph OSD started OK after adjusting network, replacement went
24 matches
Mail list logo