[Bug 1815252] Re: virtio-9p-pci passthrough fsync hang

[Thomas Huth]

Sorry that nobody commented to this ticket in the past... Anyway:

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 please 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.


** Changed in: qemu
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1815252

Title:
  virtio-9p-pci passthrough fsync hang

Status in QEMU:
  Incomplete

Bug description:
  Tested against QEMU: e47f81b617684c4546af286d307b69014a83538a

  and $qemu-system-x86_64 --version
  QEMU emulator version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.9)
  Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers

  + exec sudo qemu-system-x86_64 -enable-kvm -bios /usr/share/ovmf/OVMF.fd -cpu 
host -smp sockets=1,cpus=4,cores=2 -m 2048 -vga none -nographic -chardev 
socket,id=chrtpm0,path=/tmp/clrwifi/swtpm2/tpm-sock -tpmdev 
emulator,id=tpm0,chardev=chrtpm0 -device tpm-tis,tpmdev=tpm0 -device 
virtio-rng-pci -netdev user,id=mynet0,hostfwd=tcp::10022-:22 -device 
virtio-net-pci,netdev=mynet0 -kernel /home/.../Documents/c/iwd/tools/bzImage 
-append 'console=ttyS0,115200n8 quiet kvm-intel.nested=1 init=/usr/bin/bash 
initcall_debug tsc=reliable no_timer_check noreplace-smp cryptomgr.notests 
rootfstype=9p root=/dev/root rootflags=trans=virtio,version=9p2000.u rw' -fsdev 
local,id=fsdev-root,path=mnt,security_model=passthrough -device 
virtio-9p-pci,fsdev=fsdev-root,mount_tag=/dev/root
  [    0.000000] Linux version 4.19.0-rc2 (...) (gcc version 7.3.0 (Ubuntu 
7.3.0-27ubuntu1~18.04)) #10 SMP Fri Feb 8 13:55:20 PST 2019
  [    0.000000] Command line: console=ttyS0,115200n8 quiet kvm-intel.nested=1 
init=/usr/bin/bash initcall_debug tsc=reliable no_timer_check noreplace-smp 
cryptomgr.notests rootfstype=9p root=/dev/root 
rootflags=trans=virtio,version=9p2000.u rw
  [    0.000000] KERNEL supported cpus:
  [    0.000000]   Intel GenuineIntel
  [    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
  [    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
  [    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
  [    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
  [    0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 
bytes, using 'standard' format.
  [    0.000000] BIOS-provided physical RAM map:
  [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
  [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000007fffff] usable
  [    0.000000] BIOS-e820: [mem 0x0000000000800000-0x0000000000807fff] ACPI NVS
  [    0.000000] BIOS-e820: [mem 0x0000000000808000-0x000000000080ffff] usable
  [    0.000000] BIOS-e820: [mem 0x0000000000810000-0x00000000008fffff] ACPI NVS
  [    0.000000] BIOS-e820: [mem 0x0000000000900000-0x000000007e87efff] usable
  [    0.000000] BIOS-e820: [mem 0x000000007e87f000-0x000000007e888fff] ACPI NVS
  [    0.000000] BIOS-e820: [mem 0x000000007e889000-0x000000007e889fff] ACPI 
data
  [    0.000000] BIOS-e820: [mem 0x000000007e88a000-0x000000007e88bfff] usable
  [    0.000000] BIOS-e820: [mem 0x000000007e88c000-0x000000007e88ffff] ACPI NVS
  [    0.000000] BIOS-e820: [mem 0x000000007e890000-0x000000007e8a9fff] reserved
  [    0.000000] BIOS-e820: [mem 0x000000007e8aa000-0x000000007e8b9fff] ACPI NVS
  [    0.000000] BIOS-e820: [mem 0x000000007e8ba000-0x000000007e8bafff] reserved
  [    0.000000] BIOS-e820: [mem 0x000000007e8bb000-0x000000007e9e5fff] usable
  [    0.000000] BIOS-e820: [mem 0x000000007e9e6000-0x000000007e9edfff] ACPI NVS
  [    0.000000] BIOS-e820: [mem 0x000000007e9ee000-0x000000007eb1afff] reserved
  [    0.000000] BIOS-e820: [mem 0x000000007eb1b000-0x000000007fb9afff] usable
  [    0.000000] BIOS-e820: [mem 0x000000007fb9b000-0x000000007fbf2fff] reserved
  [    0.000000] BIOS-e820: [mem 0x000000007fbf3000-0x000000007fbfafff] ACPI 
data
  [    0.000000] BIOS-e820: [mem 0x000000007fbfb000-0x000000007fbfefff] ACPI NVS
  [    0.000000] BIOS-e820: [mem 0x000000007fbff000-0x000000007ff3ffff] usable
  [    0.000000] BIOS-e820: [mem 0x000000007ff40000-0x000000007ff5ffff] reserved
  [    0.000000] BIOS-e820: [mem 0x000000007ff60000-0x000000007fffffff] ACPI NVS
  [    0.352469] acpiphp_ibm: ibm_acpiphp_init: acpi_walk_namespace failed
  Started bpfilter
  bash: cannot set terminal process group (-1): Inappropriate ioctl for device
  bash: no job control in this shell
  grep: /proc/cpuinfo: No such file or directory
  grep: /proc/cpuinfo: No such file or directory
  root@clr / # passwd
  ...
  openat(AT_FDCWD, "/etc/nshadow", O_WRONLY|O_CREAT|O_TRUNC, 0666) = 4
  umask(077)                              = 077
  openat(AT_FDCWD, "/etc/shadow", O_RDONLY|O_CREAT|O_CLOEXEC, 000) = 5
  fcntl(5, F_GETFL)                       = 0x8000 (flags O_RDONLY|O_LARGEFILE)
  fstat(5, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
  fchown(4, 0, 0)                         = 0
  fchmod(4, 0100644)                      = 0
  lseek(5, 0, SEEK_CUR)                   = 0
  fstat(5, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
  read(5, "", 8192)                       = 0
  close(5)                                = 0
  fstat(4, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
  write(4, "root:$6$jihvB1NonG88C5Yt$kvDCqF7"..., 124) = 124
  fsync(4 <- hung here

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1815252/+subscriptions