Your message dated Tue, 11 Jan 2022 13:32:51 +0300
with message-id <[email protected]>
and subject line Re: Bug#1003523: sata disk rotation_rate argument doesn't work
anymore
has caused the Debian Bug report #1003523,
regarding sata disk rotation_rate argument doesn't work anymore
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1003523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003523
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: qemu-system-x86
Version: 1:6.2+dfsg-1
Severity: important
X-Debbugs-Cc: [email protected]
I have been using libvirt (virtual-manager) and also I have been doing system
updates regularly last two days, since this update to qemu I am unable start
guest OS with following arguments in libvirt xml configuration.
<qemu:commandline>
<qemu:arg value="-set"/>
<qemu:arg value="device.sata0-0-0.rotation_rate=1"/>
</qemu:commandline>
I am not 100% sure if this is just qemu issue, it could be libvirt and qemu
issue. Because libvirt packages were also updated along with this.
This is the error I get, when I try to start the guest OS:
Error starting domain: internal error: process exited while connecting to
monitor: qemu-system-x86_64: -set device.sata0-0-0.rotation_rate=1: there is no
device "sata0-0-0" defined
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.15.0-2-amd64 (SMP w/24 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages qemu-system-x86 depends on:
ii ipxe-qemu 1.0.0+git-20190125.36a4c85-5.1
ii libaio1 0.3.112-13
ii libc6 2.33-2
ii libcapstone4 4.0.2-5
ii libfdt1 1.6.1-1
ii libfuse3-3 3.10.5-1
ii libgcc-s1 11.2.0-13
ii libglib2.0-0 2.70.2-1
ii libgnutls30 3.7.2-5
ii libibverbs1 38.0-1
ii libjpeg62-turbo 1:2.1.2-1
ii libnettle8 3.7.3-1
ii libnuma1 2.0.14-3
ii libpixman-1-0 0.40.0-1
ii libpmem1 1.11.1-3
ii libpng16-16 1.6.37-3
ii librdmacm1 38.0-1
ii libsasl2-2 2.1.27+dfsg2-2
ii libseccomp2 2.5.3-2
ii libslirp0 4.6.1-1
ii libudev1 249.7-1
ii liburing2 2.1-2
ii libvdeplug2 4.0.1-3
ii libxendevicemodel1 4.14.3+32-g9de3671772-1
ii libxenevtchn1 4.14.3+32-g9de3671772-1
ii libxenforeignmemory1 4.14.3+32-g9de3671772-1
ii libxengnttab1 4.14.3+32-g9de3671772-1
ii libxenmisc4.14 4.14.3+32-g9de3671772-1
ii libxenstore3.0 4.14.3+32-g9de3671772-1
ii libxentoolcore1 4.14.3+32-g9de3671772-1
ii libzstd1 1.4.8+dfsg-3
ii qemu-system-common 1:6.2+dfsg-1
ii qemu-system-data 1:6.2+dfsg-1
ii seabios 1.15.0-1
ii zlib1g 1:1.2.11.dfsg-2
Versions of packages qemu-system-x86 recommends:
ii ovmf 2021.11-1
ii qemu-block-extra 1:6.2+dfsg-1
ii qemu-system-gui 1:6.2+dfsg-1
ii qemu-utils 1:6.2+dfsg-1
Versions of packages qemu-system-x86 suggests:
pn samba <none>
pn vde2 <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
On 11.01.2022 13:11, themightydeity wrote:
Package: qemu-system-x86
Version: 1:6.2+dfsg-1
Severity: important
X-Debbugs-Cc: [email protected]
I have been using libvirt (virtual-manager) and also I have been doing system
updates regularly last two days, since this update to qemu I am unable start
guest OS with following arguments in libvirt xml configuration.
<qemu:commandline>
<qemu:arg value="-set"/>
<qemu:arg value="device.sata0-0-0.rotation_rate=1"/>
</qemu:commandline>
I am not 100% sure if this is just qemu issue, it could be libvirt and qemu
issue. Because libvirt packages were also updated along with this.
This is the error I get, when I try to start the guest OS:
Error starting domain: internal error: process exited while connecting to
monitor: qemu-system-x86_64: -set device.sata0-0-0.rotation_rate=1: there is no
device "sata0-0-0" defined
Um. I've no idea what you're taking about here.
You defined custom command-line option in libvirt xml file, which refers to
a certain device name assigned - most likely - by libvirt. After some changes
this name isn't there anymore. I'd say you should either name that device
explicitly instead of relying on libvirt to name it, or use some other way to
add the option you need.
To me it is a wrong usage, or wrong expectation.
More, I've no idea a hdd property can be set by using -set instead of adding
arguments to -device ide-hd (or equivalent) parameter. I don't know, but I'd
say this too is a wrong usage.
Closing this bugreport. If you still think it is a buggy behavour instead of
wrong usage, feel free to reopen it and provide information about why ou
think so.
Thanks,
/mjt
--- End Message ---
