search for: 8589934592

...s a virtio block device of 10GB size. dd if=/dev/zero of=/dev/vda bs=8M count=1024 oflag=direct With and without patches bandwidth which has a bit wide range does not look that different from each other. Without patches =============== ---------- 1 --------- 1024+0 records in 1024+0 records out 8589934592 bytes (8.6 GB, 8.0 GiB) copied, 1.95557 s, 4.4 GB/s ---------- 2 --------- 1024+0 records in 1024+0 records out 8589934592 bytes (8.6 GB, 8.0 GiB) copied, 2.05176 s, 4.2 GB/s ---------- 3 --------- 1024+0 records in 1024+0 records out 8589934592 bytes (8.6 GB, 8.0 GiB) copied, 1.88314 s, 4.6 GB/s -...

...s a virtio block device of 10GB size. dd if=/dev/zero of=/dev/vda bs=8M count=1024 oflag=direct With and without patches bandwidth which has a bit wide range does not look that different from each other. Without patches =============== ---------- 1 --------- 1024+0 records in 1024+0 records out 8589934592 bytes (8.6 GB, 8.0 GiB) copied, 1.95557 s, 4.4 GB/s ---------- 2 --------- 1024+0 records in 1024+0 records out 8589934592 bytes (8.6 GB, 8.0 GiB) copied, 2.05176 s, 4.2 GB/s ---------- 3 --------- 1024+0 records in 1024+0 records out 8589934592 bytes (8.6 GB, 8.0 GiB) copied, 1.88314 s, 4.6 GB/s -...

