The seeding [1] of it is also quite clear on why it is still there.
"""
# This stack is no more very relevant, but was in the early days of internet
# dialin. This stack is a candidate for demotion, but OTOH received no
# bugs/CVEs over the last years and therefore can stay as-is for now.
# ppp
I hope the links and explanations added will help you in future uploads.
Even better, next time be available on IRC after the ping, but I understand
it might be rather late for you - so this isn't a complaint but a
recommendation.
The upload to noble should unblock you there, once you verified
For now https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.10-1ubuntu1 looks just as good as in my tests.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/2042902
Title:
I've created the merge of 1.2.10 by following [1], then re-added the patch
of Ethan and that of you Artur.
I hope I didn't add too many issues :-)
At least I'm sure I got this whole topic much forward.
The merge including all I mentioned can be seen here (As training material
for how this upload
I contacted Ethan who created the one patch I could not track down.
He had all the information that I needed:
- This is actually from
- https://github.com/alsa-project/alsa-ucm-conf/pull/321
- https://github.com/alsa-project/alsa-ucm-conf/pull/322
- related to private LP bug 2037058
- Not yet
Analyze for merge readiness:
The current delta is:
* d/p/0001-ucm2-Qualcomm-sc8280xp-fix-device-numbers.patch
* d/p/0001-acp63-add-initial-support-for-AMD-Pink-Sardine-ACP63.patch
* d/p/0002-acp63.conf-use-symbolic-link.patch
* d/p/0003-acp62-add-initial-support-for-AMD-ACP-v6.2-RPL.patch
=>
I got a ping on patch pilot duty, sadly on my ping back if they would be
available for questions if I find more that needs to be sorted out was
unanswered. So I need to carry all into this bug.
This is kind of a log of my own understanding process, feel free to ignore it:
Proposed change:
- It
@phil
As I said above for me it mostly was "I'm sure some change was expected, but so
much?".
It has various benefits as gladly outlined by Dimitri, fixing many
issues, but coming at a price tag.
Seeing how big the price tag is for small size, high density cases I
consider it potentially too
> it only gets activated when you install ksmtuned (which is not
installed by default).
No, installing qemu-system-... will also enable it.
So Seth gladly filed bug 2033565 to discuss and change this now or at least
towards 24.04.
--
You received this bug notification because you are a member
> @paelzer Are you happy to adjust your regression testing/metrics gathering to
> increase the
> memory required knowing that it was a conscious decision to switch kernel and
> incur the
> performance hit for the benefit of using a kernel with more support and less
> reported bugs?
I am.
In
IMHO: If it turns out unfixable, this at least needs to be a release
notes entry
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2032933
Title:
Mantic (23.10) minimal images increase in
One thing that came up when discussing with SMB as an obvious "uses mem
more in a kernel" are the structures needed per POSSIBLE cpu.
Comparing the system that I downgraded I found from [1]:
With the -kvm kernel before:
kernel: setup_percpu: NR_CPUS:64 nr_cpumask_bits:1 nr_cpu_ids:1
Checking kernels:
1. This already uses linux-image-virtual, it is not the even bigger
linux-image-generic.
2. The change of the image build sadly combined it all
a) new image build/seeding by CPC
b) different kernel type -kvm -> -virtual that uses generic
c) switch of kernel versions
We
>From the daily runs on images I can see that 6.2.0-1008 seems to be fixed in
>that regard.
It loses just as much as it formerly gained.
Since this arrived in lunar-updates/security should we close this bug?
--
You received this bug notification because you are a member of Kernel
Packages,
Mauricio is right in all he asks for, except most of them are "style"
which I'd recommend but not insist on.
$ dquilt rename -P 0001-arm64-support-more-than-one-crash-kernel-
regions.patch lp2024479-arm64-support-more-than-one-crash-kernel-
regions.patch
I thought it would be only refreshed, but
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2025984/+attachment/5683998/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2025984/+attachment/5683997/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2025984/+attachment/5683999/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2025984/+attachment/5684000/+files/acpidump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2025984/+attachment/5683995/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2025984/+attachment/5683996/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2025984/+attachment/5683994/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2025984/+attachment/5683993/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Hi,
we haven't even been able to strip off all the weight we gained with bug
2015867 and now I've found another change eating another ~13mb.
This time it might again be all intentional, and maybe even unchangeable.
But I'd like to file it so that you can consciously think
Seen the first lunar test with the fix.
Overall we now have:
- 859 mb (before) -> 984 mb (bug) -> 899 mb (fixed)
So there would be more to get back to the old sizes, but I've understood
that this seemed to be what can be done for now.
I'll update again to confirm once I see the change land in
Hi,
I was rechecking the numbers after a while as you called this fix released and
confirmed for some more cleanup in mantic. AFAIC even Lunar didn't improve.
To better see it I'll attach an image of daily metrics, it didn't
recover since my report on early April and Lunar as well as Mantic are
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2019040
Title:
linux-*: please enable dm-verity kconfigs to
Just picking on linux-headers for now it is more or less what I
expected.
It went 26 -> 107 mb and I see new directories for rust of:
81M
linux-headers-6.2.0-1003-kvm_6.2.0-1003.3_amd64.deb.extract/usr/src/linux-headers-6.2.0-1003-kvm/rust
228K
This isn't about the deb size, but about the size as extracted on the system.
Especially headers will most likely compress really well into the deb.
Comparing the latest 5.19 with the recent 6.2 [1][2] that got through propose
migration we can see the increase just fine. debsizes as downloaded
This is ran on daily images, the kernel versions are already listed above.
Hence no need to ran apport-collect for this issue.
Setting to "Confirmed"
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Public bug reported:
Hi,
in the regular monitoring of metrics there was a bump in disk size last week.
The default image once installed consumes now 994 (formerly 859) megabytes.
Looking at the consumers there was much noise, but the biggest change
was
linux-headers-5.19.0-1008-kvm 25197 ->
** Changed in: cloud-initramfs-tools (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lowlatency in Ubuntu.
https://bugs.launchpad.net/bugs/1967593
Title:
kernel
** Tags removed: update-excuse
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1985956
Title:
linux-libc-dev and libc6-dev do not agree who owns fsconfig_command
Status in glibc
Thanks for the ping Markus, let us know if you run into it again on another
system
e1000 as fallback is fine, but also slow IMHO.
So I hope you we can one day find what it was.
** Changed in: qemu (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you
Bionic was already reset for other reasons at the end of march this year.
Jammy was already reset for other reasons in January this year.
Kinetic was already reset for other reasons in May this year (and Lunar is
based on that).
Only Focal was left open and is now queued.
--
You received this
I was lost in old habits when providing MRs for hints, sorry.
This doesn't need hints to land, since it is broken in release due to external
changes a set of baseline runs with migration-reference/0 will work just as
much and be less effort.
Scheduling those now ...
P.S. That will unblock the
I prepared and linked a set of changes to hint the current version as badtest.
Please consider merging them as this version will be broken permanently until a
new upload will fix this issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Patch added: "suggested fix to apply in -dev and SRU so that tests will work
again"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1998184/+attachment/5633150/+files/0001-Fix-tests-to-be-compatible-to-jammy.patch
** Also affects: ubuntu-fan (Ubuntu Lunar)
Importance:
Public bug reported:
This breaks all ubuntu-fan autopkgtest since Jammy was released in April
2022.
Miriam found it while checking an autopkgtest regression in bug 1995260
Summary:
- the tests in test_local_lxd hardcode to "lts"
local series='lts'
- due to that we always test the latest
Some insight of the check on the history of this out of the many updates
on the upstream bug:
On master branch this was introduced via:
commit 159d8c274fd92438ca6d7068d7a5eeda157227f4
Author: Mika Westerberg
Date: Wed Jun 9 13:25:33 2021 +0300
ACPI: Pass the same capabilities to the _OSC
Hey,
the error message inside libvirt is from parsing PCI VPD Data.
If you say removing that card removes the message it seems to indicate that the
VPD of that device is either
a) broken as coming from the device and needs a FW Update (or report to Intel
to create one)
or
b) valid VPD data but
FYI: Adding libvirt here and marking it as update-excuse, so that the
to-be-expected FTBFS can be understood.
Once fixed in either package I can hit rebuild and move on through migration.
It built fine on a PPA overriding this problem in an ugly way and otherwise
than this build issue here works
Since this happens on build and not on a target system, I'll mark it
confirmed without providing the data that the Kernel bot asks for.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Also affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
** Tags
You can usually replicate that behavior by starting a few guests and
instead of shutdown stopping the libvirt-guests service.
If that works in your case as well it will easen having a look, so let
me ask does that work for you?
--
You received this bug notification because you are a member of
And something on arm64 already forces this, despite only being in -proposed.
For example if someone tries
linux-libc-dev (<5.19.0-1),
to avoid this FTBFS for now that works on all other architectures (right now),
but on arm64 gives me:
Missing build dependencies: linux-libc-dev (<= 5.19.0-1)
Public bug reported:
Right now in kinetic-proposed builds are failing due to both sets of
headers defining fsconfig_command.
(kinetic-amd64)root@Keschdeichel:/build/libvirt-LTnG76/libvirt-8.6.0/debian/build#
apt-cache policy libc6-dev linux-libc-dev
libc6-dev:
Installed: 2.36-0ubuntu1
Hi,
I have a system that recently shows (same kernel upgrade) the same issue.
I've also found [1] which I think the kernel team might want to participate and
track.
They seem to have identified a patch that potentially needs to be
reverted - at least to confirm it is what now causes this.
There
FYI
There was a request on IRC to also promote firmware-sof
Moving that here to have an auditable trail why things were changed - also I
guess we'd want to have an explicit ack by the kernel team that this is the
very same case.
>From #ubuntu-release
[11:53] ubuntu-archive: Please move the
Just stating (for my future self any anyone else) that for the other way
around (removing features that were never enabled before) there is code
that could handle that [1][2]. In a similar fashion libvirt could try to
consider older sources before this change as "ok I accept to not insist
on this
These were also backported into Focals kernel in:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893115
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895174
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895879
Therefore also fixed in Focal.
(and also fixes of those fixes
The identified fixes got merged in 5.9 and later.
So Impish and later are good.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi,
I'm coming by cleaning old open bugs to ensure nothing gets forgotten for too
long and or clutters the view to the remaining issues.
This case here - as Paride outlined almost two years ago - is already
covered and discussed in bug 1833586 . We won't/can't SRU it and there
was no further
Arr, this is a bad case :-/
First of all - yes Sven it is a regression. Somewhat relieved by having
a workaround, but not making it not a regression.
First of all I have to beg all your pardon for not seeing this earlier,
due to the bug tasks being closed most of the review passed that we have
For easier debugging this can be reproduced on any affected system
(Tried KVM and EC2) by just running:
$ sudo systemctl start hv-kvp-daemon.service
^^ This will stall while one would assume it should quick-exit due to
the ConditionVirtualization not being met.
A full cycle (90 second stall)
On a fresh AWS instance I already see it stalling on package install, I
do not even need to reboot :-/
ubuntu@ip-172-31-16-15:~$ sudo apt install linux-cloud-tools-common
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages
Public bug reported:
I see a boot stall on a normal qemu/libvirt based KVM guest using an almost
fresh cloud image a stall on boot:
While live on the console I see:
[ OK ] Reached target System Time Set.
[ OK ] Finished Load AppArmor pro…s managed internally by snapd.
[* ] A start job is
** Package changed: kvm (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967894
Title:
KVM IPI Virtualization support for SPR
Status in linux package in
This is actually fixed already in 5.13.0.39.44 as shown above, but the
root cause that I'm facing is that edge-Kernel is behind non -egde:
$ rmadison -a amd64 -u ubuntu linux-image-generic-hwe-20.04-edge | grep focal
linux-image-generic-hwe-20.04-edge | 5.13.0.27.29~20.04.13 | focal-security |
FYI for a different test I upgraded the system to Impish and on the
5.13.0-39-generic there neither of the two kernel bugs happens.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1966870
I tried things once more, this time OVS wasn't active at all (in the
former try it was active after boot and then disabled) - still failing.
Next I tried to use a different kernel(5.4.0-105-generic)
I don't know when in >5.4 this started to fail, it surely worked a few
months ago already using
As the last stage in the crash is in
? blk_mq_exit_hctx+0x160/0x160
I was looking if there was anything else with block devices going on.
I found another crash right at boot/init time (this one is also in the attached
currentDmesg.txt).
[ 537.566942] [ cut here ]
[
I have tried the same again, this time with openvswitch unconfigured (but still
running).
ubuntu@node-horsea:~$ sudo ovs-vsctl del-br ovsbr0
ubuntu@node-horsea:~$ sudo ovs-vsctl show
8dfc2067-7b9b-48d7-a50a-df17bbd3cb6c
ovs_version: "2.13.5"
chcpu disabling/enabling still crashes.
Ok, I have manually retried this - we do not need the KVM guest, it is the
chcpu that kills it.
Simplifying description ...
** Summary changed:
- Focal 20.04.4 crashing when using openvswitch/hugepages
+ Focal 20.04.4 crashing when using openvswitch and disabling CPUs
** Description changed:
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574134/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574141/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574136/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574145/+files/acpidump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574138/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574143/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574144/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574137/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574142/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574139/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574140/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574133/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1966870
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574135/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1966870
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574132/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574131/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1966870
Public bug reported:
Hi I'm facing the following crash now two times in a row while runnign the same
test - so somewhat reproducible it seems:
[ 1444.399448] BUG: kernel NULL pointer dereference, address: 0008
[ 1444.431172] #PF: supervisor write access in kernel mode
[ 1444.454715]
** Tags removed: server-todo
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1964093
Title:
nfsver=3,udp not working anymore
Status in linux package in Ubuntu:
Confirmed
Bug
** Bug watch added: Debian Bug tracker #900821
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900821
** Also affects: debian via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900821
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are
FYI: If you want/need a test - builds of the qemu that have that are in
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4753
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags added: intel-bug-december-2021
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1954473
Title:
KVM Shared Virtual Memory (SVM)
Status in linux package in Ubuntu:
Incomplete
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
** Tags added: intel-bug-december-2021
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1954465
Title:
KVM AIA User IPI
Status in linux package in Ubuntu:
Incomplete
Bug description:
** Tags added: intel-bug-december-2021
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1954468
Title:
KVM Architectural LBRs
Status in linux package in Ubuntu:
Incomplete
Bug
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
** Tags added: intel-bug-december-2021
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1954464
Title:
kvm SPR support for AMX
Status in linux package in Ubuntu:
Incomplete
Bug
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
** Tags added: intel-bug-december-2021
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1954472
Title:
KVM Scalable I/O Virtualization
Status in linux package in Ubuntu:
Incomplete
** Tags added: intel-bug-december-2021
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1954466
Title:
KVM Protection Keys for Supervisor Pages (PKS)
Status in linux package in Ubuntu:
** Tags added: intel-bug-december-2021
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1954474
Title:
KVM notify VM Exit
Status in linux package in Ubuntu:
Incomplete
Bug
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
*** This bug is a duplicate of bug 1952246 ***
https://bugs.launchpad.net/bugs/1952246
Hi Masato, I think I have re-discovered that with more detail in bug 1952246
Still waiting for the kernel team to look at.
** This bug has been marked a duplicate of bug 1952246
5.13 (I/J/F-HWE) Hosts
1 - 100 of 693 matches
Mail list logo
