I installed and tested the 5.8.0-1034-azure kernel and it worked as
expected.
I created a Ubuntu 20.04 VM and installed the “5.8.0-1034” kernel this way:
1. Enable the “proposed” kernel by running the below as “root” (refer to
https://wiki.ubuntu.com/Testing/EnableProposed):
cat
Public bug reported:
Hi,
I'm debugging an iptables-restore failure, which happens about 5% of the
time when I keep stopping and starting the Linux VM. The VM has only 1
CPU, and kernel version is 4.15.0-1098-azure, but I suspect the issue may
also exist in the mainline Linux kernel.
When the fail
I reported the issue to the mailing list:
https://lwn.net/ml/linux-kernel/MW2PR2101MB0892FC0F67BD25661CDCE149BF529%40MW2PR2101MB0892.namprd21.prod.outlook.com/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Thanks, Marcelo! I tested all the 3 kernels and they worked as we
expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902531
Title:
[linux-azure] IP forwarding issue in netvsc
To manage notifi
Hyper-V team just identified a bug where the Hyper-V hypervisor can
truncate the host SYSENTER_ESP/EIP to 16 bits on VMexit for some reason.
A further investigation is ongoing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
VM Exit is a term in the Intel CPU's Virtualization support (VMX). It
means the execution of the guest CPU is interrupted and the execution
"jumps" to some function in the hypervisor; the hypervisor analyzes the
reason of the VM Exit, and handles the VM exit properly, and then the
execution "jumps"
VM exits are pretty frequent and normal. "VM exits occur in response to certain
instructions and events in VMX non-root operation" (see CHAPTER 27
VM EXITS of
https://software.intel.com/content/www/us/en/develop/download/intel-64-and-ia-32-architectures-sdm-volume-3c-system-programming-guide-part
Sure, will do. But AFAICT, there is no ETA yet. Even if the fix was made
today, it would take quite some time (at least a few months?) to deploy
the fix to the whole Azure fleet. :-(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
@mhcerri
I only tested Gen1 VM (4.13.0-1004-azure-edge) on my local Hyper-V host (WS
2016), and couldn't repro the issue, i.e. reloading hv_netvsc and changing MTU
worked fine.
As I understand, I think the bug was originally reported against
4.13.0-1001.1 (I did not test this version). That's
@mhcerri
I'm using
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/, e.g.
for 4.13.0-1004-azure-edge, I mean:
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/commit/?h=azure-edge-next&id=21d8a99f88af972684618521cf19adafe24dc566.
Please let me know i
@mhcerri
FYI: I'm not using any kernel from http://kernel.ubuntu.com/~mhcerri/azure/.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1735546
Title:
[hyper-v] reloading netvsc issue on linux-azure 4.1
@mhcerri
Thanks for the explanation! I built the kernels directly from the git repo and
I didn't use the binary packages (I thought they should be the same). What's
your repro-rate? Yesterday as Chris tested linux-azure-edge 4.13.0-1004.4 + my
pull request, the repro rate was only ~1%, meaning
The fix is in the PCI tree now:
"PCI: hv: Fix hibernation in case interrupts are not re-create" (
https://git.kernel.org/pub/scm/linux/kernel/git/lpieralisi/pci.git/commit/?h=pci/hv&id=915cff7f38c5e4d47f187f8049245afc2cb3e503
)
--
You received this bug notification because you are a member of U
The fix is in the mainline kernel now:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=19873eec7e13fda140a0ebc75d6664e57c00bfb1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
rcu_access_pointer(sk->sk_filter) is basically the same as
sk->sk_filter.
If sk->sk_filter is true, the change makes no difference.
If sk->sk_filter is false, the change also drops a UDP packet with incorrect
UDP checksum by "goto csum_error;". Without the change, the packet is dropped
in udp_re
https://lore.kernel.org/netdev/20200728015505.37830-1-de...@microsoft.com/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888715
Title:
UDP data corruption caused by buggy udp_recvmsg() ->
skb_cop
Unluckily this commit breaks hibernation:
0a14dbaa0736 ("video: hyperv_fb: Fix hibernation for the deferred IO feature"):
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/+git/focal/commit/?h=Ubuntu-azure-5.4.0-1022.22&id=0a14dbaa0736a6021c02e74d42cf3a7ca5438da6
We should inc
Unluckily this commit breaks hibernation:
0a14dbaa0736 ("video: hyperv_fb: Fix hibernation for the deferred IO feature"):
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/+git/focal/commit/?h=Ubuntu-azure-5.4.0-1022.22&id=0a14dbaa0736a6021c02e74d42cf3a7ca5438da6
The kernel he
To reproduce the issue, I created a Ubuntu 20.04 VM on Azure (the kernel
version was "5.4.0-1022-azure #22-Ubuntu"), and I ran "echo disk >
/sys/power/state" in the VM and then checked the Azure serial console of
the VM and found the warning in commen #8 and suspending couldn't finish
normally (it
Hi Marcelo, yes, please revert
0a14dbaa0736 ("video: hyperv_fb: Fix hibernation for the deferred IO feature").
No other change is needed.
In the future, when a4ddb11d297e is included, 0a14dbaa0736 should also
be included.
--
You received this bug notification because you are a member of Ubuntu
Detailed steps to repro the issueo on Azure:
1. Create a VM with the image "Ubuntu Server 20.04 LTS - Gen1". Any VM size
should be fine. Here I use "Standard E4-2ds_v4 (2 vcpus, 32 GiB memory)".
2. Add an extra disk of 64GB to the VM via Azure portal.
3. Login the VM via ssh and check the kernel
FYI: the fix is in the upstream linux-4.4.y branch now:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v4.4.233&id=c514bb4147e2c667cf82f9aa7689cf442078c13f
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Since the 5.0 linux-azure kernel is not maintained anymore, IMO we don't
have to fix this bug for it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902531
Title:
[linux-azure] IP forwarding issue i
I'll provide the instructions to reproduce the bug on Azure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902531
Title:
[linux-azure] IP forwarding issue in netvsc
To manage notifications about t
Here is how I reproduce the bug:
Create 3 Ubuntu 16.04 VMs (VM-1, VM gateway, VM-2) on Azure in the same
Resource Group. The kernel should be the linux-azure kernel
4.15.0-1098.109~16.04.1 (or newer). I use Gen1 VM but Gen2 should also
has the same issue; I use the "East US 2" region, but the iss
To use Azure UDR, I referred to this page:
https://campus.barracuda.com/product/cloudgenfirewall/doc/72516173/how-
to-configure-azure-route-tables-udr-using-azure-portal-and-arm/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
This is the network config. Let me know if you need more info.
** Attachment added: "network-config.png"
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1902531/+attachment/5430820/+files/network-config.png
--
You received this bug notification because you are a member of Ubuntu
B
There is another important bug fix for hibernation:
net/mlx5: Fix crash upon suspend/resume
(https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=8fc3e29be9248048f449793502c15af329f35c6e).
So far the fix is only present in the net.git tree, but I expect it will
be in the mai
FYI: the patch "net/mlx5: Fix crash upon suspend/resume" is in v5.7 now
(i.e. today's latest mainline):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.7&id=8fc3e29be9248048f449793502c15af329f35c6e
--
You received this bug notification because you are a member of U
@Joshph, "the test kernel in #25" means the #4 in the link of #25,
i.e. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667007/comments/4
It looks to me the patch is not included. Just want to confirm my guess.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
@Joshph
Can you please confirm the patch
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665097/comments/4) is
included in the test kernel in #25?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Thanks, Joseph!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1650058
Title:
[Hyper-V/Azure] Please include Mellanox OFED drivers in Azure kernel
and image
To manage notifications about this bug
I created a new pull request against the master-next branch
(709d133bc3132eac96e455b9c94b8c5b78479393, Ubuntu-azure-4.11.0-1006.6)
of https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-
azure/log/?h=master-next:
https://github.com/dcui/linux/compare/709d133bc3132eac96e455b9c94b8c5b78
@mhcerri: I believe the hypercalls are documented in "Hypervisor Top
Level Functional Specification v5.0b.pdf" (https://docs.microsoft.com
/en-us/virtualization/hyper-v-on-windows/reference/tlfs).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
We actually only need one patch here. I have posted it to LKML:
https://patchwork.kernel.org/patch/9995011/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721576
Title:
[Hyper-V] hvsock: add proper
However, when I look at the 4.11 ubuntu-azure kernel
(https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-
azure/log/?h=master-next), I think we need to pull more related vmbus
patches from the mainline, because there are already non-trivial
differences.
Since we're moving to 4.13 (ht
I read through the long bug log and found an interesting thing:
In #36, Andrey Vertexx (vertexx) reported the issue was fixed by the
kernel in #30, but later Andrey thought the same kernel couldn't work
any more?
In #47, #48, #54, #59 a lot of people , Aleksey (noirfry) , Khallaf
(mkhallaf), E
@fastlanejb are you on Windows Server 2012 R2 or 2016? Is your VM
running some I/O intensive workload when the live backup happens? It
looks you get the OOM issue every time you do the live backup? I'm
digging into the issue, and trying to reproduce it first.
--
You received this bug notification
Let me add 2 more symptoms:
1) dockerd can exit due to SIGSEGV. The issue does NOT always happen:
after such a failure, sometimes a retry can succeed.
# systemctl start docker; systemctl status docker
Job for docker.service failed because a fatal signal was delivered to the
control process. See
BTW, issue #2 in the last comment doesn't always happen either.
Sometimes a retry would succeed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1719045
Title:
[Hyper-V] Docker failures with linux-azu
I got the issue (comment #4) with Standard_D16_v3 (16 vcpus, 64GB
memory).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1719045
Title:
[Hyper-V] Docker failures with linux-azure 4.11.0-1011
To man
Yes, I confirm this is the patch we need for the Enhanced Session mode.
The patch was originally made to fix a different issue, but it can also
fix the VM panic we see with Enhanced Session mode, because the cause is
the same: there is a race
static int __init hvs_init(void)
{
int ret;
BTW, I tested "modprobe -r hv_netvsc; modprobe hv_netvsc" and "ip link
set dev eth0 mtu 3000; ip link set dev eth0 mtu 4500" with 4.13.0-1004
-azure-edge on WS 2016 (Version 1607, OS build 14393:1943).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
I can't reproduce the issue with 4.13.0-1004-azure-edge
(https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-
azure/commit/?h=azure-edge-
next&id=21d8a99f88af972684618521cf19adafe24dc566)
It looks this bug has been fixed by some patch between linux-azure
4.13.0-1001.1 and 4.13.0-1004-
Public bug reported:
Ubuntu-azure-edge-4.13.0-1005.5 (https://git.launchpad.net/~canonical-
kernel/ubuntu/+source/linux-azure/tag/?h=azure-edge-next&id=Ubuntu-
azure-edge-4.13.0-1005.5) has some bugs:
1) After "Disable and re-Enable the Integration Services devices (Time
Sync, Hearbeat, Shutdown,
BTW, the 19 commits in the pull request is on this branch:
https://github.com/dcui/linux/commits/decui/azure-edge-next-Ubuntu-azure-edge-4.13.0-1005.5-20171204
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
To resolve the above 3 issues, I created this pull request based on
Ubuntu-azure-edge-4.13.0-1005.5 (https://git.launchpad.net/~canonical-
kernel/ubuntu/+source/linux-azure/commit/?h=azure-edge-
next&id=ec62f77bbe0697ce128f71fac4fc45c99b6f40d1).
The pull request is hosted in my own git repo:
https
@leann Actually I'm not sure if the pull request in bug 1736283 can fix
this bug. It looks 4.13.0-1004-azure-edge has already fixed this bug
somehow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17355
Is this a 100% repro? If yes, can you check if adding the "nopti" kernel
parameter can fix the issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745169
Title:
Kernel tried to execute NX-protecte
I happened to see this bug and want to add one more patch:
https://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/commit/?h=pci/host-hv&id=60e2e2fbafdd1285ae1b4ad39ded41603e0c74d0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
@jrp, it looks the patch in comment #26 is unrelated to this bug?
The patch is for cxlflash (Support for IBM CAPI Flash), which doesn't exist in
a VM running on Hyper-V.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Please merge the pull request too:
https://github.com/dcui/linux/compare/350771e4b20a888e9d5d857f46497ae08e8cf8bb...dcui:decui/upstream-ubuntu-marcelo/lp1707285-update-linux-azure
(only 2 patches)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
The patch has been in the mainline tree:
https://github.com/torvalds/linux/commit/e89ce1f89f62c7e527db3850a91dab3389772af3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713884
Title:
[CIFS] Fix max
First I created a Ubuntu 16.04 VM on Azure, which could reproduce the bug, and
"uname -a" showed:
Linux decui-u1604-hwe 4.4.0-92-generic #115~14.04.1-Ubuntu SMP Thu Aug 10
15:06:53 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
I installed the xenial/, and confirmed it resolved the bug:
Linux decui-u16
People are working on this issue: e.g. it looks the patch may work around it:
https://patchwork.kernel.org/patch/10012603/ (it would be great if somebody can
test the patch)
Long will send one more patch:
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1517902.html
--
You receive
The root cause of the bug is:
Ubuntu 14.10(I'm using the daily build of Aug 27 ) blacklists hyperv_fb:
/etc/modprobe.d/fbdev-blacklist.conf: blacklist hyperv_fb
Is there a reason?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
The patch has been in the mainline tree:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=30467e0b3be83c286d60039f8267dd421128ca74
Can Ubuntu people please check if the patch has been included in Ubuntu?
--
You received this bug notification because you are a member of
I have the same issue when installing Ubuntu 15.04 (today's nightly build).
I believe the issue exists for Ubuntu 14.04, 14.10 either.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1285973
Title:
Ca
More information:
This also happens for the official releases of Ubuntu 14.04 and Ubuntu
14.10 on Hyper-V 2012 R2 (I only tried Generation-1 guest, but I suspect
Generation-2 guest would have the same issue).
This doesn't seem like a Hyper-V issue because
1) I think Ubuntu people should fix this
Hi, I'm using "Ubuntu 14.04.2 LTS", is there a .deb package I can
directly "dpkg -i"?
Or, can I use "apt-get install xxx" to get the updated correct binary?
Thanks a lot!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
It turns out the issue also exists in the latest mainline kernel!
The fix "x86, pageattr: Prevent overflow in slow_virt_to_phys() for X86_PAE" is
there, but a later patch "x86/mm: Fix slow_virt_to_phys() to handle large PAT
bit"
(https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/
@f-bosch Hi Frederik, we're really sorry that this backup-can-cause-
filesystem-remounted-readonly issue has been there for long time! We
definitely want to get it fixed as soon as possible. Unluckily according
to my understanding of the long thread here, I think we had difficulty
trying to reprod
@f-bosch Hi Frederik, about the second issue you mentioned ("The more
data getting on the disk, the higher the spikes are...requests that
involve write operations tend to have these characteristics") in #54,
it looks there is a storage I/O performance downgrade somehow.
Do you think if it's relat
Frederik, Thanks for the new information!
About the I/O perf downgrade:
1. I don't think more occupied disk space should harm the perf so greatly (http
resopnse time: from <100ms to several seconds).
2. The perf downgrade appeared recently but the backup issue appeared
long long ago. Why do you
My update:
It looks the issue is somehow related to the backup, but I tend to think there
is a bug somewhere in the storvsc driver code -- it's very hard to track it
down because before the ext4 read-only issue happens, the ext4 file system may
have been somewhat corrupted.
--
You received t
Sorry, I was moved to another project so I couldn't debug the issue with
full-time.
Hi Joshua R. Poulson (jrp), can you please find more resource for this
bug?
My previous debugging made me think the root cause might be in the
storvsc driver code, but unluckily I'm not an expert in that area. :-
Thanks @f-bosch for your clarification in #62. So my understanding is:
the (temporary) I/O downgrade during the period of backup might be
caused by the fact the disk space has been almost used up (?) recently,
but it also might be somehow related to the backup. Let's focus on the
backup issue at
@f-bosch @jsalisbury
I can reproduce the issue consistently within 5~6 hours with a Ubuntu 15.10 VM.
In /var/log/syslog, several minutes before the file system is remounted
as read-only, the hv_vss_daemon has stopped working: the daemon just
always hangs on the poll() , not receiving freeze/thaw
> "BTW, Since Ubuntu 15.04's "
typo.. 15.04 -> 15.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1470250
Title:
[Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
Backups
To ma
I suspect the race condition may be in vss_on_msg() with the non-thread-
safe variable vss_transaction.state.
And I guess the below patch may have fixed the issue (the patch hasn't be in
the upstream yet):
http://lkml.iu.edu/hypermail/linux/kernel/1510.3/04218.html
I can only test the patch tomo
The patch mentioned in #72 can't help -- still bad luck. :-(
But I can confirm: before the issue happens, somehow athe host doesn't send us
freeze/thaw commands any longer.
we need further debugging...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
When the issue happens (it looks due to the layout of the struct somehow...),
can you try the small workaround patch at
https://patchwork.ozlabs.org/patch/518469/?
I paste it below:
diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h
index 88a0069..7233790 100644
--- a/include/li
BTW, I'm not sure if comment #10 could helps or not -- just FYI. :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521053
Title:
Network Performance dropping between vms on different location in
If the patch has been in Wily, I don't think Wily should have this bug.
Please test Wily to confirm this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1292400
Title:
task systemd-udevd:1906 blocked
I'm suffering from the same issue with Ubuntu 14.10 guest on Hyper-V.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1359439
Title:
[7.287663] systemd-logind[1057]: Failed to start unit
user@12
I think https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756247#53 gave
the root cause and a workaround(see comment #58 at the same link...)
And,
root@decui-VM:~# systemctl
Failed to get D-Bus connection: No connection to service manager.
root@decui-VM:~#
--
You received this bug notification b
FYI: the patches have been merged into Linus's tree:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=45d727cee9e200f5b351528b9fb063b69cf702c8
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b29ef3546aecb253a5552b198cef23750d56e1e4
--
You recei
This is a known issue (e.g., see
https://bugzilla.oracle.com/bugzilla/show_bug.cgi?id=14640) we're
working on:
Looks the below commit is causing the issue on WS 2008 R2 (2012 R2 is
OK):
>From 505216ebc571ea906445f5d50d9660ac73b26bac Mon Sep 17 00:00:00 2001
From: K. Y. Srinivasan
Date: Wed, 9 J
The patches have been in the mainline tree:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bda3253043c54a705c8352096194ab6216e2e5c1
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bb0445765866e5b1607af81e2f48ca5a8efbeed8
https://git.kernel.org/
This is caused by a bug kernel API used by recent hyper-v synthetic
network driver in Ubuntu 14.04 (Ubuntu 13.10 is not affected).
This only affects 32-PAE Linux VM when the VM has more-than-about-4GB
memory.
I have fixed the issue:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/
This turns out a host issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1052743#c31
Anyway, it's a minor issue.
So let's wait for the host update (the next release :-)
** Bug watch added: Red Hat Bugzilla #1052743
https://bugzilla.redhat.com/show_bug.cgi?id=1052743
--
You received this bug
KY is trying to make a bunch of fixes to the storvsc driver. This one
will be addressed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1397590
Title:
storvsc attaches the same virtual HDD multiple t
The patch has been sent out.
>From d4e9952a49981e70344692494fd33e254e4eebf5 Mon Sep 17 00:00:00 2001
From: K. Y. Srinivasan
Date: Mon, 15 Dec 2014 16:49:26 -0800
Subject: [PATCH 3/4] Drivers: scsi: storvsc: Fix a bug in storvsc limits
Commit 4cd83ecdac20d30725b4f96e5d7814a1e290bc7e changed the l
ext2.ko itself does support fsfreeze, but typical linux distros, like
Ubuntu, don't supply ext2.ko at all now -- instead, they usually supply
ext3.ko and have ext4 built-in.
So when we mount an ext2 partition, actually the kernel is registering
the ext4 driver as an ext2 driver and in this case th
I believe it’s a configuration issue:
If we use the default Ubuntu kernel as the ”dump capture kernel“[1], we
need to reserve more memory – the default 128MB, generated by the linux-
crashdump post-install script, is not enough, causing a -ENOMEM
failure/BUG in a function of tree_plugin.h.
This i
FYI: another colleague confirmed the above finding:
"
I looked into it and I can confirm the finding.
Tested on Ubuntu 1410
Linux ubuntu 3.16.0-9-generic #14-Ubuntu SMP Fri Aug 15 15:03:57 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
VMname: ubuntu1410
With the default crashkernel=128M@64M w
I can confirm now hibernation can work with 5.4.0-1023, despite a
harmless warning:
root@decui-tmp-2004:~# echo disk >/sys/power/state
[ 56.945758] PM: hibernation entry
[ 57.165520] Filesystems sync: 0.007 seconds
[ 57.169492] Freezing user space processes ... (elapsed 0.001 seconds) done.
Public bug reported:
There are failed logs after resume from hibernation in NV6 (GPU passthrough
size) VM in Azure:
[ 1432.153730] hv_pci 47505500-0001--3130-444531334632: hv_irq_unmask()
failed: 0x5
[ 1432.167910] hv_pci 47505500-0001--3130-444531334632: hv_irq_unmask()
failed: 0x5
Th
Public bug reported:
Description of problem:
On Azure, if the VM is Stopped(deallocated) and later Started, the VF NIC's
VMBus Instance GUID may change, and as a result hibernation/resume can hang
forever.
This happens to the latest stable release of the linux-azure
5.4.0-1023.23 kernel and the
Public bug reported:
Description of problem:
In a VM with CX4 VF NIC on Azure, after hibernation/resume, the TX/RX packet
counters stop increaseing.
This issue doesn't exist in VM with a CX3 VF NIC.
This happens to the latest stable release of the linux-azure
5.4.0-1023.23 kernel and the latest
We also need the second and the third patch:
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=de214e52de1bba5392b5b7054924a08dbd57c2f6
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=da26658c3d7005aa67a706dceff7b2807b59e123
--
You received this
I checked with Matthew and found Matthew only applied the first patch
[1]; after I applied the second patch [2], I'm no longer seeing any
crash or memory corruption issue in Matthew's VM.
BTW, the Windows Server 2019 host running Matthew's VM doesn't work with
NIC SR-IOV correctly: when SR-IOV is
The 5.4.0-1075-azure and newer kernels are broken in that the VM can
easily panic when the Mellanox VF NIC is removed and added due to Azure
host servicing events or the below manual "unbind/bind" test (here the
GUID can be different in different VMs):
for i in `seq 1 1000`;
do
cd /sys/bus/vmb
The 5.4-based linux-azure kenel (https://git.launchpad.net/~canonical-
kernel/ubuntu/+source/linux-azure/+git/bionic/log/?h=azure-5.4) is also
affected by the bug. Will it be fixed as well? I see the 4.15, 5.11,
5.13 linux-azure kernels are explicited listed at the top of this page,
but the 5.14-b
typo... By "but the 5.14-based one is not listed.", I meant the "...
5.4-based ...", not 5.14-based.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959216
Title:
linux-azure: CONFIG_FB_EFI=y
To man
Hi Tim, thanks! I saw the CONFIG_FB_EFI=y change to the v5.4 linux-azure
focal/master-next branch here:
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/+git/focal/log/?h=master-next
My Ubuntu 18.04 (Bionic) VM, which was created from the Azure
marketplace Ubuntu 18.04 image
Got it. I apprecite the clarification. Obviously I was not clear 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/1959216
Title:
linux-azure: CONFIG_FB_EFI=y
To manage notifications about
The link to "[PATCH] scsi: storvsc: Fix a race in sub-channel creation
that can cause panic" is
https://lkml.org/lkml/2018/11/26/159
or
https://lore.kernel.org/patchwork/patch/1016903/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I guess we can close the bug now?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777128
Title:
[Hyper-V] patches for SR-IOV post-bionic GA
To manage notifications about this bug go to:
https://bugs
More patches are required: https://lkml.org/lkml/2018/11/2/182
It looks we'll have to wait for some time, before the kernel stabilizes...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792349
Title:
1 - 100 of 150 matches
Mail list logo
