Displaying 20 results from an estimated 7000 matches similar to: "fstrim support in libvirt/qemu guests"
2014 Nov 03
2
Re: fstrim support in libvirt/qemu guests
On Mon, Nov 3, 2014 at 4:24 PM, Michal Privoznik <mprivozn@redhat.com> wrote:
> On 01.11.2014 05:30, Dennis Jacobfeuerborn wrote:
>>
>> Hi,
>> I'm trying to find out how to enable fstrim support for libvirt/qemu
>> guests. Specifically I'm trying to enable this on a CentOS 7 host (qemu
>> 1.5). I searched the web but only found very vague information
2014 Nov 03
0
Re: fstrim support in libvirt/qemu guests
On 01.11.2014 05:30, Dennis Jacobfeuerborn wrote:
> Hi,
> I'm trying to find out how to enable fstrim support for libvirt/qemu
> guests. Specifically I'm trying to enable this on a CentOS 7 host (qemu
> 1.5). I searched the web but only found very vague information and no
> clear documentation on the requirements or how to modify the guest xml
> to enable discard/fstrim
2014 Nov 03
0
Re: fstrim support in libvirt/qemu guests
On 11/3/2014 8:43 AM, Andrey Korolyov wrote:
> On Mon, Nov 3, 2014 at 4:24 PM, Michal Privoznik <mprivozn@redhat.com> wrote:
>> On 01.11.2014 05:30, Dennis Jacobfeuerborn wrote:
>>> Hi,
>>> I'm trying to find out how to enable fstrim support for libvirt/qemu
>>> guests. Specifically I'm trying to enable this on a CentOS 7 host (qemu
>>>
2013 Oct 10
4
BUG relating to fstrim on btrfs partitions
I think I found a bug affecting btrfs filesystems and users invoking fstrim to discard unused blocks: if I execute a `fstrim -v /` twice, the amount trimmed does not change on the 2nd invocation AND it takes just as long as the first. Why do I think this is a bug? When I do the same on an ext4 partition I get different behavior: the output shows 0 B trimmed and it does is instantaneously when I
2018 Sep 05
2
[PATCH] sparsify: Fix test-virt-sparsify-in-place-fstrim-unsupported.sh
Since Linux commit f663b5b38fff trimming vfat is now supported by
Linux. This broke the test which assumed it was not supported. Use
another filesystem (minix) which does not support trimming instead.
Thanks: Daniel P. Berrangé and Pino Toscano.
---
...virt-sparsify-in-place-fstrim-unsupported.sh | 17 ++++++++++-------
1 file changed, 10 insertions(+), 7 deletions(-)
diff --git
2016 Jan 20
1
LVM thin volumes fstrim operation not supported
I still get the "the discard operation is not supported" fstrim error
when the LVs are set to "nopassdown"
Seems that when I use ext4 the fstrim reports that it worked but the
LVs Data% does not decrease after the fstrim. xfs just throws the
error.
I've also been looking at the output of lsblk -D
# lsblk -D
NAME DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO
xvdb
2016 Jan 19
2
LVM thin volumes fstrim operation not supported
Hi All
I'm trying to setup my LVM thin pool to support discards so that the pool
can reclaim space even if the underlying device doesn't support trim. It is
my understanding that all thin pools should support trim even if the
underlying device doesn't. (please correct me if I'm wrong here)
I have one centos server that does support trim and everything is working
correctly but any
2016 Aug 12
4
[PATCH 1/2] v2v: Make fstrim warning clearer (RHBZ#1366456).
This reverts the change made for RHBZ#1168144. The warning is now
always displayed.
It would be nice to make the warning actionable, but there is not a
lot that end users can do since fstrim is such a complex topic
interacting with all filesystem and storage layers.
---
v2v/v2v.ml | 6 +-----
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/v2v/v2v.ml b/v2v/v2v.ml
index
2016 Aug 12
2
Re: [PATCH 1/2] v2v: Make fstrim warning clearer (RHBZ#1366456).
On Fri, Aug 12, 2016 at 04:50:31PM +0200, Pino Toscano wrote:
> On Friday, 12 August 2016 10:37:29 CEST Richard W.M. Jones wrote:
> > This reverts the change made for RHBZ#1168144. The warning is now
> > always displayed.
> >
> > It would be nice to make the warning actionable, but there is not a
> > lot that end users can do since fstrim is such a complex topic
2016 Aug 05
1
Re: [PATCH 2/4] daemon: fstrim: Turn "discard operation is not supported" into ENOTSUP.
On Friday, 5 August 2016 12:22:45 CEST Richard W.M. Jones wrote:
> Because we run the external fstrim command we don't have access to the
> kernel errno when it fails. However in the case where it prints this
> specific error message, turn that into errno ENOTSUP.
> ---
Can you please note this behaviour in the documentation of the fstrim
API?
Thanks,
--
Pino Toscano
2015 Dec 09
4
win2008r2 update on centos 6 host made system unbootable
On 09.12.2015 00:39, NightLightHosts Admin wrote:
> On Tue, Dec 8, 2015 at 5:26 PM, Dennis Jacobfeuerborn
> <dennisml at conversis.de> wrote:
>> Hi,
>> today we ran into a strange problem: When performing a regular Windows
>> 2008r2 update apparently among other things the following was installed:
>> "SUSE - Storage Controller - SUSE Block Driver for
2011 Dec 28
13
fstrim on BTRFS
Hi!
With 3.2-rc4 (probably earlier), Ext4 seems to remember what areas it
trimmed:
merkaba:~> fstrim -v /boot
/boot: 224657408 bytes were trimmed
merkaba:~> fstrim -v /boot
/boot: 0 bytes were trimmed
But BTRFS does not:
merkaba:~> fstrim -v /
/: 4431613952 bytes were trimmed
merkaba:~> fstrim -v /
/: 4341846016 bytes were trimmed
Is it planned to add this feature to BTRFS
2011 Jul 21
3
Experience with Centos running off usb-stick(s)
Hi,
I'm trying to build a redundant duo of firewalls/routers/gateways and I'm
thinking about not putting any disks in them and instead using a usb-stick
raid-1 as storage.
Has anyone any experience with this? Since the machines will be running
pretty much only iptables, conntrackd and keepalived there is not going to
be a lot of disk activity going on and the plan is to do all the
2018 Feb 27
5
Any alternatives for the horrible reposync
Hi,
I'm currently trying to mirror a couple of yum repositories and the only
tool that seems to be available for this is reposync.
Unfortunately reposync for some inexplicable reason seems to use the yum
config of the local system as a basis for its work which makes no sense
and creates all kinds of problems where cache directories and metadata
gets mixed up.
Are there any alternatives? Some
2018 Feb 28
1
Any alternatives for the horrible reposync
On 27.02.2018 16:45, Stephen John Smoogen wrote:
> On 27 February 2018 at 06:11, Dennis Jacobfeuerborn
> <dennisml at conversis.de> wrote:
>> Hi,
>> I'm currently trying to mirror a couple of yum repositories and the only
>> tool that seems to be available for this is reposync.
>> Unfortunately reposync for some inexplicable reason seems to use the yum
2015 Nov 05
1
RFE: 'fstrim' minimum block size when sparsifying qcow2 should be 64K
As the minimum block size to discard in qcow2 is 64K, any point in
fstrimming smaller contiguous blocks?
TIA,
Y.
2018 Mar 19
2
Network interface name of guest via python API
Hi,
I'm trying to get some basic data from running guests on a libvirt HV
but one thing I'm missing is the name of the network interfaces of the
guests. I can get the MAC address from the XML but there seems to be no
function to actually get the name of the interface.
The only function that comes close is this one:
2015 Apr 15
2
Update to 1503 release problem
On 15 Apr 2015 13:22, "Dennis Jacobfeuerborn" <dennisml at conversis.de> wrote:
>
> On 15.04.2015 12:41, Alessandro Baggi wrote:
> > Hi there,
> > Yesterday I've updated from 7 to 7.1 and today I've noticed on 2 server
> > that postgresql systemd file was replaced with default values. This make
> > postgres to no start and webserver give me
2015 Jan 24
3
VLAN issue
Do you need the whole configuration? On the switch end, we have the
relevant VLAN (VLAN 48) with the assigned IP address of 192.168.48.101 and
the range of ports (Gi1/0/1 - Gi1/0/8) assigned to that VLAN.
Seems - and acts - like a legitimate setup and works fine, except for this
particular instance.
Thanks.
Boris.
On Fri, Jan 23, 2015 at 8:54 PM, Dennis Jacobfeuerborn <
dennisml at
2015 Jan 17
1
Re: Guests using more ram than specified
On 16.01.2015 15:14, Michal Privoznik wrote:
> On 16.01.2015 13:33, Dennis Jacobfeuerborn wrote:
>> Hi,
>> today I noticed that one of my HVs started swapping aggressively and
>> noticed that the two guests running on it use quite a bit more ram than
>> I assigned to them. They respectively were assigned 124G and 60G with
>> the idea that the 192G system then has