incus storage volume attach prevents startup of VM for some (longer than 14 characters?) storage names with qemu 9.1.1 #1536
Comments
|
Hi @stgraber |
|
Yep, I assigned it to you now! |
|
Hi @christophhagemann, I just try to reproduce the same error, I coundn't get the same error though. |
|
I setup a VM Debian 12 running incus 6.8 and ZFS as storage pool. Maybe I didn't copy some configuration correctly, which's likely part of the problem 🤔 |
|
Ah, I see. This is related to the qemu version. For unrelated reasons
(support for pipewire) I'm using debian's qemu, which is version 9.1.1
(Debian 1:9.1.1+ds-5) and fails. Incus' internal qemu in
/opt/incus/bin is version 9.0.4 (v9.0.4-dirty) and works.
|
christophhagemann
changed the title
|
@christophhagemann I installed qemu 9.1.1 on debian 12 VM and incus 6.8. |
|
I was thinking, maybe I need to try running incus on debian 13 🤔 |
|
Hi @stgraber, I had tried to reproduce the same error running incus on debian trixie but qemu 9.2.0 isn't supported yet. Do you have any clue what could I do to reproduce the error, and also could we do something on incus side to handle this problem ? |
|
To reproduce the problem on trixie, use snapshot.debian.org.
Put this stanza in /etc/apt/sources.list
deb [check-valid-until=no] https://snapshot.debian.org/archive/debian/20241201/ trixie main
and then
sudo apt install qemu-system-x86=1:9.1.1+ds-5
(and possibly some other qemu-* packages, IIRC)
Don't forget to disable incus' internal qemu.
But: If this bug is triggered only in such specific circumstanzes that
I'm the only one affected, it might not be worth the time tracking this
down. From my point of view this could be closed or marked wontfix. I
myself can work around it.
Best regards
Christoph
Am Sonntag, dem 05.01.2025 um 10:43 -0800 schrieb Helder Ardachnikoff:
… Hi @stgraber, I had tried to reproduce the same error running incus
on debian trixie but qemu 9.2.0 isn't supported yet.
Do you have any clue what could I do to reproduce the error, and also
could we do something on incus side to handle this problem ?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
I'm getting this issue on Arch Linux. At first, I got the following error: I saw this was a result of QEMU 9.2 breaking things, and that this was fixed in #1522 . Next, I received the following error when trying to start my VM: Below are the steps I used to reproduce this error: incus init trinity-poc \
--empty \
--vm \
-c limits.cpu=4 \
-c limits.memory=8GiB
incus storage volume create default trinity_poc_hdd_0 size=8GB --type=block
incus storage volume attach default trinity_poc_hdd_0 trinity-poc
incus storage volume import default \
~/debian-12.8.0-amd64-netinst.iso \
debian-iso-volume \
--type=iso
incus config device add trinity-poc iso-volume disk \
pool=default \
source=debian-iso-volume \
boot.priority=10
incus start trinity-poc --consoleCrucially, this does not happen if the storage volumes attached to a VM have shorter names. |
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Required information
api_status: stable
api_version: "1.0"
auth: trusted
public: false
auth_methods:
auth_user_name: admin
auth_user_method: unix
environment:
addresses:
architectures:
certificate: |
-----BEGIN CERTIFICATE-----
MIICEzCCAZmgAwIBAgIRAPdHUyKadiOihPOlPJZoPFwwCgYIKoZIzj0EAwMwODEZ
MBcGA1UEChMQTGludXggQ29udGFpbmVyczEbMBkGA1UEAwwScm9vdEBwYy1oeXBl
cnZpc29yMB4XDTI0MTExNjE5MDk0MloXDTM0MTExNDE5MDk0MlowODEZMBcGA1UE
ChMQTGludXggQ29udGFpbmVyczEbMBkGA1UEAwwScm9vdEBwYy1oeXBlcnZpc29y
MHYwEAYHKoZIzj0CAQYFK4EEACIDYgAEXrfQJsctleWwF03XLGnJGMVijQ0ZUnYD
BK5bfmJexluhvFL2Pp9FtRaVSw/sBqR8AJ4oN5sqm3A9gB2obT7ZcfIOrWdNr1tY
VI0IH4LveIPGkJCYoW4/seFBIePrRS1Mo2cwZTAOBgNVHQ8BAf8EBAMCBaAwEwYD
VR0lBAwwCgYIKwYBBQUHAwEwDAYDVR0TAQH/BAIwADAwBgNVHREEKTAngg1wYy1o
eXBlcnZpc29yhwR/AAABhxAAAAAAAAAAAAAAAAAAAAABMAoGCCqGSM49BAMDA2gA
MGUCMEZ6Hs6TmNI+IeKWvxDoDmffkyBIjE8Ut8uFWxWCa85D6iwmlag7qa/DbH6F
yK0UCwIxAOUmtzx/dhtaZXCbb74B0K/2TUUDKLPPHpZ7xvm6NtJKhHFCrDVBxlfn
LKA0Mylg7Q==
-----END CERTIFICATE-----
certificate_fingerprint: 986d30c1248d8e6f2ba145232a39a7dfd1bb6bb11bcd8b91d684b64240005f82
driver: lxc | qemu
driver_version: 6.0.2 | 9.2.0
firewall: nftables
kernel: Linux
kernel_architecture: x86_64
kernel_features:
idmapped_mounts: "true"
netnsid_getifaddrs: "true"
seccomp_listener: "true"
seccomp_listener_continue: "true"
uevent_injection: "true"
unpriv_binfmt: "true"
unpriv_fscaps: "true"
kernel_version: 6.11.7-amd64
lxc_features:
cgroup2: "true"
core_scheduling: "true"
devpts_fd: "true"
idmapped_mounts_v2: "true"
mount_injection_file: "true"
network_gateway_device_route: "true"
network_ipvlan: "true"
network_l2proxy: "true"
network_phys_macvlan_mtu: "true"
network_veth_router: "true"
pidfd: "true"
seccomp_allow_deny_syntax: "true"
seccomp_notify: "true"
seccomp_proxy_send_notify_fd: "true"
os_name: Debian GNU/Linux
os_version: ""
project: default
server: incus
server_clustered: false
server_event_mode: full-mesh
server_name: pc-hypervisor
server_pid: 778
server_version: "6.8"
storage: zfs
storage_version: 2.2.6-2
storage_supported_drivers:
version: 2.2.6-2
remote: false
version: 6.6.3
remote: false
version: "1"
remote: false
Issue description
Incus fails to start a VM when I attach specifically (too long?) named block devices with
Steps to reproduce
incus create images:debian/trixie/default/amd64 mytestvm --vmincus storage volume create incus my_testing_blockdevice --type=block size=400GBincus storage volume attach incus my_testing_blockdevice mytestvmincus start mytestvmInformation to attach
The bug doesn't occur for device names shorter than 15 characters.
my_testing_bloworks,my_testing_blocdoesn't.qemu.qmp.log is here: https://pastebin.com/i0tCXDGB
Thanks for this great piece of software and your hard work! Let me know if I can help debug things further.
Best regards,
Christoph Hagemann
The text was updated successfully, but these errors were encountered: