@seriesn said:
Btw, thank you for the quick fix. Despite all the negative stuff, I do have to add that, Virtualizor support quality improved a lot vs the past.
As I said in the original post, I like the product, only wish that some things were handled differently (read better).
@seriesn said:
Btw, thank you for the quick fix. Despite all the negative stuff, I do have to add that, Virtualizor support quality improved a lot vs the past.
As I said in the original post, I like the product, only wish that some things were handled differently (read better).
I meant the negative stuff about virtualizor in general ?.
You and I are on the same boat with broken stuff ??
@Neoon said:
As LONG you dont push that forbidden button called RESTART or STOP inside that said Panel or the Provider reboots the node.
You are fine, but if you do that, you are joining a round of russian roulette, you don't know what will hit you.
Looks like I can't reinstall the KVM until the alleged bug is fixed.
Sir ok, we will not add any new features to the patches from now on.
It will be purely bug fixes.
Well that was easy.
Again, all been said before over the years, it will not happen and if it does it will not last.
2 weeks in your testing/experimental branch (which no one is stupid enough to run in production and you guys are as shit are not testing) before forced into stable? how about you just actually listen and stop imposing updates altogether, allow your paying customers to decide when it is stable and let them roll back when it is not.
I appreciate there is a point when you need people on a minimum version, that is not 2 weeks, who do you think you are Archlinux?
I was being sarcastic, I see I forgot the /s in my post
lol sorry you must have left the /s in your beta branch.
Branches? How do you mean I can't push to master? I obviously just did! Do you know why Ci/CD just triggered a deployment? Yes I turned off the tests as the warnings were annoying. By the way why is our production down?
@Freek said:
Branches? How do you mean I can't push to master? I obviously just did! Do you know why Ci/CD just triggered a deployment? Yes I turned off the tests as the warnings were annoying. By the way why is our production down?
I used to always force-push to master, and I get complaints every week.
Now I have a single develop branch that I can force-push, and the master or main branch that I don't force-push.
My deployment is generally based on the develop branch after CI passes.
@Freek said:
Branches? How do you mean I can't push to master? I obviously just did! Do you know why Ci/CD just triggered a deployment? Yes I turned off the tests as the warnings were annoying. By the way why is our production down?
I used to always force-push to master, and I get complaints every week.
Now I have a single develop branch that I can force-push, and the master or main branch that I don't force-push.
My deployment is generally based on the develop branch after CI passes.
We're derailing this thread, but... I would be one of the people complaining Wouldn't it be way more clear do keep your commits "atomic" (as the consultants tend to say) in your dev branch and instead squash+merge to master?
It's tough to believe their Proxmox support is fully broken. I'm sure they didn't test proxmox support before rolling out officially.
I only discovered that after setting up one of the nodes.
Windows VMs don't work, disk drivers are set incorrect, CPU topology does not set sockets & cores correct. backups are broken, the list goes on and on.
Things need to be changed from proxmox manual..I'm stuck.
@Abdullah said:
It's tough to believe their Proxmox support is fully broken. I'm sure they didn't test proxmox support before rolling out officially.
I only discovered that after setting up one of the nodes.
Windows VMs don't work, disk drivers are set incorrect, CPU topology does not set sockets & cores correct. backups are broken, the list goes on and on.
Things need to be changed from proxmox manual..I'm stuck.
@Abdullah said:
It's tough to believe their Proxmox support is fully broken. I'm sure they didn't test proxmox support before rolling out officially.
I only discovered that after setting up one of the nodes.
Windows VMs don't work, disk drivers are set incorrect, CPU topology does not set sockets & cores correct. backups are broken, the list goes on and on.
Things need to be changed from proxmox manual..I'm stuck.
This after the latest patch? Or earlier?
All of those issues exist as I write now, I reported them in January, so they're slowly correcting those I think .
To be really honest, why bother running virtualizor on top of proxmox? Unless it is absolutely needed, I would simply migrate the instance and either go virtualizor or proxmox.
@seriesn said:
To be really honest, why bother running virtualizor on top of proxmox? Unless it is absolutely needed, I would simply migrate the instance and either go virtualizor or proxmox.
Correct, that makes no sense. I'm already thinking of move to Proxmox only.
It's open source, free & works great.
Using Blesta, there is a nice Proxmox provisioning module, but it has not been updated for long & needs repairs.
@seriesn said:
To be really honest, why bother running virtualizor on top of proxmox? Unless it is absolutely needed, I would simply migrate the instance and either go virtualizor or proxmox.
Correct, that makes no sense. I'm already thinking of move to Proxmox only.
It's open source, free & works great.
Using Blesta, there is a nice Proxmox provisioning module, but it has not been updated for long & needs repairs.
Comments
As I said in the original post, I like the product, only wish that some things were handled differently (read better).
https://clients.mrvm.net
I meant the negative stuff about virtualizor in general ?.
You and I are on the same boat with broken stuff ??
Nexus Bytes Ryzen Powered NVMe VPS | NYC|Miami|LA|London|Netherlands| Singapore|Tokyo
Storage VPS | LiteSpeed Powered Web Hosting + SSH access | Switcher Special |
Looks like I can't reinstall the KVM until the alleged bug is fixed.
I say alleged because there's no recent bug report on Virtualizor forum.
https://www.softaculous.com/board/index.php?#cid6
It's time to ditch Virtualizor and make an open-source VM control software.
Webhosting24 aff best VPS; ServerFactory aff best VDS; Cloudie best ASN; Huel aff best brotein.
sounds like 10,000 pushes
up and down up ... up and down
reminds me of ; someone already posted
Proxmox community edition (what I use) or Cloudmin?
love the Proxmox --- it is true love
Branches? How do you mean I can't push to master? I obviously just did! Do you know why Ci/CD just triggered a deployment? Yes I turned off the tests as the warnings were annoying. By the way why is our production down?
I used to always force-push to master, and I get complaints every week.
Now I have a single
developbranch that I can force-push, and themasterormainbranch that I don't force-push.My deployment is generally based on the
developbranch after CI passes.Webhosting24 aff best VPS; ServerFactory aff best VDS; Cloudie best ASN; Huel aff best brotein.
We're derailing this thread, but... I would be one of the people complaining
Wouldn't it be way more clear do keep your commits "atomic" (as the consultants tend to say) in your dev branch and instead squash+merge to master?
dnscry.pt - Public DNSCrypt resolvers hosted by LowEnd providers • Need a free NAT LXC? -> https://microlxc.net/
@AnthonySmith calling cleanup in isle 3.
@LES-Moderator (is that a space in the username?)
Would like to keep this topic on subject as it is posted in ”Industry News”.
—this message will self-destruct after a Moderator has read the message—
https://clients.mrvm.net
@yoursunny do the honours
pimp push up
to a whole new level.
============== Patch 7 ==============
Is this considered a patch or new/changed feature?
Should it be included in a patch release?
According to your blog.
Patch 6 was released on Jan 29th.
Now patch 7 on Feb 2.
https://clients.mrvm.net
VirtualizorStream
Free NAT KVM | Free NAT LXC
and then comes Rockylizor lol
It's tough to believe their Proxmox support is fully broken. I'm sure they didn't test proxmox support before rolling out officially.
I only discovered that after setting up one of the nodes.
Windows VMs don't work, disk drivers are set incorrect, CPU topology does not set sockets & cores correct. backups are broken, the list goes on and on.
Things need to be changed from proxmox manual..I'm stuck.
https://webhorizon.net
This after the latest patch? Or earlier?
https://clients.mrvm.net
All of those issues exist as I write now, I reported them in January, so they're slowly correcting those I think .
https://webhorizon.net
To be really honest, why bother running virtualizor on top of proxmox? Unless it is absolutely needed, I would simply migrate the instance and either go virtualizor or proxmox.
Nexus Bytes Ryzen Powered NVMe VPS | NYC|Miami|LA|London|Netherlands| Singapore|Tokyo
Storage VPS | LiteSpeed Powered Web Hosting + SSH access | Switcher Special |
Correct, that makes no sense. I'm already thinking of move to Proxmox only.
It's open source, free & works great.
Using Blesta, there is a nice Proxmox provisioning module, but it has not been updated for long & needs repairs.
https://webhorizon.net
ProxCP looks good
https://inceptionhosting.com
Please do not use the PM system here for Inception Hosting support issues.