search for: blockstate

An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20120314/0496343e/attachment.htm>

Hi, all. While monitoring KVM VMs’ disk utilisation using libvirt API “virDomainBlockStats", I find that the results acquired is not consistent with the value read from /proc/[vm_pid]/io(i only care about “rd_bytes" and “wr_bytes” fields). Since libvirt doesn’t support host level monitoring, i have to calculate the host’s disk utilisation by reading from the /proc/diskstats file.

...CET DEBUG: StartTransactionCommand 2013-01-24 11:09:59 CET STATEMENT: SELECT dummy,to_user,from_user FROM user_shares 2013-01-24 11:09:59 CET DEBUG: StartTransaction 2013-01-24 11:09:59 CET STATEMENT: SELECT dummy,to_user,from_user FROM user_shares 2013-01-24 11:09:59 CET DEBUG: name: unnamed; blockState: DEFAULT; state: INPROGR, xid/subid/cid: 0/1/0, nestlvl: 1, children: 2013-01-24 11:09:59 CET STATEMENT: SELECT dummy,to_user,from_user FROM user_shares 2013-01-24 11:09:59 CET LOG: statement: SELECT dummy,to_user,from_user FROM user_shares 2013-01-24 11:09:59 CET DEBUG: CommitTransaction...

On 04/27/2017 04:31 PM, Stefano Ricci wrote: > Here is the backtrace of the libvirt process just started [Just a side note, you shouldn't top post on technical lists. Gmail sucks at this.] > > https://pastebin.com/R66myzFp Looks like libvirtd is trying to spawn /usr/bin/qemu-system-x86_64 but it takes ages to init. In the debug logs you might see the actual command line that

On 04/29/2017 04:38 AM, Stefano Ricci wrote: > 2017-04-28 14:33 GMT+02:00 Michal Privoznik <mprivozn@redhat.com>: >> On 04/27/2017 04:31 PM, Stefano Ricci wrote: >>> Here is the backtrace of the libvirt process just started >> >> [Just a side note, you shouldn't top post on technical lists. Gmail >> sucks at this.] >> >>> >>>

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everyone, Is this being worked on? I rather need this thing... Although my system is Debian Lenny, not RH: kulfon 10.0.0.228 /etc/default % dpkg -l | grep libvirt ii libvirt-bin 0.4.6-10+lenny1 the programs for the libvirt library ii libvirt0 0.4.6-10+lenny1 library for

Hi all, I want to attach cdrom by libvirt.py .But can't find a func in libvirt.py can finish this work. Who can help me ? Regard -- Seven Ling E-mail: jiejie.ling at qq.com

On 06/24/2014 02:24 AM, coperd wrote: > > It is supposed that the VM’s disk “rd_bytes" and “wr_bytes" should never exceed the value of the physical disk respectively, right ? That's a question for the qemu folks. > Doesn’t > libvirt virDomainBlockStats read disk information from “proc” ? No, libvirt reads it from the qemu QMP command query-blockstats. Beyond that,

2017-04-28 14:33 GMT+02:00 Michal Privoznik <mprivozn@redhat.com>: > On 04/27/2017 04:31 PM, Stefano Ricci wrote: >> Here is the backtrace of the libvirt process just started > > [Just a side note, you shouldn't top post on technical lists. Gmail > sucks at this.] > >> >> https://pastebin.com/R66myzFp > > Looks like libvirtd is trying to spawn

Just to clarify my problems: For each KVM virtual machine, it is actually a process running on the host. The $pid in "/proc/$pid/io" represents the VM process’s PID. All my work is done on the host, not inside the VMs. Take the VM process’s pid is “pid”, What the /proc/$pid/io records is io statistics of the VM from the host’s perspective. I understand that qemu might do some I/O

2017-04-29 7:24 GMT+02:00 Michal Privoznik <mprivozn@redhat.com>: > On 04/29/2017 04:38 AM, Stefano Ricci wrote: >> 2017-04-28 14:33 GMT+02:00 Michal Privoznik <mprivozn@redhat.com>: >>> On 04/27/2017 04:31 PM, Stefano Ricci wrote: >>>> Here is the backtrace of the libvirt process just started >>> >>> [Just a side note, you shouldn't

I was hoping that we could use QMP (now semi-stable since qemu 0.14) to hot plug disks. Unfortunately this is not yet possible. There is no drive_add QMP command which would be necessary for adding drives. We (Red Hat) hacked in a drive_add command into RHEL 6 (only for use by libvirt). This doesn't help us with upstream or Fedora. We could still use the human monitor, but obviously this

As planned the new release is available at: ftp://libvirt.org/libvirt/ It is a rather large release with near 400 commits included. From an user point of view the main improvement is likely to be when using migration as various work has been done to extend the protocol and to avoid having the migration command stop other concurrent operations (like virsh list). See below for a number of