diff options
Diffstat (limited to 'results/classifier/118/virtual/816860')
| -rw-r--r-- | results/classifier/118/virtual/816860 | 61 |
1 files changed, 61 insertions, 0 deletions
diff --git a/results/classifier/118/virtual/816860 b/results/classifier/118/virtual/816860 new file mode 100644 index 000000000..79de178ab --- /dev/null +++ b/results/classifier/118/virtual/816860 @@ -0,0 +1,61 @@ +virtual: 0.914 +KVM: 0.909 +performance: 0.878 +device: 0.772 +network: 0.741 +graphic: 0.713 +hypervisor: 0.696 +semantic: 0.651 +register: 0.601 +PID: 0.591 +vnc: 0.546 +permissions: 0.539 +architecture: 0.538 +ppc: 0.522 +kernel: 0.521 +socket: 0.508 +mistranslation: 0.483 +VMM: 0.476 +boot: 0.476 +peripherals: 0.459 +risc-v: 0.440 +files: 0.436 +x86: 0.363 +assembly: 0.357 +i386: 0.335 +user-level: 0.310 +arm: 0.296 +debug: 0.231 +TCG: 0.187 + +Guest machine freezes when NFS mount goes offline + +I have a virtual KVM machine that has 2 CDROM units with ISOs mounted from a NFS mount point. When NFS server goes offline the virtual machine blocks completely instead of throwing read errors for the CDROM device. + +Host: Proxmox VE 1.8-11 (Debian GNU/Linux 5.0) +KVM commandline version: QEMU emulator version 0.14.1 (qemu-kvm-devel) +Guest: Windows 7 professional SP 1 + +On Wed, Jul 27, 2011 at 10:09 AM, Igor Blanco <email address hidden> wrote: +> Public bug reported: +> +> I have a virtual KVM machine that has 2 CDROM units with ISOs mounted +> from a NFS mount point. When NFS server goes offline the virtual machine +> blocks completely instead of throwing read errors for the CDROM device. +> +> Host: Proxmox VE 1.8-11 (Debian GNU/Linux 5.0) +> KVM commandline version: QEMU emulator version 0.14.1 (qemu-kvm-devel) +> Guest: Windows 7 professional SP 1 + +Thanks for reporting this. There are instances where QEMU performs +blocking operations in a thread that will prevent the guest from +running. I suspect you are hitting this case and refactoring work +needs to be done to ensure that QEMU threads never block. + +Stefan + + +Can you still reproduce this problem with the latest version of QEMU (currently version 2.9.0)? + +[Expired for QEMU because there has been no activity for 60 days.] + |