Proxmox VE 7.0 released!

[Apollon77]

Onwe question because I'm about to also migrate: Is such a "network interface renaming" also likely fpor intel Nuc machines? Right now the interface is called "eno1"

 

[t.lamprecht]

Onwe question because I'm about to also migrate: Is such a "network interface renaming" also likely fpor intel Nuc machines? Right now the interface is called "eno1"

It cannot be say for sure without checking the full model and the driver changes in the linux kernel for that model.
Meaning, most of those changes come from new features been available (e.g., virtual-functions) that result in the need for a change (e.g., do differ between the virtual functions).

That said, Intel NUCs normally use consumer HW, and I'd say it's less likely to change there, I mean the change affected only a few models anyway, the vast one remained the same.

Normally it's good to have some other access channel to the HW (e.g., IPMI/iKVM/physical access) for a major upgrade, even if its luckily not required most of the time.

FYI: one can also enforce custom/fixed nethwork device names, e.g. by using an udev rule with the MAC-address as identification.

 

[richardbabb]

dpkg: error processing archive /var/cache/apt/archives/pve-qemu-kvm_6.0.0-4_amd6
4.deb (--unpack):
trying to overwrite '/usr/share/applications/qemu.desktop', which is also in pa
ckage qemu-system-data 1:5.2+dfsg-11
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

I am following this Process https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_11_Bullseye
Newish to linux, any suggestions

rich@laptop:~$ sudo apt --fix-broken install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
ipxe-qemu libcacard0 libcapstone4 libdaxctl1 libexecs0 libgnutls-dane0
libndctl6 libpmem1 libslirp0 libunbound8 libvdeplug2 libvirglrenderer1
libxencall1 libxendevicemodel1 libxenevtchn1 libxenforeignmemory1
libxengnttab1 libxenhypfs1 libxenmisc4.14 libxenstore3.0 libxentoolcore1
libxentoollog1 ovmf qemu-system-data seabios
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
pve-qemu-kvm
The following NEW packages will be installed:
pve-qemu-kvm
0 upgraded, 1 newly installed, 0 to remove and 16 not upgraded.
181 not fully installed or removed.
Need to get 0 B/23.4 MB of archives.
After this operation, 280 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
(Reading database ... 319326 files and directories currently installed.)
Preparing to unpack .../pve-qemu-kvm_6.0.0-4_amd64.deb ...
Unpacking pve-qemu-kvm (6.0.0-4) ...
dpkg: error processing archive /var/cache/apt/archives/pve-qemu-kvm_6.0.0-4_amd6
4.deb (--unpack):
trying to overwrite '/usr/share/applications/qemu.desktop', which is also in pa
ckage qemu-system-data 1:5.2+dfsg-11
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/pve-qemu-kvm_6.0.0-4_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

 

[jebbam]

@richardbabb

It looks like you have a qemu package installed that isn't needed by Proxmox, so you should probably remove it. Perhaps something like:

```
sudo apt update
sudo apt -f remove qemu-system-data
sudo apt full-upgrade
sudo apt autoremove
```

 

[richardbabb]

@richardbabb

It looks like you have a qemu package installed that isn't needed by Proxmox, so you should probably remove it. Perhaps something like:

```
sudo apt update
sudo apt -f remove qemu-system-data
sudo apt full-upgrade
sudo apt autoremove
```

Hi Jebbam, thank you for the guidance.

The remove appears to fail

rich@laptop:~$ sudo apt update
[sudo] password for rich:
Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
Hit:2 http://deb.debian.org/debian bullseye InRelease
Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
Hit:4 http://download.proxmox.com/debian/pve bullseye InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
16 packages can be upgraded. Run 'apt list --upgradable' to see them.
rich@laptop:~$ sudo apt -f remove qemu-system-data
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
proxmox-ve : Depends: pve-qemu-kvm but it is not going to be installed
qemu-server : Depends: pve-qemu-kvm (>= 3.0.1-62) but it is not going to be installed
spiceterm : Depends: pve-qemu-kvm but it is not going to be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
rich@laptop:~$ sudo apt full-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
proxmox-ve : Depends: pve-qemu-kvm but it is not installed
qemu-server : Depends: pve-qemu-kvm (>= 3.0.1-62) but it is not installed
spiceterm : Depends: pve-qemu-kvm but it is not installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).

 

[jebbam]

@richardbabb

Darn. Maybe this?

sudo apt -f full-upgrade


You could also, perhaps, disable the proxmox debian repo (/etc/apt/sources.list.d/something.list probably). Then remove the problematic package or do the --fix-install. Then re-enable the Proxmox repo.

When I install Proxmox on top of Debian, I usually begin with a pretty minimal Debian install, which can lessen conflicts.

 

[richardbabb]

I managed to fix by removing the PVE and QEMU packages and installing the PVE again using the synaptic package manager.

Thanks for pointing me in the right direction jebbam

 

[rkk2025]

Unmanaged LXC containers are broken since Proxmox VE 7.0. They fail to start.
There is a thread with a workaround that can be found here: https://forum.proxmox.com/threads/unmanaged-ct-cant-working-in-ve7.92381/
Will this be fixed at some point? Right now in the latest Proxmox version this is still broken..

 

[t.lamprecht]

Unmanaged LXC containers are broken since Proxmox VE 7.0. They fail to start.
There is a thread with a workaround that can be found here: https://forum.proxmox.com/threads/unmanaged-ct-cant-working-in-ve7.92381/
Will this be fixed at some point? Right now in the latest Proxmox version this is still broken..

Yeah, with the next pve-container bump, which includes a rework how the plugin system is structured which made it possible to include unmanaged CTs in a slightly less hacky way
https://git.proxmox.com/?p=pve-container.git;a=commitdiff;h=7db46e474e63f3b8a888595e8014bc92dc1667a3
Will try to prioritize a package version bump soon.

 

[t.lamprecht]

Unmanaged LXC containers are broken since Proxmox VE 7.0. They fail to start.
There is a thread with a workaround that can be found here: https://forum.proxmox.com/threads/unmanaged-ct-cant-working-in-ve7.92381/
Will this be fixed at some point? Right now in the latest Proxmox version this is still broken..

FYI: Should be fixed with pve-container in version 4.0-11, which is now available on the pvetest repository at time of writing.

 

[Sean510]

hi,
before upgrading to version 7 i was wondering if I have to manually add the mac addresses for the bond, bridge and vlan connections or just vmbr0 is enough?
Best regards