2017-08-30 18:35:34 +03:00
<domain type= 'qemu' >
<name > QEMUGuest1</name>
<uuid > c7a5fdbd-edaf-9455-926a-d65c16db1809</uuid>
<memory unit= 'KiB' > 219136</memory>
<currentMemory unit= 'KiB' > 219136</currentMemory>
<vcpu placement= 'static' > 1</vcpu>
<os >
<type arch= 'i686' machine= 'pc' > hvm</type>
<boot dev= 'hd' />
</os>
<clock offset= 'utc' />
<on_poweroff > destroy</on_poweroff>
<on_reboot > restart</on_reboot>
<on_crash > destroy</on_crash>
<devices >
<emulator > /usr/bin/qemu-system-x86_64</emulator>
<disk type= 'network' device= 'disk' >
<driver name= 'qemu' type= 'raw' cache= 'none' />
qemu: Add TLS support for Veritas HyperScale (VxHS)
Alter qemu command line generation in order to possibly add TLS for
a suitably configured domain.
Sample TLS args generated by libvirt -
-object tls-creds-x509,id=objvirtio-disk0_tls0,dir=/etc/pki/qemu,\
endpoint=client,verify-peer=yes \
-drive file.driver=vxhs,file.tls-creds=objvirtio-disk0_tls0,\
file.vdisk-id=eb90327c-8302-4725-9e1b-4e85ed4dc251,\
file.server.type=tcp,file.server.host=192.168.0.1,\
file.server.port=9999,format=raw,if=none,\
id=drive-virtio-disk0,cache=none \
-device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,\
id=virtio-disk0
Update the qemuxml2argvtest with a couple of examples. One for a
simple case and the other a bit more complex where multiple VxHS disks
are added where at least one uses a VxHS that doesn't require TLS
credentials and thus sets the domain disk source attribute "tls = 'no'".
Update the hotplug to be able to handle processing the tlsAlias whether
it's to add the TLS object when hotplugging a disk or to remove the TLS
object when hot unplugging a disk. The hot plug/unplug code is largely
generic, but the addition code does make the VXHS specific checks only
because it needs to grab the correct config directory and generate the
object as the command line would do.
Signed-off-by: Ashish Mittal <Ashish.Mittal@veritas.com>
Signed-off-by: John Ferlan <jferlan@redhat.com>
2017-08-30 18:06:00 +03:00
<source protocol= 'vxhs' name= 'eb90327c-8302-4725-9e1b-4e85ed4dc251' >
2017-08-30 18:35:34 +03:00
<host name= '192.168.0.1' port= '9999' />
</source>
<target dev= 'vda' bus= 'virtio' />
<serial > eb90327c-8302-4725-9e1b-4e85ed4dc251</serial>
<address type= 'pci' domain= '0x0000' bus= '0x00' slot= '0x04' function= '0x0' />
</disk>
qemu: Add TLS support for Veritas HyperScale (VxHS)
Alter qemu command line generation in order to possibly add TLS for
a suitably configured domain.
Sample TLS args generated by libvirt -
-object tls-creds-x509,id=objvirtio-disk0_tls0,dir=/etc/pki/qemu,\
endpoint=client,verify-peer=yes \
-drive file.driver=vxhs,file.tls-creds=objvirtio-disk0_tls0,\
file.vdisk-id=eb90327c-8302-4725-9e1b-4e85ed4dc251,\
file.server.type=tcp,file.server.host=192.168.0.1,\
file.server.port=9999,format=raw,if=none,\
id=drive-virtio-disk0,cache=none \
-device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,\
id=virtio-disk0
Update the qemuxml2argvtest with a couple of examples. One for a
simple case and the other a bit more complex where multiple VxHS disks
are added where at least one uses a VxHS that doesn't require TLS
credentials and thus sets the domain disk source attribute "tls = 'no'".
Update the hotplug to be able to handle processing the tlsAlias whether
it's to add the TLS object when hotplugging a disk or to remove the TLS
object when hot unplugging a disk. The hot plug/unplug code is largely
generic, but the addition code does make the VXHS specific checks only
because it needs to grab the correct config directory and generate the
object as the command line would do.
Signed-off-by: Ashish Mittal <Ashish.Mittal@veritas.com>
Signed-off-by: John Ferlan <jferlan@redhat.com>
2017-08-30 18:06:00 +03:00
<disk type= 'network' device= 'disk' >
<driver name= 'qemu' type= 'raw' cache= 'none' />
<source protocol= 'vxhs' name= 'eb90327c-8302-4725-9e1b-4e85ed4dc252' >
<host name= '192.168.0.2' port= '9999' />
</source>
<target dev= 'vdb' bus= 'virtio' />
<serial > eb90327c-8302-4725-9e1b-4e85ed4dc252</serial>
<address type= 'pci' domain= '0x0000' bus= '0x00' slot= '0x05' function= '0x0' />
</disk>
<disk type= 'network' device= 'disk' >
<driver name= 'qemu' type= 'raw' cache= 'none' />
<source protocol= 'vxhs' name= 'eb90327c-8302-4725-9e1b-4e85ed4dc253' tls= 'no' >
<host name= '192.168.0.3' port= '9999' />
</source>
<target dev= 'vdc' bus= 'virtio' />
<serial > eb90327c-8302-4725-9e1b-4e85ed4dc252</serial>
<address type= 'pci' domain= '0x0000' bus= '0x00' slot= '0x06' function= '0x0' />
</disk>
2018-05-29 14:57:17 +03:00
<disk type= 'network' device= 'disk' >
<driver name= 'qemu' type= 'raw' cache= 'none' />
<source protocol= 'nbd' tls= 'yes' >
<host name= 'example.com' port= '1234' />
</source>
<target dev= 'vdd' bus= 'virtio' />
<address type= 'pci' domain= '0x0000' bus= '0x00' slot= '0x07' function= '0x0' />
</disk>
2017-08-30 18:35:34 +03:00
<controller type= 'usb' index= '0' >
<address type= 'pci' domain= '0x0000' bus= '0x00' slot= '0x01' function= '0x2' />
</controller>
<controller type= 'pci' index= '0' model= 'pci-root' />
<input type= 'mouse' bus= 'ps2' />
<input type= 'keyboard' bus= 'ps2' />
<memballoon model= 'none' />
</devices>
</domain>
