I've opened https://bugs.launchpad.net/cloud-images/+bug/1900852 related
to removing uart1 connections in the base Vagrantfile. We can move
discussion there related to the issue found for derivative images via
Packer, and generally removing it.
I, too, had been under the impression that due to the
I've actually done some checks on latest versions, and it looks like we
can. I'll make a public bug to match the internal ticket I made to
remove the connection.
We've got a release tomorrow (20201022), so the change will go into the
next devel release first, then get SRU'd back.
--
You received
@haggan-era, I don't think it was possible before but now turning the port off
completely could make sense. The following links seem to be related:
- https://bugs.launchpad.net/cloud-images/+bug/1573095/comments/58
- https://bugs.launchpad.net/cloud-images/+bug/1573095/comments/59
--
You receive
Thanks @giner, that's good to know.
If this is the case, why doesn't the official focal image use this
solution (rather than setting the serial port to File::NULL)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
@haggan-era, uartmode disconnected means that the port is available for
the vm. If uart is set to off then the port will not be available at
all. In past the os wouldn't boot in such case (this is why the dummy
port was introduced) however the latest images seem to work.
--
You received this bug
@haggan-era, uartmode disconnected means that the port is available for
the vm. If it uart set to of them then the port will not be available at
all. In past the os wouldn't boot in this case (this is why the dummy
port was introduced) at all however the latest images seem to work.
--
You receive
@giner, I tried setting the uart1 to "disconnected" in the past, but
then the VM on Windows slows down to a halt.
@jchittum
After investigating it, I saw that indeed the OVF file contains "/dev/null". I
used packer in the process, which basically does if I understand correctly
creates a VM based
@haggan-era, could you open a new bug on this issue? Please provide the
following information:
1. version of Windows, vagrant, virtualbox, and Ruby in use on the Windows
computer
2. the Vagrantfile used to create the new .box
3. any steps to reproduce the issue.
On first smell it seems like a R
@haggai-eran, what if you try to disable the port completely?
```
config.vm.provider "virtualbox" do |vb|
vb.customize [ "modifyvm", :id, "--uart1", "off" ]
end
```
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
@jchittum, thanks for the fix. I validated it and it seemed to work.
I came into a related issue however - I've created an image that is
based on ubuntu/focal64 on a Linux system. When trying to use it on a
Windows system, I got the following error:
```
Stderr: VBoxManage.exe: error: RawFile#0 fa
Confirmed, thanks for your work 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/1874453
Title:
ubuntu/focal64 very slow to boot and reboots once
To manage notifications about this bug go to:
@jchittum, confirmed also your fix using fresh `vagrant init ubuntu/focal64`
and `vagrant up`
thx
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874453
Title:
ubuntu/focal64 very slow to boot and r
I've confirmed that the latest Vagrant box published has the fix. I've
also confirmed that users can overwrite the default passing of the
serial console to a File::NULL and write to a different file.
For everyone affected, run a `vagrant box update` on Focal boxes. This
will grab the latest box. I
This bug was fixed in the package livecd-rootfs - 2.664.7
---
livecd-rootfs (2.664.7) focal; urgency=medium
[ Stanislav German-Evtushenko / John Chittum ]
* Send Vagrant serial connection to NULL. (LP: #1874453)
-- Robert C Jennings Wed, 23 Sep 2020
13:32:32 -0500
** Changed
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874453
Title:
ubuntu/focal64 very slow to boot and reboots once
To m
SRU for Focal testing.
Created 2 Vagrant boxes to cover the 2 main build cases of CPC (produced
of the Vagrant image and user of the hook changed)
box A: Created via ubuntu-bartender(https://github.com/chrisglass
/ubuntu-old-fashioned/tree/master/scripts/ubuntu-bartender) utilizing
the source dow
Hello Jake, or anyone else affected,
Accepted livecd-rootfs into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/livecd-
rootfs/2.664.7 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
** Description changed:
SRU
[IMPACT]
* Users are unable to boot a vagrant image, as the boot time without a serial
console connection exceeds the vagrant timeout
* bug is focal as well as latest devel devel release.
* Upload fixes the bug by creating a serial console connection to
** Merge proposal linked:
https://code.launchpad.net/~jchittum/livecd-rootfs/+git/livecd-rootfs/+merge/391169
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874453
Title:
ubuntu/focal64 very slo
** Description changed:
+ SRU
+
+ [IMPACT]
+
+ * Users are unable to boot a vagrant image, as the boot time without a serial
console connection exceeds the vagrant timeout
+ * bug is focal as well as latest devel devel release.
+ * Upload fixes the bug by creating a serial console connection to
** Changed in: cloud-images/groovy
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874453
Title:
ubuntu/focal64 very slow to boot and reboots once
To manage
Updated Groovy Vagrant box has been pushed to Atlas, and tested. Steps
below, Vagrantfile at bottom:
1. create a minimal Vagrantfile for testing
2. `vagrant box update`
3. check box is at a serial 20200917 or newer (if done now, 20200917 should
download)
4. `vagrant up`
5. observe it now boots fa
Also, for anyone that has run a Focal or Groovy box, and had it hang
completely with it not showing up in Virtualbox GUI for stopping, the
following can get the image unlocked for future work (without a reboot)
vboxmanage startvm --type emergencystop
vboxmanage unregistervm
If you're unsure of
fix in livecd-rootfs/master has been merged, built, and tested. Groovy
boxes with any serial with a date 20200917 or newer should have the fix
(we're working on getting this published now). I am also beginning the
SRU procedure to backport the change into Focal.
Thank you giner for the providing
This bug was fixed in the package livecd-rootfs - 2.687
---
livecd-rootfs (2.687) groovy; urgency=medium
[ Stanislav German-Evtushenko / John Chittum ]
* Send Vagrant serial connection to NULL. (LP: #1874453)
-- Robert C Jennings Tue, 15 Sep 2020
15:25:19 -0500
** Changed in
MP, taking giner's work and integrating all the needs for livecd-rootfs
SRU process is going:
https://code.launchpad.net/~jchittum/livecd-rootfs/+git/livecd-
rootfs/+merge/389918
Should be moving in Groovy soon, and then SRU'd back to Focal.
** Also affects: cloud-images/focal
Importance: Und
** Changed in: cloud-images
Assignee: (unassigned) => John Chittum (jchittum)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874453
Title:
ubuntu/focal64 very slow to boot and reboots once
To
** Package changed: linux (Ubuntu) => livecd-rootfs (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874453
Title:
ubuntu/focal64 very slow to boot and reboots once
To manage notifications a
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874453
Title:
ubuntu/focal64 very slo
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874453
Title:
ubuntu/focal64 very slow to b
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874453
Title:
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 sy
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 Ubuntu
Bugs, w
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 Ubuntu
Bugs, which is subscribed to Ubu
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 Ubuntu
Bugs, which is subscribed to
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-
official-vagrant-boxes-for-20-0
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874453
Title:
ubuntu/focal64 very slow to boot and reboots on
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874453
Titl
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 pani
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 V
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 th
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?
https://app.vagrantup.com/ubuntu/boxes/eoan64/versions/20200522.0.
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
Va
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874453
Title:
ubuntu/f
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 boot.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874453
Title:
ubuntu/focal64 very slow to boot and reboots once
To manage
48 matches
Mail list logo
