search for: blockinfo

Hi devs & users, The Telemetry service of OpenStack, project code name Ceilometer, is using libvirt.domain.blockInfo() to get disk's physical, allocation and capacity information [1]. However, when disk is network type with protocol ceph, the blockInfo() always fail with: libvirtError: internal error: missing storage backend for network files using rbd protocol. [2] After reading some libvirt code, I think i...

Some time ago I developed a fast BitVector class to use in some research here. It uses expression templates to fuse operation loops and runs much faster than the existing BitVector for some important use-cases. It also has the ability to efficiently report if a BitVector's contents changed after some operation. For example: ETBitVector A = ... ETBitVector B = ... ETBitVector C = ... bool

...virt/images/test-disk1 [root@virt83 ~]# qemu-img info /var/lib/libvirt/images/test-disk1 image: /var/lib/libvirt/images/test-disk1 file format: raw virtual size: 705M (739573760 bytes) disk size: 705M Notice how that raw image is seen with a size of 705M by ls, du and qemu-img however when I get a blockinfo using libvirt-python using the blockInfo() call I get this: {'source': '/var/lib/libvirt/images/test-disk1', 'target': 'vda'} [2423276348619671841L, 739577856L, 739577856L] Obviously the first value (capacity) is way too large to be correct. Any ideas if this is a...

...ow a shared block info block state. I'd agree with him that such a design would be possible while still allowing multiple block info blocks; the design I have in mind would decouple the block info state from not only the cursor but the reader. The interface would look like this: class BitstreamBlockInfo { // block info block state, i.e. everything matching *BlockInfo* in the current BitstreamReader interface }; class BitstreamCursor : SimpleBitstreamCursor { // existing BitstreamCursor interface here /// Read a block info block into a BitstreamBlockInfo object, and return it. BitstreamBl...

...d block info block state. I'd agree with him that such a design would be possible while still allowing multiple block info blocks; the design I have in mind would decouple the block info state from not only the cursor but the reader. The interface would look like this: > > class BitstreamBlockInfo { > // block info block state, i.e. everything matching *BlockInfo* in the current BitstreamReader interface > }; > > class BitstreamCursor : SimpleBitstreamCursor { > // existing BitstreamCursor interface here > > /// Read a block info block into a BitstreamBlockInfo o...

Hi, I am using virStorageVolGetInfo to get the volume size virStorageVol.download to download a normal file for VDSM project. I want to add support for block devices as well, I was able to see the size via virDomainBlockInfo and download via virDomain.blockPeek which is works fine for both file and block device. 1. Can I depend on virDomainBlockInfo for non block devices? 2. Does the virDomainBlockInfo return the correct physical size for normal file? 3. Performance wise do we have a difference between virStorageVol.d...

...info block state. I'd agree with him that such a design would be possible while still allowing multiple block info blocks; the design I have in mind would decouple the block info state from not only the cursor but the reader. The interface would look like this: >> >> class BitstreamBlockInfo { >> // block info block state, i.e. everything matching *BlockInfo* in the current BitstreamReader interface >> }; >> >> class BitstreamCursor : SimpleBitstreamCursor { >> // existing BitstreamCursor interface here >> >> /// Read a block info block...

...Vol.download to download a > normal file for VDSM project. Normal as in a 'raw' fully allocated file? As opposed to a sparse and/or container (e.g. qcow2) file? > > I want to add support for block devices as well, I was able to see > the size > via virDomainBlockInfo and download via virDomain.blockPeek which is > works > fine for both file and block device. As described in the bz, but for others benefit... While looking into this I found a commit Eric Blake made: http://libvirt.org/git/?p=libvirt.git;a=commit;h=0282ca45a0a4c384226d526d4878cacd7...

Hi,all, i used the libvirt Python API in OpenStack environment,Now how to get disk usage size of domain(It is used size,not total size,can get total size using blockInfo(),)? How to get a memory usage of Domain Windows? I hope get help from you! Very Thanks ! Leo Tod

