sorry, to be more clear:
If I make a fresh install in my environment by hand it works.
If I make a fresh install in my environment with my build workflow it doesn't
works.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ok, I made a lot of tests, here a report:
- made a fresh installation with hyper-v on windows 10 -> all works fine
- made a fresh installation with hyper-v on windows server 2012 r2 in our
environment -> all works fine
- all test on existing vms can reproduce the issue as described
environment
** Attachment added: "second screen of a vm boot before the issue"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674635/+attachment/4842339/+files/kernel-stuck-02.PNG
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Attachment added: "last screen of a vm boot at the issue"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674635/+attachment/4842340/+files/kernel-stuck-03.PNG
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "first screen of a vm boot before the issue"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674635/+attachment/4842338/+files/kernel-stuck-01.PNG
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
4ddd2ccae5e00fc62ca72410d2fc8ea668747134 does not boot
p.s. on our side we are still investigating and we are focusing on the boot
configuration, do you have some details about the right device should be
selected in the hypervisor?
just the hard drive?
the efi file in efi partition? (which name
I updated the base image where we make new installation from to the version
4.4.0-67-generic and it works.
Trying to make a new vps from that image and it stucks just after the hdd clone.
The problem seems to be related to the disk clone process.
--
You received this bug notification because
b4e22b8a3d9d5746380e8d400cd9134567ffe675 works fine.
Testing the reverted...
--
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/1674635
Title:
Kernel linux-image-4.4.0-67-generic prevent
Reverted kernel works fine on 2 server:
root@ID11600:~# uname -a
Linux ID11600.example.com 4.4.0-71-generic #92~lp1674635Revert SMP Mon Mar 27
18:33:16 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
8df3e3271ae0bd4d85aff701abc88d6b5526f7fe works fine
--
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/1674635
Title:
Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft
I recheck in a few minutes...
--
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/1674635
Title:
Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft
Hyper-v 2012r2 Gen2 VM
6c71f5ccfa0545c2f397c0ce74f52c3470cc75b6 works fine
--
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/1674635
Title:
Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft
oot@raziel:~# uname -a
Linux raziel.cristianocasella.com 4.4.0-67-generic
#88~lp1674635Commit6c71f5ccfa SMP Thu Mar 23 21:07:48 UTC 2017 x86_64 x86_64
x86_64 GNU/Linux
It works
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Really sorry, I made a typo :(
8df3e3271ae0bd4d85aff701abc88d6b5526f7fe does not boot.
--
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/1674635
Title:
Kernel linux-image-4.4.0-67-generic
same results for me:
b06640ee040e347f122d0e885383da3efdb15ccd works fine
c7e300f2972c4d9a0dcd2d305556b14abb26be2b does not boot
--
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/1674635
thanks for your support
--
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/1674635
Title:
Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft
Hyper-v 2012r2 Gen2 VM
Status
got same troubles also on version 4.4.0-70 (just released:
https://launchpad.net/ubuntu/+source/linux/4.4.0-70.91)
--
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/1674635
Title:
Kernel
patched kernel works:
root@ID11600:~# uname -a
Linux ID11600.example.com 4.4.0-71-generic #92~lp1674635Patched SMP Mon Mar 27
22:33:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
apport information
** Tags added: apport-collected xenial
** Description changed:
After updating the kernel inside the virtual machine to the version
4.4.0-67-generic, at the next boot the vm will stuck in a black screen at every
try. An hard reset is required.
The only workaround is to
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1674635/+attachment/4841481/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1674635/+attachment/4841487/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1674635/+attachment/4841483/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1674635/+attachment/4841484/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1674635/+attachment/4841486/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1674635/+attachment/4841488/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1674635/+attachment/4841485/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1674635/+attachment/4841482/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I added the logs, keep in mind that I collected the logs from the vm
started with previous version of the kernel (can't boot the vm with the
affected version).
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of
Public bug reported:
After updating the kernel inside the virtual machine to the version
4.4.0-67-generic, at the next boot the vm will stuck in a black screen at every
try. An hard reset is required.
The only workaround is to set the default in grub to the previous version.
The virtual machine
installed both packages as requested and gone in the same troubles :(
--
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/1674635
Title:
Kernel linux-image-4.4.0-67-generic prevent the boot
working with xenial and proposed:
root@raziel:~# uname -a
Linux raziel.cristianocasella.com 4.4.0-74-generic #95-Ubuntu SMP Wed Apr 12
09:50:34 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug
If noone else can test Yakkety I can do it tomorrow
--
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/1674635
Title:
Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft
working with yakkety and proposed:
root@ID11547:~# uname -a
Linux ID11547.example.com 4.8.0-48-generic #51-Ubuntu SMP Wed Apr 12 13:00:47
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety
--
You received this bug
33 matches
Mail list logo
