http://bugzilla.opensuse.org/show_bug.cgi?id=1157366 http://bugzilla.opensuse.org/show_bug.cgi?id=1157366#c2 James Fehlig <jfehlig@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jfehlig@suse.com) | --- Comment #2 from James Fehlig <jfehlig@suse.com> --- (In reply to Bruce Rogers from comment #1)
What I see in your seabios debug log is that after the normal "Booting from 0000:7c00" the next thing printed by the bios is "In resume (status=0)", which indicates the CPU was reset. Some something bad is happening.
Since you tie this report to the -display none option, I assume that without "-display none", the guest boots ok?
Yes, it boots fine without '-display none'.
For the record, I'm booting a Leap 15.1 guest similarly to what you have for a qemu commandline, and don't see this problem, so more info is needed. I am using Tumbleweed as the host OS though. (If I remember right in private conversation, you thought the host didn't matter. Is that right?)
Right. I've seen the problem on Leap 15.1 and TW hosts. IIRC, Liang has also seen the problem with TW guest.
What additional details can be provided?
Another way to reproduce is with virt-install. E.g. virt-install --name leap15.1 --ram 2048 --vcpus 2 --machine pc --virt-type kvm --location http://download.opensuse.org/distribution/leap/15.1/repo/oss/ --extra-args console=ttyS0 --arch x86_64 --disk /home/jfehlig/virt/images/test/disk0.qcow2 --network bridge=br0,mac=00:16:3e:0d:e4:15 --wait 0 --initrd-inject /home/jfehlig/virt/images/test/autoinst.xml --graphics none Once the install starts, you can connect to the console with 'virsh console leap15.1' and watch the install progress. After install the machine will shutdown. Restart it again with 'virsh start leap15.1 --console' and you will see the problem. You wont see the problem if '--graphics none' is dropped from the virt-install command. BTW, I'll attache the autoyast file I'm using, which installs a minimal Leap 15.1 system.
Can you try w/out using -cpu host and see if that affects the behavior?
I've tried without and see the same problem. -- You are receiving this mail because: You are on the CC list for the bug.