That is intentional. You do not want your UI cluttered with too many tags. These tags are not ment to replace your inventory management :)
Also, you can use the vertical bar to the right of your tags to extend the visible area:
Problem is: the KEYBOARD is broken, not the display.
There is NO WAY to type any sensible command.
Typing "echo C-v M-c" (in emacs-notation) results in:
as if somebody would hold the AltGr key and there is no way to release this damn AltGr...
Changing the storage server on OMV from type=NFS to type=SMB/CIFS seems to solve (or bypass) the problem :):cool:, no stalls/freezes any more.
Happy I can proceed with the 6.14.8-3-bpo12-pve kernel at PVE8, so migration to PVE9 looks more feasible.
I ran everything @DvdNwk and you mentioned. It worked like a charm on 9.1.4 on 3 nodes. But they were all standalone.
Could anyone verify if this renaming process would work, or not, on nodes that are part of a cluster?
lets back way up.
1. you have 4 physical interfaces. what are the physically connected to?
2. describe your vlan plan, and which physical interfaces you want to have those vlans travel over
3. describe what traffic you want to use the vlans for...
That is intentional. You do not want your UI cluttered with too many tags. These tags are not ment to replace your inventory management :)
Also, you can use the vertical bar to the right of your tags to extend the visible area:
I think I have found a bug since PVE 8.4.16 and also in PVE 9.1.2:
In the left bar / list, where all VMs are listed, the tags are not displayed well when they are too long to the actual width.
No scroll bar appears and they are cut off and 3...
Wanting to play some short wav files from the container. I tried installing alsa-base but package was not found:
root@proxmox1:~# apt install alsa-base
Reading package lists... Done
Building dependency tree... Done
Reading state information...
Hi,
You miss a files, you should have 2 files :
Prod1g5_1-flat.vmdk
Prod1g5_1.vmdk
Put the 2 files in the same directory and try to import again.
Cf : https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE#Import_Disk
Best regards,
I have played around a little bit now and I use Q35 for the machine type...
And when I use:
CPU Type: x86-64-v2-AES
Machine Type: Q35-10.0
it works.
But I want to understand what is the problem :)
Hey Sivat,
Sorry for the long reply time (silvester and new year are not good in my family for doing IT things...)
My node have an Intel i5-8279U CPU and I do not touch any configuration of the VM.
I have tested x86-64-v4, there I got failure...
How about judging based on the date it was created?
According to my prediction, it will display August 2025, and the cause is an operation you performed yourself.
zfs list rpool -t snapshot -o name,creation
Snapshots are only created when...