...Havivi <shavivi at redhat.com> wrote: > Hi, > > I am using virStorageVolGetInfo to get the volume size > virStorageVol.download to download a > normal file for VDSM project. > > I want to add support for block devices as well, I was able to see the size > via virDomainBlockInfo and download via virDomain.blockPeek which is works > fine for both file and block device. > > 1. Can I depend on virDomainBlockInfo for non block devices? > 2. Does the virDomainBlockInfo return the correct physical size for normal > file? > 3. Performance wise do we have a diffe...

...e? and network.persistent? - Update Domain class, implementing conn.domain_xml_from_native, conn.domain_xml_to_native, dom.migrate_to_uri, dom.migrate_set_max_downtime, dom.managed_save, dom.has_managed_save?, dom.managed_save_remove, dom.security_label, dom.block_stats, dom.memory_stats, dom.blockinfo, dom.block_peek, dom.memory_peek, dom.active?, dom.persistent?, dom.snapshot_create_xml, dom.num_of_snapshots, dom.list_snapshots, dom.lookup_snapshot_by_name, dom.has_current_snapshot?, dom.revert_to_snapshot, dom.current_snapshot, snapshot.xml_desc, snapshot.delete, dom.job_info, and do...

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

Reid Spencer <rspencer <at> reidspencer.com> writes: > Hi Joshua, Hi, thanks for the reply. > On Mon, 2007-09-03 at 21:34 +0000, Joshua Haberman wrote: > > I also have a few questions about the format: > > > > - it appears that the only magic number in the file is > > application-specific. This seems unfortunate, because it means that > >

...e(CI.getArgOperand(i), InstID, Vals, VE); // fixed param. > + } > + } > > // Emit type/value pairs for varargs params. > if (FTy->isVarArg()) { ... > @@ -1514,8 +1553,8 @@ static void WriteFunction(const Function &F, ValueEnumerator &VE, > // Emit blockinfo, which defines the standard abbreviations etc. > static void WriteBlockInfo(const ValueEnumerator &VE, BitstreamWriter &Stream) { > // We only want to emit block info records for blocks that have multiple > - // instances: CONSTANTS_BLOCK, FUNCTION_BLOCK and VALUE_SYMTAB_BLOCK...

On Tue, Apr 4, 2017 at 12:36 PM, Duncan P. N. Exon Smith < dexonsmith at apple.com> wrote: > > On 2017-Apr-04, at 12:12, Peter Collingbourne <peter at pcc.me.uk> wrote: > > On Mon, Apr 3, 2017 at 8:13 PM, Mehdi Amini <mehdi.amini at apple.com> wrote: > >> >> On Apr 3, 2017, at 7:08 PM, Peter Collingbourne <peter at pcc.me.uk> wrote: >>

Hi, I'm trying to solve a problem from StructurizeCFG not actually handling regions with multiple exits. Sample IR attached. StructurizeCFG doesn't touch this function, exiting early on the isTopLevelRegion check. SIAnnotateControlFlow then gets confused and ends up inserting an if into one of the blocks, and the matching end.cf into one of the return/unreachable blocks. The input to

Hi all, I've been looking into how to make llvm bitcode files smaller. There is one simple change that appears to shrink linked bitcode files by about 15%. See this spreadsheet for some rough data: https://docs.google.com/spreadsheet/ccc?key=0AjRrJHQc4_bddEtJdjdIek5fMDdIdFFIZldZXzdWa0E The change is in how operand ids are encoded in bitcode files. Rather than use an "absolute

...structure for CFGStructurizer > +// > +//===----------------------------------------------------------------------===// > + > +namespace llvmCFGStruct > +{ > +template<class PassT> > +struct CFGStructTraits { > +}; > + > +template <class InstrT> > +class BlockInformation { > +public: > + bool isRetired; > + int sccNum; > + //SmallVector<InstrT*, DEFAULT_VEC_SLOTS> succInstr; > + //Instructions defining the corresponding successor. > + BlockInformation() : isRetired(false), sccNum(INVALIDSCCNUM) {} > +}; > + > +template...