[libvirt] [PULL v2 17/43] memory-device: fix alignment error message

[Eduardo Habkost]

From: David Hildenbrand <david at redhat.com>

We're missing "x" after the leading 0.

Reviewed-by: David Gibson <david at gibson.dropbear.id.au>
Reviewed-by: Igor Mammedov <imammedo at redhat.com>
Signed-off-by: David Hildenbrand <david at redhat.com>
Message-Id: <20181005092024.14344-2-david at redhat.com>
Signed-off-by: Eduardo Habkost <ehabkost at redhat.com>
---
 hw/mem/memory-device.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/hw/mem/memory-device.c b/hw/mem/memory-device.c
index 6de4f70bb4..0b52fe2c5e 100644
--- a/hw/mem/memory-device.c
+++ b/hw/mem/memory-device.c
@@ -120,7 +120,7 @@ uint64_t memory_device_get_free_addr(MachineState *ms, const uint64_t *hint,
 
     /* address_space_start indicates the maximum alignment we expect */
     if (QEMU_ALIGN_UP(address_space_start, align) != address_space_start) {
-        error_setg(errp, "the alignment (0%" PRIx64 ") is not supported",
+        error_setg(errp, "the alignment (0x%" PRIx64 ") is not supported",
                    align);
         return 0;
     }
-- 
2.18.0.rc1.1.g3f1ff2140