On 06/07/2012 10:33 AM, Gianluca Cecchi wrote: > On Thu, Jun 7, 2012 at 4:01 PM, Cole Robinson wrote: >> Nope, that's something different, so keep that. But do drop the <address >> type='pci'... line from the <disk> block, and libvirt will generate you a >> new one. >> >> - Cole >> > > ah...ok sorry for the confusion.. too many virt* things ;-) > > BTW it is working like a charm at the moment without any complaint. > Even the encrypted /home I have inside the guest that has > /dev/mapper/luks-4b0a873a-72bf-4153-b188-65ee9a6449f1 > as first field of /etc/fstab > I'm going to do some testing. > Thank you very much in the mean time > Any problems with the disk config when managing any other parameter in > virt-manager for this vm, such as adding a network card or other > things? > > For the note, after starting the domain, the <disk> and <controller> > blocks has been changed this way: > > <disk type='file' device='disk'> > <driver name='qemu' type='qcow2'/> > <source file='/var/lib/libvirt/images/f17.img'/> > <target dev='sda' bus='scsi'/> > <address type='drive' controller='0' bus='0' target='0' unit='0'/> > </disk> > > <controller type='scsi' index='0' model='virtio-scsi'> > <address type='pci' domain='0x0000' bus='0x00' slot='0x06' > function='0x0'/> > </controller> > > Gianluca
That's all expected, it's libvirt adding stable device addressing so that some future qemu update doesn't change defaults and rearrange your hardware, which can upset guests (particularly windows). - Cole _______________________________________________ virt mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/virt
