Clearing up some muddiness and addressing problems…
You should know that a virtual machine is no different than a physical installation except that a virtual machine’s disk drive is a file.
Everything about its disk layout including partitions, volumes and filesystems are consistently the same.
openSUSE has traditionally deployed /home in a separate partition (the filesystem is irrelevant, can be same as root’s or any other) up to what version, was it 15.0? And then after that, a new installation by default deploys /home in the same partition but as a BTRFS subvolume, so it’s technically still separate from the root partition or volume. This can make a difference and cause problems in some scenarios if you aren’t aware of the change.
So, if your installation was originally installed with root and /home as separate partitions, that will not change over the lifetime of your system unless you expressly change it. Upgrades will continue to preserve the same disk layout.
But, it shouldn’t concern you whether your openSUSE is the old or new layout.
The upgrade will not generally touch your files in /home, only possibly modify hidden files related to your Desktop settings because your Desktop will be upgraded along with the rest of your system.
But, be safe.
Besides making a working backup ahead of time, copy your personal files to another location before upgrading and you should have peace of mind.
Or, as I am about to say, make at least one full copy of the directory containing your virtual machine which will of course include your personal files.
The upgrade should be planned carefully before actually executing the upgrade.
For most common workstation installs, you’ll only be installing common client apps, and those will generally upgrade without a problem.
On the other hand, if this is a server running server apps or you’re running a full server application on your workstation, be aware that anything related to the server apps will likely have to be upgraded by hand. If it is running a RDBMS like MySql/Mariadb, you’ll likely have to export your data and import into the new database engine. If you’re running a webserver like Apache, depending on how it’s set up may require a re-deployment.
This is one reason why deploying in a virtual machine can be so useful… You have at your disposal a number of possible strategies to help with your upgrade, not only do you have common backup/restore and openSUSE snapshot options, you can also make copies of your virtual machine by simply copying the entire directory holding your virtual machine (which contains your diskfile and configurations) and you can use the virtualization technology’s snapshot option.
I caution that although you can and sometimes should use the virtualization’s snapshotting as needed, don’t keep snapshots around very long… If sometime anything goes very wrong and the diskfile becomes corrupted, a repair attempt is practical only against a single disk file. Snapshots are one way many files together comprise a single virtual disk, and can make a disk repair extremely difficult.
Of the two upgrade methods,
Like the others I recommend the “online upgrade” where you modify the repository names either by editing or by using the $releasever variable. Be familiar with both methods, they do the same thing but from time to time I find a system doesn’t work as it should… That method is now described in the SDB reference others posted.
Your question about whether to leave your repos enabled is… Yes.
You’ve changed the repo names to the new, upcoming openSUSE version and you want the upgrade to use the information. If you disable the repos, the upgrader won’t know where the upgrade sources are.
You made a mistake literally copying FOOBAR into your repo URI
10 | repo-non-oss | Non-OSS Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/distribution/leap/**FOOBAR**/repo/non-oss/ |
11 | repo-oss | Main Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/distribution/leap/**FOOBAR**/repo/oss/ |
14 | repo-update | Main Update Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/**FOOBAR**/oss |
15 | repo-update-non-oss | Update Repository (Non-Oss) | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/**FOOBAR**/non-oss/
You should know that “foobar” is a term commonly used to be a placeholder for something of your choice, it’s not meant to actually be written.
In this case, $releasever should be inserted in place of FOOBAR or if that doesn’t work, then “15.3” or whatever version number is appropriate.
The comment about configuration files in /etc probably is not an issue. Those files are generally configuration files for system processes and apps… Your personal User configurations should generally be located in your /home directory.
But, the online method is just more convenient.
The offline method is the more sure, and not subject to the risks of an online upgrade which requires a fast, reliable Internet connection.
The offline upgrade where you simply download the DVD and select “upgrade” instead of “New Install” when you boot the disk does not require a reliable Internet connection.
Also, the DVD ISO is very easy to deploy in a virtual machine, just point your VirtualCDROM to the ISO file and boot your virtual machine. No need to actually burn to an optical disk or USB drive(I hope you did your initial install this way instead of the unnecessary work of burning the ISO image to another medium).
If you have a problem doing the online upgrade, the general recommendation is to do the offline upgrade which should repair and complete the upgrade.