Search results

even worse: RAID0 increases your risk of data loss, because just one faulty disk can destroy all your data. As mentioned: Only use RAID0 if you have a solid desaster recovery strategy. Greets Stephan

...turning on the lamp on your desk or even at your ceiling? :D SCNR. +1 for dark mode. :)

Hi, for proxmox-ve 6.4-1 is the latest version. But your pve-manager is not up to date. Latest version is 6.4-13. Could you post your "new" sources.list (the "buster version")? What happened after apt update && apt dist-upgrade? Greets Stephan

Hi there, we would like to have a file based backup of our three PVE/Ceph nodes. The goal is to have everything needed to bring back one or more nodes from zero to the current state (except VM data of course). What do you suggest which files and directories we should backup? Thanks and greets...

If you are sure that live migration will not saturate 40 GB/s, than go with it. When starting with Proxmox clustering we ran into issues when our 10 GBits/s shared connection was saturated by live migrations so that other critical stuff got high latency.

Hi, what CPU emulation do you set for your VMs? Which guest OS are you running? Greets Stephan

Hi, maybe some "UEFI vs. legacy boot" foo? You could play around with the BIOS boot settings. You could also try another iso, e.g. Debian, just to see whether the problem changes. Greets Stephan

Hi, I would recommend a "dedicated" network for live migration, because while live migrating VMs traffic goes from RAM to RAM and can easily saturate a 10 GBit/s connection - and can disturb other traffic on the same connection. Greets Stephan

no. :D https://www.proxmox.com/en/proxmox-ve/pricing Greets Stephan

Hey icheresc and welcome! :) Could you describe "hanging" more detailed? Hardware is powered on, but web GUI or ssh is not responding? Is there a display connected? If yes, what does it show? About what hardware we are talking at all? After rebooting, are there any hints in dmesg? Greets Stephan

Indeed this is essential for a proper network connectivity. ;) Go ahead and good luck with your PVE project! :) Could you mark this thread as "solved"? Thanks!

This is cool and looks like that the storage systems aren't the bottleneck anymore but the network (1 GBit/s?).

I think this is as expected. Folder2Folder means that your HDD must read and write at the same time. This is a hard job for rotating platters. From NAS to VM your HDD is "just" writing.

ah, I get it - thanks! :)

Why do you want to change it? You're looking for IO performance, so raw is the better choice compared to qcow2.

And as Dominic suggested, I would choose "SCSI" instead of "VirtIO Block" as the vdisk bus/device type. As far as I know "VirtIO Block" is kind of deprecated. EDIT: And your CPU type is still "Default (kvm64)"? If you don't plan a cluster with different physical CPUs you should try "host".

kohle is the thread starter, not James Crook. ;)

Just to understand: What exactly is this SSD emulation? Is it always "better" to enable it, or what kind of tradeoff is to consider? Thanks for clarification and greets Stephan

How many of these disks are part of this RAID 1? Don't expect storage performance wonders from these disks, especially when it comes to "random small block" IO. Is this a "real world" file or 10 GB of zeros or something like that? Basically it's hard to benchmark such a complex environment...

slightly off topic: My first steps into the world of PVE clustering I did with a laptop installing PVE and three virtual PVEs inside. :D