From dd71adaeb09a1efc4a94835151cab9aa93cdd816 Mon Sep 17 00:00:00 2001 From: Paul Vaduva Date: Wed, 8 Nov 2017 13:13:30 +0100 Subject: Update release info with limitations from COSNOSCR-544 Signed-off-by: Paul Vaduva --- .../doc/known_bugs_and_limitations.xml | 31 ++++++++++++++++++++-- 1 file changed, 29 insertions(+), 2 deletions(-) (limited to 'book-enea-nfv-core-release-info') diff --git a/book-enea-nfv-core-release-info/doc/known_bugs_and_limitations.xml b/book-enea-nfv-core-release-info/doc/known_bugs_and_limitations.xml index d87ebe2..77d9264 100644 --- a/book-enea-nfv-core-release-info/doc/known_bugs_and_limitations.xml +++ b/book-enea-nfv-core-release-info/doc/known_bugs_and_limitations.xml @@ -27,7 +27,7 @@ For an aarch64 architecture, QEMU describes a CPU in terms of Vendor, Model and Revision number in contrast with the x86 architecture, where CPU supported features (e.g. the instruction - set supported) are used. + set supported) are used. QEMU lacks support in describing a CPU in terms of features for an aarch64 architecture, causing the migration of VMs between @@ -367,6 +367,33 @@ + + + Volumes fail to attach during the first few seconds of a VM + booting procedure + + + + Description and Impact + + There is a short period of a few seconds after a VM stated + the boot procedure when attaching an external volume will result + in an error to claim the qemu assigned bus in the guest Image + kernel. + + Disks attached in the first few seconds of the booting + procedure of a VM, will fail to register in the guest VM.. + + + + Workaround + + Attach volumes to a VM only before the VM is booting or + after the period of a few seconds has passed since the booting + procedure started. + + + @@ -402,4 +429,4 @@ --> - + \ No newline at end of file -- cgit v1.2.3-54-g00ecf