[PATCH] Set device model when creating rfb console via XenAPI

[Jim Fehlig <jfehlig@novell.com>]

[-- Attachment #1: Type: text/plain, Size: 283 bytes --]

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>


[-- Attachment #2: xenapi-console-dm.diff --]
[-- Type: text/x-patch, Size: 897 bytes --]

diff -r dc0f82bcc7a1 tools/python/xen/xend/XendConfig.py
--- a/tools/python/xen/xend/XendConfig.py	Thu Mar 13 15:00:43 2008 -0600
+++ b/tools/python/xen/xend/XendConfig.py	Thu Mar 13 15:02:13 2008 -0600
@@ -1282,6 +1282,12 @@ class XendConfig(dict):
                     target['devices'][dev_uuid] = ('vfb', dev_info)
                     target['console_refs'].append(dev_uuid)
 
+                    # if console is rfb, set device_model ensuring qemu
+                    # is invoked for pvfb services
+                    if 'device_model' not in target['platform']:
+                        target['platform']['device_model'] = \
+                            xen.util.auxbin.pathTo("qemu-dm")
+
                     # Finally, if we are a pvfb, we need to make a vkbd
                     # as well that is not really exposed to Xen API
                     vkbd_uuid = uuid.createString()

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel