On Thu, Sep 21, 2023 at 10:50:07 +0100, Bhasker C V wrote: > Attaching win11.xml > Please note that this used to work fine. It is failing now on libvirt- > 9.7.0-1 > > On Thu, Sep 21, 2023 at 9:13 AM Peter Krempa <pkrempa@xxxxxxxxxx> wrote: > > > On Thu, Sep 21, 2023 at 09:05:43 +0100, Bhasker C V wrote: > > > Adding libvirt mailing list > > > apologies for cross-posting > > > libvirt version: 9.7.0-1 > > > > > > On Thu, Sep 21, 2023 at 8:39 AM john doe <johndoe65534@xxxxxxxx> wrote: > > > > > > > On 9/21/23 09:32, Bhasker C V wrote: > > > > > I am getting an error with libivrt when I create a VM > > > > > > > > > > ``` > > > > > $ sudo virsh create ./win11.xml > > > > Please attach the XML used here. It comes from a code path which > > shouldn't be possible to reach. > > > > > > > error: Failed to create domain from ./win11.xml > > > > > error: internal error: mishandled storage format 'none' > > > > > > > > > > ``` > > > > > > > > > > This is after I have done a dist-upgrade (was working fine before) > > > > > debian trixie. > > > > Which version did you have before? > > > > > > > > > > > > error message says > > > > > qemuBlockStorageSourceGetBlockdevFormatProps:1227 : internal error: > > > > > mishandled storage format 'none' > > > > > <on_poweroff>destroy</on_poweroff> > <on_reboot>restart</on_reboot> > <on_crash>destroy</on_crash> > <pm> > <suspend-to-mem enabled='no'/> > <suspend-to-disk enabled='no'/> > </pm> > <devices> > <emulator>/usr/bin/qemu-system-x86_64</emulator> > <disk type='file' device='disk'> > <driver name='qemu' type='qcow2' cache='unsafe'/> > <source file='/var/virt/WINDOWS/WIN11' index='2'/> > <target dev='vda' bus='virtio'/> > </disk> Could you please also attach the output of: qemu-img info --backing-chain '/var/virt/WINDOWS/WIN11' > <disk type="file" device="disk"> > <driver name="qemu" type="raw" cache="unsafe"/> > <source file="/var/virt/WINDOWS/DUMMY"> > <format type='gpt'/> > </source> > <target dev="vdb" bus="virtio"/> > </disk> In the definition I don't see anything that would hint that anything with the disk config is broken, for qcow2 volumes we do auto-detection of backing images, thus the request for the output of the command above.
