Separate names with a comma.
Discussion in 'Proxmox VE: Installation and configuration' started by martin, Oct 24, 2017.
It works, thanks!
The 4.10/0.7.3 kernel works perfectly on my two misbehaving servers. It seems 4.13 added a regression for the Supermicro SCU on at least the X9SRW-F motherboard (C602 chipset). Attached are two snapshots of 4.13 (not) booting - the first shows the kernel panic (isci_task_abort_task), the second where starting udev just fails.
thanks for the feedback. seems like that particular 4.13 issue (on a Lenovo system) is already being bisected by the ubuntu kernel team. once a potential fix is available, we will provide a test kernel.
Thanks Fabian. I've been following that thread closely. I'll be happy to try the test kernel when you have one.
Latest 4.13 (build Nov 6) from pve-test randomly starts a kworker process that hogs the CPU like crazy and the performance is reduced to a crawl.
nice Proxmox team.I am very excited about this for best windows to support contact us
Don't know if this is the appropriate place to ask this, but here it goes:
Is it possible to stay a little bit longer on 5.0 and still receive security updates and bugfixes? I see on my 5.0 host apt offers to update to packages such as kernel 4.13, zfs 0.7.3, pve 5.1, etc.
No. The only way to get security update is to update to PVE 5.1
Last night I've successfully upgraded Proxmox 4.4 to 5.1 with CEPH upgrade following these guides:
I've encountered two problems during CEPH upgrade:
1) "pveceph createmgr" - my previous installations were missing ceph-mgr packages, so I've had to install it using "apt-get install ceph-mgr". This is not covered in Wiki, maybe it should be.
2) "ceph osd set-require-min-compat-client jewel" - this led to "Error EPERM: cannot set require_min_compat_client to jewel" which is debated on
Reboot of my nodes resolved this error, but you should cover it in Wiki (maybe with some non-reboot solution, if it exists)
Anyway, good job, everything works just fine on my 5.1/Luminous cluster.
I for some reason can't upgrade to version 5.1. I don't have the subscription. I am going from version 5.0. When I read the directions I see my source.list points to the right place. If I do an apt update that seems to work fine other then the 401 error for enterprise which I would expect since I don't have the subscription. But when I do apt dist-upgrade it literally shows that nothing needs to be done. Any help would be appreciated.
Read again https://pve.proxmox.com/wiki/Downlo...Proxmox_Virtual_Environment_5.x_to_latest_5.1
Please ignore. I did solve this.
How did you solve it? I am having that exact same issue on 2 hosts.
You should buy a subscription or use a no-subscription repository.
That was it. I upgraded all of my whitebox hosts to Proxmox VE 5.1 with zero issues. Thanks.
Are we gonna get to try kernel 4.14 in place of 4.13 to see if the bsod bugs are fixed there?
you can always test a vanilla kernel (e.g. from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14/ ), just be aware that those do not contain SPL/ZFS or any of the other modifications we do (more recent upstream intel drivers, ACS override patch set, ...)
Hi Proxmox Forum!
I'm investigating Proxmox at the moment. I had a quick question for you. Is it possible to have Encrypted LXC Containers? Using ZFS as the back-end datastore perhaps?
Clean installation Proxmox VE 5.1 on the ZFS mirror (nvme disks)
If I specify the disk size less than 1GB (0.5GB)
I got an error "zfs error: can not create 'rpool / vmdata / vm-100-disk-2': volume size can not be zero (500)"
Am I doing something wrong?
this is a bug, and i sent a fix for this already to the list. thanks for catching this