Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1629523
| From | Satoru Takeuchi <satoru.takeuchi@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [BUG] x86: failed to boot a kernel on a Ryzen machine |
| Date | 2017-04-24 15:10 +0200 |
| Message-ID | <tzLUC-7pd-13@gated-at.bofh.it> (permalink) |
| References | <tzG8y-3DA-19@gated-at.bofh.it> <tzK2u-6io-21@gated-at.bofh.it> <tzLrA-6Zn-21@gated-at.bofh.it> <tzLBf-72B-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
At Mon, 24 Apr 2017 14:48:46 +0200, Borislav Petkov wrote: > > On Mon, Apr 24, 2017 at 09:39:12PM +0900, Satoru Takeuchi wrote: > > I used the following auto-test tool (its backend is ktest). > > > > https://github.com/satoru-takeuchi/elkdat > > > > This problem can be reproduced by the following command on Ubuntu 16.04. > > > > ``` > > $ sudo apt-get install git vagrant libvirt-bin libvirt-dev kernel-package qemu-kvm libssl-dev libncurses5-dev > > Can you minimize that reproducer? I.e, can you dump only the qemu > command line options from this setup? > > They're enough to be able to start a guest with your config without me > having to install all that other stuff. OK. Is it sufficient information? ``` qemu-system-x86_64 -enable-kvm -name elkdat_ktest -S -machine pc-i440fx-xenial,accel=kvm,usb=off -cpu Opteron_G3,+smap,+adx,+rdseed,+bmi2,+smep,+avx2,+bmi1,+fsgsbase,+perfctr_nb,+perfctr_core,+topoext,+tce,+wdt,+skinit,+osvw,+3dnowprefetch,+cr8legacy,+extapic,+cmp_legacy,+pdpe1gb,+fxsr_opt,+mmxext,+rdrand,+f16c,+avx,+osxsave,+xsave,+aes,+movbe,+sse4.2,+sse4.1,+fma,+ssse3,+pclmuldq,+ht,+vme -m 512 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 12de0e96-5d01-4ab0-b0b3-165f55999960 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-elkdat_ktest/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/lib/libvirt/images/elkdat_ktest.img,format=qcow2,if=none,id=drive-virtio-disk0 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x3,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=26,id=hostnet0,vhost=on,vhostfd=28 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:e4:6f:3e,bus=pci.0,addr=0x5 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 127.0.0.1:0 -k en-us -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on ``` Thanks, Satoru > > Thanks. > > -- > Regards/Gruss, > Boris. > > Good mailing practices for 400: avoid top-posting and trim the reply.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [BUG] x86: failed to boot a kernel on a Ryzen machine Borislav Petkov <bp@alien8.de> - 2017-04-24 13:10 +0200
Re: [BUG] x86: failed to boot a kernel on a Ryzen machine Satoru Takeuchi <satoru.takeuchi@gmail.com> - 2017-04-24 14:40 +0200
Re: [BUG] x86: failed to boot a kernel on a Ryzen machine Borislav Petkov <bp@alien8.de> - 2017-04-24 14:50 +0200
Re: [BUG] x86: failed to boot a kernel on a Ryzen machine Satoru Takeuchi <satoru.takeuchi@gmail.com> - 2017-04-24 15:10 +0200
Re: [BUG] x86: failed to boot a kernel on a Ryzen machine Borislav Petkov <bp@alien8.de> - 2017-04-25 11:40 +0200
Re: [BUG] x86: failed to boot a kernel on a Ryzen machine Paolo Bonzini <pbonzini@redhat.com> - 2017-04-26 09:50 +0200
Re: [BUG] x86: failed to boot a kernel on a Ryzen machine Borislav Petkov <bp@alien8.de> - 2017-04-26 10:20 +0200
Re: [BUG] x86: failed to boot a kernel on a Ryzen machine Satoru Takeuchi <satoru.takeuchi@gmail.com> - 2017-04-26 13:50 +0200
Re: [BUG] x86: failed to boot a kernel on a Ryzen machine Paolo Bonzini <pbonzini@redhat.com> - 2017-04-26 19:00 +0200
Re: [BUG] x86: failed to boot a kernel on a Ryzen machine Satoru Takeuchi <satoru.takeuchi@gmail.com> - 2017-04-27 02:50 +0200
Re: [BUG] x86: failed to boot a kernel on a Ryzen machine Paolo Bonzini <pbonzini@redhat.com> - 2017-04-28 15:40 +0200
Re: [BUG] x86: failed to boot a kernel on a Ryzen machine Satoru Takeuchi <satoru.takeuchi@gmail.com> - 2017-04-29 23:10 +0200
Re: [BUG] x86: failed to boot a kernel on a Ryzen machine Masami Hiramatsu <mhiramat@kernel.org> - 2017-04-25 17:00 +0200
Re: [BUG] x86: failed to boot a kernel on a Ryzen machine Satoru Takeuchi <satoru.takeuchi@gmail.com> - 2017-04-26 14:00 +0200
Re: [BUG] x86: failed to boot a kernel on a Ryzen machine Borislav Petkov <bp@alien8.de> - 2017-04-26 15:00 +0200
csiph-web