The Virt-Manager Storage Disks Fedora 18 host.

[poma]

On 17.04.2013 19:32, poma wrote:
> On 17.04.2013 17:33, Frank Murphy wrote:
>> On Wed, 17 Apr 2013 15:58:20 +0200
>> poma <pomidorabelisima at gmail.com> wrote:
>>
>>> Mount points are the mount points, regardless of the disks
>>> layout. :)
> 
> […]
> 
>> What are you talking about?
> 
> What am I talking about!? :)
> 
>> If the stated disk in Virt-Manager is sdf for  eg Fedora-17
>> and the host then changes it to sdg, it's still sdf in virt-Manager.
>> Thus it complains about the image not being found.
> 
> You haven't confirmed the first question.
> That part you left out in this response, and it is essential to clarify
> the problem. ;)

Hah!
Frank, it would be nice of you to use the correct terminology[1]. ;)
Your so called "virt-images" are not a virtual machines per se.
It is possible that you do not use physical discs as a block based
storage pool, nor as a storage volumes at all - but you're adding them
directly to guests as a physical devices.
So an UUID[2] is probably what you need:
/etc/libvirt/qemu/Magrathea.xml
[…]
<disk type='block' device='disk'>
  <driver name='qemu' type='raw'/>
  <source dev='/dev/disk/by-uuid/x8-x4-x4-x4-x12'/>
  <target dev='sda' bus='scsi'/>
  <address type='drive' controller='0' bus='0' target='0' unit='0'/>
</disk>
[…]


poma


[1]
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html-single/Virtualization_Administration_Guide/index.html
[2] http://en.wikipedia.org/wiki/Universally_unique_identifier