Comment 10 for bug 1221190

I just tested trunk and didn't see the behaviour described in this report.

I have nova setup to use raw files

$ grep cow /etc/nova/nova.conf
use_cow_images = False

I then booted, stopped & rescued an instance

$ nova boot --flavor m1.small --image f16-x86_64-openstack-sda f16demo
$ nova stop f16demo
$ nova rescue f16demo

When I look at the config libvirt generated, it is correctly setting 'raw' as the disk type
# virsh dumpxml instance-00000003

    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='none'/>
      <source file='/home/berrange/src/cloud/data/nova/instances/cd627e5e-928d-47c2-a24c-e1ccfb01ab6d/disk.rescue'/>
      <target dev='vda' bus='virtio'/>
      <alias name='virtio-disk0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='none'/>
      <source file='/home/berrange/src/cloud/data/nova/instances/cd627e5e-928d-47c2-a24c-e1ccfb01ab6d/disk'/>
      <target dev='vdb' bus='virtio'/>
      <alias name='virtio-disk1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </disk>

> Libvirt description of the rescued instance will contain the entry for the second disk with attribute type="qcow2", even though it should be "raw" - same as the original instance.

@stanislaw What version of Nova do you see this behaviour with ? Today's GIT master doesn't show it