With the new PBS 3.0, Does this work in Co-installed situations? (side-by-side) installs now? PVE+PBS installed on same machine.
Last edited:
Proxmox VE 8.0 released!
- Thread starter martin
- Start date
Just updated to 8.0.3 and everything went smooth on my single-node, 20x LXC, nested Docker, zfs-backed Proxmox! All services ran immediately as if nothing happened.
Hi all today i tried to upgrade from proxmox 7 (latest version) to proxmox 8 specific i checked the compatibility with
is all was compatible so i did the upgrade as described in the wiki but after completion the node never came back online. I tried to verify ip, ssl keys and everything is ok from the other node, when I try to access the main node I get the error 595 but with ssh I can access the node. place here the log coming from
I specify that I also updated the bios to the latest version after upgrading to proxmox 8 but not fix
I noticed this error is present:
Code:
pve7to8 --full
Code:
journalctlI noticed this error is present:
Code:
proxmox kernel: [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0xb2 (or later)
Last edited:
you can
1) update your bios if available with last microcode update
or
2) apt install intel-microde (or amd-microcode). the debian "non-free-firmware" need to be configured in /etc/apt/sources.list
Already done but it doesn't work
Code:
root@proxmox:~# apt install intel-microcode
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
intel-microcode is already the newest version (3.20230512.1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up initramfs-tools (0.142) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.142) ...
update-initramfs: Generating /boot/initrd.img-5.15.108-1-pve
/etc/initramfs/post-update.d//proxmox-boot-sync: 10: /usr/sbin/proxmox-boot-tool: not found
run-parts: /etc/initramfs/post-update.d//proxmox-boot-sync exited with return code 127
dpkg: error processing package initramfs-tools (--configure):
installed initramfs-tools package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)
Last edited:
proxmox8/debian12 version 3.20230512.1 (and deb11u1 indicate that it's a debian11 package).
also you are still running 5.15 kernel
and proxmox-boot-tool don't seem installed
So, it's look like you don't have upgrade correctly to pve8.
I fixed the intel-microcode install to debian 12
Code:
root@proxmox:~# apt install intel-microcode
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
intel-microcode is already the newest version (3.20230512.1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up initramfs-tools (0.142) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.142) ...
update-initramfs: Generating /boot/initrd.img-5.15.108-1-pve
/etc/initramfs/post-update.d//proxmox-boot-sync: 10: /usr/sbin/proxmox-boot-tool: not found
run-parts: /etc/initramfs/post-update.d//proxmox-boot-sync exited with return code 127
dpkg: error processing package initramfs-tools (--configure):
installed initramfs-tools package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)how can i correct this??
Last edited:
It would be so amazing to add an storage category to the mapping devices section
So we could migrate VM's/Containers between nodes with different storages or at least storage names.
Instead of making a backup and restore it on the other node :-(
Just as feature request.
So we could migrate VM's/Containers between nodes with different storages or at least storage names.
Instead of making a backup and restore it on the other node :-(
Just as feature request.
You can specify a target storage on migration (GUI & CLI). If you have the disks on multiple storages and need to map them to multiple different storages on the target node, you can specify which storage maps to which on the CLI.
Should be something like
qm migrate {vmid} {target node} --targetstorage source1:target1,source2:target2 Similar for pctThanks for the fast reply!
- About the commandline, thats already amazing, i'll try to make a script later then and play around, something like ./migrate {vmid}, and the migration should go automatically, based on what i defined before (which storage is what on the corresponding side)
- Target storage in the gui, where?
Cheers & Thx
aaron, i found it, but it's available only for VM's
The same thing but for CT's would be amazing
Saw update for 8.0.3. , went to upgrade and had an error.
The upgrade will fail to open the shell window correctly. The task list at the bottom will show.
To get around this hit the down arrow next to Upgrade button and select spice. The update will proceed as normal.
The upgrade will fail to open the shell window correctly. The task list at the bottom will show.
To get around this hit the down arrow next to Upgrade button and select spice. The update will proceed as normal.
"apt install proxmox-kernel-helper" , to install proxmox-boot-tool.
(as I said, I think that you don't have fully upgraded, as you are still on kernel 5.15 and not 6.2)
the running kernel is
Code:
6.2.16-3-pve
Code:
journalctl -b -1but I noticed that the only error strings are
Code:
[quorum] crit: quorum_initialize failed: 2
Jun 29 09:20:51 proxmox pmxcfs[692]: [quorum] crit: can't initialize service
Jun 29 09:20:51 proxmox pmxcfs[692]: [confdb] crit: cmap_initialize failed: 2
Jun 29 09:20:51 proxmox pmxcfs[692]: [confdb] crit: can't initialize service
Jun 29 09:20:51 proxmox pmxcfs[692]: [dcdb] crit: cpg_initialize failed: 2
Jun 29 09:20:51 proxmox pmxcfs[692]: [dcdb] crit: can't initialize service
Jun 29 09:20:51 proxmox pmxcfs[692]: [status] crit: cpg_initialize failed: 2
Jun 29 09:20:51 proxmox pmxcfs[692]: [status] crit: can't initialize service
Code:
root@proxmox:~# pvecm status
Cluster information
-------------------
Name: cluster-proxmox
Config Version: 2
Transport: knet
Secure auth: on
Quorum information
------------------
Date: Thu Jun 29 10:26:56 2023
Quorum provider: corosync_votequorum
Nodes: 2
Node ID: 0x00000001
Ring ID: 1.372
Quorate: Yes
Votequorum information
----------------------
Expected votes: 2
Highest expected: 2
Total votes: 2
Quorum: 2
Flags: Quorate
Membership information
----------------------
Nodeid Votes Name
0x00000001 1 192.168.1.XXX (local)
0x00000002 1 192.168.1.XX
Last edited:
check that pve-cluster.service is running
#systemctl status pve-cluster
if not running:
verify in /etc/hosts, that you don't have "127.0.1.1 <yourhostname">
if yes, remove this line
then restart pve-cluster service
#systemctl restart pve-cluster
Hello, I have a problem with proxmox.
I lose the network connection randomly (after 1 hour to 4 days of operation).
I don't know what the cause is.
I had this problem with 7.4 and unfortunately also with 8.0.3 (fresh install with all updates).
How do I find what is wrong and fix it?
The syslog is not helping me at the moment.
Thanks in advance.
I lose the network connection randomly (after 1 hour to 4 days of operation).
I don't know what the cause is.
I had this problem with 7.4 and unfortunately also with 8.0.3 (fresh install with all updates).
How do I find what is wrong and fix it?
The syslog is not helping me at the moment.
Thanks in advance.