[Spice-devel] Bug 1200592: Xp and Raw PDO
ToddAndMargo
ToddAndMargo at zoho.com
Fri Mar 13 19:03:37 PDT 2015
On 03/13/2015 12:54 PM, ToddAndMargo wrote:
> On 03/13/2015 10:23 AM, Christophe Fergeau wrote:
>> Hi,
>>
>> On Thu, Mar 12, 2015 at 04:16:56PM -0700, ToddAndMargo wrote:
>>> On 03/11/2015 12:36 PM, Christophe Fergeau wrote:
>>> Hi Christophe,
>>>
>>> This VM was an XP-Pro-SP3 on a new, blank hard drive, with
>>> no updates applied. (I did not apply the updates as the only
>>> thing I use it for is Go To Assist and I am sick and tired
>>> of the problems associated with M$'s updates. Plus any
>>> bad guys that want at it are going to have to figure out how
>>> to get by iptables on the host machine. But that is a story
>>> for another day and group.)
>>>
>>> The first spice guest tools I tried to install was:
>>> spice-guest-tools-0.74.exe
>>> No other guest tool had been applied to that point.
>>>
>>> Did you VM have any other guest tool previously applied?
>>
>>
>> I just did a fresh XP-Pro-SP3 install. I created the VM in
>> virt-manager, SPICE graphics, QXL graphics, added the SPICE
>> agent channel, then did the install. On first boot, I disabled
>> automatic updates, installed firefox as otherwise the spice-guest-tools
>> 0.74 download tends to be corrupt, installed spice-guest-tools,
>> rebooted, and the agent is working as expected. I think it was even
>> working before the reboot.
>>
>>>
>>> Looking at "vioser.sys" in Windows Explorer, Properties,
>>> I get the following:
>>>
>>> XP: 51.64.104.5200 (spice-guest-tools-0.52.exe)
>>> W7: 61.64.104.5200 (spice-guest-tools-0.74.exe)
>>
>> Here it's 51.65.104.7400 after installing spice-guest-tools-0.74.exe on
>> that XP box.
>>
>>
>>> And, is this the first guest tool you tried to apply?
>>
>> Yes it is the first and only spice-guest-tools installation ever made on
>> that install.
>>
>> Christophe
>>
>
> Mumble. Mumble.
>
> Thank you for checking.
>
>
>
Hi Christophe,
Just a long shot, but here is my XML file
-T
<!--
WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE
OVERWRITTEN AND LOST. Changes to this xml configuration should be made
using:
virsh edit KVM-WinXP2
or other application using the libvirt API.
-->
<domain type='kvm'>
<name>KVM-WinXP2</name>
<uuid>100b8bf4-63c5-f497-17f0-45e4d143e5db</uuid>
<memory unit='KiB'>4194304</memory>
<currentMemory unit='KiB'>4194304</currentMemory>
<vcpu placement='static'>4</vcpu>
<os>
<type arch='x86_64' machine='rhel6.4.0'>hvm</type>
<boot dev='cdrom'/>
<boot dev='hd'/>
</os>
<features>
<acpi/>
<apic/>
<pae/>
</features>
<cpu mode='custom' match='exact'>
<model fallback='allow'>Nehalem</model>
<vendor>Intel</vendor>
<topology sockets='1' cores='4' threads='8'/>
<feature policy='require' name='tm2'/>
<feature policy='require' name='est'/>
<feature policy='require' name='monitor'/>
<feature policy='require' name='ss'/>
<feature policy='require' name='vme'/>
<feature policy='require' name='dtes64'/>
<feature policy='require' name='rdtscp'/>
<feature policy='require' name='ht'/>
<feature policy='require' name='ds'/>
<feature policy='require' name='pbe'/>
<feature policy='require' name='tm'/>
<feature policy='require' name='pdcm'/>
<feature policy='require' name='vmx'/>
<feature policy='require' name='ds_cpl'/>
<feature policy='require' name='xtpr'/>
<feature policy='require' name='acpi'/>
</cpu>
<clock offset='localtime'>
<timer name='rtc' tickpolicy='catchup'/>
</clock>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<emulator>/usr/libexec/qemu-kvm</emulator>
<disk type='file' device='disk'>
<driver name='qemu' type='qcow2' cache='none'/>
<source file='/home/kvm/KVM-WinXP2.img'/>
<target dev='hda' bus='ide'/>
<address type='drive' controller='0' bus='0' target='0' unit='0'/>
</disk>
<disk type='file' device='cdrom'>
<driver name='qemu' type='raw'/>
<source file='/home/kvm/XP-Pro-SP3-OEM.iso'/>
<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='0x06'
function='0x0'/>
</controller>
<interface type='bridge'>
<mac address='52:54:00:21:2c:51'/>
<source bridge='br0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03'
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' port='5902' autoport='no' listen='127.0.0.1'>
<listen type='address' address='127.0.0.1'/>
</graphics>
<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='0x05'
function='0x0'/>
</memballoon>
</devices>
</domain>
More information about the Spice-devel
mailing list