This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 2215339 - [CNV-4.11] Windows guest paused after IO error
Summary: [CNV-4.11] Windows guest paused after IO error
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Storage
Version: 4.11.3
Hardware: x86_64
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Adam Litke
QA Contact: Jenia Peimer
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-15 15:13 UTC by José Enrique
Modified: 2023-12-14 16:11 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-12-14 16:11:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   CNV-30003 0 None None None 2023-12-14 16:11:47 UTC

Description José Enrique 2023-06-15 15:13:06 UTC 
Description of problem:

Windows Server 2019 guest paused after an IO error.

Storage based on IBM Spectrum Scale, volumeModefilesystem and accessMode ReadWriteMany.


How reproducible:


Steps to Reproduce:
1. Start a Windows Server guest
2. Run some storage stress test.
3. VM paused because IO error.

Version:
Openshift 4.11.3
IBM Spectrum Scale 2.7
Comment 2 Yan Du 2023-06-21 12:55:18 UTC 
VM paused because of IO error is an expected behavior.
And could you please describe the vm/vmi events to check when it started to pause
Comment 4 Yan Du 2023-06-28 12:20:51 UTC 
Are you able to resume the VM after paused by virtctl or UI? we need to understand why the IO error from the storage
Comment 23 Stefan Hajnoczi 2023-08-10 17:38:56 UTC 
By the way, the image size issue suggests another test:

Boot the VM without configuration changes but increase the image size to a multiple of 4,096 bytes first (e.g. "truncate %4096 /path/to/disk0/disk.img").

If the guest runs successfully with just the image size change, then we can be fairly sure the issue is caused by the image size.

Maybe some component should print a warning if the disk image is not a multiple of at least 512 bytes.
Note You need to log in before you can comment on or make changes to this bug.