Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am attempting to setup an ISCSI target using the qcow2 image format. It does not appear that tgtd supports the qcow2 format. The disk size will show zero or give a 250kb or so disk size. My question is what is the best way to setup a virtual disk using iscsi? For example I would like to create an ISCSI 1TB virtual disk. The disk would not consume 1TB but would have 1TB available. As data is added to it, the actual file size would grow.
Micro$oft has the ability to use VHD files to do this.I can easily setup a dd image file that consumes the entire size specified and ISCSI will work fine. But filling up an entire 1TB drive in my application is not practical. Any help would be appreciated.
This should work and I feel like I have seen the how to on it not too long ago.
In a very basic sense it would be the same as a virtual image on a scsi drive. We know that work. The issue here is that you may not have iscsi support in the loading. What you are trying do is boot or load some OS or virtual machine client, correct?
Correct. I am looking for disk storage and not to boot an OS. The sparse file idea works. However, I am looking to use the Fuse file system to store the virtual drive. Sparse files do not show up correctly on a fuse file system. I am looking to mount a folder to Amazon or Rackspace using fuse, and then store a virtual disk inside the folder. ISCSI would use this virtual disk as storage and the file would grow as space is needed. I know performance would not be great but it would work for my needs. QCow2 is not necessarily a requirement as long as I do not need to allocate the full amount of space to the storage.
ISCSI > virtual disk > stored on a cloud Rackspace or AWS.
Basically an ISCSI drive that has 1TB of storage housed in a cloud. That grows as files are stored in it.
Thanks for the responses. If anyone has any further feedback that would be great. I will continue trying to pursue the idea and will post if I figure it out. Thanks!
but that's the thing - qcow2 provides a block device. Give your machine access to a larger LUN (or increase the LUN size - most SANs allow you to do that) and you've got a larger block device, but the partition on it will be the same size. Expand a qcow2 or raw file, while a VM is running, and it'll also have a larger block device attached, but the partitions will not change.
All I'm saying is that this behaviour is the same on all systems, and you can expand the partition's size live, using the OS tools, without powering down your machine.