Public bug reported:
Description:
To support VM instances with >255 vCPUS, we need the patch set below
backported to the Azure 4.18 kernel. These patches include -
- New Hyper-V IOMMU driver. This driver will be Hyper-V specific.
- Minor update to the Hyper-V specific virtual PCI code. Need
Thanks All.
A newer Azure Agent which no longer touches cloud-init data is already
in the pipeline.
--
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/1803173
Title:
cloud-init disables use
** Tags removed: verification-needed-artful verification-needed-xenial
** Tags added: verification-done-artful verification-done-xenial
--
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/174305
FYI, we are looking for this in the default Xenial kernel as well.
There are some bare metal systems in use that wouldn't be able to use
the Azure kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
Hi,
The team has tested the kernel in comment #5 and confirmed that it
resolves the issue. Thanks!
BTW, we need this patch in Xenial as well since we are using the LTS.
Steve
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubu
I'll double check, but I don't think it's needed in linux-image-azure.
Do you have a link to the test kernel packages?
--
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/1743053
Title:
libat
No longs, this is an upstream fix from the vendor.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1743053
Title:
lib
Public bug reported:
Some SSD drives made by LiteOn can crash the kernel due to bad drivers.
A fix for this issue has been submitted upstream:
https://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git/commit/?h=for-4.15-fixes
LITEON EP1 has the same timeout issues as CX1 series devices.
Reve
Hi Joseph,
We've tested your previous Xenial test kernel from comment #5. Have
there been any changes that we need to test again, or can we test when
the kernel moves to proposed?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in U
Test case from comment #3 passed using the -proposed kernel for Xenial
and Yakkey.
** Tags removed: verification-needed-xenial verification-needed-yakkety
** Tags added: verification-done-xenial verification-done-yakkety
--
You received this bug notification because you are a member of Kernel
Pa
** Tags removed: verification-needed-xenial verification-needed-yakkety
** Tags added: verification-done-xenial verification-done-yakkety
--
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/1669
Hi,
The test looks good, here are my repro steps:
1) Create an Ubuntu 16.04 VM in Azure
2) Attach 128GB data disk
3) Partition and format the disk
# wipefs --all /dev/sdc
# sgdisk -Z /dev/sdc
# sgdisk -n '1:2048::264191' /dev/sdc
# mkfs.ext4 /dev/sdc1
Expected result: mkfs sho
Public bug reported:
Related bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657539
This issue was fixed in Zesty, but also impacts the Xenial and Yakkety
kernels. Can you please pull this patch back to Xenial+?
https://git.kernel.org/cgit/linux/kernel/git/axboe/linux-
block.git/commi
No logs needed. Thanks.
** Description changed:
There has been work upstream to enable encryption support for SMB3
- connections. This is particularly useful with the Azure Files feature as
- encryption is required to connected to an Azure Files storage share from
- on-prem or from a different
Public bug reported:
There has been work upstream to enable encryption support for SMB3
connections. This is particularly useful with the Azure Files feature as
encryption is required to connected to an Azure Files storage share from
on-prem or from a different region.
The relevant commits are as
Public bug reported:
When using Azure Files, a "Host is down" error can occur with the Linux
CIFS client when the client has been idle for an extended period of
time. Commit 4fcd1813e640 mostly resolved this issue and is already
integrated into the Xenial kernel.
The following additional patch i
It seems the Utopic kernel is impacted as well, I tested
3.16.0-62-generic released on 2/27. I thought that kernel was EOL. Can
we revert the fix here as well?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1551419
Title:
Fix UUID endianness patch breaks cloud-init on Azure
S
Public bug reported:
On Azure, cloud-init relies on the system-uuid as based by SMBIOS a
unique ID for a cloud instance. If this ID ever changes, then cloud-
init will attempt to reprovision the VM.
This recent kernel patch in the Ubuntu kernel corrects the endianness
for some SMBIOS fields, but
** Tags removed: verification-needed-trusty verification-needed-vivid
** Tags added: verification-done-trusty verification-done-vivid
--
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/1498206
KY has pushed a patch to LKML that resolves this issue:
https://lkml.org/lkml/2015/11/18/690
This patch needs to be applied to the Vivid kernel and beyond. This is
a critical patch, can you please take this patch as sauce for now so we
can get it out as quickly as possible?
--
You received this
HI Joseph,
Can we please raise the priority of this to get it into Trusty and Vivid
as soon as possible? We are seeing more repros of this issue on Azure.
Thanks,
Steve
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ht
No logs required.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1498206
Title:
Fix CPU lockup on Hyper-V/Azure
Sta
Public bug reported:
Description of problem:
Large sized VMs with 32 VCPUs and more than 100G memory sometimes hang at boot,
and the console keeps printing logs like "soft lockup - CPU#14 stuck for 23s!"
This particular issue can be resolved with the following patch upstream:
https://git.kernel
Testing complete, no issues found. Thanks!
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
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/1445195
Titl
Our team has tested the Vivid proposed kernel and found no regressions.
Performance is comparable to previous test kernels.
Thanks!
** Tags removed: verification-needed-vivid
** Tags added: verification-done-vivid
--
You received this bug notification because you are a member of Kernel
Package
Hi Joseph,
Do you know will these patches will be available in the next kernel
maintenance release?
Thanks!
Steve
--
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/1445195
Title:
[Hyper-V
@Joseph, I swear I thought I responded to this bug, sorry for the delay.
We have finished testing the Trusty kernel you posted at
http://kernel.ubuntu.com/~jsalisbury/lp1445195/trusty, and confirmed
performance is better.
Thanks!
Steve
--
You received this bug notification because you are a memb
We tested the Utopic kernel and it works fine now. No crashes or issues
and performance is better.
Thanks!
--
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/1445195
Title:
[Hyper-V] Kerne
We'll test this new kernel. It appears the directory
"/~jsalisbury/lp1445195/utopic" is empty, but it looks like the kernel
was placed in the "/~jsalisbury/lp1445195" directory instead. I assume
this is the correct kernel, but to be safe can you confirm?
Thanks!
Steve
--
You received this bug
Both these test kernels for Trusty and Utopic worked as well.
Thanks,
Steve
--
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/1463584
Title:
[Hyper-V] Add support for VMBus panic notifier
The test team has tested the Vivid kernel and confirmed that it works as
expected. So let's please ack these patches for the next Vivid kernel.
The Utopic kernel provided crashes at boot time, so we're unable to test
that. Can you help us debug that issue?
--
You received this bug notification
No logs required.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1463584
Title:
Add support for VMBus panic notifier
Test case on Hyper-V:
- Run: "echo c > /proc/sysrq-trigger"
- If the Panic Notifier code is present, an event 18590 should be logged.
--
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/1463
Public bug reported:
Please take these patches to our Hyper-V VMBus driver to enable kernel
crash notification:
Drivers: hv: vmbus: Add support for VMBus panic notifier handler
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/hv?id=96c1d0581d00f7abe033350edb021a9d94
Hi,
OK, sorry for the delay and misunderstanding. I tested linux-
image-3.2.0-80-generic from precise-proposed and confirmed that it also
has the patch and the issue is resolved.
Thanks again,
Steve
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
Hi,
I confirmed the fix in comment #4. Is there something I should click on
here to validate the fix?
Thanks,
Steve
--
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/1417313
Title:
[Hype
Hi Joseph,
We've tested this kernel and no longer see this issue. I think we are
OK to proceed.
Thanks!
Steve
--
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/1417313
Title:
[Hyper-V] v
Thanks for this, we will take this kernel and test. The issue is
intermittent and would likely only show up during stress tests, so it
may take a few days for results.
Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubun
Public bug reported:
This issue impacts Ubuntu 12.04.
Whenever a device is unregistered in vmbus_device_unregister
(drivers/hv/vmbus_drv.c), the device name in the log message may contain
garbage as the memory has already been freed by the time pr_info is
called. Log example:
[ 3149.170475] h
Public bug reported:
Please take these upstream patches for the Hyper-V VMBus driver. In
some cases we are seeing crashes due to these bugs on Hyper-V and Azure.
commit 72c6b71c245dac8f371167d97ef471b367d0b66b
Author: K. Y. Srinivasan
Date: Wed Aug 27 16:25:34 2014 -0700
Drivers: hv: vm
Hi,
The Azure test team has completed testing the proposed kernel package
for Trusty and verified that all fixes work as expected. Please mark
this as verification complete.
Thanks!
Steve
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Andy, thanks for taking these. All these changes passed our tests
except for TRIM.
It looks like we'll need to take a closer look at how to fix TRIM
upstream. We probably will not get that upstream before kernel freeze.
Do you think it be possible to re-base your original patch to re-enable
SPC-
Thanks Srikanth. These logs look typical of some of our stress tests.
Can you confirm that the other tests passed, including the new fix
upstream to enable unmap/trim?
Thanks,
Steve
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux i
44 matches
Mail list logo
