On 1/25/22 16:09, George R Goffe via test wrote:
Could I get someone from this list to take a peek at the above named bug report please?
I'm STILL seeing this issue with the "latest" Fedora upgrade. The extra text
does NOT appear in the dmesg output.
Could it be something with console support
Sergio,
Thanks for responding to this question.
I upgraded the host (FC37 now) and the problem appeared.
I installed a fresh (latest) Fedora Core iso and started my "usual"
customization. When I changed the grub.cfg file by deleting the "quiet"
parameter from the command line, the gibberish
On 1/25/22 16:09, George R Goffe via test wrote:
Could I get someone from this list to take a peek at the above named bug report please?
I'm STILL seeing this issue with the "latest" Fedora upgrade. The extra text
does NOT appear in the dmesg output.
Could it be something with console support
Hi George,
you are using rawhide kernel, VirtualBox officially , just support
stable kernels .
how you install VirtualBox and what is the host system and are you
using virtualbox_guest_additions ?
Depending in what packages you are using . you should report in
different places , because we
On Wed, 2022-01-26 at 00:09 +, George R Goffe via test wrote:
> Hi,
>
> Could I get someone from this list to take a peek at the above named
> bug report please? I'm STILL seeing this issue with the "latest"
> Fedora upgrade. The extra text does NOT appear in the dmesg output.
>
> Could it
Hi George,
Does the VM run after boot up?. The text file of the error was just the
kernel ident string, not an error.
The giberish, well since it's a VM it could be something with the
vdagent utils maybe I guess.
Stephen
On Wed, 2022-01-26 at 00:09 +, George R Goffe via test wrote:
> Hi,
>
Hi,
Could I get someone from this list to take a peek at the above named bug report
please? I'm STILL seeing this issue with the "latest" Fedora upgrade. The extra
text does NOT appear in the dmesg output.
Could it be something with console support in VirtualBox?
Best regards and STAY SAFE!
