On 11/28/2013 07:12 PM, David Highley wrote:
"Cole Robinson wrote:"
>
> On 11/18/2013 11:14 PM, David Highley wrote:
>> "Cole Robinson wrote:"
>>>
>>> On 11/14/2013 11:33 PM, David Highley wrote:
>>>> First off I'm not very experienced setting up and running virtual
guest
>>>> systems. I install Fedora 20 Beta using virt-manager. It is hosted on a
>>>> Fedora 19 system.
>>>>
>>>> 1) Reocurring issue with the pointer not being visible in the guest
>>>> window. Some times cleared by stopping and restarting the guest
>>>> system. Most of the time need to force stop.
>>>
>>> Please provide the guest config: sudo virsh dumpxml $vmname
>>
>> <domain type='kvm'>
>> <name>BetaFedora20-x64</name>
>> <uuid>56527a8f-d3c9-054c-6882-16ce154ca811</uuid>
>> <memory unit='KiB'>4194304</memory>
>> <currentMemory unit='KiB'>4194304</currentMemory>
>> <vcpu placement='static'>4</vcpu>
>> <os>
>> <type arch='x86_64'
machine='pc-i440fx-1.4'>hvm</type>
>> <boot dev='hd'/>
>> </os>
>> <features>
>> <acpi/>
>> <apic/>
>> <pae/>
>> </features>
>> <clock offset='utc'/>
>> <on_poweroff>destroy</on_poweroff>
>> <on_reboot>restart</on_reboot>
>> <on_crash>restart</on_crash>
>> <devices>
>> <emulator>/usr/bin/qemu-kvm</emulator>
>> <disk type='file' device='disk'>
>> <driver name='qemu' type='raw'/>
>> <source
file='/var/lib/libvirt/images/BetaFedora20-x64.img'/>
>> <target dev='vda' bus='virtio'/>
>> <address type='pci' domain='0x0000' bus='0x00'
slot='0x05' function='0x0'/>
>> </disk>
>> <disk type='block' device='cdrom'>
>> <driver name='qemu' type='raw'/>
>> <target dev='hdc' bus='ide'/>
>> <readonly/>
>> <address type='drive' controller='0' bus='1'
target='0' unit='0'/>
>> </disk>
>> <controller type='usb' index='0'>
>> <address type='pci' domain='0x0000' bus='0x00'
slot='0x01' function='0x2'/>
>> </controller>
>> <controller type='ide' index='0'>
>> <address type='pci' domain='0x0000' bus='0x00'
slot='0x01' function='0x1'/>
>> </controller>
>> <controller type='virtio-serial' index='0'>
>> <address type='pci' domain='0x0000' bus='0x00'
slot='0x04' function='0x0'/>
>> </controller>
>> <controller type='pci' index='0'
model='pci-root'/>
>> <interface type='direct'>
>> <mac address='52:54:00:1b:4b:94'/>
>> <source dev='p57p1' mode='bridge'/>
>> <model type='rtl8139'/>
>> <address type='pci' domain='0x0000' bus='0x00'
slot='0x07' function='0x0'/>
>> </interface>
>> <serial type='pty'>
>> <target port='0'/>
>> </serial>
>> <console type='pty'>
>> <target type='serial' port='0'/>
>> </console>
>> <channel type='spicevmc'>
>> <target type='virtio' name='com.redhat.spice.0'/>
>> <address type='virtio-serial' controller='0'
bus='0' port='1'/>
>> </channel>
>> <input type='tablet' bus='usb'/>
>> <input type='mouse' bus='ps2'/>
>> <graphics type='spice' autoport='yes'/>
>> <sound model='ich6'>
>> <address type='pci' domain='0x0000' bus='0x00'
slot='0x03' function='0x0'/>
>> </sound>
>> <video>
>> <model type='qxl' ram='65536' vram='65536'
heads='1'/>
>> <address type='pci' domain='0x0000' bus='0x00'
slot='0x02' function='0x0'/>
>> </video>
>> <memballoon model='virtio'>
>> <address type='pci' domain='0x0000' bus='0x00'
slot='0x06' function='0x0'/>
>> </memballoon>
>> </devices>
>> </domain>
>
> I haven't heard other reports about the disappearing pointer. If you can
> reliably reproduce, please open a bug against virt-manager (if that's where
> you are reproducing) with the above config, content of
> /var/log/libvirt/qemu/$vmname.log, and extra points for a screen cast of the
> actual error so we can see it going wrong.
I now believe now it is a timing issue. If you start up the client and
login right after the Gnome greeter comes ready the pointer disappears
after logging in. I also notice in the Virtual Machine Manager that it
still has a high CPU usage. If you delay a few seconds, not minutes. The
issue does not show up.
Interesting. please file a spice-gtk bug so we can track this, listing all the
info you mentioned here. bonus points if you can capture a screencast
demonstrating it. gnome-shell has built in screencasting with ctrl+shift+alt+r
if that's your desktop. Please mention the bug here when it is filed.
Thanks,
Cole