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.
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
@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
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): apparmo
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 g
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 stat
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
[... norma
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
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.0
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 th
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
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
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 bu
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
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 toke
15 matches
Mail list logo
