summary refs log tree commit diff stats
path: root/results/classifier/118/device/175
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--results/classifier/118/device/17531
-rw-r--r--results/classifier/118/device/175446
-rw-r--r--results/classifier/118/device/175459765
-rw-r--r--results/classifier/118/device/175940
-rw-r--r--results/classifier/118/device/175949251
5 files changed, 233 insertions, 0 deletions
diff --git a/results/classifier/118/device/175 b/results/classifier/118/device/175
new file mode 100644
index 00000000..94f2a980
--- /dev/null
+++ b/results/classifier/118/device/175
@@ -0,0 +1,31 @@
+device: 0.823
+network: 0.635
+arm: 0.528
+performance: 0.513
+graphic: 0.409
+debug: 0.379
+VMM: 0.361
+register: 0.353
+risc-v: 0.342
+boot: 0.336
+ppc: 0.325
+socket: 0.291
+files: 0.250
+TCG: 0.239
+architecture: 0.188
+kernel: 0.177
+KVM: 0.150
+PID: 0.147
+hypervisor: 0.110
+semantic: 0.098
+i386: 0.090
+peripherals: 0.090
+vnc: 0.085
+virtual: 0.077
+x86: 0.056
+assembly: 0.055
+user-level: 0.051
+mistranslation: 0.046
+permissions: 0.033
+
+qmp monitor deadlock (with spice events for ex)
diff --git a/results/classifier/118/device/1754 b/results/classifier/118/device/1754
new file mode 100644
index 00000000..e239f659
--- /dev/null
+++ b/results/classifier/118/device/1754
@@ -0,0 +1,46 @@
+device: 0.852
+performance: 0.808
+architecture: 0.782
+graphic: 0.781
+files: 0.712
+mistranslation: 0.667
+register: 0.490
+PID: 0.489
+boot: 0.483
+hypervisor: 0.482
+kernel: 0.481
+semantic: 0.470
+x86: 0.464
+i386: 0.460
+permissions: 0.452
+vnc: 0.424
+peripherals: 0.395
+assembly: 0.372
+debug: 0.371
+ppc: 0.367
+socket: 0.339
+user-level: 0.304
+network: 0.289
+arm: 0.277
+VMM: 0.274
+risc-v: 0.261
+KVM: 0.260
+TCG: 0.207
+virtual: 0.105
+
+QEMU wrongly requires SD card sizes to be a power of two
+Description of problem:
+QEMU arbitrarily requires SD card sizes to be a power of 2. However, this behavior does not match the real world, and I am unable to pass a *physical* SD card into the guest operating system.
+```
+$ sudo qemu-system-aarch64 -M raspi2b -drive file=/dev/mmcblk0,if=sd,format=raw
+qemu-system-aarch64: Invalid SD card size: 29.7 GiB
+SD card size has to be a power of 2, e.g. 32 GiB.
+You can resize disk images with 'qemu-img resize <imagefile> <new-size>'
+(note that this will lose data if you make the image smaller than it currently is).
+```
+Steps to reproduce:
+1. Insert a physical SD card into your host system and make a note of its device name. It will be something like `/dev/mmcblk0`
+2. Attempt to start a guest OS with the SD card attached. See the command above.
+3. You will get an error saying that the card size is not a power of two.
+Additional information:
+
diff --git a/results/classifier/118/device/1754597 b/results/classifier/118/device/1754597
new file mode 100644
index 00000000..db10d9bb
--- /dev/null
+++ b/results/classifier/118/device/1754597
@@ -0,0 +1,65 @@
+device: 0.810
+x86: 0.778
+boot: 0.762
+virtual: 0.747
+socket: 0.701
+graphic: 0.659
+architecture: 0.630
+PID: 0.617
+permissions: 0.595
+user-level: 0.588
+network: 0.577
+hypervisor: 0.559
+KVM: 0.549
+kernel: 0.532
+performance: 0.527
+risc-v: 0.516
+peripherals: 0.498
+semantic: 0.476
+files: 0.455
+mistranslation: 0.451
+ppc: 0.450
+register: 0.443
+arm: 0.430
+VMM: 0.411
+TCG: 0.402
+vnc: 0.390
+debug: 0.372
+i386: 0.337
+assembly: 0.315
+
+qemu-system-x86_64 broken on ubuntu 17.10
+
+I have run a virtual machine over the past three years without problems, but the update to Ubuntu 17.10 broke it: the machine falls into an infinite boot loop.
+
+$ qemu-system-x86_64 --version
+QEMU emulator version 2.10.1(Debian 1:2.10+dfsg-0ubuntu3.5)
+
+$ sudo qemu-system-x86_64 -enable-kvm -usb \
+    -chardev stdio,id=char0 \
+    -device usb-host,vendorid=0x056a,productid=0x00c6 \
+    -device usb-host,vendorid=0x04a9,productid=0x2220 \
+    -soundhw all \
+    -m 2048 -cpu core2duo -machine q35  \
+    -smp 2 \
+    -device usb-mouse  \
+    -vga std  \
+    -device isa-applesmc,osk="CONFIDENTIAL" \
+    -smbios type=2 \
+    -device ide-drive,bus=ide.0,drive=HDD \
+    -drive id=HDD,if=none,cache=none,file=hdd.img \
+    -device ide-drive,bus=ide.3,drive=ScrapHDD \
+    -drive id=ScrapHDD,if=none,cache=none,file=scrap.img \
+    -netdev tap,id=net0,ifname=tap0,script=no \
+    -device e1000,netdev=net0,id=nic0,mac=00:aa:00:60:00:01
+
+$ uname -a
+Linux behemoth 4.13.0-36-generic #40-Ubuntu SMP Fri Feb 16 20:07:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
+
+$ lsb_release -a
+No LSB modules are available.
+Distributor ID:	Ubuntu
+Description:	Ubuntu 17.10
+Release:	17.10
+Codename:	artful
+
diff --git a/results/classifier/118/device/1759 b/results/classifier/118/device/1759
new file mode 100644
index 00000000..1300321e
--- /dev/null
+++ b/results/classifier/118/device/1759
@@ -0,0 +1,40 @@
+device: 0.948
+i386: 0.935
+graphic: 0.929
+files: 0.893
+boot: 0.865
+architecture: 0.846
+PID: 0.768
+debug: 0.740
+x86: 0.728
+arm: 0.654
+vnc: 0.603
+performance: 0.543
+socket: 0.512
+register: 0.501
+TCG: 0.455
+mistranslation: 0.424
+semantic: 0.379
+ppc: 0.355
+user-level: 0.320
+network: 0.293
+VMM: 0.265
+assembly: 0.247
+permissions: 0.244
+kernel: 0.209
+risc-v: 0.196
+virtual: 0.148
+hypervisor: 0.134
+peripherals: 0.036
+KVM: 0.030
+
+qemu-system-i386 error during install windows 95/98
+Description of problem:
+Installation of the Windows starts but when Windows 95 is supposed to copy files it failes like: ![qemu803_win95](/uploads/40e94adda4cdf5c57fa751d5db04ef7b/qemu803_win95.png)
+Installation of Windows 98 failes like: ![qemu803_win98](/uploads/110ece638cd71f8ec41dd029379af807/qemu803_win98.png)
+Steps to reproduce:
+1. get boot floppy & install cd for windows 95
+2. create hard drive C image
+3. try to install Windows 95
+Additional information:
+
diff --git a/results/classifier/118/device/1759492 b/results/classifier/118/device/1759492
new file mode 100644
index 00000000..59c22f20
--- /dev/null
+++ b/results/classifier/118/device/1759492
@@ -0,0 +1,51 @@
+device: 0.852
+graphic: 0.837
+virtual: 0.819
+mistranslation: 0.697
+semantic: 0.653
+user-level: 0.648
+performance: 0.638
+network: 0.566
+hypervisor: 0.561
+i386: 0.543
+peripherals: 0.515
+register: 0.509
+files: 0.508
+permissions: 0.505
+architecture: 0.492
+debug: 0.490
+vnc: 0.472
+risc-v: 0.470
+x86: 0.459
+ppc: 0.456
+PID: 0.443
+VMM: 0.439
+socket: 0.414
+boot: 0.385
+TCG: 0.362
+assembly: 0.328
+KVM: 0.312
+kernel: 0.303
+arm: 0.240
+
+suspend/resume is not supported for vm with tpm device
+
+I have used libvirt with qemu to create a vm with tpm device, when I suspend the vm and resume it, libvirt will
+raise error:
+libvirtError: internal error: process exited while connecting to monitor: Enter char_pty_open
+I find some materials:
+https://wiki.qemu.org/Features/TPM
+https://lists.gnu.org/archive/html/qemu-devel/2015-05/msg05355.html
+They present qemu haven't supported tpm suspend/resume, Does someone have any advice on how to resolve the problem?
+
+qemu version: 2.10.2
+vm image version: centos 7.2
+
+Thanks
+
+The QEMU project is currently considering to move 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 to "New" within the next 60 days, otherwise this report will be marked as "Expired". Or mark it as "Fix Released" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience.
+
+
+[Expired for QEMU because there has been no activity for 60 days.]
+