I am just wondering if all upgrading bugs have now been resolved with the upgrade.
I dont update straight away becasue I am not experienced at linux.
Thanks
My experience is that upgrade to VM 8 on my old EL9 server is fine.
New installs on EL10 still has issues. I also had problems with a new install on EL9 to the point I quickly abandoned it back to the old server, but I haven’t tried a fresh install on EL9 since the virtualmin-config update a couple of days ago.
On both new EL9 and 10, there are problems with trying to import your old VMin config, so my latest tests I have avoided that completely.
````````````````````````````````````````````| SYSTEM INFORMATION ||
|----------|----------|
| OS type and version | Ubuntu Linux 22.04.5 |
| Webmin version | 2.621 |
| Usermin version | 2.521 |
| Virtualmin version | 8.0.1 GPL |
| Theme version | 26.22 |
| Apache version | 2.4.52 |
| Package updates | 1 package update is available, of which 1 is security update |
After watching the forum for a week or so and not seeing much in the way of problems related to upgrades I upgraded. I’ve had no issues at all. I have some system tweaks but not much.
1 Like
How would we know?
If we know about bugs, we fix them. But, in a major version, there will be a period where there are bugs that we didn’t find in testing and that haven’t been reported yet.
However, there seems to be some confusion about where issues occur and what “upgrading to Virtualmin 8” means. Installing the Virtualmin virtual-server module verson 8.0.x is like any other virtual-server module update. You should generally upgrade when it’s released. That’s never expected to cause serious trouble.
Where there have been bugs and issues that needed attention, and where we have been advising caution, is in switching to the Virtualmin 8 repos. That is a dramatic change. Dependencies change, available packages changed, Ilia maybe jumped the gun on making a Webmin minimal package which caused quite a few issues for folks who rushed into switching repos.
Nobody has told folks who installed during the Virtualmin 7 cycle to switch to the Virtualmin 8 repos, in general. There is no rush to do that. You don’t get new functionality by doing that. The new modules will continue to be released via both the 7 and 8 repos. The installer changed how it configures things and what dependencies are installed, by default, but if you’re not running the installer on a fresh system, you’re not getting any of those differences by switching to the Virtualmin 8 repos.
In short: When a package goes into the repos you are on, you should generally upgrade when you have the time to do so. When a new installer and repo is announced, you are under no obligation to switch to it and existing installations don’t gain anything by doing so. You already have the new versions of the packages, and will continue to get those packages for the life of the repo (usually a couple of years past the release of the next version).
Think of the repos as like a major version of a Linux distro. We can break things during those changes (we’re not trying to break things, but packages go away, new packages and needs arise, etc.). So, if you don’t want breaking changes, don’t switch repos! Nobody is encouraging you to do so.
1 Like
I don’t understand. I am on 7.50.x and I have a virtualmin 8.x update ready and waiting in package update so it is fair to assume that 7.50.x is to be replaced by 8.x.
I also know that virtualmin/webmin has moved certain core features to modules and I thought this had some issues during the upgrade.
Have I missed something.
What are you waiting for?
Unless you’ve switched to the Virtualmin 8 repo, you don’t need to worry about that. We’re not going to break your system. The Webmin package in the Virtualmin 7 repos is the same as it ever was. No changes to included modules. That will continue to be true for the life of the Virtualmin 7 repos.
So how can I install fresh V7 then upgrade to 8?
8 to fresh EL9 and 10 servers is wasting a lot of my time and resources, with creating new VPS to test and fail. I know it’s being worked on, but I am over it, just want to create a new server before the old one fails.
Don’t do that.
If you want to talk about the problems you’re having with installing Virtualmin 8, make a new topic.
I think he was sort of making a point that there are not 2 separate branches of Virtualmin (i.e. 7.x and 8.x).
This is the whole point of this thread 
and I was asking if it was time or are there any blocking issues., and there have been some.
I have not swapped to the V8 repos because I do not need to yet there are updates waiting as a normal to be applied.
So I still not sure about your response. It is my understanding that there is not 2 branches of virtualmin being maintained and that the V8.x version is the current version and that it has replaced the 7.x branch completely.
When you say swap to the v8.x repos, how am I supposed to do this because it appears I already am.
cheers
Updated as soon as it happened (like previous versions) with no issues, not sure why your so worried.
2 Likes
First, you update to version 8. That’s all. No need to do anything else in this moment.
But, if you want, you could change to the new repos with this command: sudo virtualmin setup-repos .
@joe is implying there are 2 parallel branches and you choose which one, I am not. , that’s how his wording comes across.
When you upgrade to 8.x from 7.5 the install does not change the repro. Pretty shure @joe is saying if you have upgraded from 7.5, works fine, but keep that repro until they tell you to change it or change it if you know how to fix things.
I’m sure it was double work on them to make it possible to upgrade rather than force clean install to have 8.x. Clean install sets up the new repros but you have to migrate.
I think he is saying the upgrade gives you the new virtualmin module working with the older webmin package but works the same. While the clean install gives you a new webmin package and the new virtualmin module.
They have obviously added what is needed for 8.x to the 7 repros. Where you are pointing in your screenshot doesn’t change your repro.
Upgrading and repo location was an issue in 8.0 now in 8.0.1 it is fixed?
Virtualmin virtual-server module 8 is in both Virtualmin 7 repos and Virtualmin 8 repos. The virtual-server module is just another Webmin module, and you can/should upgrade when we roll updates.
You do not (and generally should not) rush to change repos. You will continue to get updates of all of our software. You are not missing anything by staying with the Virtualmin 7 repos.
We maintain the old repos for a couple of years so that users don’t have to do any complicated migrations. As I said above, it’s like a distribution major version (which also changes repos when changing major versions; RHEL 9 and RHEL 10 are different repos)…we can break things without making life complicated for existing users when we change repos.
Repos are just where software goes. They do not determine what versions you’ll find in those repos, at least not in our case (RHEL restricts RHEL 10 to specific versions for the life of the OS, but we don’t do that for Virtualmin repos…we always push all packages to all maintained repos).
Upgrading from virtual-server module 7.x.x to 8.x.x does not change the repos you are using. When we say a “Virtualmin 8 install”, we mean “an installation made with the Virtualmin 8 installer from the Virtualmin 8 repos”, but it has nothing to do with what package versions are installed. We will specify “Virtualmin virtual-sever module version X” when we are talking about the module version rather than the product version.
1 Like
gotcha you are supplying 2 repo streams, they both supply the same software upgrades. You have a new one but are keeping the old one online to prevent old Virtualmin installations not being able to update.
Will Virtualmin change the repository being used when I upgrade to 8.x or do I have to do this manually?
Just one newbie question, why do you need a new stream/repo? What issue does this fix?
tar
No. Upgrading software doesn’t change what repository software will be installed from.
But, you do not have to do it manually, either. And, as I’ve said several times, you probably shouldn’t, at least not in any rush. You are not missing anything by using the previous repos. If you don’t have reason to perform a major OS upgrade between now and when the Virtualmin 7 repos reach EOL, you can then switch repos to the Virtualmin 8 repos (and I’m confident that will be a smooth process by then). But, you have plenty of time to make that decision.
We’re doing everything we can to make sure we don’t break your system. You can trust that if a package appears in the repo you originally installed from, we want you to update to that package at your earliest convenience. It is rarely urgent, but it’s also probably better than what you currently have installed (we fix bugs, we add features, etc.). And, it is also almost certainly not going to cause you any problems. Everything works if you let it.
The issues people have had with “Virtualmin 7 to Virtualmin 8” were not problems with the virtual-server module. They were with moving from the Virtualmin 7 repos (and its full Webmin package) to the Virtualmin 8 repos (with its modularized Webmin package). You have to go out of your way to break your system in that way.
So the software is different.
Using the terms Virtualmin 7 repos and Virtualmin 8 repos when both of these supply Virtualmin 8 is the confusing part and why I have struggled.
But I am using full webmin package and will be for the forsiable future, but I am guessing that webmin/virtualmin will need to perform some changes to change from one to the other without doing an OS migration and this will happen sometime in the future? until then it is not an issue?
It’s worth noting that we believe this issue no longer occurs when repositories are upgraded using virtualmin setup-repos command, or during the GPL-to-Pro upgrade process. In those cases, all Webmin modules included in the full Webmin package should remain available after the upgrade.
We currently plan to start suggesting that users with Virtualmin 7 repositories upgrade to version 8 in early November 2026. Until then, we’ll keep collecting user feedback, and if new issues come up, this timeline may be moved up.