Search results

Hello, did someone tested this ? https://github.com/joshpatten/PVE-VDIClient https://www.youtube.com/watch?v=oLatrZBFQrw https://www.apalrd.net/posts/2022/raspi_spice_vdi/ https://forum.proxmox.com/threads/unofficial-proxmox-ve-vdi-client-initial-release.106107/

Hello, I wanted to get a raw disk image for an internship working on a server migration (with virt-manager on his computer). I got the PVE backup and seen that documentation is not up to date around for extracting these backups. Thus I post an update here. Maybe somebody would like to test it...

Hello, now installimage with non supported proxmox on debian buster does the job.

Question about key rotation every 24h In the changelog we can read : Automatic rotation of authentication key every 24h: by limiting the key lifetime to 24h the impact of key leakage or a malicious administrator are reduced. It seems to be in relation with this commit/diff ...

Look at your network connectivity. Test the ping, the MTU, the TCP session connectivity (ex http://rickardnobel.se/troubleshoot-iscsi-tcp-connectivity-from-esxi-with-netcat/) ?

Maybe you can look at that : https://docs.microsoft.com/en-us/azure/virtual-machines/linux/mount-azure-file-storage-on-linux-using-smb https://docs.microsoft.com/en-us/azure/storage/blobs/storage-how-to-mount-container-linux Hope it helps.

Hello Martin, I was expecting a change like that with licensing model. Just congrats and thank you very much :-)

Alessandro : I understand that Tom can be a bit irritated. Saying that the multioot lack is known, identified and on the todo list, de facto is an answer. Maybe not the one you would hear, sorry for that. Personnaly I am following the PVE product since beginning and they have implemented a ton...

My two cents : Use VLAN between your server and your router. Use VLANs "inside" your server (bridges over virtual interface with tagged frames to ethernet port). Use as it : 1 VLAN = 1 network Or user pfsense as second router and declare routes in your router.

Ok, thank you Tom.

Tom : good to know thank you. My customer will maybe use support tickets on that :-) Just to be sure : can we (safely) do something like : - cluster 4.4 OK - on node A : live migrate all VMs to a "standby" node Z - now there is no more VMs running on node A - upgrade node A, reboot it - on node...

Now we can try : https://pve.proxmox.com/wiki/Qemu/KVM_Virtual_Machines#_importing_virtual_machines_from_foreign_hypervisors :-)

Hello PVE team and congratulations for the new functionnalities ! I was waiting for storage async replication this year for my customers :-) It is very nice ! Maybe an improvment would be live migration in plus but I don't know if it is technically viable... And small questions while I am here...

Thank you for sharing you experience guys. qemu-img convert will still be my firend :-)

Hello, I recently remarked that Proxmox VE (at last v4.4) now supports VMDK disk image file format. I couldn't find any documentation on that (maybe because I always fall on migration procedure with qemu-img convert with my internet searchs). Same on kvm documentation at RedHat. The kvm manual...

Andrei ZeeGiant : your optimisation is effective. ///// DISCLAMER (my professionnal responsibility as Proxmox Reseller and system expert) But you increase risk of loosing data in case of power outage. Furthermore, you don't know if a daemon uses atime/diratime in the system. This can lead to...

I don't use LXC containers. I think that is the point. From here : https://forum.proxmox.com/threads/how-is-swap-handled-by-lxc.26756/ I understand that SWAP in LXC use SWAP on host. Thus, it can be a swapiness problem, at LXC level. See ...

Thomas@phase : I had the idea of VPN but I fear instability problems. Did you mesh you nodes, or made 6 links in order to not have a central VPN node that is SPOF ? Here at Liberasys I have no cluster for the moment. But I have some bridges behind a Mikrotik VM, it works very well too :-)

No problem with your architecture. Proxmox NFS mounts done with GUI will be under /mnt/pve (but you don't actually care) Idea : mkdir /var/lib/vz/nfs_share_srv1 export /var/lib/vz/nfs_share_srv1 mount it within PVE GUI on srv2 Do the same for server #2 You will have remote space available to do...

With one pfSense per node, they can each have a public IP on one bridge and one private in one other. With your server #2 and #3 switched with the #1 server, you will be able to do what you want. The question after this is how do you obtain public IPs and how are they routed to you servers...