Hi Brent,
first of all I'm glad that you got around things via my suggestions.
There is a reason why those device types are usually recommended in
newer guides as well as being the default in higher level tools like
virt-manager, uvtool, ... is virtio nowadays. It is just more capable.
Thanks for
Incidentally, I was able to fix my immediate problem by switching the
disk type to scsi, based on the suggestions given by Christian Ehrhardt.
It's still an open bug that could cause other people some grief. It
sure caused me plenty.
--
You received this bug notification because you are a membe
I've come up with a more minimal test that doesn't require the whole
GNS3 infrastructure.
1. Create a one-line 'meta-data' file:
{instance-id: ubuntu, local-hostname: ubuntu}
2. Create the following 'user-data' file:
#cloud-config
hostname: ubuntu
network:
config: disabled
resize_rootfs: nobl
Even without proper trimming from GNS there would be a regular cleanup on the
FS anyway.
Ubuntu has a timer based fstrim to clean up space that was freed without
trim/discard awareness.
Assuming that your consumed space is not just inode overhead (I can't
help with that) you could check if this
Also to attack this from a different angle simultaneously - have you
maybe already tried this on older/newer Ubuntu Hosts and did it behave
differently there?
** Changed in: qemu (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bu
Hi Brent,
thank you for all the detail and dedication already spent on this!
Just to be sure as there are two theories up for discussion:
1. ext4lazyinit fills it all
2. gns3 with discard=on fills it all due to maybe DISCARD being ignored
I was reading through the links and discussions and I wan
Finally about discard to the guest.
I see you have ,discard=on in your qemu commandline.
But that is only half the deal, depending on various other setup details the
guest can recognize or not recognize that.
I do not know all the details of your setup but at least in the past
there was quit
best guess as to the package
** Package changed: ubuntu => qemu (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974100
Title:
inode lazy init in a VM fills virtual disk with garbage
To man
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
