search for: 196k

...1444632 3364432 Swap: 2064376 176 2064200 The BIOS sees all of the RAM. In fact, it looks to me like the kernel knows 6 GB is available. But, it is only using 4.8 GB because I see this in dmesg: Memory: 4808464k/6291456k available (2106k kernel code, 0k reserved, 1299k data, 196k init) What happened to the other 1 GB+ of RAM? BTW, the server isn't running all the newest updates, but it is running the latest CentOS 4 kernel (2.6.9-42.0.10.ELsmp). Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.19-1.2911.fc6 i686 GNU/Linux 11:39:08 up 2 days, 10:28, 2 users, load...

...ow2 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 file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 196K cluster_size: 65536 backing file: /mnt/vmimages/centos6.img backing file format: raw Format specific information: compat: 0.10 refcount bits: 16 - when creating a snapshot, the resulting file is a qcow2 version 3 (comapt=1.1) file. Example: [root@gdanti-lenovo vmimages]# virsh snapshot...

...ummy device 80x25 Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Software IO TLB disabled vmalloc area: d1000000-f51fe000, maxmem 2d7fe000 Memory: 255340k/270336k available (2056k kernel code, 6800k reserved, 716k data, 196k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. calibrate_delay_direct() failed to get a good estimate for loops_per_jiffy. Probably due to long platform interrupts. Consider using "lpj=" boot option. Security Framework v1.0.0 initialized Cap...

...dio - more than 12x, where I only need about 4x. Hopefully that means I have plenty of room to tweak so I can fit it in my limited resources. My resources: - 48MHz 32-bit ARM Cortex-M0 - 32k RAM (of which I probably on have 16-24k available) - 256k ROM (of which I probably only have 128-196k available) I have no doubt that I can fit the design in ROM - I've already tried ripping out the decoder, and a stripped build can fit in 160k. But, on speed and RAM, any thoughts on the feasibility, or what I'd have to do to make this work? P.S. I sent this to the mailing list before,...

...gt; Version-Release number of selected component (if applicable): > nbdkit-v1.9.1 > qemu-utils-2.12+dfsg-3+b1 > > How reproducible: > 100% > > Steps: > 1. Create a qcow2 file > # qemu-img create disk 1G -f qcow2 This creates a 1GB virtual size qcow2 (real size is about 196K): $ ll disk -rw-rw-r--. 1 rjones rjones 196624 Nov 21 09:20 disk $ file disk disk: QEMU QCOW Image (v3), 1073741824 bytes > 2. Export the qcow2 file then try to read it via nbd url > # nbdkit file file=disk -e raw -v This exports the disk using the export name "raw". However nbd...

...images]# 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 > file format: qcow2 > virtual size: 8.0G (8589934592 bytes) > disk size: 196K > cluster_size: 65536 > backing file: /mnt/vmimages/centos6.img > backing file format: raw > Format specific information: > compat: 0.10 > refcount bits: 16 > > - when creating a snapshot, the resulting file is a qcow2 version 3 > (comapt=1.1) file. Example: >...

...virt/images/serve.lordcritical.bimg-20130920-170511'. hn LibVirtKvm-scripts # qemu-img info /var/lib/libvirt/images/serve.lordcritical.bimg-20130920-170511 image: /var/lib/libvirt/images/serve.lordcritical.bimg-20130920-170511 file format: qcow2 virtual size: 40G (42949672960 bytes) disk size: 196K cluster_size: 65536 backing file: /var/lib/libvirt/images/serve.lordcritical.bimg-20130920-170121 backing file format: qcow2 hn LibVirtKvm-scripts # cheers t. > Thanks! > >> At the moment i try: >> >> https://bitbucket.org/guilhemfr/virt-back > > Seems very inte...

...dio - more than 12x, where I only need about 4x. Hopefully that means I have plenty of room to tweak so I can fit it in my limited resources. My resources: - 48MHz 32-bit ARM Cortex-M0 - 32k RAM (of which I probably on have 16-24k available) - 256k ROM (of which I probably only have 128-196k available) I have no doubt that I can fit the design in ROM - I've already tried ripping out the decoder, and a stripped build can fit in 160k. But, on speed and RAM, any thoughts on the feasibility, or what I'd have to do to make this work? Brian -- -- Brian Silverman Ready Set STE...

...counts: true refcount bits: 16 corrupt: false Same operation using qemu-img convert: $ qemu-img convert -O qcow2 /home/nsoffer/var/libvirt/images/tiny.qcow2 convert.qcow2 $ qemu-img info convert.qcow2 image: convert.qcow2 file format: qcow2 virtual size: 102M (107374592 bytes) disk size: 196K cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false So with libvirt we downloaded 102M, and qemu copied only 196K. Nir

Hello, I face a problem on the nbdkit server: Version-Release number of selected component (if applicable): nbdkit-v1.9.1 qemu-utils-2.12+dfsg-3+b1 How reproducible: 100% Steps: 1. Create a qcow2 file # qemu-img create disk 1G -f qcow2 2. Export the qcow2 file then try to read it via nbd url # nbdkit file file=disk -e raw -v nbdkit: debug: TLS disabled: could not load TLS certificates nbdkit:

Hi,guys I wanna to get the disk snapshot size, but found nothing libvirt commands related,except qemu-img. I create two disk snapshots, but nothing return its' size [root@cskvm01 qcow2]# qemu-img info /mnt/e6758700-af68-3c06-ade3-53f5f9b93507/e2cf6551-0d2c-4382-a86c-8ba633954ff2 image: /mnt/e6758700-af68-3c06-ade3-53f5f9b93507/e2cf6551-0d2c-4382-a86c-8ba633954ff2 file format: qcow2 virtual

