Re: [libvirt-users] virsh blockcopy: doesn't seem to flatten the chain by default

2014-07-04 Thread Kashyap Chamarthy
On Thu, Jul 03, 2014 at 11:08:15AM -0600, Eric Blake wrote: > On 07/02/2014 01:12 PM, Kashyap Chamarthy wrote: > > > We have this simple chain: > > > > base <- snap1 > > > > Let's quickly examine the contents of 'base' and 'snap1' images: > > > > > Now, let's do a live blockcopy (with a '-

Re: [libvirt-users] memoryStats question

2014-07-04 Thread Ján Tomko
On 07/04/2014 03:18 PM, Claudio Bley wrote: > At Thu, 03 Jul 2014 17:46:14 +0300, > Gleb Voronich wrote: >> >> >>> virDomainMemoryStats() gets those stats, if qemu is new enough to >>> provide them, and if the guest cooperates to provide them. >> Well I use the latest QEMU 2.0.0 >> I have the lates

[libvirt-users] libvirt behind stunnel4

2014-07-04 Thread Parthipan
Hi, I'm trying this setup where an stunnel4 (listening for clients on port 16514) connects to an unencrypted libvirt backend (on port 16509). When I point the virsh client to stunnel4 it hangs. Looking via tshark: 1. virsh completes ssl handshake with stunnel4 2. stunnel4 completes tcp handshake

Re: [libvirt-users] memoryStats question

2014-07-04 Thread Claudio Bley
At Thu, 03 Jul 2014 17:46:14 +0300, Gleb Voronich wrote: > > > > virDomainMemoryStats() gets those stats, if qemu is new enough to > > provide them, and if the guest cooperates to provide them. > Well I use the latest QEMU 2.0.0 > I have the latest CentOS 6.5 installed on the guest and unfortunat

Re: [libvirt-users] Acces to hypervisor from a KVM guest

2014-07-04 Thread Eric Blake
On 07/04/2014 04:23 AM, Jean-Pierre Ribeauville wrote: > Hi, > >>From a KVM guest, I want to retrieve the hostname of the host on which the >>hypervisor is running. > Before doing that by using libvirt API, I first try via virsh. Well, virsh just uses the libvirt API under the hood. I'd sugges

[libvirt-users] Acces to hypervisor from a KVM guest

2014-07-04 Thread Jean-Pierre Ribeauville
Hi, >From a KVM guest, I want to retrieve the hostname of the host on which the >hypervisor is running. Before doing that by using libvirt API, I first try via virsh. So, I run virsh and the run hostname command.( got that in virsh help : hostname print the hypervis

Re: [libvirt-users] os/type/machine/pc-xxxx meaning ? following live migration issue after an upgrade

2014-07-04 Thread Daniel P. Berrange
On Fri, Jul 04, 2014 at 11:22:13AM +0200, Benoit Rousselle wrote: > Thanks for the quick answer :D > > 2 more questions: > - what is the exact meaning of ABI ? Any aspect of the hardware that is visible to the guest. eg IRQ numbers, I/O ports, memory ranges, PCI config spec values, etc, etc. >

Re: [libvirt-users] os/type/machine/pc-xxxx meaning ? following live migration issue after an upgrade

2014-07-04 Thread Benoit Rousselle
answering my first question: On Fri 04 Jul 2014 11:22:13 AM CEST, Benoit Rousselle wrote: - what is the exact meaning of ABI ? Application Binary Interface ___ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listin

Re: [libvirt-users] os/type/machine/pc-xxxx meaning ? following live migration issue after an upgrade

2014-07-04 Thread Benoit Rousselle
Thanks for the quick answer :D 2 more questions: - what is the exact meaning of ABI ? - Can you explain why live migration was failing pc-0.12 on kvm 1.1 ? Thanks, Benoit. On Fri 04 Jul 2014 11:10:57 AM CEST, Daniel P. Berrange wrote: On Fri, Jul 04, 2014 at 11:04:53AM +0200, Benoit Rousselle

Re: [libvirt-users] os/type/machine/pc-xxxx meaning ? following live migration issue after an upgrade

2014-07-04 Thread Daniel P. Berrange
On Fri, Jul 04, 2014 at 11:04:53AM +0200, Benoit Rousselle wrote: > Dear All, > > I have upgrade my hypervisors: > qemu-kvm0.12.5 => 1.1.2 > libvirt-bin 0.8.3-5 => 0.9.12.3 > (debian6 to debian7) > > After that upgrade, i noticed that live

[libvirt-users] os/type/machine/pc-xxxx meaning ? following live migration issue after an upgrade

2014-07-04 Thread Benoit Rousselle
Dear All, I have upgrade my hypervisors: qemu-kvm0.12.5 => 1.1.2 libvirt-bin 0.8.3-5 => 0.9.12.3 (debian6 to debian7) After that upgrade, i noticed that live migration was most of the time failing (freeze) (not always) I also noticed that

Re: [libvirt-users] memoryStats question

2014-07-04 Thread Gleb Voronich
Then your problem is your libvirt is too old. It is the combination of qemu new enough to provide stats (qemu1.4; probably not present in the qemu shipped in CentOS, but present in your self-built 2.0) and libvirt new enough to read stats (v1.1.1 or newer; which is in RHEL 7.0, but not backpor