Displaying 20 results from an estimated 216 matches for "cluster_size".
2019 Apr 23
1
Autodetecting backing file properties when using vol-create-as
...f 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
refcount bits: 1...
2009 Oct 27
2
[PATCH 3/4] scsi-disk: Factor out SCSI command emulation
...uint64_t sector;
uint32_t sector_count;
- struct iovec iov;
+ struct iovec *iov;
QEMUIOVector qiov;
BlockDriverAIOCB *aiocb;
struct SCSIRequest *next;
@@ -72,7 +72,8 @@ struct SCSIDiskState
This is the number of 512 byte blocks in a single scsi sector. */
int cluster_size;
uint64_t max_lba;
- int sense;
+ uint8_t sense[SCSI_SENSE_LEN];
+ uint8_t sense_len;
char drive_serial_str[21];
QEMUBH *bh;
};
@@ -90,13 +91,12 @@ static SCSIRequest *scsi_new_request(SCSIDevice *d, uint32_t tag)
free_requests = r->next;
} else {...
2009 Oct 27
2
[PATCH 3/4] scsi-disk: Factor out SCSI command emulation
...uint64_t sector;
uint32_t sector_count;
- struct iovec iov;
+ struct iovec *iov;
QEMUIOVector qiov;
BlockDriverAIOCB *aiocb;
struct SCSIRequest *next;
@@ -72,7 +72,8 @@ struct SCSIDiskState
This is the number of 512 byte blocks in a single scsi sector. */
int cluster_size;
uint64_t max_lba;
- int sense;
+ uint8_t sense[SCSI_SENSE_LEN];
+ uint8_t sense_len;
char drive_serial_str[21];
QEMUBH *bh;
};
@@ -90,13 +91,12 @@ static SCSIRequest *scsi_new_request(SCSIDevice *d, uint32_t tag)
free_requests = r->next;
} else {...
2015 Mar 15
3
how to get disk snapshot size
...ng 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 size: 5.0G (5368709120 bytes)
disk size: 1.0G
cluster_size: 65536
Snapshot list:
ID TAG VM SIZE DATE VM CLOCK
1 4fc42d73-8257-42bd-8807-81700fd3c689 0 2015-03-15 21:05:55
01:05:53.583
2 2fd6aeab-cb26-446d-b1c6-e8d70d33f651 0 2015-03-15 21:50:35
00:00:00.000
After wrote data to the disk,...
2013 Apr 12
1
after snapshot-delete, the qcow2 image file size doesn't decrease
...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 State
--------------------------------...
2013 Sep 03
3
Is virsh blockcommit supported? Thanks a lot
...valid argument: top '/vms/images/Vmtest1_base_1' in chain for '/vms/images/Vmtest1' has no backing file
1
root at cvk-31:/vms/images# qemu-img info /vms/images/Vmtest1_base_1
image: /vms/images/Vmtest1_base_1
file format: qcow2
virtual size: 9.8G (10485760000 bytes)
disk size: 6.0M
cluster_size: 2097152
backing file: /vms/images/Vmtest1_base
root at cvk-31:/vms/images# qemu-img info --backing-chain /vms/images/Vmtest1
image: /vms/images/Vmtest1
file format: qcow2
virtual size: 9.8G (10485760000 bytes)
disk size: 140M
cluster_size: 2097152
backing file: /vms/images/Vmtest1_base_1
image:...
2015 Oct 16
2
[PATCH] New API: ntfsresize_info
...CLEANUP_FREE char *err = NULL, *out = NULL;
+ CLEANUP_FREE_STRING_LIST char **lines = NULL;
+ int r;
+ size_t i;
+ char *p;
+ int64_t ret, volume_size = 0;
+ const char *size_pattern = "You might resize at ",
+ *full_pattern = "Volume is full",
+ *cluster_size_pattern = "Cluster size",
+ *volume_size_pattern = "Current volume size:";
+ int is_full = 0;
+ int32_t cluster_size = 0;
+
+ /* FS may be marked for check, so force ntfsresize */
+ r = command (&out, &err, str_ntfsresize, "--info", "-ff&qu...
2015 Jun 02
2
preallocation=full Vs preallocation=metadata
Hi All
I was reading through this:
http://kashyapc.com/2011/12/02/little-more-disk-io-perf-improvement-with-fallocateing-a-qcow2-disk/
I was basically searching for pointers on improving disk I/O.
I wanted to know the purpose of preallocation=full &
preallocation=metadata , What is the difference between them ? and which
one would yield a better disk I/O speed ?
Appreciate your
2015 Oct 16
0
[PATCH 1/2] New API: get_min_size
...CLEANUP_FREE char *err = NULL, *out = NULL;
+ CLEANUP_FREE_STRING_LIST char **lines = NULL;
+ int r;
+ size_t i;
+ char *p;
+ int64_t ret, volume_size = 0;
+ const char *size_pattern = "You might resize at ",
+ *full_pattern = "Volume is full",
+ *cluster_size_pattern = "Cluster size",
+ *volume_size_pattern = "Current volume size:";
+ int is_full = 0;
+ int32_t cluster_size = 0;
+
+ /* FS may be marked for check, so force ntfsresize */
+ r = command (&out, &err, str_ntfsresize, "--info", "-ff&qu...
2015 Oct 19
5
Re: [PATCH 1/2] New API: vfs_min_size
..._t i;
> + char *p;
> + int64_t ret, volume_size = 0;
The scope of "ret" could be reduced to only the if below where it is
used.
> + const char *size_pattern = "You might resize at ",
> + *full_pattern = "Volume is full",
> + *cluster_size_pattern = "Cluster size",
> + *volume_size_pattern = "Current volume size:";
> + int is_full = 0;
> + int32_t cluster_size = 0;
> +
> + /* FS may be marked for check, so force ntfsresize */
> + r = command (&out, &err, str_ntfsresize, &q...
2015 Oct 19
0
[PATCH 1/2] New API: vfs_min_size
...CLEANUP_FREE char *err = NULL, *out = NULL;
+ CLEANUP_FREE_STRING_LIST char **lines = NULL;
+ int r;
+ size_t i;
+ char *p;
+ int64_t ret, volume_size = 0;
+ const char *size_pattern = "You might resize at ",
+ *full_pattern = "Volume is full",
+ *cluster_size_pattern = "Cluster size",
+ *volume_size_pattern = "Current volume size:";
+ int is_full = 0;
+ int32_t cluster_size = 0;
+
+ /* FS may be marked for check, so force ntfsresize */
+ r = command (&out, &err, str_ntfsresize, "--info", "-ff&qu...
2015 Oct 20
0
[PATCHv3 1/2] New API: vfs_min_size
...har *device)
+{
+ CLEANUP_FREE char *err = NULL, *out = NULL;
+ CLEANUP_FREE_STRING_LIST char **lines = NULL;
+ int r;
+ size_t i;
+ int64_t volume_size = 0;
+ const char *size_pattern = "You might resize at ",
+ *full_pattern = "Volume is full",
+ *cluster_size_pattern = "Cluster size",
+ *volume_size_pattern = "Current volume size:";
+ int is_full = 0;
+ int32_t cluster_size = 0;
+
+ /* FS may be marked for check, so force ntfsresize */
+ r = command (&out, &err, str_ntfsresize, "--info", "-ff&qu...
2015 Oct 20
0
[PATCHv4 1/2] New API: vfs_minimum_size
...har *device)
+{
+ CLEANUP_FREE char *err = NULL, *out = NULL;
+ CLEANUP_FREE_STRING_LIST char **lines = NULL;
+ int r;
+ size_t i;
+ int64_t volume_size = 0;
+ const char *size_pattern = "You might resize at ",
+ *full_pattern = "Volume is full",
+ *cluster_size_pattern = "Cluster size",
+ *volume_size_pattern = "Current volume size:";
+ int is_full = 0;
+ int32_t cluster_size = 0;
+
+ /* FS may be marked for check, so force ntfsresize */
+ r = command (&out, &err, str_ntfsresize, "--info", "-ff&qu...
2016 Jun 15
2
virt-sparsify changing the apparent-size of files
....img
2.4G input.qcow2
790M output.qcow2
The only way I have found to check the full virtual size of the file
after virt-sparsify is with qemu-img:
root@testingbox:/tmp/test # qemu-img info input.qcow2
image: input.qcow2
file format: qcow2
virtual size: 50G (53687091200 bytes)
disk size: 2.3G
cluster_size: 65536
Format specific information:
compat: 1.1
lazy refcounts: true
root@testingbox:/tmp/test # qemu-img info output.qcow2
image: output.qcow2
file format: qcow2
virtual size: 50G (53687091200 bytes)
disk size: 789M
cluster_size: 65536
Format specific information:
compat: 1.1
lazy...
2016 Jun 15
2
virt-sparsify changing the apparent-size of files
....img
2.4G input.qcow2
790M output.qcow2
The only way I have found to check the full virtual size of the file
after virt-sparsify is with qemu-img:
root@testingbox:/tmp/test # qemu-img info input.qcow2
image: input.qcow2
file format: qcow2
virtual size: 50G (53687091200 bytes)
disk size: 2.3G
cluster_size: 65536
Format specific information:
compat: 1.1
lazy refcounts: true
root@testingbox:/tmp/test # qemu-img info output.qcow2
image: output.qcow2
file format: qcow2
virtual size: 50G (53687091200 bytes)
disk size: 789M
cluster_size: 65536
Format specific information:
compat: 1.1
lazy...
2013 Jun 10
2
Re: virsh snapshot-create and blockcopy
...up-blockcopy/gentoo-template/gentoo-template.qcow2
hn ~ # qemu-img info --backing-chain
/opt/virt-backup-blockcopy/gentoo-template/gentoo-template.qcow2
image: /opt/virt-backup-blockcopy/gentoo-template/gentoo-template.qcow2
file format: qcow2
virtual size: 130G (139586437120 bytes)
disk size: 30G
cluster_size: 65536
Just to make myself clear. I want to backup the qcow image /with/ the
internal snapshot. Is that even possible with blockcopy?
thanks and best regards.
>> virsh snapshot-delete gentoo-template --current
>>
>> But if i restore the /opt/virt-backup-blockcopy/gentoo-templa...
2015 Mar 16
0
Re: how to get disk snapshot size
...-----------------------------------------------
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: 39M (41126400 b...
2015 Oct 19
5
[PATCHv2 0/2] Introduce vfs_min_size API to get minimum filesystem size.
Tried to make it in accordance with your comments.
Difference to v1:
Added reply_with_error where necessary.
Changed name get_min_size -> vfs_min_size.
Maxim Perevedentsev (2):
New API: vfs_min_size
Include resize2fs_P into vfs_min_size.
daemon/Makefile.am | 1 +
daemon/daemon.h | 2 ++
daemon/ext2.c | 45 ++++++++++++++++++++++++++-----
daemon/fs-min-size.c | 49
2016 Jun 22
0
Re: [libvirt-users] virt-sparsify changing the apparent-size of files
...rent size and
identifies as qcow2 as shown below.
# ls -slh testimage.qcow2
2.5G -rw-r--r-- 1 root root 51G Jun 22 20:22 testimage.qcow2
# qemu-img info testimage.qcow2
image: testimage.qcow2
file format: qcow2
virtual size: 50G (53687091200 bytes)
disk size: 2.4G
cluster_size: 65536
Format specific information:
compat: 1.1
lazy refcounts: true
Now we sparsify (/bigtmp is on a larger partition then / to give
virt-sparsify enough room to work with so it does not complain).
root@testingbox: 08:59 PM # virt-sparsify testimage.qcow2
testimage1.q...
2016 Jun 22
3
Re: [libvirt-users] virt-sparsify changing the apparent-size of files
On Wed, Jun 22, 2016 at 12:40:40AM -0500, libvirt_users@skagitattic.com wrote:
> So you are saying when I do the virt-sparsify its converting the image
> from raw to [qcow2]?
No. virt-sparsify will use the same input and output formats, unless
you use the --convert option.
> I studied the man page for virt-sparsify and tried again with
> the flag "--format raw"