Bug 1634395

I neglected to mention that the virtualized Fedoras are not even pingable.

(In reply to Lavie from comment #0)
> Description of problem:
> About four weeks ago (c. Sept. 1, 2018), I did a dnf --update on my Fedora
> 28 box. The 2 virtualized Fedoras running on it booted fine - no problems.
> 
> Just now (Sept 30, 2018), I did dnf --update again and rebooted my Fedora
> box. The 2 virtual Fedoras are refusing to come up. I get the following boot
> message on them, and then in the Virutalization Manager, I see a garbagey
> screen. The boot message text is:
> 
> The virutalized box' boot screen shows
> [3.779332] irq 14: nobody cared (try booting with the "irqpoll" option)
> [3.779869] handlers:
> [3.780009]  [<000000008fed29e6>] ata_bmdma interrupt
> [3.780009]  Disabling IRQ #14

Is this the whole boot output or you trimmed it?

Anyway, it doesn't really sound like a libvirt issue, but let's not ditch that idea just yet. Can you attach the full VM XML config?

(In reply to Erik Skultety from comment #2)
> (In reply to Lavie from comment #0)
> > The virutalized box' boot screen shows
> > [3.779332] irq 14: nobody cared (try booting with the "irqpoll" option)
> > [3.779869] handlers:
> > [3.780009]  [<000000008fed29e6>] ata_bmdma interrupt
> > [3.780009]  Disabling IRQ #14

> Is this the whole boot output or you trimmed it?
> 
> Anyway, it doesn't really sound like a libvirt issue, but let's not ditch
> that idea just yet. Can you attach the full VM XML config?

This is all I see in the Virtualization Manager. Then I see a GNOME desktop begin to come up (the three progressive dots at the bottom - it only gets to the 3rd dot), and then a garbled screen.

Please excuse my nubie-ness, but how to I extract a full VM XML Conifg?

Created attachment 1489049 [details]
Domain XML Dump for a Virtual Host

Domain XML Dump for a Virtual Host

I have attached the XML file, as requested (Google is your friend...)

There was a small mistake in my previous comment. When the Gnome desktop starts, it only gets to the SECOND of the three dots at the bottom of them screen, and NOT the 3rd dot, as I erroneously reported.

Additional info:
I assumed that you were going to eventually ask me for the guests' boot.log files, so I investigated how to access them.

I found a tool called guestfish. When I ried to read the disks with "guestfish -d MyGuest -i --ro", I got a log error message and dump, which I am attaching - just in case it helps.

Created attachment 1489101 [details]
guestfish dump

Hi Friends,

I think I'm being hit by this as well.
Seeing same behaviour on fresh install as well as on old VMs that definitely worked in the past.

I noticed same problem on old F27 system as well as on freshly installed F28.
I am suspecting that it may have something to do with CPU model as they are both Core2 series.

My exact CPU is "Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz" as reported by cpuinfo.

I also have access to newer i5 system, and even though everything is of same version (F28), VMs work perfectly fine there.

Exact CPU there is "Intel(R) Core(TM) i5-7300U CPU @ 2.60GHz"

This is what the output looks like on an Core2 machine:
https://imgur.com/a/maUPJFl

As you can see, we're still in kernel messages and still haven't switched root.

Please let me know if there is anything else I can provide.

Kind regards,
Momcilo "Momo" Medic.
(fedorauser)

Dragi Momcilo,


I think you are on to something. My CPU is VERY old.

Here's its details:

vendor_id       : GenuineIntel
cpu family      : 6
model           : 23
model name      : Pentium(R) Dual-Core  CPU      E6500  @ 2.93GHz
stepping        : 10
microcode       : 0xa0b
cpu MHz         : 2512.201
cache size      : 2048 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 2


Sa poštovanjem,
Meron Lavie ("Lavie")

This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.