Hi,
I've installed following releases :
libvirt-daemon-driver-qemu-1.2.8-16.el7_1.3.x86_64
qemu-kvm-1.5.3-86.el7_1.5.x86_64
qemu-kvm-common-1.5.3-86.el7_1.5.x86_64
qemu-guest-agent-2.1.0-4.el7.x86_64
ipxe-roms-qemu-20130517-6.gitc4bce43.el7.noarch
qemu-img-1.5.3-86.el7_1.5.x86_64
I use this lib
Hi,
Discard this request , I was investigating on the wrong compute node.
It works fine.
Sorry for incovenience.
Regards,
J.P.
De : Jean-Pierre Ribeauville
Envoyé : mercredi 20 janvier 2016 16:20
À : 'qemu-discuss@nongnu.org'
Objet : channel device "state" value miss
Hi,
I've installed a OpenStack KILO all-in-one .
For private need , I've to add a channel device to all my GUESTS on my compute
node.
It works fine (e.g. via a virsh command).
Problem is that , in the xml describing the Guest , this 'state' value :
showing if the channel is connected o
Hi,
As using a blocking socket for a virtio device channel leads to be blocked if
nobody has opened the corresponding /dev/virtio-ports within the Guest , I
tried to use a non-blocking socket and
to check whether the socket is writeable via FD_ISSET().
I'm wondering why a virtio device cha
Hi,
I'm wondering how to explain following metrics I got from
virDomainMemoryStats(), regarding memory stats for the two GUESTS running on my
host.
1) virDomainGetXMLDesc() shows these values :
memmax (1024000.00) memcurrent(1024000.00) memmax (2048000.00)
.memcurr
Hi,
I set up a channel device between host and Windows guest by adding such lines :
I notice that , if the host side has not open the socket, then write issued by
the guest fails with following error :
C:\>copy omv_bdc_var "\\.\Global\omnivision_123.agent"
Used t
