Has anyone tried running a F26 guest in qemu/kvm with the latest 4.12.8-300 kernel?
When it comes to GNOME I can only boot to multi-user mode, not graphical, by removing rhgb from the boot parameters. If I attempt to boot to graphical mode it hangs at "Started user manager for UID 42" with UID 42 belonging to gdm. If I boot to multi-user mode and then login and use "startx" I am presented with a black screen and maybe the "Activities" indicator in the upper left.
When it comes to KDE, which is configured for sddm, it will boot to graphical mode if I remove "rhgb quiet" from the boot parameters. However, the screen cannot be resized and issuing a "xrandr --output Virtual-0 --auto" is not effective and may result an apparent hang or a display which goes wonky in that it seems it thinks it is resized....but it isn't and the mouse isn't where it thinks it is.
Any similar experiences?
On 08/26/2017 08:44 AM, Ed Greshko wrote:
Has anyone tried running a F26 guest in qemu/kvm with the latest 4.12.8-300 kernel?
When it comes to GNOME I can only boot to multi-user mode, not graphical, by removing rhgb from the boot parameters. If I attempt to boot to graphical mode it hangs at "Started user manager for UID 42" with UID 42 belonging to gdm. If I boot to multi-user mode and then login and use "startx" I am presented with a black screen and maybe the "Activities" indicator in the upper left.
When it comes to KDE, which is configured for sddm, it will boot to graphical mode if I remove "rhgb quiet" from the boot parameters. However, the screen cannot be resized and issuing a "xrandr --output Virtual-0 --auto" is not effective and may result an apparent hang or a display which goes wonky in that it seems it thinks it is resized....but it isn't and the mouse isn't where it thinks it is.
Any similar experiences?
Just to clarify a bit. I'm talking about the guest running the latest kernel. My host is running the latest. I installed F26 guest and it worked fine with the initial kernel-4.11.11-300 but the above is what I'm seeing with the 4.12.8-300 kernel in the guest.
Den 2017-08-26 kl. 02:50, skrev Ed Greshko:
On 08/26/2017 08:44 AM, Ed Greshko wrote:
Has anyone tried running a F26 guest in qemu/kvm with the latest 4.12.8-300 kernel?
When it comes to GNOME I can only boot to multi-user mode, not graphical, by removing rhgb from the boot parameters. If I attempt to boot to graphical mode it hangs at "Started user manager for UID 42" with UID 42 belonging to gdm. If I boot to multi-user mode and then login and use "startx" I am presented with a black screen and maybe the "Activities" indicator in the upper left.
When it comes to KDE, which is configured for sddm, it will boot to graphical mode if I remove "rhgb quiet" from the boot parameters. However, the screen cannot be resized and issuing a "xrandr --output Virtual-0 --auto" is not effective and may result an apparent hang or a display which goes wonky in that it seems it thinks it is resized....but it isn't and the mouse isn't where it thinks it is.
Any similar experiences?
Just to clarify a bit. I'm talking about the guest running the latest kernel. My host is running the latest. I installed F26 guest and it worked fine with the initial kernel-4.11.11-300 but the above is what I'm seeing with the 4.12.8-300 kernel in the guest.
Yes, I got precise this problem with kernel 4.12.4-300 and 4.12.8-300 for Gnome Workstation VM under KVM/qemu. I am running Fedroa 25 updated yesterday (Friday 25th August 2017).
On 08/26/2017 06:33 PM, Jon Ingason wrote:
Den 2017-08-26 kl. 02:50, skrev Ed Greshko:
On 08/26/2017 08:44 AM, Ed Greshko wrote:
Has anyone tried running a F26 guest in qemu/kvm with the latest 4.12.8-300 kernel?
When it comes to GNOME I can only boot to multi-user mode, not graphical, by removing rhgb from the boot parameters. If I attempt to boot to graphical mode it hangs at "Started user manager for UID 42" with UID 42 belonging to gdm. If I boot to multi-user mode and then login and use "startx" I am presented with a black screen and maybe the "Activities" indicator in the upper left.
When it comes to KDE, which is configured for sddm, it will boot to graphical mode if I remove "rhgb quiet" from the boot parameters. However, the screen cannot be resized and issuing a "xrandr --output Virtual-0 --auto" is not effective and may result an apparent hang or a display which goes wonky in that it seems it thinks it is resized....but it isn't and the mouse isn't where it thinks it is.
Any similar experiences?
Just to clarify a bit. I'm talking about the guest running the latest kernel. My host is running the latest. I installed F26 guest and it worked fine with the initial kernel-4.11.11-300 but the above is what I'm seeing with the 4.12.8-300 kernel in the guest.
Yes, I got precise this problem with kernel 4.12.4-300 and 4.12.8-300 for Gnome Workstation VM under KVM/qemu. I am running Fedroa 25 updated yesterday (Friday 25th August 2017).
Good to know I'm not alone. Now to try and figure out what component a BZ should be filed against.....
On 08/26/2017 06:33 PM, Jon Ingason wrote:
Den 2017-08-26 kl. 02:50, skrev Ed Greshko:
On 08/26/2017 08:44 AM, Ed Greshko wrote:
Has anyone tried running a F26 guest in qemu/kvm with the latest 4.12.8-300 kernel?
When it comes to GNOME I can only boot to multi-user mode, not graphical, by removing rhgb from the boot parameters. If I attempt to boot to graphical mode it hangs at "Started user manager for UID 42" with UID 42 belonging to gdm. If I boot to multi-user mode and then login and use "startx" I am presented with a black screen and maybe the "Activities" indicator in the upper left.
When it comes to KDE, which is configured for sddm, it will boot to graphical mode if I remove "rhgb quiet" from the boot parameters. However, the screen cannot be resized and issuing a "xrandr --output Virtual-0 --auto" is not effective and may result an apparent hang or a display which goes wonky in that it seems it thinks it is resized....but it isn't and the mouse isn't where it thinks it is.
Any similar experiences?
Just to clarify a bit. I'm talking about the guest running the latest kernel. My host is running the latest. I installed F26 guest and it worked fine with the initial kernel-4.11.11-300 but the above is what I'm seeing with the 4.12.8-300 kernel in the guest.
Yes, I got precise this problem with kernel 4.12.4-300 and 4.12.8-300 for Gnome Workstation VM under KVM/qemu. I am running Fedroa 25 updated yesterday (Friday 25th August 2017).
FYI, https://bugzilla.redhat.com/show_bug.cgi?id=1485743 has been submitted.
-
Ed Greshko -
Jon Ingason