Public bug reported:
I'm trying to disable FIPS from an Ubuntu Pro FIPS 18.04 image in AWS. I
updated to the latest ua client in the daily PPA. I have a prompt to
disable it but it fails:
ubuntu@ip-172-31-60-238:~$ sudo add-apt-repository ppa:canonical-server
/ua-client-daily
wrong project
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916773
Title:
ua disable fips doesn't work in ua client 27
To manage notifications about this bug go to:
** Tags added: cpe-onsite
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794307
Title:
docker login fails Cannot autolaunch D-Bus without X11
To manage notifications about this bug go to:
** Attachment added: "Screenshot"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893985/+attachment/5407094/+files/fips-azure-crash.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893985
Public bug reported:
In Azure, updating an instance to the latest Azure optimised fips-
updates kernel (4.15.0-2007-azure-fips) leaves the system in an
unbootable state.
The serial console shows the following and reboots:
Checking kernel image: /boot/vmlinuz-4.15.0-2007-azure-fips
Kernel
Yes this works as expected now.
Only the esm-apps service as an impact on the "are receiving/could
receive security updates with ESM Apps" statement now, and the message
changes as expected depending on if esm-apps is enabled or disabled.
Thank you.
--
You received this bug notification
** Attachment added: "Suggested flowchart of how the decision to reboot should
be when using livepatch"
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1747499/+attachment/5390197/+files/livepatch-flowchart-davecore-suggestion.png
--
You received this bug notification because
Thanks @brian-murray. However it doesn't look like it fixed it, it seems
to be even worse now. It doesn't tell me I am getting the security
updates when I have ESM-apps enabled:
ubuntu@ip-172-31-55-253:~$ bzr branch lp:~brian-murray/update-manager/u-s-s-new
ubuntu@ip-172-31-55-253:~$ cd
Here are some extra details about the status of livepatch when a kernel
upgrade is required.
I am running an 18.04 VM with an old 4.15.0-20-generic kernel from April
2018. Here is status in yaml format:
ubuntu@bioniclivepatcholdkernel:~$ canonical-livepatch status --format yaml
client-version:
Public bug reported:
It looks like ubuntu-security-status assumes that ESM Apps is enabled
when only ESM Infra is enabled.
There is no problem with ESM Apps and ubuntu-security-status. It's just
that it looks like ESM Infra gives a false positive about receiving the
updates.
Reproducer with an
Public bug reported:
Installing python3-distro-info on Ubuntu 16.04 breaks the ubuntu-
security-status script.
The script runs before I install python3-distro-info:
ubuntu@ip-172-31-14-142:~$ ./ubuntu-security-status --universe
473 packages installed on Ubuntu 16.04 LTS, of which:
2 packages
I just hit this issue with an Ubuntu 20.04 daily build. I noticed it
when I tried to split my Terminator shell. I used ibus-setup to change
the emoji shortcut to something else.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Corey, I'm sorry the deployment I had was in bionic only. Can you queue
it up on your side?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750384
Title:
Cannot Delete Recordset / Zone in ng_dns
I tested python-designate-dashboard version 6.0.0-0ubuntu1.2 from
bionic-proposed on Ubuntu 18.04.3 LTS and I confirm I can delete the DNS
zone successfully now.
ubuntu@juju-96d97f-22-lxd-14:~$ grep proposed /etc/apt/sources.list
deb http://archive.ubuntu.com/ubuntu/ bionic-proposed restricted
I just found out about this. I wanted to get rid of the screen tearing
that I observed on my Nitro AN515-53 laptop running Ubuntu 18.04.3 LTS
with NVIDIA GeForce GTX 1050 Mobile GPU.
I used https://askubuntu.com/a/020 and set nvidia_drm modeset=1 but
then my external monitors didn't work
subscribed ~field-medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750384
Title:
Cannot Delete Recordset / Zone in ng_dns panels
To manage notifications about this bug go to:
Subscribed ~field-medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853200
Title:
cpu features hle and rtm disabled for security are present in
/usr/share/libvirt/cpu_map.xml
To manage
** Description changed:
When trying to launch an instance in OpenStack Queens on Ubuntu 18.04
with the new kernels, this error happens:
Error: Failed to perform requested operation on instance "david", the
instance has an error status: Please try again later [Error: Exceeded
maximum
Public bug reported:
When trying to launch an instance in OpenStack Queens on Ubuntu 18.04
with the new kernels, this error happens:
Error: Failed to perform requested operation on instance "david", the
instance has an error status: Please try again later [Error: Exceeded
maximum number of
@darmadoo: The cloud-init package is baked into the cloud images that
MAAS uses to deploy instances. You have to wait for the next cloud image
that will contain this fixed cloud-init, or you can use the workaround
in my comment #16 to use a previous image in the meantime.
--
You received this
As an FYI, my workaround for this is to grab the squasfh file from
https://images.maas.io/ephemeral-v3/daily/bionic/amd64/20190930/ and
copy it over the file /var/lib/maas/boot-
resources/current/ubuntu/amd64/ga-18.04/bionic/daily/squashfs on my MAAS
nodes (assuming you deploy Ubuntu 18.04 with
We're seeing a new issue with cloud-init 19.2.36 failing with python
exception "Not all expected physical devices present ..." during bionic
image deployment from MAAS. The issue seems to happen when bonds are
used. Tagged this SRU with regression-update.
See
Tested packages from stein-proposed on ceph-mon units:
BEFORE:
root@juju-1101fd-18-lxd-0:~# ceph -s
cluster:
id: 832cb0a6-a3e7-11e9-bedc-00163e7eca36
health: HEALTH_WARN
Module 'crash' has failed dependency: invalid syntax (module.py,
line 48)
[...]
We're seeing this with ceph 13.2.6 on bionic with the stein cloud
archive
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835354
Title:
disco: ceph-mgr unable to load crash module under py3
To
subscribed ~field-medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835354
Title:
disco: ceph-mgr unable to load crash module under py3
To manage notifications about this bug go to:
Hi Corey, I don't have access to a Disco cloud to test. Can we still get
this fix in stein? This is a blocker for a customer deployment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826875
Title:
Hi Corey, I don't have access to a Disco cloud to test. Can we still get
this fix in stein? This is a blocker for a customer deployment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808951
Title:
Unsubscribed field-critical since there's a workaround to use package in
stein-proposed and fix seems to be on the way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826875
Title:
[stein]
I subscribed field-critical to this bug as this is affecting a customer
deployment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808951
Title:
python3 + Fedora + SSL + wsgi nova deployment, nova
I subscribed field-critical to this bug as this is affecting a customer
deployment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826875
Title:
[stein] 'Percona-XtraDB-Cluster prohibits use of DML
I also have verified that this fix works on bionic-stein, removing the
verification-stein-needed tag.
** Tags removed: verification-stein-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826875
I confirm the package in stein-proposed fixes the issue.
** Tags removed: verification-stein-needed
** Tags added: verification-stein-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808951
Public bug reported:
The InfiniBand configuration settings from the 4.15 linux-azure kernel
are not in the 4.18 linux-azure kernel.
This is a request to apply the same InfiniBand settings to the 4.18
linux-azure kernel.
The following settings are only in the 4.15 linux-azure kernel (tested
with
Public bug reported:
This is a request to enable CONFIG_NO_HZ_FULL=y in the linux-azure
kernels(currently 4.15 and 4.18) in order to increase NVME disks
performance.
The current CONFIG_NO_HZ configuration in linux-azure kernels is the
following (tested on 4.15.0-1037, 4.15.0-1039 and
Public bug reported:
Host changes have altered how the PCI GUID is presented to the guest and
the patches for PCI IDs in 4.15.0-1037 do not properly handle the new
condition.
Impact:
Instances with multiple GPUs are only seeing one.
Workaround:
4.15.0-1036 does not have this behavior.
@lazamarius1: Just to clarify, the fix is scheduled to go in the 4.15
kernel in Bionic which is the same kernel as the Xenial HWE kernel. So
there's no need to add anything to the Affects section. You will see a
new linux-hwe 4.15 kernel in xenial-proposed once this is ready to test.
Thanks!
--
[VERIFICATION BIONIC]
I can modprobe the mq-deadline, kyber and bfq schedulers but it looks
like doing a modprobe of the cfq and deadline schedulers doesn't list
them as choices in the available schedulers:
# uname -r
4.18.0-1009-azure
# modprobe bfq
# modprobe cfq-iosched
# modprobe
[VERIFICATION BIONIC]
On an Asus ROG STRIX B450-I motherboard with a Ryzen 7 1700 cpu:
$ diff lspci.before lspci.after
22c22
< 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models
00h-0fh) Data Fabric Device 18h Function 6
---
> 00:18.6 Host bridge: Advanced Micro
[VERIFICATION BIONIC]
On an Acer Aspire V5-561P laptop:
$ diff lspci.before lspci.after
13,14c13,14
< 01:00.0 Ethernet controller: Broadcom Limited NetXtreme BCM57786 Gigabit
Ethernet PCIe (rev 01)
< 01:00.1 SD Host controller: Broadcom Limited BCM57765/57785 SDXC/MMC Card
Reader (rev 01)
---
You can clone the ubuntu-xenial kernel:
git clone git://kernel.ubuntu.com/ubuntu/ubuntu-xenial.git
And then grep for the commit you're looking for. There's a few different
ways to do it, I do:
git log --oneline | grep "Expose SMT control init function"
--
You received this bug notification
@overlord: AFAIK, there is no simple reproducer test case for this
issue. The ideal testing scenario for a bug and fix like this one would
be for each user who reported this issue to use a test kernel with the
fix in their environment and report back if the issue still manifests or
not after some
Hi overlord. An easy way to check the updates included in released
kernels is to look at the "-changes" mailing list for your Ubuntu
release.
In this situation it would be https://lists.ubuntu.com/archives/xenial-
changes/
And you can find that new kernel here:
Public bug reported:
There was a previous request in bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671203 to limit
the IO scheduler to NOOP in linux-azure. The other schedulers were
turned off and NOOP was made the default.
However with new upstream releases, new schedulers where
I tested the systemd 229-4ubuntu21.11 package from xenial-proposed in
Ubuntu 16.04 in KVM and also confirm I cannot reproduce the issue with
this updated package:
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.5 LTS
Release:16.04
Hi Marcelo,
Maybe I'm doing something wrong but I still don't see the Mellanox
devices with this 4.18.0-1005 kernel from the CKT PPA:
ubuntu@lp1794477:~$ sudo add-apt-repository ppa:canonical-kernel-team/ppa
ubuntu@lp1794477:~$ sudo apt install linux-azure-edge
ubuntu@lp1794477:~$ sudo
bionic-tree/4.18.0-1004 with all the packages:
$ sudo dpkg -i
linux-modules-4.18.0-1004-azure_4.18.0-1004.4~18.04.1LP1794477_amd64.deb \
linux-modules-extra-4.18.0-1004-azure_4.18.0-1004.4~18.04.1LP1794477_amd64.deb
\
bionic-tree/4.18.0-1004:
ubuntu@lp1794477:~$ uname -a
Linux lp1794477 4.18.0-1004-azure #4~18.04.1 SMP Wed Nov 21 20:07:48 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@lp1794477:~$ dmesg | grep -i mella
[6.337786] mlx4_core: Mellanox ConnectX core driver v4.0-0
[6.374260]
4.18.0-1004:
ubuntu@lp1794477:~$ uname -a
Linux lp1794477 4.18.0-1004-azure #5~lp1794477 SMP Wed Nov 21 19:19:16 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@lp1794477:~$ dmesg | grep -i mella
[6.009608] mlx4_core: Mellanox ConnectX core driver v4.0-0
[6.045063] mlx4_ib_add: mlx4_ib:
4.18.0-1003:
ubuntu@lp1794477:~$ uname -a
Linux lp1794477 4.18.0-1003-azure #4~lp1794477 SMP Wed Nov 21 18:32:18 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@lp1794477:~$ dmesg | grep -i mella
[5.701478] mlx4_core: Mellanox ConnectX core driver v4.0-0
[5.732267] mlx4_ib_add: mlx4_ib:
4.18.0-1001:
ubuntu@lp1794477:~$ uname -a
Linux lp1794477 4.18.0-1001-azure #2~lp1794477 SMP Wed Nov 21 16:06:45 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@lp1794477:~$ dmesg | grep -i mella
[5.701988] mlx4_core: Mellanox ConnectX core driver v4.0-0
[5.730013] mlx4_ib_add: mlx4_ib:
4.18.0-1002:
ubuntu@lp1794477:~$ uname -a
Linux lp1794477 4.18.0-1002-azure #3~lp1794477 SMP Wed Nov 21 16:41:12 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@lp1794477:~$ dmesg | grep -i mella
[5.723350] mlx4_core: Mellanox ConnectX core driver v4.0-0
[5.751281] mlx4_ib_add: mlx4_ib:
I can see the Mellanox devices with that 4.17.0-1001-azure kernel.
I installed the new kernel:
sudo dpkg -i linux-
modules-4.17.0-1001-azure_4.17.0-1001.2~lp1794477_amd64.deb linux-
modules-extra-4.17.0-1001-azure_4.17.0-1001.2~lp1794477_amd64.deb linux-
These are the packages I see installed out of the box in the instance:
ubuntu@lp1794477:~/41701001$ dpkg -l | grep 4.15.0-1030.31 | sort
ii linux-azure-cloud-tools-4.15.0-1030 4.15.0-1030.31
amd64Linux kernel version specific cloud tools for version
Hi Joseph,
Is there a special way I should install these? I tried:
sudo dpkg -i *
But I get:
Selecting previously unselected package linux-azure-cloud-tools-4.17.0-1001.
(Reading database ... 56547 files and directories currently installed.)
Preparing to unpack
Hi Chris. I spoke to Joseph and I think we have everything we need to
start the bisect. We'll get started and keep you posted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794477
Title:
I can reproduce the issue in Azure with Ubuntu 18.04 and the kernel
linux-azure-edge 4.18.0.1004.5 from bionic-proposed.
I use an instance of type "Standard F4s_v2 (4 vcpus, 8 GB memory)"
I launch the instance and get the 4.15.0-1030-azure kernel:
$ lsb_release -a
No LSB modules are available.
I also noticed walinuxagent in Ubuntu 18.10 (cosmic) installed the
python3-distro dependency when upgrading the walinuxagent package (which
was expected).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I upgraded walinuxagent to version 2.2.32-0ubuntu1 (from -proposed) on 4
instances (trusty, xenial, bionic and cosmic). I rebooted the 4
instances and verified the serial console still works for each one. I
didn't run additional tests. Maybe the Azure team has more in-depth
automated tests they
Hi Eric,
I confirm with the sosreport in ppa:slashd/lp1775195 I no longer see the
passwords anymore:
# grep password
sosreport-xeniallandscape-20181114150420/etc/landscape/service.conf
password = []
password = []
store_password = []
I couldn't find any other issues with
Ran test in Xenial LXD container:
# dpkg -l | grep sosreport
ii sosreport3.6-1ubuntu0.16.04.1
amd64Set of tools to gather troubleshooting data from
a system
# apt-cache policy sosreport
sosreport:
Installed:
Public bug reported:
The new Minimal Ubuntu 18.10 image has iptables test failures in Azure
because iptables isn't present in the Minimal image.
This is a request to add a dependency to iptables in the walinuxagent
package.
** Affects: walinuxagent (Ubuntu)
Importance: Undecided
I have a user who confirms the 4.15.0-39 kernel fixes this issue:
# uname -a
Linux 4.15.0-39-generic #42~16.04.1-Ubuntu SMP Wed Oct 24 17:09:54
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
# cat /proc/fs/fscache/stats
FS-Cache statistics
Cookies: idx=2 dat=283731 spc=0
Objects: alc=278557 nal=0
I tested the package cloud-init 0.7.5-0ubuntu1.23 from trusty-proposed
and confirm it works as expected.
# TEST KEYS
$ cat googlekeys
test:ssh-rsa [...]+1LRl t...@example.com
ubuntu:ssh-rsa [...]+2LRl t...@example.com
cloudinit:ssh-rsa [...]+3LRl test
# CREATE THE INSTANCE
$
I tested the new package ubiquity 2.21.63.9 from xenial-proposed with
Ubuntu 16.04.3 and confirm the Cancel button on the select language
screen now reboots the system. I tested multiple times and ended up
doing a full real OEM install without any issues.
** Tags removed:
I tested friendly-recovery 0.2.31ubuntu2 in Xenial/16.04.3 LTS.
Selecting network Enable networking" from the Recovery Menu now enables
the network and DNS successfully. I can "cat /etc/resolv.conf" vs before
I couldn't. I don't see any issues with dependencies or asking for tty-
ask-password or
@Guillaume: I am Eric's colleague from comment #21. I was able to
reproduce the issue in Azure with your reproducer in comment #5. I'll
show Eric how I reproduced the issue and he'll be able to follow up with
you. Thanks!
--
You received this bug notification because you are a member of Ubuntu
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793430
Title:
Page leaking in cachefiles_read_backing_file while
Hi Guillaume, would it be possible to provide step-by-step instructions
to reproduce this issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796376
Title:
Bug #1739107 fix causes
Marking bug as Invalid since this looks like this might have been
related to the South Central US datacenter outage.
** Changed in: python3-stdlib-extensions (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Hi Ivan, the best way to engage Canonical Support to get assistance with
this issue will be to file a support case on support.canonical.com and
attach an sosreport of the affected system that is collected when the
issue happens. See my previous comment #5 for the details of sosreport.
Please check
There is a similar situation where apt-get wants to remove packages when
strict dependencies (equal version number) cannot be met. For example
dovecot-core/dovecot-pop3d/dovecot-imapd.
After installing Ubuntu 16.04.3 LTS from the ISO, install the 3 packages
from the release pocket:
$ sudo apt
I have confirmation that the kernel in -proposed fixes the issue in
xenial.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have confirmation that the kernel in -proposed fixes the issue in
xenial.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Ivan,
I launched an Hadoop HDInsight cluster in Azure and I see it runs on 6
nodes (2 head nodes and 4 worker nodes). Are those nodes the kind of
nodes that this issue is about? If so, is there a way I can have access
to those nodes or is it intentionally blocked for Azure users?
In any case,
Hi Ivan. I'll have to learn about HDInsight then. I was hoping to get a
list of steps I can follow to fast track the learning process. I'll see
what I can do this week. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Ivan. Can you post steps to reproduce this issue? Or at least steps
to get a similar environment running to get familiar with this bug? (for
those who are not familiar with HDInsight). Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Description changed:
+ [Impact]
+
Pressing Cancel during Ubuntu 16.04.3 Server installation after OEM
install and after running oem-config-prepare aborts the installation.
The behaviour is different from a regular Ubuntu 16.04.3 Server
installation (without OEM) where the option at
Public bug reported:
This request is to pull in the following patch for NVMe bug from
https://lore.kernel.org/patchwork/patch/974880/ in the linux-gcp kernel:
===
This patch adds full memory barrier into nvme_dbbuf_update_and_check_event
function to ensure that the shadow doorbell is written
Hi Hans. I'd like to be able to reproduce the issue. I tried booting an
Ubuntu 18.04 instance twice in Azure but I couldn't reproduce the issue.
Do you have an idea how I could reproduce this?
This type of error usually happens when your system can't find the
package in its APT sources. Is it
I have confirmation from a user who has done verification for this
kernel. Changing to verification-done-bionic.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Request to pull this patch from upstream into the next 4.15 kernel
update:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b2adf22fdfba85a6701c481faccdbbb3a418ccfc
This fixes a regression in SMB 2/3 reconnect detection. The fix has been
I have confirmation from a user running NFS stress tests on Xenial with
this kernel and has not seen any issues. Changed tag to verification-
done-xenial.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a
@Marcelo, I have a reply from Madhuri:
Created By: Madhuri Kaniganti (portal) (07/06/2018 11:40 AM)
Just these two fixes needed:
IB/mlx5: Respect new UMR capabilities
Marking bug as invalid as it looks like the root of the issue was with
the user's own module.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have confirmation from the user who reported this that they have
tested the new kernel 4.4.0-128.154 in their test environment for a 24
hours stress test and could not reproduce the issue. I changed the tag
to verification done.
** Tags removed: verification-needed-xenial
** Tags added:
Created By: David Coronel (28/05/2018 4:28 PM)
Good day Sam, Jamie,
The kernel 4.4.0-128-generic #154 is now ready for testing by Nvidia:
linux | 4.4.0-128.154 | xenial-proposed | source
linux-image-4.4.0-128-generic | 4.4.0-128.154 | xenial-proposed | amd64, arm64,
armhf, i386, ppc64el, s390x
I confirm the "toram" workaround from Woodrow allows me to PXE netboot
the most recent Ubuntu 18.04 Desktop amd64 ISO image.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755863
Title:
netbooting
@Khaled El Mously: It's more a feature request.
** No longer affects: qemu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771238
Title:
Not able to passthrough > 32 PCIe devices to a KVM Guest
To
I removed upstream QEMU from this bug pending further analysis and so we
can go through the right channels if this needs to go upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771238
Title:
** Changed in: qemu (Ubuntu)
Importance: High => Undecided
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771238
Title:
Not able to passthrough > 32 PCIe devices to a KVM Guest
To manage
** Changed in: qemu (Ubuntu)
Importance: Critical => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771238
Title:
Not able to passthrough > 32 PCIe devices to a KVM Guest
To manage
Public bug reported:
Using an Ubuntu Server 16.04-based host with KVM hypervisor installed,
we are unable to launch a vanilla Ubuntu Server 16.04.4 guest with >= 32
PCIe devices. It is 100% reproducible. Using fewer PCIe devices works
fine. We are using the vanilla kvm and qemu packages from the
** Changed in: qemu (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769053
Title:
Cannot start a guest with more than 1TB of RAM
To manage
@Tomasz: The d-i based install image is "the traditional installer found
on the alternative downloads page" as you can read from the Download
Ubuntu Server 18.04 page[1][2][3]:
Alternative Ubuntu Server installer
If you require advanced networking and storage features such as; LVM, RAID,
Netbooting Ubuntu Desktop is not a supported installation method for
Ubuntu. The only supported way to install Ubuntu via netboot is with the
Netboot images of Ubuntu[1]. More information in the Ubuntu
documentation[2].
[1] http://cdimage.ubuntu.com/netboot/
[2]
Subscribed Canonical Kernel Distro Team to this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763456
Title:
Disable nouveau driver in linux-azure kernel
To manage notifications about this
Public bug reported:
nouveau driver updates causing problems with other kernels with
provisioning on GPU instances in Azure.
This is a request to disable the nouveau driver from the linux-azure
kernel.
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
You
@Marcelo, Josh requested that these patches be backported to the 4.13
azure kernel:
"[...]Since 4.13 needs to be the default until the 26th, could we get
them added to the 4.13 kernel?"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Josh gave this answer to Marcello's question "Just to confirm. It's not
necessary to include these config changes to the 4.13 azure kernel in
xenial, correct?":
--> 'No, this is upcoming new hardware in Azure and I'd prefer to keep
new feature work in 4.15.'
--
You received this bug
I tested the test package for Xenial in ppa:dgadomski/ubiquity-lp1749289
and it gives me a choice instead of failing now. After pressing Cancel
on the first screen, I get:
Your system is not yet configured. Press 'a' to try again, 's' for a recovery
shell, or 'r' to reboot.
[asr]
I did an OEM
1 - 100 of 170 matches
Mail list logo
