Performing the verification on Jammy.
1) Unit test verification
First, making sure that we can reproduce the problem.
# apt policy qemu-system-x86
qemu-system-x86:
Installed: 1:6.2+dfsg-2ubuntu6.19
Candidate: 1:6.2+dfsg-2ubuntu6.19
Version table:
*** 1:6.2+dfsg-2ubuntu6.19 500
** Changed in: openldap (Ubuntu Jammy)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067745
Title:
New upstream microrelease 2.5.18
To manage notifications
** Description changed:
[ Impact ]
* MRE for the latest stable OpenLDAP 2.5.x release, 2.5.18.
This update includes bugfixes only following the SRU policy exception
defined at https://wiki.ubuntu.com/OpenLDAPUpdates.
[ Major Changes ]
* See the list of bugs fixed in this
untu Jammy)
Importance: Undecided
Assignee: Sergio Durigan Junior (sergiodj)
Status: Triaged
** Tags: needs-mre-backport
** Also affects: openldap (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: openldap (Ubuntu)
Status: New => Invalid
** Changed
Thank you for taking the time to file a bug report.
From DpkgTerminalLog.txt:
unable to create '/etc/ldap/ldap.conf.dpkg-new' (while processing
'./etc/ldap/ldap.conf'): Read-only file system
This indicates that there is another issue at play here. The root
filesystem seems to be read-only,
FWIW, I built QEMU with a proposed fix here:
https://launchpad.net/~sergiodj/+archive/ubuntu/qemu-9pfs-fix
It passes the testcase provided in the bug description. I'd still like
to hear Marc's opinion here as the Security team person, but at least we
have a possible fix.
Cheers,
--
You
Hi,
I took some time today to take a closer look into this issue. I wanted
to determine whether this was coming from something that we did, or some
upstream change. Here are my findings:
1) This is not architecture-specific. I can reproduce the problem
(thanks for the script, btw!) on s390x
** Changed in: postgresql-15 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067388
Title:
New upstream microreleases 12.19, 14.12, 15.7 and 16.3
To manage
** Description changed:
[ Impact ]
Some versions of Windows hang on reboot if their TSC value is greater
than 2^54. The calibration of the Hyper-V reference time overflows
and fails; as a result the processors' clock sources are out of sync.
[ Test Plan ]
As suggested by
** Description changed:
[ Impact ]
Some versions of Windows hang on reboot if their TSC value is greater
than 2^54. The calibration of the Hyper-V reference time overflows
and fails; as a result the processors' clock sources are out of sync.
[ Test Plan ]
As suggested by
** Changed in: qemu (Ubuntu Jammy)
Status: Incomplete => In Progress
** Changed in: qemu (Ubuntu)
Status: Incomplete => Invalid
** Changed in: qemu (Ubuntu)
Status: Invalid => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Description changed:
[ Impact ]
Some versions of Windows hang on reboot if their TSC value is greater
than 2^54. The calibration of the Hyper-V reference time overflows
and fails; as a result the processors' clock sources are out of sync.
[ Test Plan ]
- TBD.
+ As suggested
Hi Mauricio,
Apologies for taking long to reply. As you know, I've been busy with
other stuff.
Thank you very much for your considerations. It seems that I jumped the
gun on this SRU and uploaded without finishing the SRU text; sorry.
Also, I liked your suggestions for more testing. I was
Noble)
Status: New => Triaged
** Changed in: postgresql-16 (Ubuntu Noble)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
** No longer affects: postgresql-15 (Ubuntu Noble)
** No longer affects: postgresql-14 (Ubuntu Noble)
** No longer affects: postgresql-12 (Ubuntu Noble)
*** This bug is a duplicate of bug 1972076 ***
https://bugs.launchpad.net/bugs/1972076
Thank you for taking the time to file a bug report.
From DpkgTerminalLog.txt, we can see that the problem seems to come from
this operation:
Setting up python3 (3.10.6-1~22.04) ...
File
Thank you for taking the time to file a bug in Ubuntu.
I can confirm the problem. I did:
# dpkg-reconfigure locales
Chose ru_RU.UTF-8 as the default locale. Logged out and in again.
Then, I launched ruby3.2 and tried to paste a Russian character, like ю
or б. They're not properly handled by
** Changed in: tmux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066914
Title:
tmux 3.4 stalls during active pane zoom
To manage notifications about
** Changed in: postgresql-12 (Ubuntu Focal)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067388
Title:
New upstream microreleases 12.19, 14.12 and 15.7
To
** Description changed:
[Impact]
- * MRE for latest stable fixes of Postgres 12, 14, and 15 released on
+ * MRE for latest stable fixes of Postgres 12, 14, and 15 released on
May 2024.
[Test Case]
- * The Postgres MREs traditionally rely on the large set of autopkgtests
-to
Hello Rudolf,
Thank you for this bug report. Would you be able to provide a small
reproducer for the problem you're experiencing? This would make it much
easier for us to understand the issue and try to find a fix for it.
Also, since you appear comfortable dealing with source code, would you
I also noticed this:
Start-Date: 2024-05-24 17:16:19
Commandline: apt-get remove --purge postgresql-15
Requested-By: kartik (1000)
Purge: postgresql-15:amd64 (15.5-0ubuntu0.23.04.1), postgresql-contrib:amd64
(15+248), postgresql:amd64 (15+248)
End-Date: 2024-05-24 17:16:27
These version
** Merge proposal linked:
https://code.launchpad.net/~sergiodj/ubuntu/+source/postgresql-12/+git/postgresql-12/+merge/466514
** Merge proposal linked:
https://code.launchpad.net/~sergiodj/ubuntu/+source/postgresql-14/+git/postgresql-14/+merge/466515
** Merge proposal linked:
** Affects: postgresql-12 (Ubuntu Focal)
Importance: Undecided
Assignee: Sergio Durigan Junior (sergiodj)
Status: Triaged
** Affects: postgresql-14 (Ubuntu Jammy)
Importance: Undecided
Assignee: Sergio Durigan Junior (sergiodj)
Status: Triaged
** Affects: postgresql
Hello William,
You can find instructions on how to report a bug against a Debian
package here: https://www.debian.org/Bugs/Reporting
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065546
Thank you for reporting a bug.
I am going to add it to our backlog, but this is not not a priority for
the team, so it may take some time before the bug is fixed. Would you
like to drive this SRU yourself? That could make things faster.
Thanks!
** Changed in: libpam-radius-auth (Ubuntu)
Hi William,
The culprit for pulling in postfix when installing the set of packages
you mentioned in the description is Emacs. This is a side effect of a
change that I made when I last merged the last version from Debian, in
an attempt to reduce the delta and make it possible to eventually sync
Thanks for the reply, Simon.
I was about to say exactly the same thing. To the extent of my
knowledge, the issue has been (at least partially) addressed on LXD, so
it should be possible to launch VMs with more than 288 vCPUs with it.
Either way, this bug has been fixed in QEMU so I am going to
in: qemu (Ubuntu)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065579
Title:
[UBUNTU 22.04] OS guest boot issues on 9p filesys
Nothing to merge yet.
** Changed in: net-snmp (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064430
Title:
Merge net-snmp from Debian unstable for
We're ahead of Debian, so there's nothing to merge.
** Changed in: vsftpd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064478
Title:
Merge vsftpd from
Hi Linh,
Thanks for the bug report.
It's strange that you're noticing this discrepancy in behaviour between
minor QEMU versions. I just double checked and confirmed that there
were no changes to Depends/Recommends relationships between the versions
you mentioned.
I also launched a LXD
** Also affects: qemu (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=1975840
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064914
Title:
Hi again, Björn,
Could you please give the following PPA a try and tell me if the package
works?
https://launchpad.net/~sergiodj/+archive/ubuntu/qemu
The QEMU version there is 1:6.2+dfsg-2ubuntu6.20~ppa1.
Thanks a lot.
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
+ [ Impact ]
+
+ Some versions of Windows hang on reboot if their TSC value is greater
+ than 2^54. The calibration of the Hyper-V reference time overflows
+ and fails; as a result the processors' clock sources are out of sync.
+
+ [ Test Plan ]
+
+ TBD.
+
+ [ Where
it would be good to have reproduction steps for the bug,
we can also rely on your help to verify the correctness of the fix (as
Paride explained).
I'll work on prepare an upload for Jammy meanwhile.
Thanks.
** Changed in: qemu (Ubuntu Jammy)
Assignee: (unassigned) => Sergio Durigan Jun
Thank you, Simon.
I can also confirm that all autopkgtests passed. Therefore, marking
this bug as verified for Jammy.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a
** Changed in: vsftpd (Ubuntu)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064478
Title:
Merge vsftpd from Debian unsta
It's also worth noting that ifupdown is being slowly deprecated in
favour of more modern solutions, like networkd-dispatcher.
Having said that, I tried placing a test script inside /etc/networkd-
dispatcher/routable.d/, but it still doesn't work.
--
You received this bug notification because
Thanks for the bug report.
I am able to reproduce the problem. There are two things to consider
here:
1) ifupdown is not part of the default desktop image and as such it
needs to be installed anyway.
2) However, even after installing ifupdown, scripts under
/etc/network/if-up.d/ don't get
Sorry, forgot to comment something else.
In the "Test Plan" section of the SRU text, could you please expand it a
bit and also include an actual execution of the udev rule in question in
order to confirm that the systemd-udev error doesn't happen anymore? It
is generally not enough to just check
Thank you for the patches.
I uploaded the Focal changes after verifying that the bug is indeed
present there. Bionic is in ESM now so I decided not to touch it; IIRC
the changes will need to go through another process in this case.
--
You received this bug notification because you are a member
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064422
Title:
Merge libvirt from Debian unsta
** Changed in: qemu (Ubuntu)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064450
Title:
Merge qemu from Debian unsta
** Changed in: sssd (Ubuntu)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064469
Title:
Merge sssd from Debian unsta
** Changed in: openldap (Ubuntu)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064434
Title:
Merge openldap from Debian unsta
** Changed in: rsync (Ubuntu)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064457
Title:
Merge rsync from Debian unsta
Andreas and I spent some time this afternoon investigating this issue.
Here are our findings.
First, we noticed that the paths being reported by apparmor on dmesg
appear to be relative to /run. This is just an impression, though: I
believe that, for some reason, apparmor/systemd/something-else
Thank you for taking the time to file a bug report.
I installed the latest version of apache2 (Jammy) here and could not
reproduce the issue. Could you please provide a minimal reproducer so
that we can determine if this is indeed a problem with the package? If
you could, please provide the
Public bug reported:
Hi,
Telegraf was added in Ubuntu back in 2020 as part of the LMA (Logging,
Monitoring and Alert) effort, but priorities have changed since then and
the package is no longer maintained in the distribution. Telegraf is
also one of those "hard" packages to maintain because it
Doesn't https://bugs.launchpad.net/ubuntu/+source/dns-root-
data/+bug/2045297 already address this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061911
Title:
check if new addresses for
Hi Mauricio,
Thanks for the detailed explanations, as usual.
I took some time here to read your patch. It took me down the rabbit
hole and I did some archaeology to find out what these "inhibit*"
pointers are about. It was fun; I learned that they were introduced
back in 2012 as a means to
Still no further activity on the upstream bug, apparently.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2014964
Title:
kea does not manage exported shared library symbols visibility
To manage
This is not a bug in ssl-cert. It's a bug in libapache2-mod-auth-
mellon, more specifically in the way it configures openssl to generate
its certificate. From /usr/sbin/mellon_create_metadata:
cat >"$TEMPLATEFILE" < Triaged
** Changed in: ssl-cert (Ubuntu Jammy)
Status: Confirmed => Fix
Upstream fix:
https://github.com/latchset/mod_auth_mellon/commit/c6102de6ff651bf763400cb59202d9abe384f615
** Bug watch added: github.com/latchset/mod_auth_mellon/issues #105
https://github.com/latchset/mod_auth_mellon/issues/105
** Also affects: mod-auth-mellon via
** Changed in: squid (Ubuntu Jammy)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2040470
Title:
Upstream microrelease of squid 5.9
To manage notifications
Performing the verification on Jammy.
First, verifying that we can reproduce the problem.
# apt policy qemu-system-x86
qemu-system-x86:
Installed: 1:6.2+dfsg-2ubuntu6.18
Candidate: 1:6.2+dfsg-2ubuntu6.18
Version table:
*** 1:6.2+dfsg-2ubuntu6.18 500
500
Hello Dominic,
Thanks for reporting a bug.
Noble is currently in Feature Freeze, which means that only bug fixes
can be uploaded to the archive. Based on the release notes for version
2.13.1 of amavisd, there is at least one new feature being introduced in
this release, which makes it
Thank you for taking the time to file a bug report.
This sounds like a local configuration problem. If you believe this is
a bug in the package, could you please provide more technical details
about what is happening? Log files from Samba, for example, would help
with the diagnostic.
I see
libhx doesn't FTBFS on Noble. Closing this as Invalid.
** Changed in: libhx (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060826
Title:
hxtools ftbfs in
** Merge proposal linked:
https://code.launchpad.net/~sergiodj/ubuntu/+source/qemu/+git/qemu/+merge/464242
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061005
Title:
Merge qemu from Debian
I will use this bug to track the merge of 8.2.2.
QEMU 8.2.3 will be released after the planned Final Freeze, so it may
not be possible to merge it after all.
** Changed in: qemu (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Hello Giuseppe,
Thank you. I went ahead and backported the necessary patches. In
total, I had to backport the following upstream commits:
fb00aa61267c8b9c57a2d1a1fa1e336d02e3bcd1
d7c72735f618a7ee27ee109d8b1468193734606a
cca0a000d06f897411a8af4402e5d0522bbe450b
I uploaded a version of QEMU
Public bug reported:
QEMU 8.2.3 will be released on 2024-04-22. I will merge it into Noble.
** Affects: qemu (Ubuntu)
Importance: High
Assignee: Sergio Durigan Junior (sergiodj)
Status: New
** Tags: needs-merge upgrade-software-version
--
You received this bug
** Description changed:
This bug tracks the following MRE updates for the Squid package:
Jammy (22.04): 5.9
This update includes bugfixes following the SRU policy exception defined
at https://wiki.ubuntu.com/SquidUpdates.
[Upstream changes]
Thanks for the fix.
Uploaded to Focal.
** Changed in: numptyphysics (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: numptyphysics (Ubuntu Focal)
Assignee: (unassigned) => Sudip Mukherjee (sudipmuk)
--
You received this bug notification because you are a member of
Thank you for the patch.
Uploaded to Focal.
** Changed in: macutils (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: macutils (Ubuntu Focal)
Assignee: (unassigned) => Sudip Mukherjee (sudipmuk)
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
This bug tracks the following MRE updates for the Squid package:
Jammy (22.04): 5.9
This update includes bugfixes following the SRU policy exception defined
at https://wiki.ubuntu.com/SquidUpdates.
[Upstream changes]
** Description changed:
This bug tracks the following MRE updates for the Squid package:
Jammy (22.04): 5.9
This update includes bugfixes following the SRU policy exception defined
at https://wiki.ubuntu.com/SquidUpdates.
[Upstream changes]
** Merge proposal linked:
https://code.launchpad.net/~sergiodj/ubuntu/+source/squid/+git/squid/+merge/464045
** Changed in: squid (Ubuntu Jammy)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ah, got it. I've added "of squid" in the title now, should read better
on Pinot. Thanks!
** Summary changed:
- Upstream microrelease 5.9
+ Upstream microrelease of squid 5.9
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: qemu (Ubuntu)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2048517
Title:
EPYC-Rome mo
Hi Bryce,
I'm following the same title pattern as established by Athos, which I
think is better in this case. Just leaving the explanation here :-).
** Summary changed:
- Upstream microrelease of squid 5.9 for noble
+ Upstream microrelease 5.9
--
You received this bug notification because
"fix" here
is to adjust the local configuration, as mentioned in the comments
above.
I'm reverting this bug's state to Invalid, then.
** Changed in: dnsmasq (Ubuntu)
Assignee: Sergio Durigan Junior (sergiodj) => (unassigned)
--
You received this bug notification because you are a membe
Hello Jan,
Thank you for reporting this bug, and for providing a good initial
analysis of the problem.
Would you have access to a host with an EPYC-Rome CPU where you can run
some tests? This is something that needs to be done in order to proceed
here, especially if we indeed decide to SRU this
On Wednesday, April 03 2024, Andreas Hasenack wrote:
> It is enabled:
>
> Types: deb
> URIs: http://ports.ubuntu.com/ubuntu-ports
> Suites: noble noble-updates noble-backports noble-proposed
> Components: main universe restricted multiverse
> Signed-By:
On Wednesday, April 03 2024, Andreas Hasenack wrote:
> This is very hard to troubleshoot at the moment, because I just can't
> get the build-dependencies installed, either with noble or noble-
> proposed:
I think you need to enable noble-updates.
--
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0
** Also affects: squid (Ubuntu Jammy)
Importance: Undecided
Status: New
** No longer affects: squid (Ubuntu Noble)
** Changed in: squid (Ubuntu Jammy)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
** Tags added: server-todo
** Description changed:
- Backport sq
*** This bug is a duplicate of bug 2019003 ***
https://bugs.launchpad.net/bugs/2019003
Thank you for reporting a bug.
This is a duplicate of bug #2019003, so I marked it as such. Please
take a look at that other bug, there may be a workaround available for
this case.
Thanks.
** This bug
I was able to reproduce the bug on Focal, and since we seem to carry the
same version on Jammy/Mantic (and likely Noble), it's probable that the
bug also happens in those releases.
For future reference:
# apt install -y libvirt-daemon-system bind9 dnsmasq
Reboot, and try bringing up the
Mauricio asked me to review the debdiff for Focal as well.
This debdiff is different because he had to implement some code to
synchronize the destruction of the worker threads with the free'ing of
the thread pool.
I looked at the new code, analyzed it as best as I could, asked a few
questions to
After some more debugging/testing, it seems like the problem is indeed
caused by compiler optimization. More specifically, LTO. Disabling it
seems to have done the trick, and I can't reproduce the segmentation
fault anymore.
Basically:
ifeq ($(DEB_HOST_ARCH),ppc64el)
export
** Changed in: libvirt (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051754
Title:
Live migration fails (missing vmx features)
To manage
Thank you, Andreas.
I will wait for bug #2046439 to clear -proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2012763
Title:
qemu-system-amd64 max cpus is too low for latest processors
To
Performing the verification on Mantic.
First, verifying that we can reproduce the problem.
# apt policy qemu-system-x86
qemu-system-x86:
Installed: 1:8.0.4+dfsg-1ubuntu3.23.10.3
Candidate: 1:8.0.4+dfsg-1ubuntu3.23.10.3
Version table:
*** 1:8.0.4+dfsg-1ubuntu3.23.10.3 500
500
OK, I tested the fixed package from your PPA and verified that it indeed
solves the issue.
Just to reiterate, then: LGTM, +1!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059272
Title:
libvirt
Hah, I didn't see your comment before I posted mine. Mid air conflict!
Anyway, thanks for providing the PPA. I'll take it for a spin :-).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059272
Mauricio,
Wow! Such an awesome reproducer. Very detailed and easy to follow.
Thanks for providing it.
I was able to verify the problem here, and looked at the upstream
patch[1] that fixes it. The rationale makes sense to me, although that
cleanup function is pretty involved and it's hard to
Fixed package uploaded to Mantic:
qemu_8.0.4+dfsg-1ubuntu3.23.10.5_source.changes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2012763
Title:
qemu-system-amd64 max cpus is too low for latest
Performing the verification on Mantic.
First, reproduce the problem.
# apt policy qemu-system-x86
qemu-system-x86:
Installed: 1:8.0.4+dfsg-1ubuntu3.23.10.3
Candidate: 1:8.0.4+dfsg-1ubuntu3.23.10.3
Version table:
*** 1:8.0.4+dfsg-1ubuntu3.23.10.3 500
500
** Changed in: qemu (Ubuntu Jammy)
Status: New => In Progress
** Changed in: qemu (Ubuntu Mantic)
Status: Confirmed => In Progress
** Changed in: qemu (Ubuntu Noble)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
On Wednesday, March 20 2024, Andreas Hasenack wrote:
> Public bug reported:
>
> sssd is currently failing to build on armhf due to build-time test
> failures[1]¨:
Without having checked anything: is this not related to the time_t
transition? The build was passing before.
I'll check more
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2012763
Title:
qemu-system-amd64 max cpus is too low for latest processors
To manage notifications about this bug go to:
Hi Jeff,
Thanks for the offer. Actually there is!
- If you could test Noble and double/triple check that we don't need to
do anything else there in order to support maxcpus, that'd be great.
Just use the "ubuntu" machine type and check if QEMU starts correct with
more than 288 vCPUs.
- Once
** Description changed:
[ Impact ]
- QEMU users on Ubuntu Jammy who try to spawn a VM with more than 288
- vCPUs will not be able to do so, because the machine types available
+ QEMU users on Ubuntu Jammy/Mantic who try to spawn a VM with more than
+ 288 vCPUs will not be able to do so,
** Description changed:
+ [ Impact ]
+
+ QEMU users on Ubuntu Jammy who try to spawn a VM with more than 288
+ vCPUs will not be able to do so, because the machine types available
+ don't support such scenario. The following error will happen:
+
+ qemu-system-x86_64: Invalid SMP CPUs 300. The
Thanks, Guilherme.
I found:
https://salsa.debian.org/utopia-
team/polkit/-/commit/81c21cdadbe0a98ca016738b8c2cc7d4f225f067
and then:
https://salsa.debian.org/libvirt-
team/libvirt/-/commit/b9b2923abfae8ec80507bc267767db4b51fb4021
which explain why we're depending on polkitd. So yeah, I
Kudos to gpiccoli for finding the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058278
Title:
[Backport] libvirt-daemon-system won't install on Focal
To manage notifications about this bug
Public bug reported:
When installing libvirt-daemon-system (from
https://launchpad.net/~canonical-server/+archive/ubuntu/server-
backports) on a Focal system, one will see the following error:
# apt install libvirt-daemon-system
Reading package lists... Done
Building dependency tree
Hello and thanks for reporting a bug.
You shouldn't need to manually chown /dev/kvm. On a fresh Ubuntu Jammy
install, I see:
# ls -la /dev/kvm
crw-rw 1 root kvm 10, 232 Mar 7 19:41 /dev/kvm
After installing qemu and virt-manager, I still see the proper
permissions/ownership, as expected.
Hi Ross,
Thanks for the feedback. It's a strange situation, indeed. And I have
to say that I cannot reproduce the issue here even after forcing qemu to
use pc-i440fx-{mantic,jammy}, which is what happens when you don't
specify type=q35. The VM boots without issues. Of course, the first
time
1 - 100 of 1002 matches
Mail list logo
