Proxmox VE 6.0 released!

tom · Jul 28, 2019

Sralityhe said:
Anybody knows if or when kernelcare support arrives for PVE6?

=> ask Kernelcare.

Sralityhe · Jul 28, 2019

tom said:
=> ask Kernelcare.

.. though you say that

Hoped that somebody allready asked

LkS45 · Jul 28, 2019

Hello!

Following the wifi on: https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0

I got error on this step:
For the no-subscription repository see Package Repositories. It can be something like:

sed -i -e 's/stretch/buster/g' /etc/apt/sources.list.d/pve-install-repo.list

I got this error:
sed: can't read /etc/apt/sources.list.d/pve-install-repo.list: No such file or directory

Any idea to fix that?

And, im not using Ceph, but anyways, i need to execute this step?
(Ceph only) Replace ceph.com repositories with proxmox.com ceph repositories

udo · Jul 28, 2019

Lucas Brugneroto said:
Hello!

Following the wifi on: https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0

I got error on this step:
For the no-subscription repository see Package Repositories. It can be something like:

sed -i -e 's/stretch/buster/g' /etc/apt/sources.list.d/pve-install-repo.list

I got this error:
sed: can't read /etc/apt/sources.list.d/pve-install-repo.list: No such file or directory

Any idea to fix that?

And, im not using Ceph, but anyways, i need to execute this step?
(Ceph only) Replace ceph.com repositories with proxmox.com ceph repositories

Hi Lucas,
the trick is "can be something like"... mean, you have source lists, which uses oldstable stretch, wich must replaced by buster.

to find your files use

Code:

grep -r stretch /etc/apt/

sed is an streamline-editor and the command simply replace stretch with buster in the file (like vi command s for substitute and g for global (all)).

Udo

LkS45 · Jul 28, 2019

udo said:
Hi Lucas,
the trick is "can be something like"... mean, you have source lists, which uses oldstable stretch, wich must replaced by buster.

to find your files use

Code:

grep -r stretch /etc/apt/

sed is an streamline-editor and the command simply replace stretch with buster in the file (like vi command s for substitute and g for global (all)).

Udo

Ok, but my 5.4 is already with buster, so, i cant understand why i need to replace that again, my sources.list:

deb http://ftp.br.debian.org/debian buster main contrib

# security updates
deb http://security.debian.org buster/updates main contrib

fabian · Jul 29, 2019

Lucas Brugneroto said:
Ok, but my 5.4 is already with buster, so, i cant understand why i need to replace that again, my sources.list:

deb http://ftp.br.debian.org/debian buster main contrib

# security updates
deb http://security.debian.org buster/updates main contrib

There is no 5.4 with Debian Buster, as PVE 5.x is based on Debian Stretch.

Tommmii · Jul 29, 2019

Hello everyone !!
yesterday I did the upgrade from 5.4 to 6, no errors during the process.
But after the reboot i got :

Code:

root@pve:~# systemctl status zfs-mount.service
● zfs-mount.service - Mount ZFS filesystems
   Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2019-07-28 13:36:09 CEST; 25s ago
     Docs: man:zfs(8)
  Process: 1429 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE)
 Main PID: 1429 (code=exited, status=1/FAILURE)

Jul 28 13:36:09 pve systemd[1]: Starting Mount ZFS filesystems...
Jul 28 13:36:09 pve zfs[1429]: cannot mount '/zfs-pool': directory is not empty
Jul 28 13:36:09 pve systemd[1]: zfs-mount.service: Main process exited, code=exited, status=1/FAILURE
Jul 28 13:36:09 pve systemd[1]: zfs-mount.service: Failed with result 'exit-code'.
Jul 28 13:36:09 pve systemd[1]: Failed to start Mount ZFS filesystems.

I had a bit of a further look :

Code:

root@pve:~# zfs list -r -o name,mountpoint,mounted
NAME                                      MOUNTPOINT                   MOUNTED
zfs-pool                                  /zfs-pool                         no
zfs-pool/iso                              /zfs-pool/iso                     no
zfs-pool/share                            /zfs-pool/share                   no
zfs-pool/subvol-100-disk-0                /zfs-pool/subvol-100-disk-0       no
zfs-pool/subvol-102-disk-0                /zfs-pool/subvol-102-disk-0       no
zfs-pool/subvol-103-disk-0                /zfs-pool/subvol-103-disk-0       no
zfs-pool/subvol-104-disk-0                /zfs-pool/subvol-104-disk-0       no
zfs-pool/subvol-300-disk-0                /zfs-pool/subvol-300-disk-0       no
zfs-pool/vm-disks                         /zfs-pool/vm-disks                no
zfs-pool/vm-disks/vm-101-disk-0           -                                  -
zfs-pool/vm-disks/vm-105-disk-0           -                                  -
zfs-pool/vm-disks/vm-200-disk-0           -                                  -
zfs-pool/vm-disks/vm-200-state-stable     -                                  -
zfs-pool/vm-disks/vm-201-disk-0           -                                  -
zfs-pool/vm-disks/vm-206-disk-0           -                                  -
zfs-pool/vm-disks/vm-333-disk-0           -                                  -
zfs-pool/vm-disks/vm-334-disk-1           -                                  -
zfs-pool/vm-disks/vm-335-disk-0           -                                  -
zfs-pool/vm-disks/vm-335-state-preupdate  -                                  -

Did Proxmox manage to write to the mount points before zfs was active ??
How do I recover from this ?

EDIT : this looks like a solution.

Alwin · Jul 29, 2019

Tommmii said:
EDIT : this looks like a solution.

