From 6dae564a9a1b56017d876491dc1bcc49eee81f01 Mon Sep 17 00:00:00 2001 From: Paul Vaduva Date: Tue, 7 Nov 2017 13:47:43 +0100 Subject: Updated doc to account for limtations in COSNOSCR-540 Signed-off-by: Paul Vaduva Conflicts: book-enea-nfv-core-release-info/doc/known_bugs_and_limitations.xml --- .../doc/known_bugs_and_limitations.xml | 19 +++++++++---------- 1 file changed, 9 insertions(+), 10 deletions(-) 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 9494eae..d87ebe2 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 @@ -24,15 +24,14 @@ Description and Impact: - For aarch64 architecture qemu describes a CPU in terms of - Vendor, Model and Revision number in contrast with x86 - architecture where CPU supported features (e. g. instruction set - supported) are used. - - Due to lack of support in qemu for describing a cpu in terms - of features for aarch64 architecture (e. g. instruction set - supported) there will be impossible to migrate VMs between hosts - with different revision CPUs. + 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. + + QEMU lacks support in describing a CPU in terms of features + for an aarch64 architecture, causing the migration of VMs between + hosts with different CPU revisions to fail. @@ -403,4 +402,4 @@ --> - \ No newline at end of file + -- cgit v1.2.3-54-g00ecf