I finally fixed it.
The issue seems to be with the tpm-tis/cpu backend (wonder why it shows up
with a different error)
For the sake of community, I am attaching the new xml file so that you can
do forensics on what changed
(I prettymuch did a virt-install --import --print-xml to redo the config
keeping everything intact)
I found another issue
If I switch the suspend-to-disk enabled="yes"
I strangely get an error
error: operation failed: Unable to find any firmware to satisfy 'efi'
I presume the errors being spit out are not accurate description of
failures anymore with libvirt and for the life of mine I could not find why
the other xml file doesnt work and why this does.
Happy libvirt-ing
On Thu, Sep 21, 2023 at 2:58?PM Bhasker C V <bhasker at unixindia.com>
wrote:
> Hi,
> I have tried that too and that did not help either (i.e adding the format
> type=gpt)
> The output you requested
>
> ```
> $ sudo qemu-img info --backing-chain /var/virt/WINDOWS/WIN11
> image: /var/virt/WINDOWS/WIN11
> file format: qcow2
> virtual size: 60 GiB (64424509440 bytes)
> disk size: 55.1 GiB
> cluster_size: 65536
> backing file: WIN11-BASE (actual path: /var/virt/WINDOWS/WIN11-BASE)
> backing file format: raw
> Format specific information:
> compat: 1.1
> compression type: zlib
> lazy refcounts: false
> refcount bits: 16
> corrupt: false
> extended l2: false
> Child node '/file':
> filename: /var/virt/WINDOWS/WIN11
> protocol type: file
> file length: 55.1 GiB (59202338816 bytes)
> disk size: 55.1 GiB
>
> image: /var/virt/WINDOWS/WIN11-BASE
> file format: raw
> virtual size: 60 GiB (64424509440 bytes)
> disk size: 26.5 GiB
> Child node '/file':
> filename: /var/virt/WINDOWS/WIN11-BASE
> protocol type: file
> file length: 60 GiB (64424509440 bytes)
> disk size: 26.5 GiB
> ```
>
> On Thu, Sep 21, 2023 at 2:52?PM Peter Krempa <pkrempa at redhat.com>
wrote:
>
>> 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 at
redhat.com>
>> 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 at mail.com>
>> 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.
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://listman.redhat.com/archives/libvirt-users/attachments/20230922/c446297e/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: win11-fixed.xml
Type: text/xml
Size: 2892 bytes
Desc: not available
URL:
<http://listman.redhat.com/archives/libvirt-users/attachments/20230922/c446297e/attachment-0001.xml>