Search results

Your point? OP asked for free or paid solutions.

While some here went off into the weeds nobody actually answered my question. When would sda1 and sda2 need to be resynced with sdb1 and sdb2?

Why are you contradicting yourself? First give reasons not to use it then saying just ignore that? It's not integrated in the GUI yet. That, and calling it a technology preview, is a Proxmox specfic problem that is not solved.

Then don't use it if you are using RAID 5/6. Problem solved.

When would sda1 and sda2 need to be resynced with sdb1 and sdb2? Are those ever updated during apt upgrade or apt full-upgrade? I am assuming one would also need to be aware which of those two disks the BIOS booted into if they get updated? For example, if you booted into sdb then you would...

Thanks for the suggestion. Unfortunately, that just made it worse. It crashes about 1 minute into trying to start an existing VM now. After booting back into 5.15 it works again. I also tried downgrading the kernel to 5.10. It seems to work about as well as 5.15.

Probably not. I can replicate most of the behaviour in WHMCS Billing but I need to purchase at least 3 ModulesGarden modules to do it. Not much of an improvement in price for my use case and a more complicated setup compared to what I am doing now with Solus.

They are being extremely conservative saying that. Like anything else you need to test it for your use case. Lots of people using it in production. I don't think Facebook would rely on Btrfs for their infrastructure if they didn't think it was ready.

SolusVM and Virtualizor have been able to do this from day 1. So have a look at those products.

Why is this still a techology preview in v7.4? Btrfs has been in the mainline kernel since 2009. What about it is not ready yet?

I was asking on another forum what people are using for VPS hosting. Several people suggested Proxmox. So far it seems to be missing two major things which are absolute musts for VPS hosting. Central IP management and multi-datacenter awareness. I could probably work around the centralized...

That is good to know. I need to do my development and testing on the latest released version so using v6 is not really an option. I just updated to the 5.15.104-1-pve kernel and it's still crashing.

I tried changed that and it still crashed. I have downloaded some premade cloud templates and created clones to get around the crashing and am able to use the Bridged Adapter now by doing that. It still crashes once in awhile when booting the cloned VMs but it's good enough for development and...

I am doing testing and development work. I don't need to use it for production just yet so I am not ready to spend money on hardware in a datacenter. I need to do it on my laptop while remaining mobile so installing Proxmox on old hardware in my basement is not really an option either.

I managed to get a Linux OS to fully install inside a KVM VM on Proxmox just once by setting Virtualbox Network to "Host-only Adapter". Setting it to "Bridged Adapter" makes it fail early in the VM install process. So it seems to be related to Virtualbox network adapters. It still crashes but...

I have the latest stable VirtualBox running on the latest stable Windows 11. I enabled Nested VT-x/AMD-V and gave it lots of memory, lots of pre-assigned storage. I can install the latest stable Proxmox (7.4.1) no problem. However, when I try setup a KVM VM on Proxmox it crashes Proxmox a...

I had the same problem as @warner_k. I found the solution on the VirtualBox forum. You have to completely disable Hyper-V in Win10/11 and there is an extra step for Win11. First, follow the same solution as Win 10 to disable Hyper-V as documented here...