then proceed with removing the zeroconf
Same problem with starting a QEMU based Win VM (GPU passthrough):
âchardev âspicevmcâ not supported without spice graphicsâ error received when attempting to start.
Downgrading to libvirt 1:8.3.0-1 (from 1:8.5.0-2) solves it.
Is there a permanent configuration/vm definition change I should apply - as this becomes a requirement?
boot with the working kernel, and run the mkinitcpio again. You can also press esc when it freezes at the logo to hopefully show some info.
sounds like you had filesystem corruption
I see this on my machine (some times):
Jul 17 18:18:03 systemd-udevd[680]: could not read from '/sys/module/acpi_cpufreq/initstate': No such device
opened 04:10AM - 01 Sep 21 UTC
udev
not-our-bug
kernel-bug
**systemd version the issue has been seen with**
> systemd-249.4-1.fc35.x86_64âŚ
**Used distribution**
> Fedora 35
**Linux kernel version used** (`uname -a`)
<!-- Make sure to enclose the pasted kernel version in `backticks`, so that
GitHub doesn't convert the `#` character typically included in it into a
reference to old GitHub issues. -->
> `Linux 5.14.0-60.fc35.x86_64 #1 SMP Mon Aug 30 16:45:32 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux`
**CPU architecture issue was seen on**
> x86_64
**Expected behaviour you didn't see**
> if it's not really a problem, then maybe it should be yellow text rather than red?
**Unexpected behaviour you saw**
> [ 2.923541] systemd-udevd[638]: could not read from '/sys/module/pcc_cpufreq/initstate': No such device
It's in red text so it's claiming this is urgent.
**Steps to reproduce the problem**
> boot
**Additional program output to the terminal or log subsystem illustrating the issue**
<!-- Please paste relevant program terminal or journal output here, ideally
when generated in debug mode (try setting the SYSTEMD_LOG_LEVEL=debug
environment variable). For very long copy/pasted data consider using a
service like https://gist.github.com/. Where copy/paste is not possible
(for example early boot or late shutdown), a photo of the screen might do
too, but text is always much preferred. -->
```text
âŚ
```
Thank you! I checked and the driver is intel_pstate.
Well, I donât know why but at this boot the error didnât show up. Hopefully, I wish it to remain like that without the error!
And yea, now I know to check cpu-freq, next time I would check if the frequency get stuck at one number when the error occurs!! For now am getting a variable cpu-frequencies.
So I guess this error may be related to cpu-driver/frequency issues!(correct me is am wrong!)
Something amd-pstate related then ^^
Yochanan
Split this topic
17 July 2022 18:22
122
I did the same, click on the 3 points and then on âRefresh databasesâ, and your system will be update.
Thanks @GaaSantAna
1 Like
Yochanan
Split this topic
18 July 2022 14:50
125
Good to know! I translate to âUpdate databaseâ because I use my system in Portuguese
1 Like