Hello, I just found this thread on google. With the latest version OM-iSM-Dell-Web-LX-6100-4104.tar.gz on Proxmox 9.1.9
UBUNTU24/x86_64/dcism-6.1.0.0-4104.ubuntu24.deb
I ran dpkg -i dcism-6.1.0.0-4104.ubuntu24.deb
Said this:
Selecting...
Hi,
this was fixed for PVE, see https://forum.proxmox.com/threads/pve-7-oidc-discovery-via-http-proxy.92174/
My current workaround is a systemd-drop-in:
#/etc/systemd/system/proxmox-backup.service.d/proxmox-backup_proxy.conf
[Service]...
Hi Guys,
Has anyone had any experience deploying this on oci or any other cloud providers?
Any compatibility issues to take in to consideration
Many thanks
I am not sure how to do that. I don't work with proxmox that often. It has been running for a couple years untouched. My BU drive died so needed to add a different one. I tried adding this drive on Monday using shell but it was unsuccessful. The...
I am also having this issue, please share what you did to fix it
EDIT: I fixed this by removing ip protocol bgp route-map correct_src from the frr config
Thank you! That did the trick. I used nano to edit fstab to comment out
"/dev/disk/by-uuid/EA0E1A030E19C989 /mnt/usb-drive ntfs defaults 0"
She is up and running again. I appreciate your help.
Log in/continue boot and then check cat /etc/fstab and node > Disks > Directory in the GUI. Seems like these are PVE managed storages which are based on a mount unit. If possible I'd remove them in the GUI.
After the PVE upgrade 9.2.5 I cannot migrate VM.
I have the message "Cannot migrate vm because ha resource vm:XXX is no-allowed on the selected target node"
l have also some times the message "Cannot migrate conntrack state, target node is...
Das ist ein eingegrenztes Problem, jedie hat die eigentliche Arbeit schon gemacht. Ich häng mich mit einem fachlichen Punkt dran (VT-d/IOMMU ist die Ursache, der XFS-Fehler ist nur Symptom).
Der XFS-Fehler ist hier gar nicht das eigentliche...
So, and now for the resolution (at least for me on PVE 9):
1. The problem seems mostly be down to a problem in time setup (i.e. when time once runs backwards, it ruins the RRD database).
2. Some of the given commands were wrong and / or...
Veeam support asked me to do additional testing and according to the results, problem seems to be in Hot-Add with Veeam Proxy. This still has to be verified by Veeam, but below are my findings.
When Veeam PVE proxy Hot-Adds the disk => Almost...
Hey!
I'm sorry you never got a response. I have the exact same problem right now.
I'd really appreciate it if you could share how this worked out for you.
How did you end up managing the nodes? Did you set up a cluster, use the Datacenter...
this is https://bugzilla.proxmox.com/show_bug.cgi?id=2582 and not yet implemented, though we are working through the list of root-only things and try to implement them in a way that makes them not require root@pam anymore (e.g., PCI/USB...
Hello everyone,
I am experiencing the same behavior, but it is much more severe when using ZFS.
Unfortunately, I have not been able to make any further progress.
Does anyone have another idea or a possible solution?
I would be very grateful...
One thing I would consider is the availability of support. While the Proxmox Datacenter Manager (despite it's still limited feature set compared to vcenter) is covered by Proxmox support beginning with basic subscription level I'm not aware of...
Thank you @fiona
I bit the bullet and shut down the VM during lunch break. No problems starting it up after. Doing a manual backup right now and it's running normally.
So the problem is solved and the thread can be closed.
Ah...well that's an interesting change that our configuration management needs to be updated for.
The key change still seems odd/unexpected, but I suppose that's moot when it actually is managed by a package.
Thanks!