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=21d8a99f88af972684618521cf19adafe24dc566)
It looks this bug has been fixed by some patch between linux-azure
4.13.0-1001.1 and
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
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
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
@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
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
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
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
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
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
@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
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),
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:
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
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
@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.
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=60e2e2fbafdd1285ae1b4ad39ded41603e0c74d0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@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.
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"
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.
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
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
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
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
---
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
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
@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
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
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
@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
@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
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
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.
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:
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
The patch has been sent out.
From d4e9952a49981e70344692494fd33e254e4eebf5 Mon Sep 17 00:00:00 2001
From: K. Y. Srinivasan k...@microsoft.com
Date: Mon, 15 Dec 2014 16:49:26 -0800
Subject: [PATCH 3/4] Drivers: scsi: storvsc: Fix a bug in storvsc limits
Commit
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
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
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:
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
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
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
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
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
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
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
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.
101 - 150 of 150 matches
Mail list logo
