Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[viostor] io hung can not recover #1204

Open
lixianming19951001 opened this issue Nov 29, 2024 · 0 comments
Open

[viostor] io hung can not recover #1204

lixianming19951001 opened this issue Nov 29, 2024 · 0 comments
Assignees
Labels

Comments

@lixianming19951001
Copy link

Describe the bug
windows io hung can not recover

To Reproduce
I downloaded the code from the master branch and reset it to commit 379f291 for compilation
My VM originally had a driver version of 24000
I replaced it with the viostor I compiled myself

  1. start a vm
    I have a local file like windows-2022-legacy-datacenter.raw, and I use SPDK AIO bdev to start the virtual machine with the vhost user protocol
  2. Use fio to stress test the C driver
    fio --name=fio-randwrite --filename=C:\test --direct=1 --iodepth=32 --rw=randwrite -thread -time_based -refill_buffers -norandommap -randrepeat=0 -group_reporting --blocksize=64k -numjobs=32 -size=30G -runtime=60000 --ioengine=windowsaio --cpus_allowed_policy=split
  3. Stop SPDK, and after sleeping for 2 minutes, start SPDK again
  4. windows io hung and can not recover
    hung
  5. Final black screen
    dark

Host:

  • Disto: [e.g. Fedora, Ubuntu, Proxmox]
  • Kernel version :5.4.56
  • QEMU version : 5.2.0
  • QEMU command line :I'm sorry, I can't provide that
  • libvirt version :4.7.0
  • libvirt XML file : I'm sorry, I can't provide that

VM:

  • Windows version : windows server 2022 datacenter
  • Which driver has a problem:viostor
  • Driver version or commit hash that was used to build the driver:379f2910b85bb6b32a0991904d2402420957bdb6

Additional context
The version before 379f291 had no issues and could automatically recover fio

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants