search for: testingbox

...;ls -lh" shows the full apparent size and "du -sh" shows the actual size. But my actual results from testing are different. In the following example input.qcow2 is before sparsify and output.qcow2 is after. Doing ls reports full size for input but a small size for the output: root@testingbox:/tmp/test # ls -lh total 3.1G -rw-r--r-- 1 root root 512M Jun 14 22:30 file.img -rw-r--r-- 1 root root 51G Jun 14 22:30 input.qcow2 -rw-r--r-- 1 root root 790M Jun 14 22:36 output.qcow2 Same when asking du for apparent-size: root@testingbox:/tmp/test # du -h --apparent-size * 512M file.img 51G...

...;ls -lh" shows the full apparent size and "du -sh" shows the actual size. But my actual results from testing are different. In the following example input.qcow2 is before sparsify and output.qcow2 is after. Doing ls reports full size for input but a small size for the output: root@testingbox:/tmp/test # ls -lh total 3.1G -rw-r--r-- 1 root root 512M Jun 14 22:30 file.img -rw-r--r-- 1 root root 51G Jun 14 22:30 input.qcow2 -rw-r--r-- 1 root root 790M Jun 14 22:36 output.qcow2 Same when asking du for apparent-size: root@testingbox:/tmp/test # du -h --apparent-size * 512M file.img 51G...

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"

...t; and "du -sh" shows the actual size. But my actual results from testing > are different. > > In the following example input.qcow2 is before sparsify and output.qcow2 > is after. > > Doing ls reports full size for input but a small size for > the output: > root@testingbox:/tmp/test # ls -lh > total 3.1G > -rw-r--r-- 1 root root 512M Jun 14 22:30 file.img > -rw-r--r-- 1 root root 51G Jun 14 22:30 input.qcow2 > -rw-r--r-- 1 root root 790M Jun 14 22:36 output.qcow2 What is file.img? > Same when asking du for apparent-size: > root@testingbox:/tmp/te...

...t; and "du -sh" shows the actual size. But my actual results from testing > are different. > > In the following example input.qcow2 is before sparsify and output.qcow2 > is after. > > Doing ls reports full size for input but a small size for > the output: > root@testingbox:/tmp/test # ls -lh > total 3.1G > -rw-r--r-- 1 root root 512M Jun 14 22:30 file.img > -rw-r--r-- 1 root root 51G Jun 14 22:30 input.qcow2 > -rw-r--r-- 1 root root 790M Jun 14 22:36 output.qcow2 What is file.img? > Same when asking du for apparent-size: > root@testingbox:/tmp/te...

...al size. But my actual results > > from testing are different. > > > > In the following example input.qcow2 is before sparsify and > > output.qcow2 is after. > > > > Doing ls reports full size for input but a small size for > > the output: > > root@testingbox:/tmp/test # ls -lh > > total 3.1G > > -rw-r--r-- 1 root root 512M Jun 14 22:30 file.img > > -rw-r--r-- 1 root root 51G Jun 14 22:30 input.qcow2 > > -rw-r--r-- 1 root root 790M Jun 14 22:36 output.qcow2 > > What is file.img? > > > Same when asking du for a...

...u created the guest. Use 'qemu-img info' to show the > > format of the input file. Show precisely the virt-sparsify command > > you are running. And use 'qemu-img info' on the output file too. > > Okay, here goes. Start off with an install > > root@testingbox:~ # virt-install --name testimage --memory 512 -l > 'http://ftp.nl.debian.org/debian/dists/jessie/main/installer-amd64/' > --disk size=50 --nographics -x "console=ttyS0" > > Starting install... > Retrieving file > MANIFEST... &gt...

...Describe > exactly how you created the guest. Use 'qemu-img info' to show the > format of the input file. Show precisely the virt-sparsify command > you are running. And use 'qemu-img info' on the output file too. Okay, here goes. Start off with an install root@testingbox:~ # virt-install --name testimage --memory 512 -l 'http://ftp.nl.debian.org/debian/dists/jessie/main/installer-amd64/' --disk size=50 --nographics -x "console=ttyS0" Starting install... Retrieving file MANIFEST... | 3.3 kB 00:00 ... Retrie...

...9; to show > > > the format of the input file. Show precisely the virt-sparsify > > > command you are running. And use 'qemu-img info' on the output > > > file too. > > > > Okay, here goes. Start off with an install > > > > root@testingbox:~ # virt-install --name testimage --memory 512 > > -l > > 'http://ftp.nl.debian.org/debian/dists/jessie/main/installer-amd64/' > > --disk size=50 --nographics -x "console=ttyS0" > > > > Starting install... > > Retrieving fi...

...works fine. I can see my home directory fine, but when trying to join the domain, it fails. ode On the PDC I am running wireshark and I can see the "SAM LOGIN" requests, but something weird I found with them was that the User Name: field in the packet was either the machine name "TESTINGBOX$" or it was blank. If never passed the user name I entered "cjamieson". The domain/workgroup I am using is set to "borran" The test user I added is "cjamieson" The samba NETBIOS name is "PDC" I am running this in VMWare to evaluate how well of solut...