Dear List,
vmadm create takes minutes to provision an 8 GiB machine before it times
out:
timed out waiting for
/var/svc/provisioning to move for
bcd0c83a-1eeb-42cd-a28b-ecb67798018a
system-smartdc-metadata:default.log.0
{"name":"metadata","hostname":"smart51","pid":4342,"brand":"kvm","zonename":"bcd0c83a-1eeb-42cd-a28b
-ecb67798018a","level":40,"err":{"message":"connect
ENOENT","name":"Error","stack":"Error: connect ENOENT\n at
errnoException
(net.js:907:11)\n at Object.afterConnect [as oncomplete]
(net.js:898:19)","code":"ENOENT"},"msg":"KVM Socket error: connect
ENOENT","time":"2017-12-07T13:59:02.903Z","v":0}
vmadm_<HOSTNAME>_2017-12-07T14:00:00.log:
{"name":"vmadmd","req_id":"d2fe7b6f-fda5-6b2c-ddb7-d81be1c62048","hostname":"<HOSTNAME>","pid":4894,"ac
tion":"waitForProvisioning","vm":"bcd0c83a-1eeb-42cd-a28b-ecb67798018a","level":50,"err":{"message":
"VM
bcd0c83a-1eeb-42cd-a28b-ecb67798018a is already not 'running'
(currently:
failed)","name":"Error","stack":"Error: VM
bcd0c83a-1eeb-42cd-a28b-ecb67798018a is already not 'running'
(currently:
failed)\n at /usr/vm/node_modules/VM.js:13544:31\n at
/usr/vm/node_modules/VM.js:8679:17\n at
/usr/vm/node_modules/VM.js:3396:13\n at ChildProcess.exithandler
(child_process.js:635:7)\n at ChildProcess.EventEmitter.emit
(events.js:98:17)\n at maybeClose (child_process.js:743:16)\n at
Process.ChildProcess._handle.onexit
(child_process.js:810:5)","code":"ENOTRUNNING"},"msg":"failed to stop VM
bcd0c83a-1eeb-42cd-a28b-ecb67798018a: VM
bcd0c83a-1eeb-42cd-a28b-ecb67798018a
is already not 'running' (currently:
failed)","time":"2017-12-07T13:59:02.035Z","v":0}
SunOS <HOSTNAME> 5.11 joyent_20170916T185915Z i86pc i386 i86pc
09:49:10 up 66 day(s), 22:08, 2 users, load average: 5.13, 4.75,
4.32
# echo ::memstat | mdb -k
Page Summary Pages MB %Tot
------------ ---------------- ---------------- ----
Kernel 10462760 40870 16%
Boot pages 68306 266 0%
ZFS File Data 15583135 60871 23%
Anon 38573434 150677 58%
Exec and libs 4909 19 0%
Page cache 16971 66 0%
Free (cachelist) 15079 58 0%
Free (freelist) 2353019 9191 4%
Total 67077613 262021
Physical 67077612 262021
# mdb -ke 'availrmem/D ; pages_pp_maximum/D'
availrmem:
availrmem: 2726431
pages_pp_maximum:
pages_pp_maximum: 2594861
# swap -sh
total: 153G allocated + 2.33G reserved = 155G used, 124G available
I could reproduce the error, the VM is now in failed state. qemu
reports (vm.log):
=== OUTPUT (2017-12-11T10:01:26Z) ===
qemu_mlock: have only locked 2202202112 of 8589934592 bytes; still
trying...
qemu_mlock: have only locked 2202202112 of 8589934592 bytes; still
trying...
qemu_mlock: have only locked 6065496064 of 8589934592 bytes; still
trying...
qemu_mlock: have only locked 6065496064 of 8589934592 bytes; still
trying...
...
<EOF>
According to our calculations there should be 32 GiB available RAM for
new VMs.
Any ideas appreciated!
Thanks in advance,
Stefan
-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription:
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com
