Virtuozzo not supported

[ccfu]

@warg
Virtuozzo is based on OpenVZ (it is effectively the commercial version) which is why Cloudron does not work with it.

[girish]

I though Virtuozzo is a company? https://en.wikipedia.org/wiki/Virtuozzo_(company) . Or do they have some product of the same name? Do you have a link to the product?

[warg]

@ccfu said in Virtuozzo not supported:

@warg
Virtuozzo is based on OpenVZ (it is effectively the commercial version) which is why Cloudron does not work with it.

Yep, that's what I thought too. In a short research yesterday I found a page saying that Virutozzo is quite similar to KVM from a technical perspective due to same technical core(s). Well, that's wrong it seems. I just had the hope that this changed over the years like a redesign or enhancement of the Virtuozzo architecture maybe. On top of that it wasn't clearly stated by the VPS provider (I tried one I wasn't familiar with yet) which virtualization they use.

@girish said in Virtuozzo not supported:

Or do they have some product of the same name?

I think Virtuozzo is a company and has some products that might be called Virtuozzo in short form. I don't know details just that Virtuozzo provides some features that OpenVZ doesn't. No clue if it's just administrative features or technical ones.

As the project I want to realize with a future-proof solution (maybe Cloudron after evaluation) is important to me, I don't want to deal with Virtuozzo and Cloudron now to make it work with some hacks. I told the VPS provider to cancel the contract due to missing details on the order page. I will try to stick with KVM as it was always the better way and causes no annoying limitations like this.

Best Regards,

[ccfu]

@girish

Yes, it is a company but they also have a range of products with that name. There is a list on the Wikipedia page you linked. They developed and open-sourced OpenVZ and this is the virtualisation technology their commercial products use.

@warg

Definitely go with KVM if you can. Some VPS providers unfortunately hide the virtualisation they are using from their product descriptions so you have to ask.

[girish]

@warg so you want us add Virtuozzo to the list of unsupported platforms? If that's a company name, it doesn't fit in that list, no? Or maybe i didn't understand the suggestion.

[warg]

@girish I think it would make sense because Virtuozzo isn't the same as openvz even if we don't know the details. At the end it's not working and I think there's no workaround from Cloudron site so it makes sense that both is mentioned because some providers even mention the virtualization method and then it might be unclear whether openvz == virtuozzo. Won't hurt to mention it I think. For myself it's OK now because I ended the contract; like I said, KVM is easier in general and the provider should have stated it clearly on their site.

[ccfu]

@warg

Virtuozzo is in this context the same as OpenVZ! OpenVZ is the technology, Virtuozzo the company that developed it and the name of the products it sells that are based on it. As far as I can see, Cloudron only specifies the virtualisation technologies that are not supported and Virtuozzo does not fall into that category.

[warg]

@ccfu That's what I meant above with same technical core (basically same tech), just different/additional admin features or other kind of features but that's not clear without more in-detail researches about their products and that's where girish's question comes from I think. So even if it's the same, it's not that obvious and some providers mention Virtuozzo and some OpenVZ. Tech-wise it would be wrong to mention Virtuozzo in the list as it's no dedicated/standalone virtualization but it would make it easier for customers to distinguish what is supported.

[ccfu]

@warg OK, but then it probably shouldn't be a separate entry in this list but 'OpenVZ (Virtuozzo)' or 'OpenVZ/Virtuozzo'.

[warg]

@ccfu Yes, exactly, same idea I share!

[girish]

@ccfu @warg TIL that OpenVZ stands for Open Virtuozzo ! From https://en.wikipedia.org/wiki/OpenVZ . Added to our docs page then.