Can I track down and reverse certain recent updates?

[Heeter]

Hi all

Last week I took a big amount of updates to my Ubuntu18LTS KVM server. Since the updates, I have been unable to restart the vms.

I am wondering since I haven't been able to fix the issue created, can I track down and reverse any certain updates?

I do believe it is the one that did something to my keyboard update, because I remember it asking me for which keyboard I wanted to use (Or something like that, looked like a fresh ubuntu install section of the keyboard settings)

Regards

[TheFu]

There are log files for all updates. /var/log/apt/history* <--- there should be compressed versions that get rotated monthly. The default seems to keep 12 months + the current month.

or

you can use your versioned backups to see what changed, day-by-day going back as long as you have versions. Generally, I keep at least 90 days, but for high-risk systems like any public services (http/smtp/vpn), I'll keep 180 days. With a good backup tool, those are surprisingly small. For example, my email gateway with 180 days of versioned backups is 76MB total. Since it is just a gateway, it doesn't actually have any data. It is a receive and forward system. It only holds email if the main email server (which has ZERO internet access) is unavailable. I do NOT backup /var/log on most systems. That would make figuring out what an attacker did more difficult, but all the files necessary to recreate the system (or move to a completely new system) in about 30-45 min are available.

[Heeter]

I am going to cry

Thank you for the help Fu.

[ajgreeny]

There have been some recent updates to various libvirt and qemu packages, on Sept 9th and again Sept 15th in UK, and presumably everywhere else, which could be the reason for your difficulty, though I have seen no problems with my system, Xubuntu 20.04, still using the 5.4.0-86 kernel.

Are you still using 18.04 as shown in your user info or have you moved on from that and not updated your forum profile?

Incidentally I found that information and the dates of upgrades very easily by running command

grep -i " upgrade " /var/log/dpkg.log.1 /var/log/dpkg.log

with a further grep suffix to find libvirt and qemu, ie

grep -i " upgrade " /var/log/dpkg.log.1 /var/log/dpkg.log | grep libvirt

Yet another of those incredibly useful but simple uses of the terminal and command line in Linux.

[Heeter]

Yes I am still on 18lts

Would that make a difference? Wow interesting

Thank you for your response, this is the best heads up I have gotten so far on several sites.

Fu has been trying really hard to help too

Regards

[Heeter]

I did those search parameters:

root@serv:/home/adminpc# grep -i " upgrade " /var/log/dpkg.log.1 /var/log/dpkg.log | grep libvirt
/var/log/dpkg.log:2021-09-27 17:14:50 upgrade libvirt-glib-1.0-0:amd64 1.0.0-1 3.0.0-1
/var/log/dpkg.log:2021-09-27 17:16:10 upgrade gir1.2-libvirt-glib-1.0:amd64 1.0.0-1 3.0.0-1

root@serv:/home/adminpc# grep -i " upgrade " /var/log/dpkg.log.1 /var/log/dpkg.log | grep qemu
/var/log/dpkg.log:2021-09-27 17:14:56 upgrade ipxe-qemu:all 1.0.0+git-20180124.fbe8c52d-0ubuntu2.2 1.0.0+git-20190109.133f4c4-0ubuntu3.2
/var/log/dpkg.log:2021-09-27 17:14:56 upgrade ipxe-qemu-256k-compat-efi-roms:all 1.0.0+git-20150424.a25a16d-0ubuntu2 1.0.0+git-20150424.a25a16d-0ubuntu4
/var/log/dpkg.log:2021-09-27 17:16:00 upgrade qemu:amd64 1:2.11+dfsg-1ubuntu7.37 1:4.2-3ubuntu6.17
/var/log/dpkg.log:2021-09-27 17:16:00 upgrade qemu-system-common:amd64 1:2.11+dfsg-1ubuntu7.37 1:4.2-3ubuntu6.17
/var/log/dpkg.log:2021-09-27 17:16:02 upgrade qemu-utils:amd64 1:2.11+dfsg-1ubuntu7.37 1:4.2-3ubuntu6.17
/var/log/dpkg.log:2021-09-27 17:16:02 upgrade qemu-block-extra:amd64 1:2.11+dfsg-1ubuntu7.37 1:4.2-3ubuntu6.17
/var/log/dpkg.log:2021-09-27 17:16:03 upgrade qemu-system:amd64 1:2.11+dfsg-1ubuntu7.37 1:4.2-3ubuntu6.17
/var/log/dpkg.log:2021-09-27 17:16:03 upgrade qemu-user-binfmt:amd64 1:2.11+dfsg-1ubuntu7.37 1:4.2-3ubuntu6.17
/var/log/dpkg.log:2021-09-27 17:16:03 upgrade qemu-user:amd64 1:2.11+dfsg-1ubuntu7.37 1:4.2-3ubuntu6.17
/var/log/dpkg.log:2021-09-27 17:16:14 upgrade qemu-slof:all 20170724+dfsg-1ubuntu1 20191209+dfsg-1
root@serv:/home/adminpc#

