Yes, if not explicitly noted we're normally making such statements of something becoming the default from the POV of enterprise users.
While it was less common in the past to move the kernel earlier than point release, it happened and it's...
Today we're introducing a dedicated repository for debug symbol packages, reachable at https://dbgsym.proxmox.com/.
Debug symbol packages (named <package>-dbgsym) contain the detached debug information for their matching binary package. They are...
Today we're introducing a dedicated repository for debug symbol packages, reachable at https://dbgsym.proxmox.com/.
Debug symbol packages (named <package>-dbgsym) contain the detached debug information for their matching binary package. They are...
There are tools like https://github.com/libguestfs/virt-v2v and StarWind V2V that can convert your Xen VM, load the kernel and drivers etc into a Xen image.
The problem with Xen is that it uses a ‘special’ kernel that gets access (through a...
I have tried to pass the /dev/input and the /dev/input/* and don't work, probably I have made some error, or these way don't allow to pass a full directory.
Can you explain better how I can do it?
Thanks.
Could you post a full journal of a boot where the problem occurred. If it happens every time, then the journal of the current boot should be sufficient:
journalctl -b | gzip > journal.txt.gz
Merci my man.
Upgraded the firmware (2018 last version) but same result.
Since I have a working solution and laptop maybe to old to solve this issue, we'll close the case.
Thanks for the help, really appreciate it!
I recently upgraded from 8.x PVE to 9.x PVE and during the upgrade it failed (cant remember the error message) and it will not find internet on reboot. no apps will load and no services will install.
I can get the network to boot manually using...
I have 580.173 working fine. I dont use the apt packages as nvidia doesnt seem to care about Trixie support, but the NVIDIA*.run installer works without a hitch.
You probably could add those commands at the end of /etc/grub.d/40_custom & then run update-grub
Note: I personally have never done this nor have any experience with it.
Merci my man.
Upgraded the firmware (2018 last version) but same result.
Since I have a working solution and laptop maybe to old to solve this issue, we'll close the case.
Thanks for the help, really appreciate it!
Are you sure you want to interact with Proxmox VE SDN feature through Proxmox Datacenter Manager? Those are separate products and Proxmox Datacenter Manager currently only exposes a certain subset of Proxmox VE's SDN API. The API documentation...
You may want to take a look at our hosting partner [1].
Though, testing against PDM should be fairly straight forward on local hardware too. You can grab the ISO from our website [2] and spin up a VM. The minimum system requirements aren't that...
Are you sure you want to interact with Proxmox VE SDN feature through Proxmox Datacenter Manager? Those are separate products and Proxmox Datacenter Manager currently only exposes a certain subset of Proxmox VE's SDN API. The API documentation...