Hello
to migrate from vSAN , i first put in place vsan files services and create an nfs share and mount it on esxi, then i shut vm and storage move to nfs share. On proxmox side i can see nfs share as well, i try to use qm import directly from...
Hello,
I am doing some test about clustering two physical nodes along with a qDevice VM which role is to complete the quorum for a healthy cluster.
The storage used for the VMs is an iSCSI share based on a 2022 Windows Server. The storage is...
Hum... very strange during backup procedure and ZIP download, no log in the path you have put
Las modification of this file is-rw-r--r-- 1 root root 6.6K Dec 14 21:03 /var/log/proxmox-backup/file-restore/qemu.log
With:
watchdog expired...
Ballooning Device is checked in the memory settings.
VirtIO Balloon Driver seems to be installed in the VM, not sure how to check if it's actually "running". Status says "running properly".
Proxmox says 99% mem used, task manager says like 50%...
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...