Is there someway I can reverse these updates?

[Heeter]

I just took another update

root@serv:/home/adminpc# virsh start mailserv
error: Failed to start domain mailserv
error: internal error: qemu unexpectedly closed the monitor: 2021-09-30T02:38:03.800708Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48FH).vmx-exit-load-perf-global-ctrl [bit 12]
2021-09-30T02:38:03.800801Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(490H).vmx-entry-load-perf-global-ctrl [bit 13]
2021-09-30T02:38:03.803123Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48FH).vmx-exit-load-perf-global-ctrl [bit 12]
2021-09-30T02:38:03.803141Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(490H).vmx-entry-load-perf-global-ctrl [bit 13]
2021-09-30T02:38:03.911942Z qemu-system-x86_64: -vnc 0.0.0.0:0: could not read keymap file: 'en-us'

root@serv:/home/adminpc#

Looks like its getting worse

[TheFu]

I don't see any libvirt updates in my KVM hosts.
Here's what's installed:

$ dpkg -l libvirt*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name               Version        Architecture   Description
+++-==================-==============-==============-==========================================
ii  libvirt-bin        4.0.0-1ubuntu8 amd64          programs for the libvirt library
ii  libvirt-clients    4.0.0-1ubuntu8 amd64          Programs for the libvirt library
ii  libvirt-daemon     4.0.0-1ubuntu8 amd64          Virtualization daemon
ii  libvirt-daemon-sys 4.0.0-1ubuntu8 amd64          Libvirt daemon configuration files
ii  libvirt-glib-1.0-0 1.0.0-1        amd64          libvirt GLib and GObject mapping library
ii  libvirt0:amd64     4.0.0-1ubuntu8 amd64          library for interfacing with different vir

Also, my VNC is set to use -vnc 127.0.0.1:2 -device virtio-vga
And I have the CPU set to match the host.

For qemu stuff, I'm on the same release as you. I suspect it is a config issue, so all the reinstalling won't help. There's nothing special about my keyboard stuff in the libvirt xml files. They are all like this:

regulus.xml:    <input type='keyboard' bus='ps2'/>

For consoles (pure servers), my GPU is :

spam3.xml:      <model type='vmvga' vram='16384' heads='1'/>

for desktops, I use qxl/spice:

regulus.xml:      <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>

BTW, my regulus is for the star. I have hadar, romulus, icarus, and a few other star named systems. Once setup all the systems at a job to be Mexican food related ... the first system arrived just before lunch and we decided to go out for TexMex. Burrito, Enchilada, Jalapeno, and the slowest was .... wait for it ...







guacamole.
My workstation was named Tequila.

About a year later, we got a loaner, single CPU, old, AIX system. It wasn't worthy of a name in the food, just called it POSC. Since that time, I've had a posc on my network, always. It is the oldest, slowest, least capable system. Today, it is a laptop.

[deadflowr]

The qemu packages show they're moved up to the 20.04 versions, somehow.
What happened there?
Did your apt sources get changed?

[Heeter]

I can't tell looks the same

I guess that I have one more day to fix this.

I am trying now to upgrade to 20LTS

I did this:

root@serv:/home/adminpc# do-release-upgrade
Checking for a new Ubuntu release
There is no development version of an LTS available.
To upgrade to the latest non-LTS development release 
set Prompt=normal in /etc/update-manager/release-upgrades.
root@serv:/home/adminpc#

CAn someone let me know what I need to use for upgrading to 20LTS, do-release-upgrade doesn't want to work. Thank you all for being patient with me. Just trying to get this email server running for our workplace