blob: 5074bc1adb255d5c68ec45e432d1b4f4d05c2056 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
|
device: 0.797
socket: 0.731
graphic: 0.729
PID: 0.728
hypervisor: 0.722
permissions: 0.692
files: 0.675
semantic: 0.675
performance: 0.656
vnc: 0.654
architecture: 0.633
risc-v: 0.622
user-level: 0.618
ppc: 0.617
mistranslation: 0.601
register: 0.586
arm: 0.579
peripherals: 0.548
assembly: 0.526
network: 0.462
virtual: 0.442
VMM: 0.427
debug: 0.410
kernel: 0.407
boot: 0.385
x86: 0.376
i386: 0.336
KVM: 0.248
TCG: 0.243
fstrim not working with image mounted to path?
guest os: windows server standard 2016
qemu agent version 100.0.0
os supports trimming
path mounted image does not support trimming
C:\Users\Administrator>fsutil behavior query disabledeletenotify
NTFS DisableDeleteNotify = 0
ReFS DisableDeleteNotify = 1
[@ ~]# virsh qemu-agent-command vps-xxx '{"execute":"guest-fstrim"}'
{"return":{"paths":[{"path":"C:\\"},{"path":"C:\\Program Files\\Microsoft\\Exchange Server\\V15\\Mailbox\\xxxx\\","error":"The given volume path is invalid. (0x89000001)"}]}}
Looks like the fstrim does not like/check images mounted on a path? Nor detects if image trimming is supported. xxxx is a ReFS mounted image without trimming support.
If I enable trimming on the ReFS image, and configure it win2016, the result is still the same.
C:\Users\Administrator>fsutil behavior query disabledeletenotify
NTFS DisableDeleteNotify = 0
ReFS DisableDeleteNotify = 0
[root@c03 ~]# virsh qemu-agent-command vps-xxx '{"execute":"guest-fstrim"}'
{"return":{"paths":[{"path":"C:\\"},{"path":"C:\\Program Files\\Microsoft\\Exchange Server\\V15\\Mailbox\\xxxx\\","error":"The given volume path is invalid. (0x89000001)"}]}}
PS. tried this on a win 2016 std server with just one fs, no problems then.
The QEMU project is currently moving its bug tracking to another system.
For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting older bugs to "Incomplete" now.
If you still think this bug report here is valid, then please switch
the state back to "New" within the next 60 days, otherwise this report
will be marked as "Expired". Or please mark it as "Fix Released" if
the problem has been solved with a newer version of QEMU already.
Thank you and sorry for the inconvenience.
[Expired for QEMU because there has been no activity for 60 days.]
|