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@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 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.
error message says qemuBlockStorageSourceGetBlockdevFormatProps:1227 : internal error: mishandled storage format 'none'
You might want to post this as well to the Libvirt mailing list.
-- John Doe
On Thu, Sep 21, 2023 at 09:05:43AM +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@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 post the win11.xml file contents too
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.
error message says qemuBlockStorageSourceGetBlockdevFormatProps:1227 : internal error: mishandled storage format 'none'
With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
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@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'
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@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@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 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@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@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.
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@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@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@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.
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@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@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@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@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.
On Fri, Sep 22, 2023 at 06:33:06AM +0100, Bhasker C V wrote:
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)
Glad to hear you managed to make it work!
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 can explain that one. suspend-to-disk.enabled=yes requires a firmware image that advertises the acpi-s4 feature, and you probably don't have one on your system. For example, on my Fedora 38 machine: $ grep acpi-s4 /usr/share/qemu/firmware/*.json $ Yeah, the error message is not very helpful. Unfortunately, due to the way firmware autoselection works, emitting a better one would be pretty much impossible :( -- Andrea Bolognani / Red Hat / Virtualization
On 9/22/23 10:34, Andrea Bolognani wrote:
On Fri, Sep 22, 2023 at 06:33:06AM +0100, Bhasker C V wrote:
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)
Glad to hear you managed to make it work!
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 can explain that one.
suspend-to-disk.enabled=yes requires a firmware image that advertises the acpi-s4 feature, and you probably don't have one on your system.
For example, on my Fedora 38 machine:
$ grep acpi-s4 /usr/share/qemu/firmware/*.json $
Yeah, the error message is not very helpful. Unfortunately, due to the way firmware autoselection works, emitting a better one would be pretty much impossible :(
You can enable debug logs and then observe why each one FW was rejected (see those VIR_DEBUG() printings in qemuFirmwareMatchDomain() [1]). 1: https://gitlab.com/libvirt/libvirt/-/blob/master/src/qemu/qemu_firmware.c?re... Michal
On 22 Sep 2023 01:34 -0700, from abologna@redhat.com (Andrea Bolognani):
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 can explain that one.
suspend-to-disk.enabled=yes requires a firmware image that advertises the acpi-s4 feature, and you probably don't have one on your system.
For example, on my Fedora 38 machine:
$ grep acpi-s4 /usr/share/qemu/firmware/*.json $
Yeah, the error message is not very helpful. Unfortunately, due to the way firmware autoselection works, emitting a better one would be pretty much impossible :(
Might a simple fix to make the error message at least slightly more helpful be to change it to something like: "Unable to find any firmware to satisfy '<whatever>' with specified settings" That would make it clearer that it isn't _necessarily_ the "efi" part (or whatever it happens to be in the specific case) which is the actual, _specific_ problem. -- Michael Kjörling 🔗 https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
On Fri, Sep 22, 2023 at 10:48:55AM +0000, Michael Kjörling wrote:
On 22 Sep 2023 01:34 -0700, from abologna@redhat.com (Andrea Bolognani):
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 can explain that one.
suspend-to-disk.enabled=yes requires a firmware image that advertises the acpi-s4 feature, and you probably don't have one on your system.
For example, on my Fedora 38 machine:
$ grep acpi-s4 /usr/share/qemu/firmware/*.json $
Yeah, the error message is not very helpful. Unfortunately, due to the way firmware autoselection works, emitting a better one would be pretty much impossible :(
Might a simple fix to make the error message at least slightly more helpful be to change it to something like: "Unable to find any firmware to satisfy '<whatever>' with specified settings"
That would make it clearer that it isn't _necessarily_ the "efi" part (or whatever it happens to be in the specific case) which is the actual, _specific_ problem.
Good idea. I've thought about doing this several times, but never actually gotten around to it. Patch on the list :) https://listman.redhat.com/archives/libvir-list/2023-September/242219.html -- Andrea Bolognani / Red Hat / Virtualization
participants (6)
-
Andrea Bolognani -
Bhasker C V -
Daniel P. Berrangé -
Michael Kjörling -
Michal Prívozník -
Peter Krempa