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

[Xen-users] VNC problem in qemu-dm

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Michael Borokhovich <michaelbor@xxxxxxxxx>
  • Date: Thu, 21 Oct 2010 17:43:29 +0200
  • Delivery-date: Thu, 21 Oct 2010 08:44:50 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=O8FDdDJxK9d0bx6vKGnVhf4fY3xsArHWKZbaQ83T6LsDBnzNPBPnyvt0KwR2s5Zp5r tu1K1++cyX2e2ifejAoBCJd16Bs5l5Er6aQdk3eeIT9o2GxhRzc3uucfWJewqhSdrZsY +FLHFooPm3JciEXn+8HI2ElFZ4BXcD2ExOgXo=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>


In xen-3.1.0 there was a 'vncfb' used for the VNC server. In case of VNC crash I could simply restart the vncfb process and the VNC server was recovered.
In xen-3.4.2 there is a 'qemu-dm' process that is responsible for VNC servers of guest domains. Unfortunately, restarting the qemu-dm process causing xen to restart the VM.

Is there is any way to restart the VNC server for a guest domain without restarting the VM?

Thanks in advance,
Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.