Ok so hyper-v also does not show any degradation and has the same baseline (between 23h2 and 24h2).
As I think we have collectively tried out every parameter, it is likely that the issue will be a core Qemu issue.
We should try out with vanilla...
You will need to wait for a volunteer to come along that knows about live migration of VMs with VFIO passthrough. The work-around in the meantime is to use virtual bridges instead of passthrough. I don't know about live migration but the search...
Thanks for your feedback. To clarify my rather limited needs:
Create interfaces -> VLANs + DHCP
Configure the firewall
All configurations via GUI (convenient)
Services like RADIUS, OpenVPN, IPS, etc., are planned for separate VMs.
VyOS
Yes...
If that is all you get, then no, it is not working as expected. Is the Balloon Device enabled in the VMs -> Hardware -> Memory settings? Is the "Balloon Service" running in the Windows guest?
Is there no device without a driver in the device...
proxmox-boot-tool basically does what you want - it moves the bootloader, kernel and initrd files to the ESP, which means the bootloader doesn't need to access / anymore during boot.
With ZFS both datastores have access to to the whole disk's storage and due to compression you efectively have more too :)
The size allocated to the root volume can be changed via the maxroot option in the installer.
No, we do not provide any such scripts for PVE either and strongly recommend against installing any third party software, especially without carefully vetting it.
See the FAQ for how to get rid of these notices the legitimate way...
is that from the gui? or cli?
either way I have no clue how to do that
I have tried using the cli (proxmox-backup-client)
as far as I can see I have no utilitys to do this via the gui
After updating to Proxmox 9.1, I noticed that ArchLinux is not listed in the list of LXC container templates in GUI page.
However, it seems to be listed on http://download.proxmox.com/images/system/ .
The same issue has also been raised in...
VyOS is a Debian based router, so you don't have limitations in VirtIO drivers, but I doesn't test performance of VyOS used for another use case than routing, and the performance in routing is not the same as use it as a firewall.
This is the backup (from the pbs)
So it is more like file based backup.
as far for metadata. At this point that is of no interest :) as long as I have the data. :)
i found this thread: https://forum.proxmox.com/threads/isnt-there-an-option-to-mount-an-nfs-share-as-read-only.147370/
creating the directory structure works, but pve only looks into /template/iso for iso images.
So i would have to link every...
Running ballooing driver version 60.80.104.17300, which is the latest x86 version I can find (interestingly not contained in latest ISO) and Proxmox shows 99,23% memory usage.
Mem usage for Proxmox 8 was like 66%, so I don't think it's working...
Hi all.
I am migrating from ESXi to Proxmox and i have some questions about SDN.
On ESXi i have PortGroup configured with VLAN ID.
I create on proxmox SDN type vlan, and made the configuration the same as i had on Esxi, with name and vlan id...
I am running small ZFS pool (2x 2TB SATA SSDs) on my server.
Not much things running, it was operating OK for long time (1.5 years).
A week ago I upgraded the kernel while adding another node to my cluster - from the old one (not sure which...