Re: [PATCH 5/7] Default console target type with no <target> element

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 10/20/2011 08:47 AM, Daniel P. Berrange wrote:
From: "Daniel P. Berrange"<berrange@xxxxxxxxxx>

When no<target>  element was set at all, the default console
target type was not being honoured

* src/conf/domain_conf.c: Set default target type for consoles
   with no<target>
---
  src/conf/domain_conf.c |    3 +++
  1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/src/conf/domain_conf.c b/src/conf/domain_conf.c
index f90bece..a4d91ed 100644
--- a/src/conf/domain_conf.c
+++ b/src/conf/domain_conf.c
@@ -3913,6 +3913,9 @@ virDomainChrDefParseXML(virCapsPtr caps,
                               nodeName);
      }

+    /* Initialize this now, in case there is no actual 'target' element at all */
+    def->targetType = virDomainChrDefaultTargetType(caps, def->deviceType);
+

ACK.

--
Eric Blake   eblake@xxxxxxxxxx    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list


[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]