[Top][All Lists]

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

Re: [Qemu-discuss] [problem] QEMU-GA & Windows 10

From: Frank Sfalanga Jr .
Subject: Re: [Qemu-discuss] [problem] QEMU-GA & Windows 10
Date: Mon, 18 Jul 2016 18:16:19 +0000

Hi Dominique,

Just returned from my trip.  Thank you for your patience. As requested,
here is a copy of the XML for this VM on the host:

<domain type='kvm'>
  <memory unit='KiB'>12617728</memory>
  <currentMemory unit='KiB'>12617728</currentMemory>
  <vcpu placement='static'>4</vcpu>
    <type arch='x86_64' machine='pc-i440fx-trusty'>hvm</type>
    <boot dev='hd'/>
  <cpu mode='custom' match='exact'>
    <model fallback='allow'>Haswell</model>
    <feature policy='require' name='tm2'/>
    <feature policy='require' name='est'/>
    <feature policy='require' name='vmx'/>
    <feature policy='require' name='osxsave'/>
    <feature policy='require' name='smx'/>
    <feature policy='require' name='ss'/>
    <feature policy='require' name='ds'/>
    <feature policy='require' name='vme'/>
    <feature policy='require' name='dtes64'/>
    <feature policy='require' name='abm'/>
    <feature policy='require' name='ht'/>
    <feature policy='require' name='acpi'/>
    <feature policy='require' name='pbe'/>
    <feature policy='require' name='tm'/>
    <feature policy='require' name='pdcm'/>
    <feature policy='require' name='pdpe1gb'/>
    <feature policy='require' name='ds_cpl'/>
    <feature policy='require' name='rdrand'/>
    <feature policy='require' name='f16c'/>
    <feature policy='require' name='xtpr'/>
    <feature policy='require' name='monitor'/>
  <clock offset='localtime'/>
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2'/>
      <source file='/var/lib/libvirt/images/Windows10.qcow2'/>
      <target dev='vda' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07'
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <target dev='hdc' bus='ide'/>
      <address type='drive' controller='0' bus='1' target='0' unit='0'/>
    <controller type='usb' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01'
    <controller type='pci' index='0' model='pci-root'/>
    <controller type='ide' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01'
    <controller type='scsi' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06'
    <interface type='direct'>
      <mac address='52:54:00:05:ac:95'/>
      <source dev='eth0' mode='vepa'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03'
    <serial type='pty'>
      <target port='0'/>
    <console type='pty'>
      <target type='serial' port='0'/>
    <input type='tablet' bus='usb'/>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <graphics type='vnc' port='-1' autoport='yes'/>
    <sound model='ich6'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04'
      <model type='vga' vram='9216' heads='1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02'
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05'

I do not see anything related to <channel type='unix'>


This is what is returned when looking for the channel:

# ls -lh /var/lib/libvirt/qemu/channel
ls: cannot access /var/lib/libvirt/qemu/channel: No such file or


Thank you in advance for any direction you can provide.

Kind regards,


-----Original Message-----
From: Dominique Ramaekers <address@hidden>
To: Frank Sfalanga Jr. <address@hidden>,
address@hidden <address@hidden>
Subject: RE: [problem] QEMU-GA & Windows 10
Date: Thu, 14 Jul 2016 09:30:33 +0000

> -----Oorspronkelijk bericht-----
> Van: Qemu-discuss [mailto:qemu-discuss-
> address@hidden Namens Frank
> Sfalanga Jr.
> Verzonden: dinsdag 12 juli 2016 19:31
> Aan: address@hidden
> Onderwerp: [Qemu-discuss] [problem] QEMU-GA & Windows 10
> Hello,
> Ubuntu 14.04LTS
> KVM/Qemu
> After a bit of struggle I was recently able to get Windows 10 running in a VM
> with kvm/qemu.  I have the virtio drivers installed and have converted the
> disk to the .qcow2 file system.
> The last piece of the puzzle is getting the QEMU GUEST AGENT working.
> I've googled around and found reports of people successfully upgrading
> Windows 7 to Windows 10 but cannot find any reports of success using
> qemu guest agent with a Windows 10 clean install.

I've done it with little trouble.

> My issue specifically is that the QEMU GUEST AGENT VSS PROVIDER will start
> if I do it manually, the GUEST AGENT itself will not, ever.  I receive the
> following error:
> ----------------------------
> ERROR 1053: The service did not respond to the start or control request in a
> timely fashion.
> ----------------------------

Please post the xml of the guest...

You should be able to find something like this in the xml:
<channel type='unix'>
      <source mode='bind' 
      <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/>
      <alias name='channel0'/>
      <address type='virtio-serial' controller='0' bus='0' port='2'/>

If not, please make sure the location for the channel exist and has the correct 
access rights:

address@hidden:~# ls -lh /var/lib/libvirt/qemu/channel
totaal 4,0K
drwxr-xr-x 10 libvirt-qemu kvm 4,0K jul  1 08:57 target

> Hopefully there is a fix, or you can point me to the correct mailing list if 
> this
> is not it.
> Thank you in advance.
> Kind regards,
> -Frank

Sorry about the late reply...

Frank Sfalanga Jr | Director, Information Technology & Application
Ph. 239-221-3309 | address@hidden
3301 Bonita Beach Road #300 | Bonita Springs | FL | 34134
Celebrating 25 years of corporate payment innovation


This message and any attachments are intended solely for the use of the
intended recipient(s) and may contain information that is privileged,
confidential or proprietary of CSI Enterprises, Inc. If you are not an
intended recipient, please notify the sender, and then please delete and
destroy all copies and attachments, and be advised that any review or
dissemination of, or the taking of any action in reliance on, the
information contained in or attached to this message is prohibited. 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]