So it looks this is considered as a feature rather than a bug for the
Ubuntu 20.04 VM image in Azure Marketplacet. To whoever uses such an
image on Azure: if you're installing a new kernel that doesn't have the
necessary drivers built-in (CONFIG_HYPERV=y, CONFIG_HYPERV_STORAGE=y),
you're supposed t
BTW, the symptom described in the Bug Description also exists in the
Ubuntu 20.04 image in Azure Marketplace.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get load
> If someone is using a kernel other than the one we provide for the
cloud, or in the case of a bug, the system will still boot (slower)
after a panic and a reboot to try again with the initrd.
Hi Steve, I guess you assume the pattern is
"panic/success/success/success/...", but actually the patter
Anyone knows who maintains the grub package shipped in the cloud-images?
Should we report a bug at https://bugs.launchpad.net/ubuntu/+source/grub2 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/187018
I think commen #6 is correct: it looks the 2018 patch introduced the
issue for us, but the patch is originally for "initrd-less boot
capabilities." and here we do need the initramfs file.
I guess the patch "ubuntu-add-initrd-less-boot-fallback.patch" is not
included into the grub shipped in the 20
Today I just repeated the test "Create a Gen-1 Ubuntu 19.10 VM on Azure,
and upgrade it to Ubuntu 20.04 by “do-release-upgrade –d" and I
reproduced this bug again, and the grub version is also 2.04-1ubuntu26!
So I suspect grub itself should be good, but some grub config file (i.e.
/etc/grub.d/10_
Sorry, this statement is wrong:
==
Today I also created a VM on my host from
https://cloud-images.ubuntu.com/focal/20200430.1/focal-server-cloudimg-amd64-azure.vhd.zip
and can not see the bug either, and the grub version is also 2.04-1ubuntu26.
Today I installed a Generation-1 Ubuntu 20.04 VM on my local Hyper-V
host from the ISO file: https://releases.ubuntu.com/20.04/ubuntu-20.04
-live-server-amd64.iso (released on 4/23/2020) and I don't see this bug
and the grub version is 2.04-1ubuntu26.
Today I also created a VM on my host from http
When the bug was originally reported on Apr 1, "We installed a Ubuntu
20.04 VM from the .iso file from http://cdimage.ubuntu.com/daily-
live/pending/ and don’t see the strange grub issue". It looks the grub
version used in the .iso file (on Apr 1) does not have the bug.
I don't think the patch in
Thanks for the reminder! I just realized Ubuntu 20.02 was already
released on 4/23. We should try it.
For the CPU firmware (CPU microcode?) update issue: sorry, it's
completely out of my scope -- I only work on Linux. Hopefully that issue
will be resolved in the near future.
--
You received this
Sorry, I made a typo above: systemd.dsystemd.default_standard_output=kmsg ==>
systemd.default_standard_output=kmsg.
BTW, it looks systemd.show_status=true makes no difference for me. I don't see
any status info during the boot-up time -- not sure if I did something wrong.
--
You received this b
I don't have much knowledge bout systemd, either :-) I just did a "man
systemd" and found the options of systemd. "man systemd" says that we
can use pass these kernel parameters to systemd:
systemd.service_watchdogs=true systemd.show_status=true
systemd.log_level=debug systemd.dsystemd.default_st
Since Alt-SysRq-w gives nothing, I'm sure the long delay is not a
kernel/driver issue but a user space issue. It looks due to some reason
I just can not reproduce the long delay. :-(
In the Hyper-V Virtual Machine Connection window's "View" menu, there is
an item "Enhanced Session". In my Ubuntu 1
I also tried xrdp mode and the VM booted up to the xrdp login window in
14 seconds, which is faster than the "native Xorg GUI mode" (which needs
30s)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18485
Sorry, I did miss this part of your previous reply:
root@stock19:~# systemctl list-jobs
JOB UNIT TYPE STATE
48 setvtrgb.service start waiting
137 system-getty.slice start waiting
1 graphical.target start waiting
102 systemd-update-utmp-runlevel.service start waiting
83 plymouth-quit-wait.servi
I agree with David. IMO this bug should be fixed ASAP. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
To manage notifications about this bug go t
It looks #48 shows some service is causing the long delay -- can you try
'systemctl list-jobs' to see active jobs, as the "Hint" says? :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848534
Title:
I created a Ubuntu 19.10 VM via "Quick Create..." and still can not
reproduce the long delay of > 1 minute: the VM can boot up to the Xorg
GUI desktop in 26 seconds.
My Windows 10 has the same version info: Version 1909 (OS Build
18363.778).
At the grub screen, can you press 'e' and, manually edi
@msgallery: BTW, you mentioned 'The "restart" button is not functional'
-- actually it is not functional only when we try to click the button by
mouse -- if we press Tab to focus on the button and then press Enter,
the VM should reboot. :-) I'll try to mention this to Hyper-V team, but
I'm not sur
BTW, my Linux kernel version is 5.3.0-46-generic #38-Ubuntu (17:37:05,
3/27/2020).
The "graphic artifact" is somehow caused by the "$vt_hanoff" kernel parameter
(check "cat /proc/cmdline").
If I manually remove the "$vt_hanoff" at the grub screen, I won't see the
"graphic artifact" -- Ubuntu gu
This is the screenshot of the graphic artifact mentioned in the previous
comment.
** Attachment added: "graphic_artifact.png"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1848534/+attachment/5352858/+files/graphic_artifact.png
--
You received this bug notification because you are a me
Today I installed a Generation-2 VM (4 virtual CPUS, 4 GB memory) from the this
.iso file:
http://releases.ubuntu.com/19.10/ubuntu-19.10-desktop-amd64.iso.
My host is Win10: Version 1909 (OS Build 18383.720) -- I got the info by
running the built-in "winver.exe" program.
The CPU type is Intel C
Hi Marcelo, I'm not sure which v5.3 kernel you mean -- the v5.3 in
Ubuntu 19.10, v5.4 in Ubuntu 20.04 or the upstream stable tree's v5.3
and newer? :-)
Here we need to make sure the 3 patches in the Bug Description are
included, and also make sure the line "if (list_empty(&hbus->children))
hbus->s
Public bug reported:
In Ubuntu 18.04 I have the below 4 lines, but in Ubuntu 20.04 (dev
build) these lines are missing:
--- /usr/share/initramfs-tools/init2020-04-01 01:15:20.533208700 +
+++ /usr/share/initramfs-tools/init 2020-04-01 00:59:43.931655200 +
@@ -163,6 +163,10 @@
BTW, the bug also applies to hwe-4.15.0-91.92_16.04.1 and Ubuntu-
hwe-5.0.0-37.40_18.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867220
Title:
Assignment of VDEV Somtimes Fails using Intel QA
The bug applies to both linux-azure-5.0.0-1032 and linux-azure
4.15.0-1074.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867220
Title:
Assignment of VDEV Somtimes Fails using Intel QAT
To manage
So let me summarize your findings on the same host of yours (I suppose
your VMs use the same config for the number of vCPUs and the memory
size. I also suppose you only tested Hyper-V Generation 2 VMs or you
confirmed Gen-1 vs. Gen-2 makes no difference):
("fast" means you can see the GUI desktop
Can Ubuntu devs please try to repro the issue? I can not repro it. :-(
Hi M, I assume you can also repro the issue with a VM created from
scratch from the server .iso (see comment #28) with a minimal
installation? If yes, can you please share the vhdx file? If you
configure the disk size to 15GB a
The typical boot-up time of my Ubuntu VM on Hyper-V is 20~30 seconds for
a Desktop version of Ubuntu, and 10~20 seconds for a Server version. I
tried Ubuntu 19.04 just now and it also took 20+ seconds.
I never achieve a boot-up time of 2s.
I do know Ubuntu can boot up fast in 2~3 seconds in WSL (
Hi M, since I can not reproduce the delay issue, I don't know what I can
do now. :-(
Do you think if it's related to Xorg?
Can you install a new VM from scratch from the server .iso
(http://releases.ubuntu.com/19.10/ubuntu-19.10-live-server-amd64.iso)
and see if you can reproduce the same issue?
I'm not sure what exact issues you're reporting.
Your VM takes too much time to boot up? How long? "systemd-analyze
blame" should collect the info for your VM.
Your VM's screen is somehow messed up temporarily during the boot-up
process? Or the boot-up process is stuck in the "text cursor" scree
Hi M, I can not reproduce the issue: just now I downloaded
http://dt0cinyuc0rrg.cloudfront.net/ubuntu-19.10-desktop-amd64.iso and
created a Generation-2 VM on Hyper-V with the .iso file. The VM boots up
fast: it boots up to the Xorg desktop in 28 seconds with 1 CPU and 2GB
memory, and in 21 seconds
@Vald: This is from your attachment:
[21965.367843] kernel BUG at
/build/linux-azure-njdnVX/linux-azure-4.15.0/net/ipv4/ip_output.c:636!
[21965.377590] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.15.0-1056-azure
#61-Ubuntu
[21965.435777] RIP: 0010:ip_do_fragment+0x571/0x860
[21965.435777] ip_fr
I guess you might have already included this patch:
15becc2b56c6 ("PCI: hv: Add hv_pci_remove_slots() when we unload the
driver")
Unluckily it turns out it is buggy and just now I had to post a further patch
for it:
[PATCH] PCI: hv: Fix panic by calling hv_pci_remove_slots() earlier
I can confirm the fix is included in the kernel "4.4.0-152.179":
https://kernel.ubuntu.com/git/ubuntu/ubuntu-
xenial.git/tree/include/linux/hyperv.h?h=Ubuntu-4.4.0-152.179
I installed the kernel, did some network tests, and it worked fine for
me:
#apt-get install linux-image-4.4.0-152-generic
#re
@rnsc: Can you please share the VM's full serial log, which can be
obtained from Azure portal's Boot Diagnostics -> Serial log?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822133
Title:
Azure In
I tried to reproduce the bug but couldn't.
My Ubuntu 18.04 VM (in West US 2, the VM size is: Basic A3 (4 vcpus, 7
GiB memory)) is still running fine, after I rebooted the VM 100 times
with the below /etc/rc.local script:
#!/bin/bash
date >> /root/reboot.log
NUM=`wc -l /root/reboot.log | cut -d' '
@Kirk: I suppose you can get your VM back by Restarting the VM by force
via Azure Portal (or Azure cmd line)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822133
Title:
Azure Instance never recove
@Kirk: Can you please share the VM's serial log, which can be obtained
from Azure portal's Boot Diagnostics -> Serial log?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822133
Title:
Azure Instance
It's glad to see the issue can not repro with the 5.0.0-1007.7 kernel.
@sfeole: The line "[ 84.247704]hyperv_fb: unable to send packet via
vmbus" usually means the VM has panicked. Do you happen to still keep
the full serial log containing this line of error? It would be good to
understand this er
When the issue happens, there is no error message in dmesg or syslog,
and it's just the host side NetVSP driver stops reading from the guest-
to-host ring, and the guest network stops working. So we don't really
have any logs to provide here.
--
You received this bug notification because you are
Hi Mathieu,
Thanks for the hint! After I changed the Pin-Priority from 400 to 600 in the
below file, I successfully installed the *3.22 version:
root@decui-g2-1604:~# cat /etc/apt/preferences.d/proposed-updates
Package: *
Pin: release a=xenial-proposed
Pin-Priority: 600
...
root@decui-g2-1604:
Hi Brian, "apt-get update; apt-get install grub2-common" still reports
"grub2-common is already the newest version (2.02~beta2-36ubuntu3.21)"
to me, and the new version can not be found.
I'm running the Ubuntu 16.04.6 LTS (4.4.0-142-generic #168-Ubuntu SMP
Wed Jan 16 21:00:45 UTC 2019 x86_64) vers
I added
deb http://archive.ubuntu.com/ubuntu/ xenial-proposed restricted main
multiverse universe
into /etc/apt/sources.list and ran "apt-get update", and when I tried to
upgrade to the .22 version, it can not be found:
root@decui-g2-1604:~# apt-get install grub2-common
Reading package lists...
It looks the .22 binary (2.02~beta2-36ubuntu3.22) for amd64 has not
appeared in the -proposed repo yet.
I can not find it in https://launchpad.net/ubuntu/xenial/+package/grub-
common and http://archive.ubuntu.com/ubuntu/dists/xenial-
proposed/main/uefi/grub2-amd64/ (please let me know if I'm look
Hi Mathieu, thank you for the explanation and pushing the fix!
Hi Brian, I'll test the new grub2 binary in a Ubuntu 16.04.6 VM 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/1826453
Title
I was not clear about the lifecycle of 16.04 and 14.04. :-)
AFAIK, there is no real need to fix the bug for 14.04.
And I understand it looks there won't be a 16.04.7, either.
Since the bug is already fixed in 18.04 (and newer? I didn't check
19.xx), it looks to me we can leave it as is for 16.04
Public bug reported:
In a Ubuntu 16.04.6 VM, which runs as a Gen2 VM on Hyper-V, I add
GRUB_GFXPAYLOAD_LINUX="text" into /etc/default/grub and run update-grub;
next, grub2 prints the below error:
error: invalid video mode specification `text'.
Booting in blind mode
This means grub2 passes a ze
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.
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:
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
Thanks, Marcolo!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786313
Title:
[Hyper-V] hv_netvsc: Fix napi reschedule while receive completion is
busy
To manage notifications about this bug go t
4.15.0-1022 (https://git.launchpad.net/~canonical-kernel/ubuntu/+source
/linux-azure/tree/drivers/net/hyperv/netvsc.c?h=master-next&id=Ubuntu-
azure-4.15.0-1022.22_16.04.1) does NOT have the fix
(6b81b193b83e87da1ea13217d684b54fccf8ee8a).
I'm not sure why the bug status was changed to Fix Committe
53 matches
Mail list logo