...of=/dev/vda bs=8M count=1024 oflag=direct > > With and without patches bandwidth which has a bit wide range does not > look that different from each other. > > Without patches > =============== > > ---------- 1 --------- > 1024+0 records in > 1024+0 records out > 8589934592 bytes (8.6 GB, 8.0 GiB) copied, 1.95557 s, 4.4 GB/s > ---------- 2 --------- > 1024+0 records in > 1024+0 records out > 8589934592 bytes (8.6 GB, 8.0 GiB) copied, 2.05176 s, 4.2 GB/s > ---------- 3 --------- > 1024+0 records in > 1024+0 records out > 8589934592 bytes (8.6 GB...

...>> >> With and without patches bandwidth which has a bit wide range does not >> look that different from each other. >> >> Without patches >> =============== >> >> ---------- 1 --------- >> 1024+0 records in >> 1024+0 records out >> 8589934592 bytes (8.6 GB, 8.0 GiB) copied, 1.95557 s, 4.4 GB/s >> ---------- 2 --------- >> 1024+0 records in >> 1024+0 records out >> 8589934592 bytes (8.6 GB, 8.0 GiB) copied, 2.05176 s, 4.2 GB/s >> ---------- 3 --------- >> 1024+0 records in >> 1024+0 records out &...

...>> >> With and without patches bandwidth which has a bit wide range does not >> look that different from each other. >> >> Without patches >> =============== >> >> ---------- 1 --------- >> 1024+0 records in >> 1024+0 records out >> 8589934592 bytes (8.6 GB, 8.0 GiB) copied, 1.95557 s, 4.4 GB/s >> ---------- 2 --------- >> 1024+0 records in >> 1024+0 records out >> 8589934592 bytes (8.6 GB, 8.0 GiB) copied, 2.05176 s, 4.2 GB/s >> ---------- 3 --------- >> 1024+0 records in >> 1024+0 records out &...

...l example of what I mean. System is CentOS Linux release 7.6.1810 (Core) with libvirt-4.5.0-10.el7_6.4.x86_64 Please let me know if I am missing something. Thanks. # create base file [root@singularity images]# qemu-img create base.qcow2 8G -f qcow2 Formatting 'base.qcow2', fmt=qcow2 size=8589934592 cluster_size=65536 lazy_refcounts=off refcount_bits=16 [root@singularity images]# qemu-img info base.qcow2 image: base.qcow2 file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 17K cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false ref...

Hi all, on a fully patched CentOS 7.4 x86-64, I see the following behavior: - when creating a new volumes using vol-create-as, the resulting file is a qcow2 version 2 (compat=0.10) file. Example: [root@gdanti-lenovo vmimages]# virsh vol-create-as default zzz.qcow2 8589934592 --format=qcow2 --backing-vol /mnt/vmimages/centos6.img Vol zzz.qcow2 created [root@gdanti-lenovo vmimages]# file zzz.qcow2 zzz.qcow2: QEMU QCOW Image (v2), has backing file (path /mnt/vmimages/centos6.img), 8589934592 bytes [root@gdanti-lenovo vmimages]# qemu-img info zzz.qcow2 image: zzz.qcow2 fi...

...is d0.qcow As follows: [root at test1 ]# virsh list Id Name State ---------------------------------------------------- 32 bfbe8ca8-8579-11e2-844a-001018951f48 running [root at test1 ]# qemu-img info d0.qcow image: d0.qcow file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 3.6G cluster_size: 65536 [root at test1 ]# ls -lh total 3.6G -rw------- 1 qemu qemu 3.6G Apr 12 17:13 d0.qcow drwx------ 2 root root 4.0K Apr 12 17:12 held [root at test1 ]# virsh snapshot-list bfbe8ca8-8579-11e2-844a-001018951f48 Name Creation Time St...

...all, > on a fully patched CentOS 7.4 x86-64, I see the following behavior: > > - when creating a new volumes using vol-create-as, the resulting file > is a qcow2 version 2 (compat=0.10) file. Example: > > [root@gdanti-lenovo vmimages]# virsh vol-create-as default zzz.qcow2 > 8589934592 --format=qcow2 --backing-vol /mnt/vmimages/centos6.img > Vol zzz.qcow2 created > [root@gdanti-lenovo vmimages]# file zzz.qcow2 > zzz.qcow2: QEMU QCOW Image (v2), has backing file (path > /mnt/vmimages/centos6.img), 8589934592 bytes > [root@gdanti-lenovo vmimages]# qemu-img info zzz.q...

This patch series is the follow up on the discussions we had before about the RFC titled [RFC,V2] virtio: Add platform specific DMA API translation for virito devices (https://patchwork.kernel.org/patch/10417371/). There were suggestions about doing away with two different paths of transactions with the host/QEMU, first being the direct GPA and the other being the DMA API based translations.

This patch series is the follow up on the discussions we had before about the RFC titled [RFC,V2] virtio: Add platform specific DMA API translation for virito devices (https://patchwork.kernel.org/patch/10417371/). There were suggestions about doing away with two different paths of transactions with the host/QEMU, first being the direct GPA and the other being the DMA API based translations.

I got really strange situation with memory on host: xe host-list params=memory-free memory-free ( RO) : 10305536 (10Mb) xe host-compute-free-memory 3147059200 (3Gb) A huge difference! And xentop show different numbers too! I will keep this host online "as is" and I am ready to provide information for debbugging or perform needed actions. -- wBR,George.

...emplates resides? Especially they exists even no any SR are created.. They contains following in other-config: default_template: true; linux_template: true; install-methods: cdrom,http,ftp; install-arch: i386; debian-release: lenny; disks: <provision><disk device="0" size="8589934592" sr="" bootable="true" type="system"/></provision>; install-distro: debianlike But this is definitive not enough for pinpoint name of kernel/initrd to download... I tried to export template, unpack it (ova.xml), look inside and yet found no lines like d...

Hi all I have CentOS Linux release 7.0.1406, libvirt 1.2.7 installed. Just after create and start inside LXC container present cgroups. Example for memory: [root@ce7-t1 /]# ls -la /sys/fs/cgroup/memory/ total 0 drwxr-xr-x 2 root root 0 Sep 15 17:14 . drwxr-xr-x 12 root root 280 Sep 15 17:14 .. -rw-r--r-- 1 root root 0 Sep 15 17:14 cgroup.clone_children --w--w--w- 1 root root 0 Sep 15

...i virt-image -o vmx -D vmdk mon03.xml mon03 ERROR Couldn't import file "mon03.xml": Couldn't import file 'mon03.xml': Disk entry for 'mon03' not found The image file itself is readable by all: ls -la /var/lib/libvirt/imageshelf/mon03.img -rw-r--r-- 1 root m4u 8589934592 Dec 3 09:25 /var/lib/libvirt/imageshelf/mon03.img ls -la mon03.xml -rw-rw-r-- 1 chandana chandana 657 Dec 5 09:08 mon03.xml <image> <name>mon03</name> <domain> <boot type="hvm"> <guest> <arch>i...

...tOS 7.4 x86-64, I see the following behavior: > > > > - when creating a new volumes using vol-create-as, the resulting file is > a > > qcow2 version 2 (compat=0.10) file. Example: > > > > [root@gdanti-lenovo vmimages]# virsh vol-create-as default zzz.qcow2 > > 8589934592 --format=qcow2 --backing-vol /mnt/vmimages/centos6.img > > Vol zzz.qcow2 created > > Yes, for sake of backcompat we default to v2 unless something > requires v3. You can't use vol-create-as to create a v3 image, > you need to use the XML input. > BTW: in virt-manager of C...

...live --config --size 8388608 2013-03-22 21:13:45.522+0000: 23183: debug : qemuMonitorSetBalloon:1690 : mon=0x7f3d6c1789e0 newmem=8388608 2013-03-22 21:13:45.522+0000: 23183: debug : virJSONValueToString:1133 : result={"execute":"balloon","arguments":{"value":8589934592 },"id":"libvirt-9"} 2013-03-22 21:13:45.522+0000: 23183: debug : qemuMonitorJSONCommandWithFd:265 : Send command '{"execute":"balloon","arguments":{"value":8589934592},"id":"libvirt-9"}' for write with FD -1 201...

...orking for a few seconds, except one disk at a time. When this cycle is finished, it looks normal again. This seems to be the flushing of the NVRAM cache. Should be solved by disabling the flush...So far so good... But I also need the memory for PostgreSQL to work, so I added: set zfs:zfs_arc_max=8589934592 to /etc/system and rebooted. Now redid my test, with terrible results.. sequential read is about 120 MB/sec. One disk should be able to handle that, 14 disks should do more than a GB/sec, and in my previous benchmark without the arc_max setting, they actually make these figures...(even when not re...

...de = 0600 user = vmail } } shutdown_clients = no ssl_cert = </etc/dovecot/private/fullchain.pem ssl_key = </etc/dovecot/private/privkey.pem syslog_facility = local6 userdb { args = /etc/dovecot/dovecot-ldap.conf.ext default_fields = home=/var/vmail/%Ld/%Ln quota_rule=*:bytes=8589934592 driver = ldap } verbose_proctitle = yes protocol lmtp { mail_plugins = " zlib quota acl notify replication sieve quota" } protocol lda { mail_plugins = " zlib quota acl notify replication sieve" } protocol imap { imap_metadata = yes mail_max_userip_connecti...

...backing_file=rbd:images/CentOS-7-x86_64-GenericCloud-1901:mon_host=[fd00\:\:cefc\:1]\:6789:auth_supported=none,backing_fmt=raw libguestfs: command: run: \ /root/libguestfs/tmp/libguestfs9gclsg/overlay1.qcow2 Formatting '/root/libguestfs/tmp/libguestfs9gclsg/overlay1.qcow2', fmt=qcow2 size=8589934592 backing_file=rbd:images/CentOS-7-x86_64-GenericCloud-1901:mon_host=[fd00\:\:cefc\:1]\:6789:auth_supported=none backing_fmt=raw cluster_size=65536 lazy_refcounts=off refcount_bits=16 libguestfs: trace: disk_create = 0 libguestfs: trace: add_drive = 0 Welcome to guestfish, the guest filesystem she...