...mv fedora-22.img fedora-22.img.sparse $ cp --sparse=never fedora-22.img.sparse fedora-22.img $ du -sh fedora-22.img 6.1G fedora-22.img Let's add a snapshot on top: $ qemu-img create -f qcow2 -o compat=1.1 -b fedora-22.img overlay.qcow2 $ du -sh fedora-22.img overlay.qcow2 6.1G fedora-22.img 196K overlay.qcow2 and sparsify the overlay: $ virt-sparsify --in-place overlay.qcow2 $ du -sh fedora-22.img overlay.qcow2 6.1G fedora-22.img 3.2M overlay.qcow2 All that happened was that the overlay got bigger (because it's now storing a bunch of qcow2 zero clusters marking the places in the b...

On 04/26/2016 09:35 AM, Shahar Havivi wrote: > On 26.04.16 15:30, Shahar Havivi wrote: >> On 26.04.16 14:14, Shahar Havivi wrote: >>> On 25.04.16 09:11, Cole Robinson wrote: >>>> On 04/25/2016 08:10 AM, Shahar Havivi wrote: >>>>> On 17.04.16 15:41, Shahar Havivi wrote: >>>>>> Hi, >>>>>> The following snippet works

...$ qemu-img create -f vmdk base.vmdk 1G $ qemu-img create -f qcow2 -o \ 'backing_file=./base.vmdk,backing_fmt=vmdk' ./overlay1.qcow2 $ qemu-img info overlay1.qcow2 image: overlay1.qcow2 file format: qcow2 virtual size: 1.0G (1073741824 bytes) disk size: 196K cluster_size: 65536 backing file: ./base.vmdk backing file format: vmdk Format specific information: compat: 1.1 lazy refcounts: false And, as near as I know, internal snapshots are a feature of qcow2 format. > Currently running libvirt 0.9.12, qemu-kvm 1.1.2 (...

Hi, I got a few centos 5 boxes installed for tests and find the following confusing messages from ?dmesg? command: Your BIOS doesn't leave a aperture memory hole Memory: 4043392k/5242880k available (2397k kernel code, 150460k reserved, 1222k data, 196k init) The machine has only 4GB memory chips installed only, so where comes the number ?5242880k? for memory? [root at centos5Cli01 ~]# cat /proc/meminfo | grep -i total MemTotal: 4045132 kB HighTotal: 0 kB LowTotal: 4045132 kB SwapTotal: 15999252 kB VmallocTotal: 34359738...

...about 4x. Hopefully that > means I have plenty of room to tweak so I can fit it in my limited > resources. > > My resources: > > - 48MHz 32-bit ARM Cortex-M0 > - 32k RAM (of which I probably on have 16-24k available) > - 256k ROM (of which I probably only have 128-196k available) > > I have no doubt that I can fit the design in ROM - I've already tried > ripping out the decoder, and a stripped build can fit in 160k. > > But, on speed and RAM, any thoughts on the feasibility, or what I'd have > to do to make this work? > > > P.S....

...ve started to see odd timeout errors between the app and webserver on this box - Can't see anything obvious and as far as i'm aware nothing has changed any ideas? 9:27am up 128 days, 21:12, 1 user, load average: 4.05, 3.45, 3.07 Mem: 1027760K av, 1022644K used, 5116K free, 196K shrd, 141620K buff Swap: 2097112K av, 624716K used, 1472396K free 215984K cached PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME COMMAND 30404 root 25 0 23848 15M 5428 S 14.0 1.5 86:54 java 7928 root 15 0 12928 12M 6172 S 1.1 1.2...

...10] TCP cubic registered [ 4.398531] NET: Registered protocol family 17 [ 4.408450] Using IPI No-Shortcut mode [ 4.417154] registered taskstats version 1 [ 4.425263] rtc_cmos 00:05: setting system clock to 2009-06-16 07:45:32 UTC (1245138332) [ 4.442439] Freeing unused kernel memory: 196k freed [ 4.490555] SCSI subsystem initialized [ 4.502222] Fusion MPT base driver 3.04.06 [ 4.511363] Copyright (c) 1999-2007 LSI Corporation [ 4.526520] Fusion MPT SAS Host driver 3.04.06 [ 4.536466] ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16 [ 4.551...

Does libvirt support snapshotting when the virtual disk comes from a vmdk file? http://wiki.libvirt.org/page/Snapshots#Desired_functionality seems to say no, since it says "'virsh snapshot', which requires all disk images to be qcow2". OTOH, man virsh, http://libvirt.org/formatsnapshot.html, and http://libvirt.org/formatdomain.html#elementsDisks seem to indicate more

...rce ------------------------------------------------ hda /export/vmimages/sn1.qcow2 Get info about the disks involved: $ qemu-img info --backing-chain /export/vmimages/sn1.qcow2 image: /export/vmimages/sn1.qcow2 file format: qcow2 virtual size: 39M (41126400 bytes) disk size: 196K cluster_size: 65536 backing file: /var/lib/libvirt/images/cirros-0.3.3-x86_64-disk.img backing file format: qcow2 Format specific information: compat: 1.1 lazy refcounts: false image: /var/lib/libvirt/images/cirros-0.3.3-x86_64-disk.img file format: qcow2 virtual size:...