From be0503dd0ab769f8a947846d4942d97e3c681737 Mon Sep 17 00:00:00 2001 From: Andrew David Wong Date: Mon, 2 Jan 2017 14:19:44 -0800 Subject: [PATCH] Clarify that second issue does not affect R3.2 or later --- configuration/secondary-storage.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/configuration/secondary-storage.md b/configuration/secondary-storage.md index a4314bbe..f04b6665 100644 --- a/configuration/secondary-storage.md +++ b/configuration/secondary-storage.md @@ -32,7 +32,8 @@ Known Issues The same problem may occur if the above procedure is attempted on a [TemplateVM][]. [[1]] - * After implementing the above procedure, starting `my-new-appvm` will cause + * This issue applies only to R3.1, not R3.2 or later: + After implementing the above procedure, starting `my-new-appvm` will cause dom0 notifications to occur stating that loop devices have been attached to dom0. This is normal. (No untrusted devices are actually being mounted to dom0.) Do not attempt to detach these disks. (They will automatically be