search for: virtualized_block_devices

...kvm_pool1" virsh # pool-autostart pool1 virsh # vol-create-as pool1 volume1 20G --allocation 15G --format qcow2 now I want to associate "volume1" to my guest OS. Following this doc: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization/sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html - why does this ask me to create a file with "dd" ? it's already been created before with the virsh pool commands, isn't it? Seems to me I'm bypassing the libvirt/virsh layer if I do that. - after that, the doc tells me to do some stuff...

...mselves? Once I'd added my LVM volume group to virsh I could see no way of then assigning one volume of that to be offered as a logical volume to one particular virtual machine. I've also seen this: http://docs.fedoraproject.org/en-US/Fedora/13/html/Virtualization_Guide/sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html#proc-Virtualization-Adding_storage_devices_to_guests-Adding_physical_block_devices_to_virtualized_guests Looks like I could use that to assign one of the LVM volumes in my LVM volume group to the VM. If anyone could explain the different function of these two...

Hi All :) I am currently involved in a project in which there is a SAN array (Sun Storagetek 2540) which exports LUNs for some servers with Centos 5.2 x86. I will be performing a migration to Centos 5.9 x86_64 in some time and am gathering needed info now :) I am trying to find the place in the OS where there is the information about LUN mappings to /dev/ devices. For example on array level I