diff options
Diffstat (limited to '')
| -rw-r--r-- | results/classifier/108/other/1186 | 32 | ||||
| -rw-r--r-- | results/classifier/108/other/1186303 | 103 | ||||
| -rw-r--r-- | results/classifier/108/other/1186984 | 69 |
3 files changed, 204 insertions, 0 deletions
diff --git a/results/classifier/108/other/1186 b/results/classifier/108/other/1186 new file mode 100644 index 000000000..26a40a574 --- /dev/null +++ b/results/classifier/108/other/1186 @@ -0,0 +1,32 @@ +device: 0.900 +permissions: 0.793 +graphic: 0.768 +PID: 0.591 +vnc: 0.574 +performance: 0.566 +semantic: 0.519 +socket: 0.490 +files: 0.457 +network: 0.356 +boot: 0.300 +debug: 0.232 +other: 0.222 +KVM: 0.021 + +qos-test fails when built with LTO and gcc-12 +Description of problem: +The issue is already discussed here [1]. I'm simply building latest QEMU release and running the test suite. I thought the issue was fixed in 7.0 but it has resurfaced. Do QEMU dev's not build with LTO? I'm not able to debug this but I can test any proposed fixes etc. Thanks. + +[1] https://lore.kernel.org/all/1d3bbff9e92e7c8a24db9e140dcf3f428c2df103.camel@suse.com/ +Steps to reproduce: +1. Build QEMU with gcc-12 and LTO enabled +2. Run make check +3. Observe test suite failures in qos-test +Additional information: +``` +Summary of Failures: + + 2/265 qemu:qtest+qtest-aarch64 / qtest-aarch64/qos-test ERROR 0.59s killed by signal 6 SIGABRT + 3/265 qemu:qtest+qtest-i386 / qtest-i386/qos-test ERROR 0.22s killed by signal 6 SIGABRT + 7/265 qemu:qtest+qtest-x86_64 / qtest-x86_64/qos-test ERROR 0.40s killed by signal 6 SIGABRT +``` diff --git a/results/classifier/108/other/1186303 b/results/classifier/108/other/1186303 new file mode 100644 index 000000000..f671e503f --- /dev/null +++ b/results/classifier/108/other/1186303 @@ -0,0 +1,103 @@ +graphic: 0.823 +socket: 0.800 +PID: 0.797 +permissions: 0.778 +device: 0.766 +performance: 0.761 +semantic: 0.748 +debug: 0.744 +other: 0.730 +network: 0.710 +KVM: 0.602 +files: 0.587 +boot: 0.560 +vnc: 0.533 + +virtual fat do not working in qemu 1.5.0 + +Guest : windows Seven / XP +Qemu version : 1.5.0 +cmd line : +-drive file=fat:floppy:/mnt/vdisk/diskconf/TEST004/,if=none,id=drive-fdc0-0-0,readonly=on +generated by libvirt : + +<disk type='dir' device='floppy'> + <driver name='qemu' type='fat'/> + <source dir='/mnt/vdisk/diskconf/TEST003/'/> + <target dev='fda' bus='fdc'/> + <readonly/> + <alias name='fdc0-0-0'/> + <address type='drive' controller='0' bus='0' target='0' unit='0'/> + </disk> + +works with qemu <= 1.4.1 + +with qemu 1.5.0 , guest does not see the floppy content. + +Regards + +same issue with qemu 1.5.1 +floopy content is seen under linux. not under Windows guest + +On Fri, May 31, 2013 at 03:26:47PM -0000, prochazka nicolas wrote: +> Public bug reported: +> +> Guest : windows Seven / XP +> Qemu version : 1.5.0 +> cmd line : +> -drive file=fat:floppy:/mnt/vdisk/diskconf/TEST004/,if=none,id=drive-fdc0-0-0,readonly=on +> generated by libvirt : +> +> <disk type='dir' device='floppy'> +> <driver name='qemu' type='fat'/> +> <source dir='/mnt/vdisk/diskconf/TEST003/'/> +> <target dev='fda' bus='fdc'/> +> <readonly/> +> <alias name='fdc0-0-0'/> +> <address type='drive' controller='0' bus='0' target='0' unit='0'/> +> </disk> +> +> works with qemu <= 1.4.1 +> +> with qemu 1.5.0 , guest does not see the floppy content. + +Thanks for reporting this bug. The vvfat block driver is not actively +maintained, but you can help us track down this bug: + +Since it used to work in QEMU 1.4.1 you could use git-bisect(1) to +identify the commit that broke vvfat. + +http://git-scm.com/book/en/Git-Tools-Debugging-with-Git#Binary-Search +https://www.kernel.org/pub/software/scm/git/docs/git-bisect.html +http://code-worrier.com/blog/git-bisect-basics/ + +Something along the lines of: + +$ git clone git://git.qemu.org/qemu.git +$ cd qemu +$ git bisect start +$ git bisect bad master +$ git bisect good v1.4.1 + +Then build from source and test at each bisect step: + +$ ./configure --target-list=x86_64-softmmu && make +$ qemu -drive file=fat:floppy:... + +If it fails: + +$ git bisect bad + +If it succeeds: + +$ git bisect good + +At the end of the process it will tell you which commit broke vvfat. + +Stefan + + +Triaging old bug tickets... Have you ever bisected the problem? Can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays? + +[Expired for QEMU because there has been no activity for 60 days.] + diff --git a/results/classifier/108/other/1186984 b/results/classifier/108/other/1186984 new file mode 100644 index 000000000..a7b75a220 --- /dev/null +++ b/results/classifier/108/other/1186984 @@ -0,0 +1,69 @@ +graphic: 0.777 +boot: 0.619 +network: 0.598 +device: 0.570 +vnc: 0.533 +performance: 0.532 +socket: 0.530 +other: 0.456 +semantic: 0.441 +PID: 0.421 +permissions: 0.391 +KVM: 0.381 +files: 0.323 +debug: 0.304 + +large -initrd can wrap around in memory causing memory corruption + +We don't use large -initrd in libguestfs any more, but I noticed that a large -initrd file now crashes qemu spectacularly: + +$ ls -lh /tmp/kernel /tmp/initrd +-rw-r--r--. 1 rjones rjones 273M Jun 3 14:02 /tmp/initrd +lrwxrwxrwx. 1 rjones rjones 35 Jun 3 14:02 /tmp/kernel -> /boot/vmlinuz-3.9.4-200.fc18.x86_64 + +$ ./x86_64-softmmu/qemu-system-x86_64 -L pc-bios \ + -kernel /tmp/kernel -initrd /tmp/initrd -hda /tmp/test1.img -serial stdio \ + -append console=ttyS0 + +qemu crashes with one of several errors: + +PFLASH: Possible BUG - Write block confirm + +qemu: fatal: Trying to execute code outside RAM or ROM at 0x00000000000b96cd + +If -enable-kvm is used: + +KVM: injection failed, MSI lost (Operation not permitted) + +In all cases the SDL display fills up with coloured blocks before the crash (see the attached screenshot). + + + +I'm using qemu from git (f10acc8b38d65a66ffa0588a036489d7fa6a593e). + +One way to reproduce this is to just use a large (200 MB) completely random initrd. Note this error seems to happen a long time before even the kernel starts up, so the actual content of the initrd doesn't matter. + +dd if=/dev/urandom of=/tmp/initrd bs=1M count=200 +qemu-system-x86_64 -kernel /boot/vmlinuz -initrd /tmp/initrd -serial stdio -append console=ttyS0 + +OK I see what's happening. Because I forgot about the -m option, qemu allocates 128 MB of RAM. It's obviously wrapping around in memory and overwriting all the low memory. + +If you add (eg) -m 1024 it works. + +Just saw something similar with qemu 2.2.1: + +KVM: injection failed, MSI lost (Input/output error) +qemu-system-x86_64: /home/bart/software/qemu-2.2.1/hw/net/vhost_net.c:264: vhost_net_stop_one: Assertion `r >= 0' failed. +2015-03-23 02:44:44.952+0000: shutting down + + +Although the error message is the same, the bug in comment 5 seems completely different. Please open a new bug about this issue, giving *all* details - including the full qemu command line. + +Thanks Richard for the quick feedback. A new bug report has been created as https://bugs.launchpad.net/qemu/+bug/1435359. + +Triaging old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays? + +The answer is I don't know. Closing this bug seems correct unless someone can reproduce the original problem. + +[Expired for QEMU because there has been no activity for 60 days.] + |