** Tags added: cscc
--
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/1726818
Title:
vagrant artful64 box filesystem too small
Status in cloud-images:
Fix Released
Status in linux packag
** Changed in: cloud-images
Status: Confirmed => Fix Released
--
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/1726818
Title:
vagrant artful64 box filesystem too small
Status in cl
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1726818
Title:
vagrant artful64 box filesystem too small
Status
This bug was fixed in the package linux - 4.13.0-38.43
---
linux (4.13.0-38.43) artful; urgency=medium
* linux: 4.13.0-38.43 -proposed tracker (LP: #1755762)
* Servers going OOM after updating kernel from 4.10 to 4.13 (LP: #1748408)
- i40e: Fix memory leak related filter prog
Removed `verification-needed-artful` and added `verification-done-
artful` tag.
--
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/1726818
Title:
vagrant artful64 box filesystem too small
S
I have validated that / file system size becomes 9.7GB
after using `-proposed` option as suggested.
# Steps to validate
- At Vagrant host
$ vagrant init ubuntu/artful64
$ vagrant ssh
- At Vagrant guest without `-proposed`
vagrant@ubuntu-artful:~$ df -h /
Filesystem Size Used Avail Use% M
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verifica
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Artful)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
** Changed in: cloud-images
Importance: Undecided => High
--
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/1726818
Title:
vagrant artful64 box filesystem too small
Status in cloud-imag
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
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/1726818
Title:
vagrant artful64 box filesystem too small
Status
I believe this also affects the bionic64 nightlies.
--
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/1726818
Title:
vagrant artful64 box filesystem too small
Status in cloud-images:
Con
** Description changed:
+ [SRU Justfication, Artful]
+
+ [Impact]
+
+ Booting the 4.13 Artful kernel with vagrant using VirtualBox trips the
+ warning:
+
+ [ 61.010337] VFS: brelse: Trying to free free buffer
+ [ 61.114875] [ cut here ]
+ [ 61.114886] WARNING: CPU: 0 PID
My current hunch is that this is due to blk optimization functionality
that landed in the kernel and perhaps the virt blk device on VirtualBox
does not support it yet.
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progr
I'll try and figure out *why* this patch is causing the kernel grief
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/1726818
Title:
vagrant artful64 box filesystem too small
St
Whilst one cannot revert this for 4.13, I did remove the offending code,
rebuilt and now one can boot without the kernel failure and the hdd is
resized correctly.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
git bisect'd to:
c20cfc27a47307e811346f85959cf3cc07ae42f9 is the first bad commit
commit c20cfc27a47307e811346f85959cf3cc07ae42f9
Author: Christoph Hellwig
Date: Wed Apr 5 19:21:07 2017 +0200
block: stop using blkdev_issue_write_same for zeroing
We'll always use the WRITE ZEROES c
I can confirm @paelzer's comment above, resize2fs after vagrant up
works. In fact this helps me in the short term, as adding `resize2fs
/dev/sda1` to the beginning of my provision script resolves my issue.
But this is just a workaround and not a real solution.
--
You received this bug notificati
Thanks, can reproduce the issue now, will debug
--
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/1726818
Title:
vagrant artful64 box filesystem too small
Status in cloud-images:
Confirm
1. Verified on both Ubuntu Linux 17.10 and Windows 10
2. The official ubuntu/artful64 box:
https://app.vagrantup.com/ubuntu/boxes/artful64. The problem is verified with
the currently latest version (v20171115.1.0)
3. Verified with the minimal vagrant configuration (see attached Vagrantfile).
Ste
Hi cking,
I rarely use it, but for me (on Xenial) the following worked.
$ sudo apt install vagrant virtualbox
$ vagrant init ubuntu/artful64
# note that you have to elminate all KVMs before you can do the next step
$ vagrant up
$ vagrant ssh
vagrant@ubuntu-artful:~$ df -h /
Filesystem Size
With the above in comment #17 I see the limited size after boot and the crash
in dmesg.
But then a repro with
$ sudo resize2fs /dev/sda1
doesn't work - well it works, but that is the problem it works to resize
without triggering the issue "again".
--
You received this bug notification because
>From the fs/buffer.c:1205 __brelse+0x21/0x30 it is impossible to deduce
what is broken. I'm trying to reproduce this using vagrant and
VirtualBox. Can you inform me of the vagrant box you are using and the
full set of instructions on how one can reproduce this. Some pertinent
facts to help me re
** Changed in: cloud-images
Status: New => Confirmed
--
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/1726818
Title:
vagrant artful64 box filesystem too small
Status in cloud-image
Thanks for the feedback. I am also unable to address the root file system size
by updating /etc/default/grub as below.
### At Vagrant host
$ vagrant init ubuntu/artful64
$ vagrant up
$ vagrant ssh
### At Vagrant guest
1. Root file syste size is 2.2G
vagrant@ubuntu-artful:~$ df -h /
Filesyste
Yasuo,
It is not exposed in any way through vagrant.
It is a kernel command line option.
You'd have to edit /etc/default/grub and add it to GRUB_CMDLINE_LINUX_DEFAULT
and then run 'update-grub'.
I had done a quick test and didn't seem to think that it fixed the
issue, but I'd be interested in he
Hi, I am getting the same problem.
> Which suggests adding 'noxsave' to the kernel command line as a
workaround.
I have been looking for how to set 'noxsave' kernel boot parameter using
Vagrant but
unable to find it. Does anyone know how to configure it?
Thank you.
--
You received this bug n
This thread shows up with that xsave warn:
https://www.virtualbox.org/pipermail/vbox-dev/2017-May/014466.html
Which suggests adding 'noxsave' to the kernel command line as a
workaround.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
So the/some interesting points of dmesg.log:
[0.00] random: get_random_bytes called from start_kernel+0x42/0x4e1
with crng_init=0
[0.00] Linux version 4.13.0-16-generic (buildd@lcy01-02) (gcc version
7.2.0 (Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
(Ubu
This is the dmesg output.
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/cloud-images/+bug/1726818/+attachment/4991630/+files/dmesg.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
The attached /var/log/cloud-init.log has 2 boots in it.
One starts at 14:15:18 (line 1) and one starting at 14:21:17,808 (line 719).
The first boot successfully updated the partition table for /dev/sda
so that the first partition (/dev/sda1) took the whole ~ 10G disk.
2017-10-24 14:15:33,338 -
30 matches
Mail list logo
