diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-05-30 16:52:07 +0200 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-05-30 16:52:17 +0200 |
| commit | 9260319e7411ff8281700a532caa436f40120ec4 (patch) | |
| tree | 2f6bfe5f3458dd49d328d3a9eb508595450adec0 /gitlab/issues/target_missing/host_missing/accel_missing/1569.toml | |
| parent | 225caa38269323af1bfc2daadff5ec8bd930747f (diff) | |
| download | qemu-analysis-9260319e7411ff8281700a532caa436f40120ec4.tar.gz qemu-analysis-9260319e7411ff8281700a532caa436f40120ec4.zip | |
gitlab scraper: download in toml and text format
Diffstat (limited to 'gitlab/issues/target_missing/host_missing/accel_missing/1569.toml')
| -rw-r--r-- | gitlab/issues/target_missing/host_missing/accel_missing/1569.toml | 35 |
1 files changed, 0 insertions, 35 deletions
diff --git a/gitlab/issues/target_missing/host_missing/accel_missing/1569.toml b/gitlab/issues/target_missing/host_missing/accel_missing/1569.toml deleted file mode 100644 index 41a0bdd92..000000000 --- a/gitlab/issues/target_missing/host_missing/accel_missing/1569.toml +++ /dev/null @@ -1,35 +0,0 @@ -id = 1569 -title = "NVMe FS operations hang after suspending and resuming both guest and host" -state = "opened" -created_at = "2023-03-30T19:26:39.695Z" -closed_at = "n/a" -labels = [] -url = "https://gitlab.com/qemu-project/qemu/-/issues/1569" -host-os = "Arch Linux" -host-arch = "x86_64" -qemu-version = "7.2.0 (Arch Linux package release 4)" -guest-os = "Void Linux" -guest-arch = "x86_64" -description = """Hello and thank you for your work on QEMU! - -Using the NVMe driver with my Seagate FireCuda 530 2TB M.2 works fine until I encounter this problem, which is reliably reproducible for me. - -When I suspend the guest and then suspend (s2idle) my host all is well until I resume the guest (manually with `virsh dompmwakeup $VMNAME`, after the host has resumed). Although the guest resumes and is interactive, it seems that anything involving filesystem operations hang forever and do not return. - -Suspending and resuming the Linux guest seems to work perfectly if I don't suspend/resume the host. - -Ultimately what I'm wanting to do is share the drive between VMs with qemu-storage-daemon. I can reproduce the problem in that scenario in much the same way. Using PCI passthrough with the same VM and device works fine and doesn't exhibit this problem. - -Hopefully that's clear enough - let me know if there's anything else I can provide.""" -reproduce = """1. Create a VM with a dedicated NVMe disk. -2. Boot an ISO and install to the disk. -3. Verify that suspend and resume works when not suspending the host. -4. Suspend the guest. -5. Suspend the host. -6. Wake the host. -7. Wake the guest. -8. Try just about anything that isn't likely already cached somewhere: `du -s /etc`.""" -additional = """I've attached the libvirt domain XML[1] and libvirtd debug logs for QEMU[2] ("1:qemu") that covers suspending the guest & host, resuming host & guest and doing something to cause a hang. I tried to leave enough time afterwards for any timeout to occur. - -1. [nvme-voidlinux.xml](/uploads/1dea47af096ce58175f7aa526eca455e/nvme-voidlinux.xml) -2. [nvme-qemu-debug.log](/uploads/42d3bed456a795069023a61d38fa5ccd/nvme-qemu-debug.log)""" |