[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1869782
Title:
The QEMU project is currently moving its bug tracking to another system.
For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting older bugs to "Incomplete" now.
If you still think this bug report here is valid, then please switch
the state back
Managed to get a coredump. Coredumps usually tell me nothing but maybe
someone here can find something useful in there...
** Attachment added: "core.1001.13055.1585661762.bz2"
https://bugs.launchpad.net/qemu/+bug/1869782/+attachment/5343797/+files/core.1001.13055.1585661762.bz2
--
You
This is a "Ubuntu Bionic" thing.
I've tried again on a VM with up-to-date Ubuntu Bionic and get the same
segfault.
For comparison I've placed the Debian build of qemu-user-static version
4.2 to my Arch Linux VM and have no crash there.
So either the kernel version or some kernel configuration.
Here we go:
https://travis-ci.com/github/VDR4Arch/vdr4arch/jobs/309187889#L332
Created with this commit:
https://github.com/VDR4Arch/vdr4arch/commit/29ec2197483bf15102c889eef2749bb0cffc0839
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to
I could run an "qemu... --version" in the chroot to get it into log.
But I'm close to 100% sure it is version 4.2 as the VM is set up from
scratch for every build and the chroot is also set up from scratch.
--
You received this bug notification because you are a member of qemu-
devel-ml, which
Is there a way that you can confirm that the QEMU being used to execute
the binaries in the chroot really really is the new one you think it is?
In this kind of setup where there's a chroot and somebody else's CI
system and so on it can be quite easy for eg the new qemu binary not to
get copied
** Description changed:
I'm not actually sure how far I can help as I so far failed to reproduce
the issue on my local VM but I get it on Travis CI every time. I even
went through the hassle of hacking a Debian repository into their Ubuntu
Bionic VM to get qemu 4.2 as I hoped a new
