From: Victor Hooi <victorhooi@yahoo.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
PVE development discussion <pve-devel@pve.proxmox.com>
Subject: Re: [pve-devel] Proxmox 7.0 beta to 7.0-8 - Now unable to start VM - cgroup isn't numeric?
Date: Wed, 7 Jul 2021 21:34:48 +1000 [thread overview]
Message-ID: <CAMnnoULw81uCdqfE+PvPh-B2fD03OCsAYQ4xPn3MGu+-oADHFw@mail.gmail.com> (raw)
In-Reply-To: <42fc9647-e5f9-a3da-6ec4-92b1b8a1cc28@proxmox.com>
Gotcha - thanks for the quick fix!
I am using the pvetest repository.
Do you know roughly how long that will take to hit the repositories?
(I just did an apt update, and it doesn't seem to have picked up a new
qemu-server version yet).
On Wed, Jul 7, 2021 at 8:10 PM Thomas Lamprecht <t.lamprecht@proxmox.com>
wrote:
> Hi,
>
> On 07.07.21 11:44, Victor Hooi wrote:
> > I recently upgraded from the Proxmox 7.0 beta, to the latest 7.0-8
> release.
> >
> > However, when I try to start a Windows VM that I created before, I now
> get
> > the following error:
> >
> > Argument "cgroup v1: 1024, cgroup v2: 100" isn't numeric in numeric ge
> (>=)
> >> at /usr/share/perl5/PVE/QemuServer.pm line 5312.
> >> TASK ERROR: start failed: org.freedesktop.DBus.Error.InvalidArgs: Value
> >> specified in CPUWeight is out of range
> >
> >
> > Did something change between the beta and the release? Is there any way
> to
> > fix the above?
>
> A qemu-server version with a regression made it to the pvetest repository
> just
> a bit ago, fixed now with qemu-server 7.0-9 that super seeded it.
>
>
next prev parent reply other threads:[~2021-07-07 11:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMnnoUK8KCAANZfav37or8t0f-hBRi2w32QVsb1n4V=siMnE8g.ref@mail.gmail.com>
2021-07-07 9:44 ` Victor Hooi
2021-07-07 10:10 ` Thomas Lamprecht
2021-07-07 11:34 ` Victor Hooi [this message]
2021-07-07 12:37 ` Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMnnoULw81uCdqfE+PvPh-B2fD03OCsAYQ4xPn3MGu+-oADHFw@mail.gmail.com \
--to=victorhooi@yahoo.com \
--cc=pve-devel@lists.proxmox.com \
--cc=pve-devel@pve.proxmox.com \
--cc=t.lamprecht@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox