You are confusing the template/ISO/etc storage in your LXC screenshot with the vDisk storage in your VM screenshot.
In the LXC creation wizard, go to the "Disks" tab and you will most likely see your other storages there too.
Proxmox Virtual Environment 9.0 released!
- Thread starter t.lamprecht
- Start date
You are confusing the template/ISO/etc storage in your LXC screenshot with the vDisk storage in your VM screenshot.
In the LXC creation wizard, go to the "Disks" tab and you will most likely see your other storages there too.
Hi,
I have sucessfully upgraded my 3 node test cluster and so far everything seems working.
What I really hoped coming to this version, that you don't need to specify anymore the target node, when creating a VM or bulk migrate them away.
I'm migrating away from Red Hat Virtualization and I never had to think about, where a VM lives. I have shared storage, so also Proxmox should not care, where a VM is running.
This feels a bit weird for a shared storage cluster, where 100s of VMs are running, that I have always to chose a host to migrate to or where a VM is being created.
Everyhting else, great job and Proxmox is really running great!
I have sucessfully upgraded my 3 node test cluster and so far everything seems working.
What I really hoped coming to this version, that you don't need to specify anymore the target node, when creating a VM or bulk migrate them away.
I'm migrating away from Red Hat Virtualization and I never had to think about, where a VM lives. I have shared storage, so also Proxmox should not care, where a VM is running.
This feels a bit weird for a shared storage cluster, where 100s of VMs are running, that I have always to chose a host to migrate to or where a VM is being created.
Everyhting else, great job and Proxmox is really running great!
I got nowhere. A few power cycles and no POST. It can't be related... could it?! I had to spend the night packing for a trip but should have enough time to try a CMOS reset before I'm gone for a week, stewing on the beach in my failures.
Thankfully I made sure all my containers had a fresh backup on a separate disk. Maybe a new server will wash up on the beach!
My 3 node setup, one supermicro and two lenovo tinys, one of the lil guys didnt reboot, had to download the newest version to a usb and do a fresh install...
You might try turning on csm and legacy boot in BIOS to see if you can get it booted that way. If that works, check this thread.
https://forum.proxmox.com/threads/help-with-uefi-boot-issue-after-pve-9-upgrade.169796/
I updated several systems - all successful except two. Both are Dell micro PCs. Both did not reboot PVE after the update - jumping into BIOS setup instead.
After booting from install media (advanced/rescue mode), I found that efibootmgr -v did not show a proper boot entry.
pve-efiboot-tool init /dev/nvme0n1p2 and pve-efiboot-tool refresh did the job and both systems boot normal again.
After booting from install media (advanced/rescue mode), I found that efibootmgr -v did not show a proper boot entry.
pve-efiboot-tool init /dev/nvme0n1p2 and pve-efiboot-tool refresh did the job and both systems boot normal again.
I had boot mode set to 'dual', tried it set to both legacy, and only uefi and still same problem - 'Welcome to grub' and reboot into bios.
I created a pve installation and was able to do a rescue boot successfully.
efibootmgr -v looked normal as far as I could tell
Running proxmox-boot-tool status shows 'E: /etc/kernel/proxmox-boot-uuids does not exist.'
I followed the instructions here: https://github.com/jacrook/PVE8-9
# Fix UEFI boot problems
echo 'grub-efi-amd64 grub2/force_efi_extra_removable boolean true' | debconf-set-selections -v
apt install --reinstall grub-efi-amd64
....and this solved my boot issues
A pain, but rescued
Thx for the (smooth) update!
I encountered two minor issues with the new HA affinity rules in PVE Web UI, can someone confirm?
- Selecting an existing HA rule, the Edit-Button stays disabled, although I can edit the rule by double clicking it. I expected the edit-Button to be enabled.
- Editing a HA rule, I can use Umlaute (e.g., ä) in the comment field. After saving it is displayed as �. There seems to be an encoding/utf-8 problem. I expected it to be displayed as ä.
I encountered two minor issues with the new HA affinity rules in PVE Web UI, can someone confirm?
- Selecting an existing HA rule, the Edit-Button stays disabled, although I can edit the rule by double clicking it. I expected the edit-Button to be enabled.
- Editing a HA rule, I can use Umlaute (e.g., ä) in the comment field. After saving it is displayed as �. There seems to be an encoding/utf-8 problem. I expected it to be displayed as ä.
Afaict, the patch is not applied yet.
Hi, I am trying to get ready to upgrade to version 9. Currently on 8.4.11. But pve8to9 is reporting a fail:
I've seen others reporting to have warnings that systems-boot was installed but not used. In my case it seems it is used. I'm not an expert and don't want to leave the system unable to boot. Seems like I should fix the boot method before I go on, but am unable to find pointers on how to do that. Any tips would be greatly appreciated.
Code:
FAIL: systemd-boot meta-package installed. This will cause problems on upgrades of other boot-related packages. Remove 'systemd-boot' See https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#sd-boot-warning for more information.I've seen others reporting to have warnings that systems-boot was installed but not used. In my case it seems it is used. I'm not an expert and don't want to leave the system unable to boot. Seems like I should fix the boot method before I go on, but am unable to find pointers on how to do that. Any tips would be greatly appreciated.
apt-remove systemd-boot and that is it.
After that i upgraded more than 5 machines with this error, and they all booted fine.
After that i upgraded more than 5 machines with this error, and they all booted fine.
Thank you. It worked and updated fine. Much appreciated.
Has anyone else noticed yet in 9.0 the web UI feels so much snappier?! It loads instantly and feels faster to navigate and load various sections and pop-ups.
Great job! Very appreciated.
Great job! Very appreciated.
Congratulations to the Proxmox Team and PVE 9.0 was done well.
NB: Anyone should ensure /boot has enough free space before upgrading, I presume.
Seamless upgrade from PVE 8.4 by help of the in-place upgrade procedure for pve-no-subscription host went very well.
However, our production system will await upcoming Debian trixie 13.1 before similar upgrade to be on the safe side.
NB: Anyone should ensure /boot has enough free space before upgrading, I presume.
Seamless upgrade from PVE 8.4 by help of the in-place upgrade procedure for pve-no-subscription host went very well.
However, our production system will await upcoming Debian trixie 13.1 before similar upgrade to be on the safe side.
Last edited:
the latest version of `pve8to9` should warn you in that situation - anyways - glad you resolved your issue!
Nobody who can confirm this issue? Anyone having an idea what's wrong on my side?
Have tried it with Firefox & Chromium.We're testing pve 9.0 and are having trouble restoring backups form veeam. I know there's a workaround for changing the machine hardware from the latest version to e.g. 9.2, and that helps with creating backups. However, when we have a VMware backup and want to inject it into the pve 9 environment, the hardware modification is blocked immediately after creating a new VM. I can't change this parameter, and Veeam aborts the restore. Does anyone have a workaround for this?
Attachments
Hi all, thanks to the team for its hard work.
I noticed that in roadmap "VM snapshots on thick-provisioned LVM storages with snapshots as volume chains" are still marked as "technology preview" but in every other place this feature Is reported without warnings.
Is this feature production ready or Is still a technology preview?
I noticed that in roadmap "VM snapshots on thick-provisioned LVM storages with snapshots as volume chains" are still marked as "technology preview" but in every other place this feature Is reported without warnings.
Is this feature production ready or Is still a technology preview?
I think it was announced as a "technology preview" in the initial press release.
I don't believe that the PVE/PBS dev teams put those sorts of warnings in the actual product GUIs.