because it want to state Closed. Otherwise, we don't notice when
the node gets deleted, and can't reliably shut the backend down.
Signed-off-by: Steven Smith <sos22@cam.ac.uk>
terminates, and that it cleans up its area of xenstore.
Tidy up argument parsing a little while I'm here.
Signed-off-by: Steven Smith <sos22@cam.ac.uk>
required if CONFIG_VT is enabled but the domain isn't currently
configured to use the PV framebuffer. Put it back in, in a slightly
more palatable form.
Signed-off-by: Steven Smith <sos22@cam.ac.uk>
closely match that of other devices.
This involves moving the logic for backend creation out of the image
handlers and in to the device handler, which is a much more sensible
place for it.
Signed-off-by: Steven Smith <sos22@cam.ac.uk>
extensively hacked based on feedback from xen-devel.
Its architecture is comparable to the common split device driver
architecture: xenfb and xenkbd modules serve as frontend in domU, and
the user space vncfb or sdlfb process serves as backend in dom0.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
For current CR8 acceleration, we do not call update_tpr_threshold() at
every VMEXIT. But at some situations, we cannot inject guest
interrupts in time. And at some critical time, it will bring up a blue
screen to 64bit Windows guest.
Now, we select to call update_tpr_threshold() at very VMEXIT
time. It's safe, and we do not see clear performance downgrade so
far.
Signed-off-by: Xiaohui Xin xiaohui.xin@intel.com
the VM UUID conflicts as well.
Also, remove the previous_restart_time node when explicitly rebooting a guest --
the user ought to be able to drive reboots faster than the safety catch.
Signed-off-by: Ewan Mellor <ewan@xensource.com>
Added a recreate call to ImageHandler, allowing the subclasses of that to
hook into the code that runs when xend restarts. This allows us in particular
to reregister the watches for HVM shutdown, and read the PID of qemu-dm from
the store.
Signed-off-by: Ewan Mellor <ewan@xensource.com>
In some situations, like when error happens in block attach for
a guest in dom0, backend send us XenbusStateClosing notification.
However, as frontend were never properly initialized, it fails
to change its own state to XenbusStateClosed, leaving the system
in a dead-end state.
Signed-off-by: Glauber de Oliveira Costa <gcosta@redhat.com>
The data buffer is only 1280 bytes long but the user-supplied length
can be as large as 0x7ff. This patch extends the buffer to 2048
bytes.
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
image then we should return to the caller who will either restart the machine
as normal or continue on as appropriate.
Signed-off-by: Ian Campbell <ian.campbell@xensource.com>
Steven Smith
Ewan Mellor
kfraser@localhost.localdomain
Alastair Tse
Tim Deegan
Ian Campbell