http://bugzilla.opensuse.org/show_bug.cgi?id=1103426 http://bugzilla.opensuse.org/show_bug.cgi?id=1103426#c1 --- Comment #1 from Ignaz Forster --- I forgot: This specific backtrace happened with kernel 4.17.7-1-default. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1103426 http://bugzilla.opensuse.org/show_bug.cgi?id=1103426#c6 Richard Brown changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |brogers@suse.com, | |rbrown@suse.com Flags| |needinfo?(brogers@suse.com) --- Comment #6 from Richard Brown --- Why don't we just make virtio the default instead of QXL? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1103426 http://bugzilla.opensuse.org/show_bug.cgi?id=1103426#c9 Chris Ward changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tjcw@physics.org --- Comment #9 from Chris Ward --- If you use boot parameter 'textmode=1' for the install, you can perform a text mode install. For me this completed normally and the resulting tumbleweed virtual system seems to be running normally (under leap 15.0). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1103426 http://bugzilla.opensuse.org/show_bug.cgi?id=1103426#c12 --- Comment #12 from Chris Ward --- The installation kernel from Tumbleweed 20180917 is 4.18.5-1 . Does this have the fix ? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1103426 http://bugzilla.opensuse.org/show_bug.cgi?id=1103426#c40 --- Comment #40 from Neil Rickert --- Not much activity on this bug lately. Today, I tried an install of Ubuntu-19.04. And the install froze part way through. I then reconfigured the install to use "virtio" instead of "QXL". This time the install went through without problems. For the original install, the visible display froze about halfway through the "copying" phase. However, it seems that the actual install went well beyond that, and possibly even completed. When I did a forced stop and reboot, the installed machine actually booted. So the install got past where grub is install and got past where the user is added. I did not try to login, so I don't know how far it got beyond the login screen. I stopped at that point, and rebooted to reinstall. -- You are receiving this mail because: You are on the CC list for the bug.