summary refs log tree commit diff stats
path: root/results/classifier/108/other/1459622
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/108/other/1459622')
-rw-r--r--results/classifier/108/other/145962243
1 files changed, 43 insertions, 0 deletions
diff --git a/results/classifier/108/other/1459622 b/results/classifier/108/other/1459622
new file mode 100644
index 000000000..a5e075dc7
--- /dev/null
+++ b/results/classifier/108/other/1459622
@@ -0,0 +1,43 @@
+performance: 0.894
+device: 0.861
+graphic: 0.741
+PID: 0.727
+KVM: 0.723
+vnc: 0.635
+network: 0.552
+permissions: 0.543
+boot: 0.524
+semantic: 0.484
+other: 0.355
+socket: 0.342
+files: 0.310
+debug: 0.185
+
+firefox hang with virtfs
+
+Firefox hangs once it starts to load pages. I tried to delete .cache/mozilla/ and .mozilla/ but it doesn't help. But if I mount tmpfs on to .mozilla (not necessary for .cache/mozilla/), pages loads fine.
+
+I started the vm as root (sudo) with the following command: qemu-system-x86_64 -enable-kvm -m 4G -virtfs local,mount_tag=qemu,security_model=passthrough,path=/mnt/qemu/ -kernel /mnt/qemu/boot/vmlinuz-linux -initrd /mnt/qemu/boot/initramfs-linux-fallback.img -append 'rw root=qemu fstype=9p' -usbdevice tablet -vga qxl -spice port=12345,disable-ticketing
+
+/mnt/qemu is a btrfs snapshot of the subvolume used as the host root
+
+Arch Linux, qemu 2.3.0, firefox 38.0.1
+
+
+
+Same situation here:
+Firefox can't handle ~/.mozilla to be a virtio-9p mount.
+Here the subvolume is ext4, mounted only at /home.
+
+I also noticed that chromium is working, but it complains about some errors:
+getrlimit(RLIMIT_NOFILE) failed
+[4809:4839:0804/230514:ERROR:backend_impl.cc(1365)] Unable to map Index file
+[4809:4839:0804/230514:ERROR:backend_impl.cc(1365)] Unable to map Index file
+[4809:4840:0804/230514:ERROR:cache_creator.cc(133)] Unable to create cache
+[4845:4845:0804/230514:ERROR:sandbox_linux.cc(340)] InitializeSandbox() called with multiple threads in process gpu-process
+
+
+Looking through old bug tickets... 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.]
+