ia64/xen-unstable

changeset 17228:06dbce4a60f9

Set device model when creating rfb console via XenAPI

When creating a rfb console via XenAPI the device model is not being
set to qemu-dm, resulting in no pvfb since qemu-dm is not launched
when domU is started. This patch sets device model when a rfb console
is created via XenAPI.

Signed-off-by: Jim Fehlig <jfehlig@novell.com>
author Keir Fraser <keir.fraser@citrix.com>
date Tue Mar 18 11:06:26 2008 +0000 (2008-03-18)
parents 939ceafa5ef9
children c949248d590a
files tools/python/xen/xend/XendConfig.py
line diff
     1.1 --- a/tools/python/xen/xend/XendConfig.py	Tue Mar 18 11:05:53 2008 +0000
     1.2 +++ b/tools/python/xen/xend/XendConfig.py	Tue Mar 18 11:06:26 2008 +0000
     1.3 @@ -1282,6 +1282,12 @@ class XendConfig(dict):
     1.4                      target['devices'][dev_uuid] = ('vfb', dev_info)
     1.5                      target['console_refs'].append(dev_uuid)
     1.6  
     1.7 +                    # if console is rfb, set device_model ensuring qemu
     1.8 +                    # is invoked for pvfb services
     1.9 +                    if 'device_model' not in target['platform']:
    1.10 +                        target['platform']['device_model'] = \
    1.11 +                            xen.util.auxbin.pathTo("qemu-dm")
    1.12 +
    1.13                      # Finally, if we are a pvfb, we need to make a vkbd
    1.14                      # as well that is not really exposed to Xen API
    1.15                      vkbd_uuid = uuid.createString()