test_driver: Implement virDomainGetLaunchSecurityInfo

Since the behaviour of launch security is heavily dependent on 3rd party
vendors (e.g. AMD SEV) where the data returned can be essentially
anything, the most reasonable approach here in the test driver is not to
try return any data.

Signed-off-by: Ilias Stamatis <stamatis.iliass@gmail.com>
Reviewed-by: Erik Skultety <eskultet@redhat.com>

diff --git a/src/test/test_driver.c b/src/test/test_driver.c
index bf9622d5c7170a164d1883d02663691bb2758f8f..8ef843b203d1c7b9d832d2f005b3b75963a9be91 100644 (file)
--- a/src/test/test_driver.c
+++ b/src/test/test_driver.c
@@ -2399,6 +2399,19 @@ testDomainGetOSType(virDomainPtr dom ATTRIBUTE_UNUSED)
 }
 
 
+static int
+testDomainGetLaunchSecurityInfo(virDomainPtr domain ATTRIBUTE_UNUSED,
+                                virTypedParameterPtr *params ATTRIBUTE_UNUSED,
+                                int *nparams,
+                                unsigned int flags)
+{
+    virCheckFlags(0, -1);
+
+    *nparams = 0;
+    return 0;
+}
+
+
 static unsigned long long
 testDomainGetMaxMemory(virDomainPtr domain)
 {
@@ -7126,6 +7139,7 @@ static virHypervisorDriver testHypervisorDriver = {
     .domainDestroy = testDomainDestroy, /* 0.1.1 */
     .domainDestroyFlags = testDomainDestroyFlags, /* 4.2.0 */
     .domainGetOSType = testDomainGetOSType, /* 0.1.9 */
+    .domainGetLaunchSecurityInfo = testDomainGetLaunchSecurityInfo, /* 5.5.0 */
     .domainGetMaxMemory = testDomainGetMaxMemory, /* 0.1.4 */
     .domainSetMaxMemory = testDomainSetMaxMemory, /* 0.1.1 */
     .domainSetMemory = testDomainSetMemory, /* 0.1.4 */