On 16.10.2011 10:54, TeLeMan wrote:
On Thu, Oct 13, 2011 at 18:48, Gerd Hoffmann wrote:
On 10/13/11 04:09, TeLeMan wrote:
On Wed, Oct 12, 2011 at 19:30, Gerd Hoffmannwrote:
qemu uses the ps/2 mouse by default. The usb tablet (or mouse) is
activated as soon as qemu sees some guest activit
On 21.10.2011 11:22, Gerd Hoffmann wrote:
Hi,
Original:
* Mouse #1: QEMU HID Tablet (absolute)
Mouse #0: QEMU PS/2 Mouse
Start from the snapshot:
* Mouse #0: QEMU PS/2 Mouse
Mouse #1: QEMU HID Tablet (absolute)
The active mouse device is not be saved into the snapshot.
That shouldn'
Hi,
> Original:
> * Mouse #1: QEMU HID Tablet (absolute)
> Mouse #0: QEMU PS/2 Mouse
>
> Start from the snapshot:
> * Mouse #0: QEMU PS/2 Mouse
> Mouse #1: QEMU HID Tablet (absolute)
>
> The active mouse device is not be saved into the snapshot.
That shouldn't hurt though. When the guest
On Thu, Oct 13, 2011 at 18:48, Gerd Hoffmann wrote:
> On 10/13/11 04:09, TeLeMan wrote:
>>
>> On Wed, Oct 12, 2011 at 19:30, Gerd Hoffmann wrote:
>>>
>>> qemu uses the ps/2 mouse by default. The usb tablet (or mouse) is
>>> activated as soon as qemu sees some guest activity on the device,
>>> i.
On 10/13/11 04:09, TeLeMan wrote:
On Wed, Oct 12, 2011 at 19:30, Gerd Hoffmann wrote:
qemu uses the ps/2 mouse by default. The usb tablet (or mouse) is
activated as soon as qemu sees some guest activity on the device,
i.e. polling for HID events. That used to work fine for both fresh
boot and
On Wed, Oct 12, 2011 at 19:30, Gerd Hoffmann wrote:
> qemu uses the ps/2 mouse by default. The usb tablet (or mouse) is
> activated as soon as qemu sees some guest activity on the device,
> i.e. polling for HID events. That used to work fine for both fresh
> boot and migration.
It does not fix u
qemu uses the ps/2 mouse by default. The usb tablet (or mouse) is
activated as soon as qemu sees some guest activity on the device,
i.e. polling for HID events. That used to work fine for both fresh
boot and migration.
Remote wakeup support changed the picture though: There will be no
polling af
