Red Hat Bugzilla – Bug 225413
Useless xen-vncfb process is created for fully virtualized domains
Last modified: 2010-10-22 08:45:30 EDT
Description of problem:
When a fully virtualized domain is started (via xm create <dom>), a xen-vncfb
process is created. However, fully virtualized domains do not require this for
the frame buffer, so it eats up a slot in the process table for no reason.
Interestingly, the useless xen-vncfb process is not created when doing a fully
virt install via virt-install; only on subsequent reboots.
xenstore-ls shows a vkbd and vfb configured for the domain, so it seems
something is mis-configured.
This is pretty simple to reproduce; just install a fully virt domain (say, RHEL4
U4), shut it down, and then start it via "xm create"; you'll see the xen-vncfb
Created attachment 146926 [details]
Rewrite old-style config into new style only for pv domains
The PVFB backend (either xen-vncfb or xen-sdlfb) is only run when the device is
configured. Unfortunately, fv configuration looks like old-style pv
configuration. The backward compatibility code rewrites it into new style,
which makes it configured. Don't do that.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Built into dist-5E-qu-candidate as xen-3.0.3-27.el5
* Thu Jun 14 2007 Daniel P. Berrange <firstname.lastname@example.org> - 3.0.3-27.el5
- Don't start a xen-vncfb process for HVM (rhbz#225413)
Thanks for the update! I'll let engineering know it's fixed in the 5.1
Resolution set to: 'RHEL 5.1'
Ticket type set to: 'Problem'
This event sent from IssueTracker by gcase
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.