Stay organized with collections
Save and categorize content based on your preferences.
If you're encountering I/O timeout errors on your Confidential VM instance, latency
might be exceeding the default timeout parameter for I/O operations submitted to
NVMe devices.
To increase the timeout parameter, add the following lines to the
/lib/udev/rules.d/65-gce-disk-naming.rules file on your VM, and then reboot:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-09 UTC."],[[["\u003cp\u003eI/O timeout errors on Confidential VM instances can occur when latency exceeds the default timeout for NVMe devices.\u003c/p\u003e\n"],["\u003cp\u003eIncreasing the I/O timeout parameter can resolve these errors.\u003c/p\u003e\n"],["\u003cp\u003eTo increase the timeout, edit the \u003ccode\u003e/lib/udev/rules.d/65-gce-disk-naming.rules\u003c/code\u003e file on the VM.\u003c/p\u003e\n"],["\u003cp\u003eAfter editing the file, the VM must be rebooted for the changes to take effect.\u003c/p\u003e\n"]]],[],null,[]]
