Hi John,
could you give it a try with the more recent virtualization stack in [1].
Since this might as well be in the kernel and not qemu/libvirt you might also
consider checking other kernel versions - not sure with your self-built driver,
but what kernels have you tried and which newer ones cou
Hi Vincent, there were various related issues and we need to be clear what is
fixed and what is open.
The one we have fixed here was only a less useful error message.
To check if - whatever exact case you hit - is fixed in a newer release
I recommend trying to upgrade (if you have a test system t
Hi Francisco,
I have re-checked but I don't see any other related code for your issue.
The PPA contains the one fix we know about.
I could think of old guests (that existed and were configured autostart before
the upgrade) to maybe stay in their odd state. But disabling and enabling
autostart fo
On Tue, May 11, 2021 at 1:35 AM Francisco Menchaca
<1921...@bugs.launchpad.net> wrote:
>
> Hi Christian,
>
> Thanks for your response.
>
> Do you mean disabling and enabling autostart to the old guests?
>
> In our dev lab worked straight away after installing the first PPA you
> bundled together, I
> @paelzer I updated the 'All open unclaimed MIR bugs' link on the MIR
> wiki page to show both NEW and CONFIRMED bugs, and I think we should be
> sure to include 'CONFIRMED' state bugs in our weekly review, not just
> 'NEW' state bugs.
Yeah I've got a notification about it.
I agree and thank you
FYI:
an update on the latest set of MPs
X:
https://code.launchpad.net/~chad.smith/ubuntu/+source/ubuntu-advantage-tools/+git/ubuntu-advantage-tools/+merge/402510
B:
https://code.launchpad.net/~chad.smith/ubuntu/+source/ubuntu-advantage-tools/+git/ubuntu-advantage-tools/+merge/402508
F:
https://c
I've seen similar issues due to e.g. a newer glibc (could be any other
program or even guest kernel) to use newer instructions and thereby
trigger an issue that exists in the emulation.
This usually ends in the need to bisect the host to identify a
(hopefully already existing) fix and then conside
** Changed in: node-jquery (Ubuntu Hirsute)
Status: Confirmed => Invalid
** Changed in: node-jquery (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/19
Per comment #1 + #24 libheif is ready - updating the state.
But the dependencies are not yet looked at in depth at all.
We will need to look for it, but first we need to make sure (likely but not
state explicitly yet) that someone wants to look after it.
I assume that foundations will own them, b
I don't know where/how but this was completed
libxcrypt | 1:2.4-1build1 | precise/universe | source
libxcrypt | 1:2.4-3ubuntu2 | trusty/universe | source
libxcrypt | 1:2.4-3.1 | xenial/universe | source
libxcrypt | 1:2.4-4| bionic/universe | source
libxcrypt |
Please make the change that pulls in ceph-iscsi and ensure you are
subscribed to the package to "own" it as the archive admins will
rightfully insist on that before promotion :-)
@Jamespage - I think this is up to you to push now right?
--
You received this bug notification because you are a mem
This was an ack and thereby ceph-iscsi this is ready as well
** Changed in: ceph-iscsi (Ubuntu)
Status: Confirmed => 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/1854362
Title:
This needs no further action after the former comment, marking it as
such
** Changed in: linux-signed-oem-osp1 (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: linux-oem-osp1 (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: linux-meta-oem-osp1 (Ubuntu)
Status: Co
This is ready, all it needs are the tasks mentioned in
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1852367/comments/2
to be resolved.
Other than that this would be ready for promotion to main.
** Changed in: mysql-8.0 (Ubuntu)
Status: Confirmed => Incomplete
--
You receiv
Old version fails:
root@h:~# apt install libvirt-dbus
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
libvirt-dbus
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 61.6 kB of
...
> And with that installation runs to completion. This is inside a 21.04
> amd64 desktop KVM virtual machine.
#1 The 21.04 environment fully works
#2 The 20.04 environment fails
#3 The qemu-of-21.04 in 20.04 environment fails
I'm not sure, but this makes me think of the kernel maybe bein
Hi Thiago,
the problem is that firewalld isn't in main and thereby not fully supported
which means that libvirt (that is in main) can not depend on it - see [1] for
some details.
Ubuntu's choice for this usually us UFW, but there is no UFW backend for
libvirt.
Being on iptables wasn't so much o
Since it was reported to have worked with former builds in Ubuntu I was
testing the former builds that were published in Hirsute.
https://launchpad.net/ubuntu/+source/qemu/1:5.2+dfsg-9ubuntu2 - failing
https://launchpad.net/ubuntu/+source/qemu/1:5.2+dfsg-9ubuntu1 - failing
https://launchpad.net/ub
FYI First regression tests LGTM, but the feature freeze on Hirsute is to
hard atm to push this right now.
Therefore this will likely be an early change in 21.10 and then SRUs for
Focal/Groovy/Hirsute.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
>From my test PPAs the version "1:5.2+dfsg-9ubuntu2~hirsuteppa3" which is
a no-change rebuild of the formerly working "1:5.2+dfsg-9ubuntu1" did in
three tries fail three times.
So we are not looking at anything that is in the qemu source or the
Ubuntu/Debian Delta applied to it. But at something
And finally after some fixups in the builders (thanks cjwatson!)
https://launchpad.net/ubuntu/+source/nss/2:3.55-1ubuntu3.1 also has built
riscv64.
All ready now
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Now the change was upstream applied and will be in v6.0.0
commit cdeaed27782835a875df7365d56d69dbe7250481
Author: Babu Moger
Date: Wed Mar 3 09:45:30 2021 -0600
i386: Add missing cpu feature bits in EPYC-Rome model
--
You received this bug notification because you are a member of Ubuntu
@Till - If I might ask to know where to expect it. What will be the
packaging (adding a dependency) or seed change that will make this show
up as component mismatch?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
> @Christian, I could add a Recommends to ipp-usb, to sane-backends, or we
> could add it to the ubuntu-desktop seed. I think sane-backends is the
> best place for the Recommends: as for scanning one would install sane-
> backends and the Recommends: would then complete the scanner driver set
> wit
The package has some tests that are meant to do iscsi root but can't be
executed fully automated.
With those one can try iscsi-root rather easy (not really easy, but better than
from scratch).
$ pull-lp-source open-iscsi
$ cd open-iscsi-2.1.3/
$ PATH=$PWD/debian/tests:$PATH
$ get-image hirsute.d
I see it now, thanks Till!
sane-airscan: sane-airscan
MIR: #1891682 (Confirmed)
[Reverse-Recommends: libsane1 (MAIN)]
Thereby moving this along to be ready for an Archive admin to promote.
** Changed in: sane-airscan (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug n
Before going into any rebuild-mania I wanted to further reduce how much builds
I'll need I've changed "qemu-system-misc" but kept the others like
"qemu-block-extra" and "qemu-system-common" - that mostly means
/usr/bin/qemu-system-riscv64 is replaced but all the roms and modules (can't
load the
Furthermore I've built (again the very same source) in groovy as
5.2+dfsg-9ubuntu2~groovyppa1 in the same PPA.
This build works as well in my tries.
So I have the same code as in "1:5.2+dfsg-9ubuntu1" three times now:
1. [1] => built 2021-03-23 in Hirsute => works
2. [2] => built 2021-04-12 in Hi
I've continued on one of the former approaches and started a full Ubuntu style
package build of the full source on arm64 in Groovy and Hirsute.
But it fell apart going out of space and I'm slowly getting hesitant to spend
more HW and time on this without
a) at least asking upstream if it is any kn
>From the error message this seems to be about concurrency:
qemu-system-riscv64: ../../util/qemu-coroutine-lock.c:57:
qemu_co_queue_wait_impl: Assertion `qemu_in_coroutine()' failed.
Aborted (core dumped)
42 void coroutine_fn qemu_co_queue_wait_impl(CoQueue *queue, QemuLockable
*lock)
43 {
4
There are two follow on changes to this code (in the not yet released qemu 6.0):
050de36b13 coroutine-lock: Reimplement CoRwlock to fix downgrade bug
2f6ef0393b coroutine-lock: Store the coroutine in the CoWaitRecord only once
They change how things are done, but are no known fixes to the curren
Also I've rebuilt the most recent master c1e90def01 about ~55 commits newer
than 6.0-rc2.
As in the experiments of Tommy I was unable to reproduce it there.
But with the data from the tests before it is very likely that this is more
likely an accident by having a slightly different timing than a f
Thanks for the answers Michael!
With Focal in my test environment I still see
Unexpected iSCSI Connection State, forcing iSCSI logout.
Logging out of session [sid: 1, target: tgt-boot-test-CgkE2Y, portal:
10.0.12.2,3260]
[ 1291.109263] sd-execu[1616]:
/usr/lib/systemd/system-shutdown/open-iscsi
** Also affects: open-iscsi (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: open-iscsi (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
** Description changed:
+ [Impact]
+
+ * The finalrd hook [1] of openiscsi runs iscsid which wants to
+check for users [2] of its IPC peers. That fails for issues
+with nss in that environment.
+
+ * The changes prep nss (libs) and if necesary fake a trivial
+/etc/passwd so that th
*** This bug is a duplicate of bug 1872527 ***
https://bugs.launchpad.net/bugs/1872527
Hi Dan,
this reminded me a lot about bug 1872527 and indeed it does when I tested it.
I tried the same stack of virtualization packages with non-K Ubuntu and there
isn't any issue.
So again it must be rela
Recent Bug 1922942 made me aware that this is again showing up in recent
versions.
Kubuntu 21.04 shows very similar symptoms, but non-KDE systems seem not
affected at all.
I was able to use it without any trouble on gnome based Ubuntus (Host and
Guest).
Does any of the involved/subscribed peopl
I agree that the CVEs will be needed.
But 103.2 also includes the next step in disabling safe browsing
=> https://blog.clamav.net/2020/06/the-future-of-clamav-safebrowsing.html
That might be ok as upstream can't provide the data anyway, but still worth to
think.
Also a bunch of other changes, bu
Source clamav -> hirsute/Proposed: current version 0.103.0+dfsg-3.1, new
version 0.103.2+dfsg-1
New changes:
clamav (0.103.2+dfsg-1) unstable; urgency=medium
* Import 0.103.2
- CVE-2021-1252 (Fix for Excel XLM parser infinite loop.)
- CVE-2021-1404 (Fix for PDF parser buffer over-read;
Reviewed as well, uploaded for Hirsute.
Once it completes there we can go for the SRUs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922976
Title:
iscsid fails to log out from target on shutdown
I finally got (temporary) hold of a EPYC 7713 which should work well for
this.
Initial detection is the same on Focal and Hirsute
EPYC-Rome
AMD
I'm glad you have 7713 and 7763 that is great for our joint testing.
I have to state that "my" 7713 have erms and are thereby happy to start
with the EPYC-Milan type.
fsrm I agree, that had to be disabled
Full CPU definition
EPYC-Milan
While that i
Upgrading to the experimental build for Focal
root@f:~# virsh domcapabilities | grep EPYC
EPYC-Milan
EPYC-Rome
EPYC-Milan
EPYC-IBPB
EPYC
EPYC-Milan
AMD
I haven't went into too much depth on this for this sniff test, but
migrations also didn't trigger issues for me into the new builds and back.
I tried a host-passthrough and a host-model migration, the latter was expanded
to (started on the old host):
EPYC-Rome
AMD
TL;DR
- I was able to confirm Markus test results
- results LGTM (other than a few hickups probably due to my special HW)
- a few questions to Markus (see below)
- With these positive resilts I'd already go on and combine this with
another SRU to prep merge proposals for F/G/H.
- Once ready and r
Hi Francisco,
I thought I had lost your activity on this case - glad to see you back on it.
Yeah the old PPA is gone - you fell victim to my bi-yearly PPA cleanup :-)
At some point I have to give launchpad all its gigabytes back ...
I rebased the branch (since it aged anyway) and have thrown a new
Hirsute done, sponsored as SRUs for Focal and Hirsute for review by the
SRU Team
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922976
Title:
iscsid fails to log out from target on shutdown
To mana
Awesome thanks for your answers Markus!
I've had a few backport questions (about potential side effects) that I
sorted out with Babu (thanks to him as well!).
With that all seems to be in place for another round of PPA updates to [1]
combining several changes tat are pre-sniffed SRUs and now bui
I've just dup'ed another new case onto this, maybe this will revive the
old case.
@KK if you happened to have found a solution/root-cause and thereby
didn't come back here this is the chance to update the case :-)
And while touching the case I just wanted to re-state that various problems in
thi
*** This bug is a duplicate of bug 1883614 ***
https://bugs.launchpad.net/bugs/1883614
Hi Luis,
I can derive from your info in [2] that you are on Xenial, so I'll mark that
for now.
Do you happen to know if it also occurs on other releases?
Two things will commonly be needed to get any furt
** Description changed:
+ [Impact]
+
+ * To avoid bugs with newer Hardware and to allow users/admins to control
+the KVM guests correctly we usually try to backport major CPU-
+detect/control features back to at least the last LTS (currently Focal)
+In SRU Terms this is under the se
** Also affects: qemu (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Groovy)
Impor
** Description changed:
[Impact]
- * To avoid bugs with newer Hardware and to allow users/admins to control
-the KVM guests correctly we usually try to backport major CPU-
-detect/control features back to at least the last LTS (currently Focal)
-In SRU Terms this is under the se
** Description changed:
- The EPYC-Rome model is missing the IBRS and SSBD flags due to an
- oversight
+ [Impact]
+
+ * IBRS was forgotten in the initial Rome type definitions.
+On one hand that makes the feature non exposed/controllable and on the
+other it can lead to crashes like bug
** Description changed:
+ [Impact]
+
+ * To avoid bugs with newer Hardware and to allow users/admins to control
+the KVM guests correctly we usually try to backport major CPU-
+detect/control features back to at least the last LTS (currently Focal)
+In SRU Terms this is under the sec
** Description changed:
[Impact]
- * To avoid bugs with newer Hardware and to allow users/admins to control
-the KVM guests correctly we usually try to backport major CPU-
-detect/control features back to at least the last LTS (currently Focal)
-In SRU Terms this is under the sec
Guest is Hirsute to have
libc6:s390x2.33-0ubuntu5 s390x
The following (not optimized for speed but readability) gives us a
simple environment-matrix for comparisons:
for r in xenial bionic focal groovy hirsute; do
uvt-simplestreams-libvirt --verbose sync --source
http://cloud-images.ub
Public bug reported:
Repro:
# Prep a backing disk
$ sudo fallocate -l 100M /tmp/zfsbase1
$ sudo fallocate -l 100M /tmp/zfsbase2
$ sudo zpool create zfsmirrortest mirror /tmp/zfsbase1 /tmp/zfsbase2
$ sudo zfs create -V 20M zfsmirrortest/vol1
$ cat > disk-zfs.xml << EOF
This even happens with the most common image-file backed disks which
further simplifies the repro:
$ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M
$ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc
$ virsh detach-disk h vdc
** Description changed:
Repro:
- # P
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1925211/+attachment/5490159/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925211
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1925211/+attachment/5490160/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925211
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1925211/+attachment/5490161/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925211
apport information
** Attachment added: "AudioDevicesInUse.txt"
https://bugs.launchpad.net/bugs/1925211/+attachment/5490158/+files/AudioDevicesInUse.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1925211/+attachment/5490162/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1925211/+attachment/5490163/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925211
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1925211/+attachment/5490164/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/192
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1925211/+attachment/5490165/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925211
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1925211/+attachment/5490167/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925211
Title:
Ho
apport information
** Attachment added: "SystemdDelta.txt"
https://bugs.launchpad.net/bugs/1925211/+attachment/5490166/+files/SystemdDelta.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925211
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1925211/+attachment/5490168/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug n
Hirsute - dmesg
# attach
[ 264.065866] crw_info : CRW reports slct=0, oflw=0, chn=1, rsc=3, anc=0,
erc=4, rsid=5
[ 264.065906] crw_info : CRW reports slct=0, oflw=0, chn=0, rsc=3, anc=0,
erc=4, rsid=0
[ 264.099347] virtio_blk virtio5: [vdc] 385 512-byte logical blocks (197
kB/193 KiB)
# detac
Hirsute - udevadm
# attach
KERNEL[319.020043] add /devices/css0/0.0.0005 (css)
KERNEL[319.020088] add /devices/css0/0.0.0005/0.0.0005 (ccw)
KERNEL[319.020103] bind /devices/css0/0.0.0005/0.0.0005 (ccw)
UDEV [319.022297] add /devices/css0/0.0.0005 (css)
UDEV [319.022802] add
FYI
[15:43] cpaelzer, this may be related
https://github.com/systemd/systemd/blob/4d484e14bb9864cef1d124885e625f33bf31e91c/NEWS#L5
And indeed it is an interesting read, but for now the question is why only with
5.11@s390x then? Maybe there is something small to get this back in line? No
one i
I was trying mainline builds [1] to pinpoint the kernel change (if any).
I had a few totally failing ones which stalled me a bit, but eventually I can
show
this helpful list:
v5.8 - working
v5.10 - working
v5.10.31 - working
v5.11 - failing
v5.11.15 - failing
v5.12-rc8 - failing
So it isn't a >5
Ok build env set up and tested the starting points.
>From that I also see:
v5.10 - working
v5.11 - failing
So from here I think I can try a bisect
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925211
commit 8cc0dcfdc1c0e0be107d0288f9c0cf1f4201be62
Author: Vineeth Vijayan
Date: Fri Nov 20 09:36:38 2020 +0100
s390/cio: remove pm support from ccw bus driver
As part of removing broken pm-support from s390 arch, remove
the pm callbacks from ccw-bus driver.The power-management fu
But it makes sense in regard to the broken use case and explains why we
see it only on s390x.
@sforshee - what should we do about it now that we know which commit it
was - just revert it asap or are there bad dependencies to it?
--
You received this bug notification because you are a member of U
Thanks Seth.
I have verified 5.11.0-16-generic #17+lp1925211v202104201520 from the PPA and
can confirm that the issue is gone.
=> The revert works as a fix \o/
For the severity/urgency at least we now know that it is s390x only (not "good"
but reduces the amount of affected people).
I'll later (
Thanks Frank for adding the mirror request to this, because either way
we sooner or later want a discussion with the s390x developers on this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925211
Tit
Hi Kaihenfeng,
Thanks for your patch suggestion! I'm semantically not sure it is the right
thing - to clarify your theory is that before it checked !resuming and before
had the check for !cdev maybe just to avoid a deference error. And now you
assume that instead of !cdev it should check if ther
I was wondering if I could trigger the same issue on an lpar as it would
raise the severity IMHO. I have no claim on completeness of these tests
in regard to all that could happen. I tried what I considered low
hanging fruits in regard to this cross check.
Pre-condition each time
- a dasd attache
I see two problems
#1
The new PPA is 4529 which seems to work in your output.
But you still have the old (deleted) one configured as well.
You'll probably want to clear that old one out:
$ sudo rm /etc/apt/sources.list.d/ci-train-ppa-service-4503-bionic.list
$ sudo apt update
(I have guessed the f
Hi Ivan,
thanks for the report and your help to make Ubuntu better.
I must admit I haven't seen this in all the time that 20.04 is out already.
I was checking logs of default installs of various Ubuntu versions but
that problem doesn't seem to happen by default.
> To me, more enduser than Ubuntu
*** This bug is a duplicate of bug 1912605 ***
https://bugs.launchpad.net/bugs/1912605
Hmm,
quite some issues around that for the short time 1:5.2+dfsg-9* is out.
It rang a bell and indeed this is just the new signature of the known bug
1912605
That in turn seems less a bug and more of a mis-
Hirsute seems also affected since 1:5.2+dfsg-9* with a slightly different, but
still same signature. I marked bug 1924991 as dup.
=> https://errors.ubuntu.com/problem/dd6db6d283c9912220e4f2c8218f9de08bd63cfb
** Also affects: qemu (Ubuntu Hirsute)
Importance: Undecided
Status: Fix Relea
Hi Pedro,
> Wouldn't it be beneficial for all guests to be shutdown before
unmounting all filesystems?
Yes on first sight that looks like a compelling suggestion.
But i've learned the hard way that usually adding dependencies eventually
breaks more things than it fixes - so let us first try to u
@Rascal - might I ask you which cpu type exactly you were using on your
old&new hosts?
In my case it was an (lscpu) "Xeon(R) Gold 6252" with microcode (dmesg)
"0x4003003, date = 2020-06-18".
It is not required, but could be useful later on or for other affected users to
know where the different
I was now able to get hold of a cascade lake chip (there are many types)
that was formerly already correctly recognized and working. In this case
I can confirm that the change didn't have any negative impact.
It was before&after:
Cascadelake-Server
Intel
> The lscpu output was added in the first two comments to this bug. These
> were 4114 and 4214 silver processors.
I didn't remember or read back all the former content :-/
Thanks for providing the answer before I asked :-)
For completeness here the `lscpu` and `cpuid -1` of my test system.
** At
As Frederick said (he did the change - thanks!) this is fixed for a while now.
In particular:
1401 qemu (1:4.2-2) unstable; urgency=medium
...
1406 [ Frédéric Bonnard ]
1407
NP, glad I could help.
Marking the bug as invalid then and best of luck with your VM!
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Old
ii libvirt-daemon-system 7.0.0-2ubuntu1 amd64Libvirt daemon
configuration files
ii qemu-system-x86 1:5.2+dfsg-9ubuntu2 amd64QEMU full system
emulation binaries (x86)
New
ii libvirt-daemon-system 7.0.0-2ubuntu2 amd64Libvirt daemon
configuration files
Old
ii libvirt-daemon-system 7.0.0-2ubuntu1 amd64Libvirt daemon
configuration files
ii qemu-system-x86 1:5.2+dfsg-9ubuntu2 amd64QEMU full system
emulation binaries (x86)
New
ii libvirt-daemon-system 7.0.0-2ubuntu2 amd64Libvirt daemon
configuration files
A few associated SRUs completed - now is the time.
This was uploaded to focal-unapproved for consideration by the SRU team.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922907
Title:
Unable to use
Thanks Lukasz!
Thereby Hirsute completed - now I've uploaded the (more usual SRUs) for Groovy
& Focal for review by the SRU Team.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921754
Title:
Add mi
Thanks Lukasz!
Thereby Hirsute completed - now I've uploaded the (more usual SRUs) for Groovy
& Focal for review by the SRU Team.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921880
Title:
Add EP
Hmmm,
indeed I remember doing a merge for 1.4 in
https://launchpad.net/ubuntu/+source/libvirt-dbus/1.4.0-1ubuntu1
I fail to remember to ahve synced it but the logs point at me :-/
Maybe when the FTFBS was fixed we thought that was all that was left ...
I beg your pardon, agree and will fix it aga
This would be re-applying the fix and should still work.
Same change as in the past (minus a typo).
Test PPA: https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/4533
For review please have a look at:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885
If we are on impish by the time we can upload then it would be
** Patch added: "libvirt-dbus-refix-1802005.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libvirt-dbus/+bug/1802005/+attachment/5491338/+files/libvirt-dbus-refix-1802005.debdiff
--
You received this bug notification because
This very much looks like
https://gitlab.com/libvirt/libvirt/-/commit/69977ff10560a80bcf5bf93f1a3f819a2d1623ca
We've seen this crash spike on the release of Ubuntu 21.04.
That probably are upgraders with a bad configuration that was always wrong but
now trigger this case.
It would hit
a) users
401 - 500 of 10728 matches
Mail list logo
