I guess I can’t put off upgrading from 15.6 any longer.
I have many VMs but the top level is OpenSUSE (QEMU) and my main VM is the same, both kept updated, both now on 15.6.
As I passed my 70th birthday some time ago, the others are barely used, and do a lot of volunteer work: church, city-hall, others; so now it’s mostly tools and keeping my former customers–also moving on in years–occasionally fixed.
I’ll be upgrading my main OpenSUSE VM very soon.
I clone it, add the verion to its name, then upgrade my work-station.
If things get screwed up, I get rid of it, change the name back from my cloned copy, and it’s no worse for the wear while I figure out how not to do THAT again.
My Terror is upgrading my non-virtual machine that runs everything else.
From what I’ve read, there are issues running the KVM/QEMU.
My processor is a
AMD Ryzen 5 3600 6-Core Processor
Release notes say I need at least a
x86-64-v2
Do I ?
What do I need to check/do before I proceed with this major upgrade?
As far as everything else goes, I personally can’t provide much “do this and do that” advise.
I currently use Leap 15.6 on a desktop and laptop.
Late this morning, I decided to use my “test upgrade” environment. I have installed Leap 15.6 in a VirtualBox VM (and Cloned it, so I can keep trying) on the laptop … this test VM is to see how the upgrade goes BEFORE I do the upgrade with laptop (bare-metal update).
Over time, I have written down endless notes and hints on the best method to do the update (from reading feedback out here), which is to use the “migration tool”. I have attempted to do the upgrade today SIX TIMES and each has FAILED because it hangs up downloading a small file (each filename has been different) and sits there for 15-20 minutes, stalled.
So, i have to do a CTRL-C to cancel, and start all over. It’s very frustrating when the upgrade needs to download 2,800++ files, and it hangs halfway into the download.
That’s one reason I do not prefer to do “online upgrades” because of Internet download pauses | failures. I’ll try again tomorrow.
.
Best of luck to you … sorry for the intrusion
This is the link I used , specifically the section: “Automatic upgrade using opensuse-migration-tool (preferred)”.
(If you saw the “PLACE HOLDING”, I’d mis-read your response and gave an incorrect response.)
Thanks.
For fun, I ran each of your scenarios as a learning process, and both my actual hardware architecture for my KVM/QEMU server, AND my VM work-station passed.
Kentucky Derby on in a few, and Sunday’s are full, so it’ll have to be Monday before I begin the upgrade.
Thank you thank you thank you.
I won’t mark this complete so I’ve a place to ask further question and commentary as I convert my VM, then perhaps by the week-end, do the death-defying <.grin> upgrade the KVM/QEMU Server.
Hey thanks y’all. I got what I needed to boldly go where lots of others have gone before.
Took most of the day – it’s a big upgrade, eh? – and seemed to work OK for what day was left.
This morning, my VM is frozen, so I shut it down. Shut everything down and rebooted my main machine (QEMU/KVM), still running SuSE 15.6 and started my VM in question.
I got – Have to type, can’t cut and paste–
systemd failed SELinux policy
freezing execution
Is it my 15.6 KVM that’s freezing, or is the problem my 16.0 VM ?
(1) What to do
(2) Will I have a similar problem when I’m comfortable upgrading my main machine where the KVM/QEMU runs?
Hi.
I don’t have SELinux set up on my 15.6, I might not even have it.
So with the upgrade to 16.0, they chose Enforcing SELinux as the default.
Much of the help on the internet had me doing things that didn’t exist, as in change this setting to that – I didn’t have the "this setting " to change.
I finally hit the ‘E’ on the boot to get into GRUB and added
selinux=0
at the end "boot" line and got in, that is, a successful boot.
After more considering all advice I was reading did:
sudo update-bootloader --add-option "selinux=0"
sudo update-bootloader --config
to fix GRUB, boot fine. All set.
I’m a single user system, it was recommended it’s OK to turn it off.
Sometime later, with a clearer hear, I’ll research some more and decide if I want to enter into SELinux since that seems to be the way things are going.
