** Package changed: linux (Ubuntu) => livecd-rootfs (Ubuntu)
--
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/1874453
Title:
ubuntu/focal64 very slow to boot and reboots once
Status in
** Merge proposal linked:
https://code.launchpad.net/~jchittum/livecd-rootfs/+git/livecd-rootfs/+merge/389918
--
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/1874453
Title:
The fix is waiting review https://code.launchpad.net/~giner/livecd-
rootfs/+git/livecd-rootfs/+merge/388963
--
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/1874453
Title:
ubuntu/focal64
The change which introduced the issue
https://code.launchpad.net/~aleks.bogdanov/livecd-rootfs/remove-vagrant-
console-log/+merge/355598
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Since I just hit this issue and found this thread amazingly useful, I
thought it might help if I post a theory about what's going on here.
The official ubuntu/bionic64 box was configured, as a default, to log
console output to a file in the Vagrantfile directory. The embedded
Vagrantfile (on my
I just tried firing up 20200629.0.0 and it has the same issue. I'm also
not able to terminate the VMs at all. I've waiting 10+ minutes for them
to stop and nothing. I eventually just killed the PIDs for everything
VirtualBox related.
--
You received this bug notification because you are a member
added the following lines in Vagrantfile to fix the issue temporary. It
wasn't required in Ubuntu 18.04
vbit.vm.provider "virtualbox" do |vb|
vb.customize [ "modifyvm", :id, "--uartmode1", "file", File::NULL ]
end
--
You received this bug notification because you are a member of Kernel
Note: My comment (#34) above is in VirtualBox 6.1.8 and without the
Serial port redirection mentioned in comment #7. With the serial port
redirection everything seems to work properly for me.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Interestingly, using the VirtualBox GUI to boot a VM created from the
20200522.0.0 vagrant box causes the entire VirtualBox GUI to hang. The
only way out of it is to force quit the VM processes.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Re #28
I have both problems using the 20200522.0.0 image on a Windows host.
Host specs: Lenovo Thinkpad P50, Intel Core i7-6700HQ, Windows 10 v1909,
tried with both VirtualBox 6.0.4 and 6.1.8.
Full details at https://askubuntu.com/questions/1243582/unable-to-boot-
Was able to recreate the slow boot. Put together a clean environment,
made a simple focal Vagrantfile only pulling the box, saw the same
things. Confirmed on a Focal host.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
was passed a related issue:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1879290
--
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/1874453
Title:
ubuntu/focal64 very slow to boot
I've set the kernel component to confirmed to move this ticket forward.
** 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.
Both problems persist on 20200522.0.0, here is the kernel panic and
reboot:
[0.883971] VFS: Cannot open root device "PARTUUID=43931bda-01" or
unknown-block(0,0): error -6
[0.885744] Please append a correct "root=" boot option; here are the
available partitions:
[0.887371] Kernel
is this post updating the boxes? could you please post which boxes are
still kernel panicking, as that should have been fixed with
https://bugs.launchpad.net/cloud-images/+bug/1873506
I'm having a bear of a time trying to reproduce the slow boots. I'm
wondering if it's host specific to MacOS and
It's still very slow. When I don't attach a serial device like you gave
an example for to the virtualbox, it still has that 90s pause between
mentioned 'printk' lines during booting and booting is slow in general.
When I do attach the serial device, it still panics the first time, but
the whole
Vagrant boxes with updated kernels have been pushed. My current tests
are showing boot times in the 30s range.
Could folks commenting on slow boot speeds in Focal and Eoan please run
a `vagrant box update` on their current setups?
apport information
** Tags added: apport-collected uec-images
** Description changed:
Using `ubuntu/focal64` version `20200423.0.0`, the boot process is
extremely slow and the box always reboots once before completing a
successful boot. With default settings, this causes a timeout in
Same behavior on eoan, both the one-off kernel panic and slow boot
without overriding the console settings.
** Tags added: eoan
--
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/1874453
Attached are some prints and logs. lshw shows that it's using a scsi
storage control with the mptspi driver. serial console logs show that
initramfsless boots using a a generic scsi driver which appears to fail
to load the root device. initramfs pulls in the mptspi driver properly,
and things
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
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/1874453
Title:
ubuntu/focal64 very slow to boot and reboots
21 matches
Mail list logo
