[Bug 1932484] Re: glmark2 crashes in benchmark with Nvidia driver
this bug is apparently not driver version related as i see the exact same errors and crash when using the NVIDIA 460, 470, and 495 drivers on my ubuntu 20.04 installation... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932484 Title: glmark2 crashes in benchmark with Nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glmark2/+bug/1932484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776575] Re: 14.04.5 safe-upgrade from QEMU 2.0.0+dfsg-2ubuntu1.42 to QEMU 2.0.0+dfsg-2ubuntu1.43 kernel panics amd64 VM guests
FWIW: here's the info for the GUEST amd64 VM that has been panicking... 20180616 GUEST uname -a: Linux haven 3.13.0-151-generic #201-Ubuntu SMP Wed May 30 14:22:13 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 20180616 GUEST cpuinfo: processor : 0 vendor_id : AuthenticAMD cpu family : 21 model : 2 model name : AMD Opteron 63xx class CPU stepping: 0 microcode : 0x165 cpu MHz : 4018.284 cache size : 512 KB physical id : 0 siblings: 1 core id : 0 cpu cores : 1 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt pdpe1gb lm rep_good nopl extd_apicid pni pclmulqdq ssse3 fma cx16 sse4_1 sse4_2 x2apic popcnt aes xsave avx f16c hypervisor lahf_lm cmp_legacy svm cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw xop fma4 tbm arat retpoline retpoline_amd vmmcall bmi1 bogomips: 8036.56 TLB size: 1024 4K pages clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: 20180616 GUEST dmidecode: https://pastebin.com/bgEvr6LK 20180616 GUEST dmesg (full): https://pastebin.com/fBZs7Mit -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776575 Title: 14.04.5 safe-upgrade from QEMU 2.0.0+dfsg-2ubuntu1.42 to QEMU 2.0.0 +dfsg-2ubuntu1.43 kernel panics amd64 VM guests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1776575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776575] Re: 14.04.5 safe-upgrade from QEMU 2.0.0+dfsg-2ubuntu1.42 to QEMU 2.0.0+dfsg-2ubuntu1.43 kernel panics amd64 VM guests
@tyhicks: i totally forgot you asked me to try testing with the HOST running an older kernel... my amd64 GUEST VMs are NOT kernel panicking :shock: :shock: :shock: 20180616 HOST uname -a: Linux shadow 3.13.0-149-generic #199-Ubuntu SMP Thu May 17 10:12:50 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 20180616 HOST cpuinfo: same as previous posted 20180616 HOST dmidecode: suspect is the same but here is the latest one, https://pastebin.com/VW3x9NaP 20180616 HOST cat /var/log/libvirt/qemu/haven-vm.log: 2018-06-16 14:13:39.077+: shutting down [... upgrade to qemu*.43 ...] [... HOST reboot ...] 2018-06-16 14:17:50.050+: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm-spice -name haven-vm -S -machine pc-i440fx-trusty,accel=kvm,usb=off -cpu Opteron_G5,+bmi1,+perfctr_nb,+perfctr_core,+topoext,+nodeid_msr,+tce,+lwp,+wdt,+skinit,+ibs,+osvw,+cr8legacy,+extapic,+cmp_legacy,+fxsr_opt,+mmxext,+osxsave,+monitor,+ht,+vme -m 768 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 8d88f791-5b85-5293-329f-943e871c4a02 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/haven-vm.monitor,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/haven-vm.img,if=none,id=drive-virtio-disk0,format=raw -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=23,id=hostnet0,vhost=on,vhostfd=25 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:6c:88:6a,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 127.0.0.1:1 -device vmware-svga,id=video0,bus=pci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 char device redirected to /dev/pts/7 (label charserial0) 20180616 HOST dmesg (full): https://pastebin.com/demTJw2V 20180616 HOST update log QEMU*.42 -> QEMU*.43: https://pastebin.com/8EfZu7Av -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776575 Title: 14.04.5 safe-upgrade from QEMU 2.0.0+dfsg-2ubuntu1.42 to QEMU 2.0.0 +dfsg-2ubuntu1.43 kernel panics amd64 VM guests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1776575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776575] Re: 14.04.5 safe-upgrade from QEMU 2.0.0+dfsg-2ubuntu1.42 to QEMU 2.0.0+dfsg-2ubuntu1.43 kernel panics amd64 VM guests
good grief... and the rest... WTH? >- dmesg $ dmesg | tail -n 50 [189401.694498] RED: port 4(vnet2) entered disabled state [189401.695136] device vnet2 left promiscuous mode [189401.695146] RED: port 4(vnet2) entered disabled state [189402.022302] type=1400 audit(1529007011.473:117): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-30c5afb2-602a-1c9c-c940-0b47cadbe52c" pid=29425 comm="apparmor_parser" [189412.938869] type=1400 audit(1529007022.390:118): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-30c5afb2-602a-1c9c-c940-0b47cadbe52c" pid=29440 comm="apparmor_parser" [189413.032182] device vnet2 entered promiscuous mode [189413.064318] RED: port 4(vnet2) entered forwarding state [189413.064369] RED: port 4(vnet2) entered forwarding state [189413.524620] kvm: zapping shadow pages for mmio generation wraparound [190751.089128] RED: port 4(vnet2) entered disabled state [190751.089351] device vnet2 left promiscuous mode [190751.089357] RED: port 4(vnet2) entered disabled state [190756.389518] type=1400 audit(1529008365.840:119): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-30c5afb2-602a-1c9c-c940-0b47cadbe52c" pid=31466 comm="apparmor_parser" [190784.008591] type=1400 audit(1529008393.460:120): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-30c5afb2-602a-1c9c-c940-0b47cadbe52c" pid=31505 comm="apparmor_parser" [190784.104215] device vnet2 entered promiscuous mode [190784.120319] RED: port 4(vnet2) entered forwarding state [190784.120341] RED: port 4(vnet2) entered forwarding state [190788.883915] kvm: zapping shadow pages for mmio generation wraparound [192525.623898] RED: port 4(vnet2) entered disabled state [192525.624178] device vnet2 left promiscuous mode [192525.624217] RED: port 4(vnet2) entered disabled state [192526.174179] type=1400 audit(1529010135.625:121): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-30c5afb2-602a-1c9c-c940-0b47cadbe52c" pid=1282 comm="apparmor_parser" [192594.838386] type=1400 audit(1529010204.289:122): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-30c5afb2-602a-1c9c-c940-0b47cadbe52c" pid=1377 comm="apparmor_parser" [192594.928167] device vnet2 entered promiscuous mode [192594.960225] RED: port 4(vnet2) entered forwarding state [192594.960234] RED: port 4(vnet2) entered forwarding state [192598.131548] kvm: zapping shadow pages for mmio generation wraparound [207463.151824] RED: port 4(vnet2) entered disabled state [207463.151976] device vnet2 left promiscuous mode [207463.151989] RED: port 4(vnet2) entered disabled state [207463.443798] type=1400 audit(1529025072.894:123): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-30c5afb2-602a-1c9c-c940-0b47cadbe52c" pid=20089 comm="apparmor_parser" [217591.715997] sqpack[32402]: segfault at 1 ip 7f66001cb943 sp 7ffda3b61c00 error 4 in libc-2.19.so[7f660018+1be000] [228402.112955] hrtimer: interrupt took 41067 ns [256193.281642] RED: port 3(vnet1) entered disabled state [256193.282064] device vnet1 left promiscuous mode [256193.282087] RED: port 3(vnet1) entered disabled state [256193.760875] type=1400 audit(1529073803.212:124): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-8d88f791-5b85-5293-329f-943e871c4a02" pid=17181 comm="apparmor_parser" [256910.451198] RED: port 2(vnet0) entered disabled state [256910.452679] device vnet0 left promiscuous mode [256910.452714] RED: port 2(vnet0) entered disabled state [256910.993308] type=1400 audit(1529074520.443:125): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-1c41785d-30f6-e6cc-de6d-706df6d47b9c" pid=18499 comm="apparmor_parser" [257116.751276] type=1400 audit(1529074726.201:126): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-8d88f791-5b85-5293-329f-943e871c4a02" pid=20932 comm="apparmor_parser" [257116.864221] device vnet0 entered promiscuous mode [257116.892371] RED: port 2(vnet0) entered forwarding state [257116.892387] RED: port 2(vnet0) entered forwarding state [257117.397095] kvm: zapping shadow pages for mmio generation wraparound [257120.544713] kvm [20982]: vcpu0 unhandled rdmsr: 0xc0011020 [257120.778098] kvm [20982]: vcpu0 unhandled rdmsr: 0xc0011021 [257120.778107] kvm [20982]: vcpu0 unhandled rdmsr: 0xc0011029 [257120.935183] kvm [20982]: vcpu0 unhandled rdmsr: 0xc0010001 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776575 Title: 14.04.5 safe-upgrade from QEMU 2.0.0+dfsg-2ubuntu1.42 to QEMU 2.0.0 +dfsg-2ubuntu1.43 kernel panics amd64 VM guests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1776575/+subscriptions -- ubuntu-bugs mailing list
[Bug 1776575] Re: 14.04.5 safe-upgrade from QEMU 2.0.0+dfsg-2ubuntu1.42 to QEMU 2.0.0+dfsg-2ubuntu1.43 kernel panics amd64 VM guests
done... what is missing? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776575 Title: 14.04.5 safe-upgrade from QEMU 2.0.0+dfsg-2ubuntu1.42 to QEMU 2.0.0 +dfsg-2ubuntu1.43 kernel panics amd64 VM guests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1776575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776575] Re: 14.04.5 safe-upgrade from QEMU 2.0.0+dfsg-2ubuntu1.42 to QEMU 2.0.0+dfsg-2ubuntu1.43 kernel panics amd64 VM guests
and the last... 20180615 HOST update log QEMU*.42 -> QEMU*.43: $ cat dosysupdate.log Execute "sudo aptitude -V safe-upgrade"? Yes/no Response: Yes. Executing "sudo aptitude -V safe-upgrade"... Reading package lists... Building dependency tree... Reading state information... Reading extended state information... Initializing package states... The following packages will be upgraded: debootstrap [1.0.59ubuntu0.9 -> 1.0.59ubuntu0.10] file [1:5.14-2ubuntu3.3 -> 1:5.14-2ubuntu3.4] gnupg-agent [2.0.22-3ubuntu1.3 -> 2.0.22-3ubuntu1.4] gnupg2 [2.0.22-3ubuntu1.3 -> 2.0.22-3ubuntu1.4] gpgsm [2.0.22-3ubuntu1.3 -> 2.0.22-3ubuntu1.4] libmagic1 [1:5.14-2ubuntu3.3 -> 1:5.14-2ubuntu3.4] libperl5.18 [5.18.2-2ubuntu1.4 -> 5.18.2-2ubuntu1.6] libruby1.9.1 [1.9.3.484-2ubuntu1.11 -> 1.9.3.484-2ubuntu1.12] perl [5.18.2-2ubuntu1.4 -> 5.18.2-2ubuntu1.6] perl-base [5.18.2-2ubuntu1.4 -> 5.18.2-2ubuntu1.6] perl-modules [5.18.2-2ubuntu1.4 -> 5.18.2-2ubuntu1.6] python3-magic [1:5.14-2ubuntu3.3 -> 1:5.14-2ubuntu3.4] qemu [2.0.0+dfsg-2ubuntu1.42 -> 2.0.0+dfsg-2ubuntu1.43] qemu-keymaps [2.0.0+dfsg-2ubuntu1.42 -> 2.0.0+dfsg-2ubuntu1.43] qemu-kvm [2.0.0+dfsg-2ubuntu1.42 -> 2.0.0+dfsg-2ubuntu1.43] qemu-system [2.0.0+dfsg-2ubuntu1.42 -> 2.0.0+dfsg-2ubuntu1.43] qemu-system-arm [2.0.0+dfsg-2ubuntu1.42 -> 2.0.0+dfsg-2ubuntu1.43] qemu-system-common [2.0.0+dfsg-2ubuntu1.42 -> 2.0.0+dfsg-2ubuntu1.43] qemu-system-mips [2.0.0+dfsg-2ubuntu1.42 -> 2.0.0+dfsg-2ubuntu1.43] qemu-system-misc [2.0.0+dfsg-2ubuntu1.42 -> 2.0.0+dfsg-2ubuntu1.43] qemu-system-ppc [2.0.0+dfsg-2ubuntu1.42 -> 2.0.0+dfsg-2ubuntu1.43] qemu-system-sparc [2.0.0+dfsg-2ubuntu1.42 -> 2.0.0+dfsg-2ubuntu1.43] qemu-system-x86 [2.0.0+dfsg-2ubuntu1.42 -> 2.0.0+dfsg-2ubuntu1.43] qemu-user [2.0.0+dfsg-2ubuntu1.42 -> 2.0.0+dfsg-2ubuntu1.43] qemu-utils [2.0.0+dfsg-2ubuntu1.42 -> 2.0.0+dfsg-2ubuntu1.43] ruby1.9.1 [1.9.3.484-2ubuntu1.11 -> 1.9.3.484-2ubuntu1.12] scdaemon [2.0.22-3ubuntu1.3 -> 2.0.22-3ubuntu1.4] 27 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 10.7 MB/32.6 MB of archives. After unpacking 13.3 kB will be used. Do you want to continue? [Y/n/?] Writing extended state information... Get: 1 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main perl amd64 5.18.2-2ubuntu1.6 [2,634 kB] Get: 2 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main libperl5.18 amd64 5.18.2-2ubuntu1.6 [1,322 B] Get: 3 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main perl-base amd64 5.18.2-2ubuntu1.6 [1,152 kB] Get: 4 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main perl-modules all 5.18.2-2ubuntu1.6 [2,684 kB] Get: 5 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main file amd64 1:5.14-2ubuntu3.4 [19.4 kB] Get: 6 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main libmagic1 amd64 1:5.14-2ubuntu3.4 [185 kB] Get: 7 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main gnupg2 amd64 2.0.22-3ubuntu1.4 [680 kB] Get: 8 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main gnupg-agent amd64 2.0.22-3ubuntu1.4 [231 kB] Get: 9 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main gpgsm amd64 2.0.22-3ubuntu1.4 [192 kB] Get: 10 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main scdaemon amd64 2.0.22-3ubuntu1.4 [163 kB] Get: 11 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main libruby1.9.1 amd64 1.9.3.484-2ubuntu1.12 [2,651 kB] Get: 12 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main ruby1.9.1 amd64 1.9.3.484-2ubuntu1.12 [35.7 kB] Get: 13 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main debootstrap all 1.0.59ubuntu0.10 [28.8 kB] Get: 14 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main python3-magic all 1:5.14-2ubuntu3.4 [4,576 B] Fetched 10.7 MB in 5s (1,873 kB/s) (Reading database ... 416079 files and directories currently installed.) Preparing to unpack .../perl_5.18.2-2ubuntu1.6_amd64.deb ... Unpacking perl (5.18.2-2ubuntu1.6) over (5.18.2-2ubuntu1.4) ... Preparing to unpack .../libperl5.18_5.18.2-2ubuntu1.6_amd64.deb ... Unpacking libperl5.18 (5.18.2-2ubuntu1.6) over (5.18.2-2ubuntu1.4) ... Preparing to unpack .../perl-base_5.18.2-2ubuntu1.6_amd64.deb ... Unpacking perl-base (5.18.2-2ubuntu1.6) over (5.18.2-2ubuntu1.4) ... Processing triggers for man-db (2.6.7.1-1ubuntu1) ... Setting up perl-base (5.18.2-2ubuntu1.6) ... (Reading database ... 416079 files and directories currently installed.) Preparing to unpack .../perl-modules_5.18.2-2ubuntu1.6_all.deb ... Unpacking perl-modules (5.18.2-2ubuntu1.6) over (5.18.2-2ubuntu1.4) ... Preparing to unpack .../file_1%3a5.14-2ubuntu3.4_amd64.deb ... Unpacking file (1:5.14-2ubuntu3.4) over (1:5.14-2ubuntu3.3) ... Preparing to unpack .../libmagic1_1%3a5.14-2ubuntu3.4_amd64.deb ... Unpacking libmagic1:amd64 (1:5.14-2ubuntu3.4) over (1:5.14-2ubuntu3.3) ... Preparing to unpack .../qemu-system-common_2.0.0+dfsg-2ubuntu1.43_amd64.deb ... Unpacking qemu-system-common (2.0.0+dfsg-2ubuntu1.43) over
Re: [Bug 1776575] Re: 14.04.5 safe-upgrade from QEMU 2.0.0+dfsg-2ubuntu1.42 to QEMU 2.0.0+dfsg-2ubuntu1.43 kernel panics amd64 VM guests
looks like my big report got cut off... sorry... here's the rest of what i had posted... starting with the libvirt guest log just before the cut off... On 06/13/2018 02:48 AM, Christian Ehrhardt wrote:> - cat /var/log/libvirt/qemu/.log $ cat /var/log/libvirt/qemu/haven-vm.log [... normal operation with .42 ...] 2018-06-15 14:43:23.028+: shutting down [... normal shutdown -h issued within guest ...] [... update from .42 to .43 files ...] [... NO HOST REBOOT ...] [... restart virtual machine manager ...] [... restart haven-vm 64bit ubuntu 14.04.5 server ...] 2018-06-15 14:58:46.362+: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm-spice -name haven-vm -S -machine pc-i440fx-trusty,accel=kvm,usb=off -cpu Opteron_G5,+bmi1,+perfctr_nb,+perfctr_core,+topoext,+nodeid_msr,+tce,+lwp,+wdt,+skinit,+ibs,+osvw,+cr8legacy,+extapic,+cmp_legacy,+fxsr_opt,+mmxext,+osxsave,+monitor,+ht,+vme -m 768 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 8d88f791-5b85-5293-329f-943e871c4a02 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/haven-vm.monitor,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/haven-vm.img,if=none,id=drive-virtio-disk0,format=raw -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=25 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:6c:88:6a,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 127.0.0.1:0 -device vmware-svga,id=video0,bus=pci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 char device redirected to /dev/pts/2 (label charserial0) >- dmesg $ dmesg | tail -n 50 [189401.694498] RED: port 4(vnet2) entered disabled state [189401.695136] device vnet2 left promiscuous mode [189401.695146] RED: port 4(vnet2) entered disabled state [189402.022302] type=1400 audit(1529007011.473:117): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-30c5afb2-602a-1c9c-c940-0b47cadbe52c" pid=29425 comm="apparmor_parser" [189412.938869] type=1400 audit(1529007022.390:118): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-30c5afb2-602a-1c9c-c940-0b47cadbe52c" pid=29440 comm="apparmor_parser" [189413.032182] device vnet2 entered promiscuous mode [189413.064318] RED: port 4(vnet2) entered forwarding state [189413.064369] RED: port 4(vnet2) entered forwarding state [189413.524620] kvm: zapping shadow pages for mmio generation wraparound [190751.089128] RED: port 4(vnet2) entered disabled state [190751.089351] device vnet2 left promiscuous mode [190751.089357] RED: port 4(vnet2) entered disabled state [190756.389518] type=1400 audit(1529008365.840:119): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-30c5afb2-602a-1c9c-c940-0b47cadbe52c" pid=31466 comm="apparmor_parser" [190784.008591] type=1400 audit(1529008393.460:120): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-30c5afb2-602a-1c9c-c940-0b47cadbe52c" pid=31505 comm="apparmor_parser" [190784.104215] device vnet2 entered promiscuous mode [190784.120319] RED: port 4(vnet2) entered forwarding state [190784.120341] RED: port 4(vnet2) entered forwarding state [190788.883915] kvm: zapping shadow pages for mmio generation wraparound [192525.623898] RED: port 4(vnet2) entered disabled state [192525.624178] device vnet2 left promiscuous mode [192525.624217] RED: port 4(vnet2) entered disabled state [192526.174179] type=1400 audit(1529010135.625:121): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-30c5afb2-602a-1c9c-c940-0b47cadbe52c" pid=1282 comm="apparmor_parser" [192594.838386] type=1400 audit(1529010204.289:122): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-30c5afb2-602a-1c9c-c940-0b47cadbe52c" pid=1377 comm="apparmor_parser" [192594.928167] device vnet2 entered promiscuous mode [192594.960225] RED: port 4(vnet2) entered forwarding state [192594.960234] RED: port 4(vnet2) entered forwarding state [192598.131548] kvm: zapping shadow pages for mmio generation wraparound [207463.151824] RED: port 4(vnet2) entered disabled state [207463.151976] device vnet2 left promiscuous mode [207463.151989] RED: port 4(vnet2) entered disabled state [207463.443798] type=1400 audit(1529025072.894:123): apparmor="STATUS" operation="profile_remove" profile="unconfined"
Re: [Bug 1776575] Re: 14.04.5 safe-upgrade from QEMU 2.0.0+dfsg-2ubuntu1.42 to QEMU 2.0.0+dfsg-2ubuntu1.43 kernel panics amd64 VM guests
On 06/14/2018 06:47 PM, Tyler Hicks wrote: > I really do appreciate your testing. I'm relying on you here because while I > did test this particular combination on a family 17h AMD processor and didn't > see such a guest panic, I don't have a family 15h AMD processor to test on. let me know if you need anything else... i'm going to downgrade again and bring those VMs back online... they've been down long enough and the minions are getting quite restless... ASIDE: BTW: i had those 13 qemu*.42 files marked as "version locked" in synaptic but aptitude still saw the .43 ones and wanted to upgrade to them... i went ahead and unlocked them so there wouldn't be any problems but now i'm highly curious as to why locking them via synaptic didn't keep the .43s from showing up with no notice that they were version locked at .42... could that have been because of where the .42 and .43 are in the file names? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776575 Title: 14.04.5 safe-upgrade from QEMU 2.0.0+dfsg-2ubuntu1.42 to QEMU 2.0.0 +dfsg-2ubuntu1.43 kernel panics amd64 VM guests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1776575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1776575] Re: 14.04.5 safe-upgrade from QEMU 2.0.0+dfsg-2ubuntu1.42 to QEMU 2.0.0+dfsg-2ubuntu1.43 kernel panics amd64 VM guests
On 06/15/2018 11:26 AM, wkitty42 wrote: > 20180615 GUEST kernel panic screen shot aww, darn-it! https://imgur.com/a/He9ukKs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776575 Title: 14.04.5 safe-upgrade from QEMU 2.0.0+dfsg-2ubuntu1.42 to QEMU 2.0.0 +dfsg-2ubuntu1.43 kernel panics amd64 VM guests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1776575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1776575] Re: 14.04.5 safe-upgrade from QEMU 2.0.0+dfsg-2ubuntu1.42 to QEMU 2.0.0+dfsg-2ubuntu1.43 kernel panics amd64 VM guests
On 06/13/2018 02:48 AM, Christian Ehrhardt wrote: > Also in addition to the Kernel Panic getting the guest log could be > useful in case qemu has thrown warnigns or errors. here's the new guest panic screen shot... how can i get the VM's boot log from the time after the grub menu launches the boot of the 64bit VM till it panics? could that contain some information that could help solve this problem? 20180615 GUEST kernel panic screen shot > Summarizing, please provide: > HW Info >- cat /proc/cpuinfo 20180615 HOST AMD FX8350 8-core 4Ghz cpuinfo (1 paragraph for space): processor : 0 vendor_id : AuthenticAMD cpu family : 21 model : 2 model name : AMD FX(tm)-8350 Eight-Core Processor stepping: 0 microcode : 0x6000822 cpu MHz : 1400.000 cache size : 2048 KB physical id : 0 siblings: 8 core id : 0 cpu cores : 4 apicid : 16 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb arat cpb hw_pstate ssbd ls_cfg_ssbd retpoline retpoline_amd npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold vmmcall bmi1 bogomips: 8036.20 TLB size: 1536 4K pages clflush size: 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm 100mhzsteps hwpstate cpb eff_freq_ro >- sudo dmidecode a fresh one after the GUEST 64bit VM kernel panics is here: https://pastebin.com/eB24w7ej > Logs: >- journalctl -xe i don't have journalctl... it is necessary? my update log is at the end below... that systemd thing isn't involved AFAICT... >- cat /var/log/libvirt/qemu/.log $ cat /var/log/libvirt/qemu/haven-vm.log [... normal operation with .42 ...] 2018-06-15 14:43:23.028+: shutting down [... normal shutdown -h issued within guest ...] [... update from .42 to .43 files ...] [... NO HOST REBOOT ...] [... restart virtual machine manager ...] [... restart haven-vm 64bit ubuntu 14.04.5 server ...] 2018-06-15 14:58:46.362+: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm-spice -name haven-vm -S -machine pc-i440fx-trusty,accel=kvm,usb=off -cpu Opteron_G5,+bmi1,+perfctr_nb,+perfctr_core,+topoext,+nodeid_msr,+tce,+lwp,+wdt,+skinit,+ibs,+osvw,+cr8legacy,+extapic,+cmp_legacy,+fxsr_opt,+mmxext,+osxsave,+monitor,+ht,+vme -m 768 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 8d88f791-5b85-5293-329f-943e871c4a02 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/haven-vm.monitor,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/haven-vm.img,if=none,id=drive-virtio-disk0,format=raw -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=25 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:6c:88:6a,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 127.0.0.1:0 -device vmware-svga,id=video0,bus=pci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 char device redirected to /dev/pts/2 (label charserial0) >- dmesg $ dmesg | tail -n 50 [189401.694498] RED: port 4(vnet2) entered disabled state [189401.695136] device vnet2 left promiscuous mode [189401.695146] RED: port 4(vnet2) entered disabled state [189402.022302] type=1400 audit(1529007011.473:117): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-30c5afb2-602a-1c9c-c940-0b47cadbe52c" pid=29425 comm="apparmor_parser" [189412.938869] type=1400 audit(1529007022.390:118): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-30c5afb2-602a-1c9c-c940-0b47cadbe52c" pid=29440 comm="apparmor_parser" [189413.032182] device vnet2 entered promiscuous mode [189413.064318] RED: port 4(vnet2) entered forwarding state [189413.064369] RED: port 4(vnet2) entered forwarding state [189413.524620] kvm: zapping shadow
Re: [Bug 1776575] Re: 14.04.5 safe-upgrade from QEMU 2.0.0+dfsg-2ubuntu1.42 to QEMU 2.0.0+dfsg-2ubuntu1.43 kernel panics amd64 VM guests
On 06/13/2018 04:55 PM, Tyler Hicks wrote: > @wkitty42, could you please try booting your host into an older kernel, > such as 3.13.0-149.199, and using qemu 2.0.0+dfsg-2ubuntu1.43 to see if > the guests still panic? i can try that, yes... i just have to find a quiet time when they are not being used too much... it should be noted that i loath having to panic my servers for these tests... i'm pretty sure i'm not the only admin that dislikes this part of the job ;) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776575 Title: 14.04.5 safe-upgrade from QEMU 2.0.0+dfsg-2ubuntu1.42 to QEMU 2.0.0 +dfsg-2ubuntu1.43 kernel panics amd64 VM guests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1776575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1776575] Re: 14.04.5 safe-upgrade from QEMU 2.0.0+dfsg-2ubuntu1.42 to QEMU 2.0.0+dfsg-2ubuntu1.43 kernel panics amd64 VM guests
On 06/13/2018 01:05 PM, Tyler Hicks wrote: > I made a typo in the kernel versions above. They should be: > >3.13.0-151-generic >3.13.0-32-generic FWIW: 3.13.0-32-generic might be the one where i tried booting the 10.04 ISO and selected the "recover a broken system" option... i'm pretty sure that that's where the second kernel panic image came from... i also want to confirm that you guys are waiting on me to reapply the qemu .43 update files, panic my 64bit VMs again and grab those reports listed in the following?? On 06/13/2018 02:48 AM, Christian Ehrhardt wrote: > Summarizing, please provide: > HW Info >- cat /proc/cpuinfo >- sudo dmidecode > Logs: >- journalctl -xe >- cat/var/log/libvirt/qemu/.log >- dmesg > > Collect the logs right after the guest crashed please. i don't have journalctl and don't have a clue what it is about... do i still need the first two listed under "HW Info"?? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776575 Title: 14.04.5 safe-upgrade from QEMU 2.0.0+dfsg-2ubuntu1.42 to QEMU 2.0.0 +dfsg-2ubuntu1.43 kernel panics amd64 VM guests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1776575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1776575] Re: 14.04.5 safe-upgrade from QEMU 2.0.0+dfsg-2ubuntu1.42 to QEMU 2.0.0+dfsg-2ubuntu1.43 kernel panics amd64 VM guests
On 06/13/2018 01:03 PM, Tyler Hicks wrote: > I want to point out that the two kernel panics that were posted are from > two different guest kernel versions: > >3.32.0-151-generic >3.32.0-32-generic > > That may indicate that the offending bug is in the host kernel and/or > QEMU. that is my thinking, as well... all of my 64bit VMs panicked... that's probably four different kernel versions on like three different distros... > @wkitty42 yes, only the logs from the host are needed. thanks for confirming that for me :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776575 Title: 14.04.5 safe-upgrade from QEMU 2.0.0+dfsg-2ubuntu1.42 to QEMU 2.0.0 +dfsg-2ubuntu1.43 kernel panics amd64 VM guests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1776575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776575] Re: 14.04.5 safe-upgrade from QEMU 2.0.0+dfsg-2ubuntu1.42 to QEMU 2.0.0+dfsg-2ubuntu1.43 kernel panics amd64 VM guests
sorry for the delay... was sleep time :) i want to reiterate that the HOST is downgraded and running the .42 QEMU code... just to make sure we're on the same page... everything i'm reporting and looking at is on the HOST... here's one paragraph from /proc/cpuinfo as requested... ->8 snip 8<- processor : 0 vendor_id : AuthenticAMD cpu family : 21 model : 2 model name : AMD FX(tm)-8350 Eight-Core Processor stepping: 0 microcode : 0x6000822 cpu MHz : 1400.000 cache size : 2048 KB physical id : 0 siblings: 8 core id : 0 cpu cores : 4 apicid : 16 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb arat cpb hw_pstate ssbd ls_cfg_ssbd retpoline retpoline_amd npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold vmmcall bmi1 bogomips: 8036.20 TLB size: 1536 4K pages clflush size: 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm 100mhzsteps hwpstate cpb eff_freq_ro ->8 snip 8<- dmidecode is here: https://pastebin.com/LQZLmQ1g i do not see any DENIED or AppArmour related messages in dmesg... at least not via various grep searches... i don't see any entries in /var/log/libvirt that i can tell are relevent... i have a log for a copy of one of the 64bit VMs and the only thing that i can see that might indicate it was panicked is the "signal 15" terminations where i had to "Force Stop" the VM... that guest was created for troubleshooting... it only had the CPU section removed and the video changed to Cirrus... it uses the original guest's img... here's that log: https://pastebin.com/cs1i6s7B for the kernel request... both were upgraded at the same time... HOST: Linux shadow 3.13.0-151-generic #201-Ubuntu SMP Wed May 30 14:22:13 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux GUEST: Linux haven 3.13.0-151-generic #201-Ubuntu SMP Wed May 30 14:22:13 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux on the kernel panic data... all i have is two screen shots from the VM's console... here's the 1st one with video set to VMVGA: https://imgur.com/a/esjOwJ9 here's the 2nd one with video set to Cirrus: https://imgur.com/a/JjoMSLF i'll have to upgrade to .43 again and then capture the logs after the guest panics... i'm guessing i only need the data from the HOST?? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776575 Title: 14.04.5 safe-upgrade from QEMU 2.0.0+dfsg-2ubuntu1.42 to QEMU 2.0.0 +dfsg-2ubuntu1.43 kernel panics amd64 VM guests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1776575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776575] Re: 14.04.5 safe-upgrade from QEMU 2.0.0+dfsg-2ubuntu1.42 to QEMU 2.0.0+dfsg-2ubuntu1.43 kernel panics amd64 VM guests
i tried and had to install some python apport thing... it is erroring
out after complaining about a bunch of things being owned by my user
1000 instead of user 0... i ran that command with sudo... so i had to
clear out the apport cache credentials and rerun it without sudo... i
got this (oauth token obfuscated)...
->8 snip 8<-
$ apport-collect 1776575
The authorization page:
(https://launchpad.net/+authorize-token?oauth_token=_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Press any key to continue or wait (5) seconds...
Waiting to hear from Launchpad about your decision...
Traceback (most recent call last):
File "/usr/share/apport/apport-kde", line 533, in
sys.exit(UserInterface.run_argv())
File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 658, in run_argv
return self.run_update_report()
File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 547, in
run_update_report
self.collect_info(ignore_uninstalled=True)
File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 1012, in
collect_info
self.ui_start_info_collection_progress()
File "/usr/share/apport/apport-kde", line 395, in
ui_start_info_collection_progress
_('The collected information can be sent to the developers '
File "/usr/share/apport/apport-kde", line 97, in __init__
Dialog.__init__(self, 'progress.ui', title, heading, text)
File "/usr/share/apport/apport-kde", line 64, in __init__
uic.loadUi(os.path.join(os.path.dirname(sys.argv[0]), ui), self)
File "/usr/lib/python2.7/dist-packages/PyQt4/uic/__init__.py", line 238, in
loadUi
return DynamicUILoader(package).loadUi(uifile, baseinstance,
resource_suffix)
File "/usr/lib/python2.7/dist-packages/PyQt4/uic/Loader/loader.py", line 50,
in __init__
UIParser.__init__(self, QtCore, QtGui, LoaderCreatorPolicy(package))
File "/usr/lib/python2.7/dist-packages/PyQt4/uic/uiparser.py", line 145, in
__init__
self.factory = QObjectCreator(creatorPolicy)
File "/usr/lib/python2.7/dist-packages/PyQt4/uic/objcreator.py", line 94, in
__init__
modinfo = plugin_locals["moduleInformation"]()
File "", line 52, in moduleInformation
File "/usr/lib/python2.7/dist-packages/qgis/__init__.py", line 26, in
from qgis.PyQt import QtCore
File "/usr/lib/python2.7/dist-packages/qgis/PyQt/QtCore.py", line 28, in
sip.setapi(api, 2)
ValueError: API 'QDate' has already been set to version 1
->8 snip 8<-
i DID accept the request...
i don't know what to do, now :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776575
Title:
14.04.5 safe-upgrade from QEMU 2.0.0+dfsg-2ubuntu1.42 to QEMU 2.0.0
+dfsg-2ubuntu1.43 kernel panics amd64 VM guests
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1776575/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
