diff options
Diffstat (limited to '')
| -rw-r--r-- | results/classifier/108/other/1459 | 50 | ||||
| -rw-r--r-- | results/classifier/108/other/1459622 | 43 | ||||
| -rw-r--r-- | results/classifier/108/other/1459626 | 35 |
3 files changed, 128 insertions, 0 deletions
diff --git a/results/classifier/108/other/1459 b/results/classifier/108/other/1459 new file mode 100644 index 00000000..1a37572b --- /dev/null +++ b/results/classifier/108/other/1459 @@ -0,0 +1,50 @@ +device: 0.792 +graphic: 0.690 +performance: 0.687 +PID: 0.635 +vnc: 0.594 +network: 0.489 +socket: 0.439 +semantic: 0.433 +files: 0.378 +permissions: 0.364 +debug: 0.266 +boot: 0.227 +other: 0.188 +KVM: 0.156 + +analyze-migration.py doesn't account for saved blocks +Description of problem: + +Steps to reproduce: +1. Make a migration snapshot that includes incremental block device (from HMP: `migrate -i "exec: cat > snap"`) +2. Load the snapshot: `scripts/analyze-migration.py -f snap` + + +``` +Traceback (most recent call last): + File "scripts/analyze-migration.py", line 605, in <module> + dump.read(dump_memory = args.memory) + File "scripts/analyze-migration.py", line 539, in read + classdesc = self.section_classes[section_key] +KeyError: ('block', 0) +``` +Additional information: +Here's pseudocode derived from `block_load` in `migration/block.c`: + +``` +N blocks of the following: + + read 64 bits: sector number and flags + (blk->sector << BDRV_SECTOR_BITS) | flags + + if flags & BLK_MIG_FLAG_EOS: + break + if flags & BLK_MIG_FLAG_PROGRESS + continue + if flags & BLK_MIG_FLAG_DEVICE_BLOCK + byte: name length + length bytes: device name string + if not flags & BLK_MIG_FLAG_ZERO_BLOCK: + read (1 << 20) bytes +``` diff --git a/results/classifier/108/other/1459622 b/results/classifier/108/other/1459622 new file mode 100644 index 00000000..a5e075dc --- /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.] + diff --git a/results/classifier/108/other/1459626 b/results/classifier/108/other/1459626 new file mode 100644 index 00000000..d30fcc41 --- /dev/null +++ b/results/classifier/108/other/1459626 @@ -0,0 +1,35 @@ +graphic: 0.717 +performance: 0.716 +device: 0.689 +KVM: 0.566 +boot: 0.506 +semantic: 0.476 +other: 0.460 +permissions: 0.412 +PID: 0.373 +network: 0.329 +files: 0.328 +socket: 0.269 +vnc: 0.225 +debug: 0.213 + +emacs (gtk3) core dumped with -vga qxl + +Emacs (gtk3) exited with bus error and core dumped with -vga qxl. If I use the builtin modesetting xorg driver, emacs could survive for a short while sometimes. If I use xf86-video-qxl (git r587.8babd05), it dies right away with the same error. It seems to corrupt xorg at some point as well, because sometimes I cannot exit i3 properly and gnome-terminal can go crazy afterwards (all letters become empty retangles). + +It doesn't seem to happen with other -vga driver. + +Error message is attached. Can also provide the core dumped but it's of 47M. + +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, xorg-server 1.17.1, linux 4.0.4, gtk 3.16.3, glib 2.44.1 + + + +Looking through old bug tickets... can you still reproduce this issue with the latest versions of QEMU, x11, kernel, spice, etc.? Or could we close this ticket nowadays? + +[Expired for QEMU because there has been no activity for 60 days.] + |