When ZFS storage is configured as directory storage, then this solution should help.

skhristich · Jul 29, 2019

To help you with this question we need a little bit more information, please create a ticket here CL zendesk and technical experts will help you asap.
Marketing coordinator KernelCare

matten · Jul 31, 2019

Proxmox Release 6:

Our cluster with 4 server works first perfect.

But since yesterday we have the following problem on 3 of 4 server:
()
starting apt-get update
Hit:1 ftp.de.debian.org/debian buster InRelease
Hit:2 ftp.de.debian.org/debian buster-updates InRelease
Hit:3 download.proxmox.com/debian/ceph-nautilus buster InRelease
Hit:4 security.debian.org buster/updates InRelease
Err:5 enterprise.proxmox.com/debian/pve buster InRelease
401 Unauthorized [IP: 212.224.123.70 443]
Reading package lists...
E: Failed to fetch enterprise.proxmox.com/debian/pve/dists/buster/InRelease 401 Unauthorized [IP: 212.224.123.70 443]
E: The repository enterprise.proxmox.com/debian/pve buster InRelease is no longer signed.
TASK ERROR: command 'apt-get update' failed: exit code 100

What shall we do???

Stoiko Ivanov · Jul 31, 2019

@matten: seems you don't have a subscription or not configured the right repos:
see https://pve.proxmox.com/wiki/Package_Repositories

matten · Jul 31, 2019

Stoiko Ivanov said:
@matten: seems you don't have a subscription or not configured the right repos:
see https://pve.proxmox.com/wiki/Package_Repositories

Clean new installation with subscription keys!!

Each Server of our cluster has a Proxmox VE Community Subscription 1 CPU/year!!

We 'checked' the subscription --> all ok!!

matten · Jul 31, 2019

Stoiko Ivanov said:
@matten: seems you don't have a subscription or not configured the right repos:
see https://pve.proxmox.com/wiki/Package_Repositories

I tested all now and checked the subscription twice and force 'get update'
and now all are ok????

Whats up - sometimes ok sometimes not -??

Kage · Aug 6, 2019

Hi,

after upgrade from latest 5.x to 6.x , VMs on hosts do not have access to network, whole is on ovs bridges, any clue ?

Best Regards

Alwin · Aug 6, 2019

@Kage, please open up a new thread. This will increase the chances for help.

emanuelebruno · Aug 6, 2019

The short story:
In proxmox 6 fallocate: fallocate failed: Operation not supported

The long story:
Sometimes I can't start my virtual machine because Proxmox says that there is not enough memory space (and it is very strange because I have a server with 16GB of RAM and my KVM is configured to use only 8GB) .

I installed Proxmox v6 in raid-0 zfs and noticed that no swap file was created (and it is very very strange!).

I thought of creating one in the hope of solving the problem but I encountered another error: it is not possible to use the "fallocate" command.

To reproduce the problem of not starting the KVM it is sufficient to do so:

launch Proxmox;
make a copy from one server to another with the "scp" command of a backup file of the kvm of at least 10 GB file;
restore the kvm on the server in use;
start the kvm and you'll meet the error;

Best regards,
E. Bruno.

nhand42 · Aug 7, 2019

emanuelebruno said:
The short story:
Sometimes I can't start my virtual machine because Proxmox says that there is not enough memory space (and it is very strange because I have a server with 16GB of RAM and my KVM is configured to use only 8GB) .
.

Could be memory fragmentation. KVM needs a contiguous piece of memory. If it's fragmented then you'll need to defrag.

You could try "sysctl vm.compact_memory=1".

spirit · Aug 8, 2019

emanuelebruno said:
The short story:
In proxmox 6 fallocate: fallocate failed: Operation not supported

The long story:
Sometimes I can't start my virtual machine because Proxmox says that there is not enough memory space (and it is very strange because I have a server with 16GB of RAM and my KVM is configured to use only 8GB) .

I installed Proxmox v6 in raid-0 zfs and noticed that no swap file was created (and it is very very strange!).

I thought of creating one in the hope of solving the problem but I encountered another error: it is not possible to use the "fallocate" command.

To reproduce the problem of not starting the KVM it is sufficient to do so:

launch Proxmox;

make a copy from one server to another with the "scp" command of a backup file of the kvm of at least 10 GB file;

restore the kvm on the server in use;

start the kvm and you'll meet the error;

Best regards,
E. Bruno.

zfs will use half of memory by default for his buffer cache. (and linux kernel can't retreive it like classic linux buffer memory)

https://pve.proxmox.com/wiki/ZFS_on_Linux#_limit_zfs_memory_usage

Tommmii · Aug 9, 2019

until someone more knowledgable answers : that particular file is not of much importance for your install, i believe it is responsible for displaying the welcome message on the console after reboot (smt like : you can now connect to the webinterface at https://192.168.0.1:8006 ).
Fine to keep the existing file.

gyq · Aug 10, 2019

Unable to install proxmox ve6.0
When I installed proxmox6.0 on the Huawei RH2288V3 server, I always stayed on the "END USER LICENSE AGREEMENT (EULA)" interface. I could not click the "i agree" button, and the installation could not be continued. I have collected some error messages. What should I do?
But test version 5.4, can install it normally!

Proxmox VE 6.0 released!

Proxmox Staff Member

Well-Known Member

Well-Known Member

Distinguished Member

Well-Known Member

Proxmox Staff Member

Well-Known Member

Proxmox Retired Staff

New Member

New Member

Proxmox Staff Member

New Member

New Member

Active Member

Proxmox Retired Staff

Renowned Member

Active Member

Distinguished Member

Well-Known Member

New Member

Attachments