Cannot schedule VM, there is no suitable system ds

Dmitry1 · September 22, 2016, 5:24pm

Hello, I can’t understand why datastore cannot be applied for VM, VM is in pending state:
Persistent or not, doesn’t matter.
Resources should be enough.

Thu Sep 22 18:18:33 2016 [Z0][VM][D]: Found 2 pending/rescheduling VMs.
Thu Sep 22 18:18:33 2016 [Z0][HOST][D]: Discovered 2 enabled hosts.
Thu Sep 22 18:18:33 2016 [Z0][SCHED][D]: Match-making results for VM 15:
Cannot schedule VM, there is no suitable system ds.

Thu Sep 22 18:18:33 2016 [Z0][SCHED][D]: Match-making results for VM 17:
Cannot schedule VM, there is no suitable system ds.

Thu Sep 22 18:18:33 2016 [Z0][SCHED][D]: Dispatching VMs to hosts:
VMID Host System DS
-------------------------

Datastore is created on target node, some images exists there:
[root@vz7-1 109]# ls -ll
total 136132
-rw-rw-r-- 1 oneadmin oneadmin 55506432 Sep 22 11:50 137ac4a4de007dac52eb3722569bd33e
-rw-r–r-- 1 oneadmin oneadmin 1048576000 Sep 22 12:06 71feef6605a7972f78fb8f937e94b95c
-rw-rw-r-- 1 oneadmin oneadmin 41943040 Sep 22 13:05 a49a52780418600c7b7183052e9a479a
-rw-rw-r-- 1 oneadmin oneadmin 41943040 Sep 22 11:50 e997633a0b9b42ccc2c6befc52a1a072
[root@vz7-1 109]# pwd
/var/lib/one/datastores/109
[root@vz7-1 109]#

On sandbox host I’ve created VM, after 36 minutes of the same error:

Thu Sep 22 15:30:57 2016 [Z0][VM][D]: Found 2 pending/rescheduling VMs.
Thu Sep 22 15:30:57 2016 [Z0][HOST][D]: Discovered 2 enabled hosts.
Thu Sep 22 15:30:57 2016 [Z0][SCHED][D]: Match-making results for VM 8:
Cannot schedule VM, there is no suitable system ds.

Thu Sep 22 15:30:57 2016 [Z0][SCHED][D]: Match-making results for VM 9:
Cannot schedule VM, there is no suitable host.

Thu Sep 22 15:30:57 2016 [Z0][SCHED][D]: Dispatching VMs to hosts:
VMID Host System DS

30 mins:

Thu Sep 22 16:06:57 2016 [Z0][VM][D]: Found 2 pending/rescheduling VMs.
Thu Sep 22 16:06:57 2016 [Z0][HOST][D]: Discovered 2 enabled hosts.
Thu Sep 22 16:06:57 2016 [Z0][SCHED][D]: Match-making results for VM 8:
Cannot schedule VM, there is no suitable system ds.

Thu Sep 22 16:06:57 2016 [Z0][SCHED][D]: Match-making results for VM 9:
Cannot schedule VM, there is no suitable host.

Thu Sep 22 16:06:57 2016 [Z0][SCHED][D]: Dispatching VMs to hosts:
VMID Host System DS
-------------------------

Thu Sep 22 16:07:27 2016 [Z0][VM][D]: Found 2 pending/rescheduling VMs.
Thu Sep 22 16:07:27 2016 [Z0][HOST][D]: Discovered 2 enabled hosts.
Thu Sep 22 16:07:27 2016 [Z0][SCHED][D]: Match-making results for VM 9:
Cannot schedule VM, there is no suitable host.

Thu Sep 22 16:07:27 2016 [Z0][SCHED][D]: Dispatching VMs to hosts:
VMID Host System DS
-------------------------
8 0 104

opend.log

Thu Sep 22 18:15:33 2016 [Z0][ReM][D]: Req:1072 UID:0 VirtualMachineUpdateTemplate result SUCCESS, 15
Thu Sep 22 18:15:33 2016 [Z0][ReM][D]: Req:1872 UID:0 VirtualMachineUpdateTemplate invoked , 17, “<DESCRIPTI…”
Thu Sep 22 18:15:33 2016 [Z0][ReM][D]: Req:1872 UID:0 VirtualMachineUpdateTemplate result SUCCESS, 17
Thu Sep 22 18:15:35 2016 [Z0][InM][D]: Host one-sandbox (0) successfully monitored.
Thu Sep 22 18:15:35 2016 [Z0][VMM][D]: VM 8 successfully monitored: DISK_SIZE=[ID=0,SIZE=40] DISK_SIZE=[ID=1,SIZE=1] STATE=a CPU=6.74 MEMORY=131072 NETRX=1452 NETTX=0
Thu Sep 22 18:15:40 2016 [Z0][InM][D]: Host 10.110.20.151 (4) successfully monitored.
Thu Sep 22 18:15:50 2016 [Z0][InM][D]: Monitoring datastore default (1)
Thu Sep 22 18:15:50 2016 [Z0][InM][D]: Monitoring datastore vz (109)
Thu Sep 22 18:15:50 2016 [Z0][ImM][D]: Datastore default (1) successfully monitored.
Thu Sep 22 18:15:50 2016 [Z0][ImM][D]: Datastore vz (109) successfully monitored.
Thu Sep 22 18:15:55 2016 [Z0][InM][D]: Host one-sandbox (0) successfully monitored.
Thu Sep 22 18:15:55 2016 [Z0][VMM][D]: VM 8 successfully monitored: DISK_SIZE=[ID=0,SIZE=40] DISK_SIZE=[ID=1,SIZE=1] STATE=a CPU=8.04 MEMORY=131072 NETRX=1452 NETTX=0
Thu Sep 22 18:15:58 2016 [Z0][ReM][D]: Req:4400 UID:1 DocumentPoolInfo invoked , -2, -1, -1, 100
Thu Sep 22 18:15:58 2016 [Z0][ReM][D]: Req:4400 UID:1 DocumentPoolInfo result SUCCESS, “<DOCUMENT_POOL></DOC…”
Thu Sep 22 18:16:00 2016 [Z0][InM][D]: Host 10.110.20.151 (4) successfully monitored.
Thu Sep 22 18:16:03 2016 [Z0][ReM][D]: Req:8688 UID:0 VirtualMachinePoolInfo invoked , -2, -1, -1, -1
Thu Sep 22 18:16:03 2016 [Z0][ReM][D]: Req:8688 UID:0 VirtualMachinePoolInfo result SUCCESS, “<VM_POOL>8</…”
Thu Sep 22 18:16:03 2016 [Z0][ReM][D]: Req:5808 UID:0 VirtualMachinePoolInfo invoked , -2, -1, -1, -1
Thu Sep 22 18:16:03 2016 [Z0][ReM][D]: Req:5808 UID:0 VirtualMachinePoolInfo result SUCCESS, “<VM_POOL>8</…”
Thu Sep 22 18:16:03 2016 [Z0][ReM][D]: Req:320 UID:0 DatastorePoolInfo invoked
Thu Sep 22 18:16:03 2016 [Z0][ReM][D]: Req:320 UID:0 DatastorePoolInfo result SUCCESS, “<DATASTORE_POOL><DAT…”
Thu Sep 22 18:16:03 2016 [Z0][ReM][D]: Req:5168 UID:0 DatastorePoolInfo invoked
Thu Sep 22 18:16:03 2016 [Z0][ReM][D]: Req:5168 UID:0 DatastorePoolInfo result SUCCESS, “<DATASTORE_POOL><DAT…”
Thu Sep 22 18:16:03 2016 [Z0][ReM][D]: Req:4576 UID:0 UserPoolInfo invoked
Thu Sep 22 18:16:03 2016 [Z0][ReM][D]: Req:4576 UID:0 UserPoolInfo result SUCCESS, “<USER_POOL><ID…”
Thu Sep 22 18:16:03 2016 [Z0][ReM][D]: Req:5232 UID:0 HostPoolInfo invoked
Thu Sep 22 18:16:03 2016 [Z0][ReM][D]: Req:5232 UID:0 HostPoolInfo result SUCCESS, “<HOST_POOL><ID…”
Thu Sep 22 18:16:03 2016 [Z0][ReM][D]: Req:3968 UID:0 ClusterPoolInfo invoked
Thu Sep 22 18:16:03 2016 [Z0][ReM][D]: Req:3968 UID:0 ClusterPoolInfo result SUCCESS, “<CLUSTER_POOL><CLUST…”
Thu Sep 22 18:16:03 2016 [Z0][ReM][D]: Req:5728 UID:0 AclInfo invoked
Thu Sep 22 18:16:03 2016 [Z0][ReM][D]: Req:5728 UID:0 AclInfo result SUCCESS, “<ACL_POOL>0…”
Thu Sep 22 18:16:03 2016 [Z0][ReM][D]: Req:1424 UID:0 VirtualMachineUpdateTemplate invoked , 15, “<![C…”
Thu Sep 22 18:16:03 2016 [Z0][ReM][D]: Req:1424 UID:0 VirtualMachineUpdateTemplate result SUCCESS, 15
Thu Sep 22 18:16:03 2016 [Z0][ReM][D]: Req:5776 UID:0 VirtualMachineUpdateTemplate invoked , 17, “<DESCRIPTI…”
Thu Sep 22 18:16:03 2016 [Z0][ReM][D]: Req:5776 UID:0 VirtualMachineUpdateTemplate result SUCCESS, 17
Thu Sep 22 18:16:05 2016 [Z0][MKP][D]: Monitoring marketplace OpenNebula Public (0)
Thu Sep 22 18:16:05 2016 [Z0][MKP][D]: Marketplace OpenNebula Public (0) successfully monitored.
Thu Sep 22 18:16:20 2016 [Z0][InM][D]: Host one-sandbox (0) successfully monitored.

ruben · September 23, 2016, 10:26am

You can get a more detailed information from the scheduler by increasing
the log level in sched.conf. It is most likely that there are conflicting
cluster requirements etc…

Dmitry1 · September 23, 2016, 11:24am

Hi, Ruben, still can’t understand why

Fri Sep 23 12:20:44 2016 [Z0][SCHED][D]: Dispatching VMs to hosts. Total time: 0.00s
Fri Sep 23 12:21:14 2016 [Z0][SCHED][D]: Getting scheduled actions information. Total time: 0.02s
Fri Sep 23 12:21:14 2016 [Z0][VM][D]: Pending/rescheduling VM and capacity requirements:
  ACTION       VM  CPU      Memory PCI   System DS  Image DS
------------------------------------------------------------
  DEPLOY       15   10      131072   0          40  DS 109: 0
  DEPLOY       17   10      131072   0          40  DS 1: 0

Fri Sep 23 12:21:14 2016 [Z0][HOST][D]: Discovered Hosts (enabled):
ID          : 0
CLUSTER_ID  : 0
MEM_USAGE   : 131072
CPU_USAGE   : 10
MAX_MEM     : 759128
MAX_CPU     : 100
FREE_DISK   : 6960
RUNNING_VMS : 1
PUBLIC      : 0

 DSID         FREE_MB
------------------------------
    0            6960

    PCI ADDRESS    CLASS   VENDOR   DEVICE     VMID
-------------------------------------------------------

ID          : 4
CLUSTER_ID  : 0
MEM_USAGE   : 0
CPU_USAGE   : 0
MAX_MEM     : 3857748
MAX_CPU     : 200
FREE_DISK   : 9582
RUNNING_VMS : 0
PUBLIC      : 0

 DSID         FREE_MB
------------------------------

    PCI ADDRESS    CLASS   VENDOR   DEVICE     VMID
-------------------------------------------------------


Fri Sep 23 12:21:14 2016 [Z0][SCHED][D]: Getting VM and Host information. Total time: 0.15s
Fri Sep 23 12:21:14 2016 [Z0][SCHED][D]: Host 0 discarded for VM 15. It does not fulfill SCHED_REQUIREMENTS.
Fri Sep 23 12:21:14 2016 [Z0][SCHED][D]: Match-making results for VM 15:
        Cannot schedule VM, there is no suitable system ds.

Fri Sep 23 12:21:14 2016 [Z0][SCHED][D]: Host 0 discarded for VM 17. It does not fulfill SCHED_REQUIREMENTS.
Fri Sep 23 12:21:14 2016 [Z0][SCHED][D]: Match-making results for VM 17:
        Cannot schedule VM, there is no suitable system ds.

Fri Sep 23 12:21:14 2016 [Z0][SCHED][D]: Match Making statistics:
        Number of VMs:            2
        Total time:               0s
        Total Cluster Match time: 0s
        Total Host Match time:    0.00s
        Total Host Ranking time:  0.00s
        Total DS Match time:      0.00s
        Total DS Ranking time:    0s

Fri Sep 23 12:21:14 2016 [Z0][SCHED][D]: Scheduling Results:

Fri Sep 23 12:21:14 2016 [Z0][SCHED][D]: Dispatching VMs to hosts:
        VMID    Host    System DS
        -------------------------

Fri Sep 23 12:21:14 2016 [Z0][SCHED][D]: Dispatching VMs to hosts. Total time: 0.00s

Dmitry1 · September 23, 2016, 2:38pm

Fri Sep 23 12:20:44 2016 [Z0][SCHED][D]: Dispatching VMs to hosts. Total time: 0.00s
Fri Sep 23 12:21:14 2016 [Z0][SCHED][D]: Getting scheduled actions information. Total time: 0.02s
Fri Sep 23 12:21:14 2016 [Z0][VM][D]: Pending/rescheduling VM and capacity requirements:
  ACTION       VM  CPU      Memory PCI   System DS  Image DS
------------------------------------------------------------
  DEPLOY       15   10      131072   0          40  DS 109: 0
  DEPLOY       17   10      131072   0          40  DS 1: 0

Fri Sep 23 12:21:14 2016 [Z0][HOST][D]: Discovered Hosts (enabled):
ID          : 0
CLUSTER_ID  : 0
MEM_USAGE   : 131072
CPU_USAGE   : 10
MAX_MEM     : 759128
MAX_CPU     : 100
FREE_DISK   : 6960
RUNNING_VMS : 1
PUBLIC      : 0

 DSID         FREE_MB
------------------------------
    0            6960

    PCI ADDRESS    CLASS   VENDOR   DEVICE     VMID
-------------------------------------------------------

ID          : 4
CLUSTER_ID  : 0
MEM_USAGE   : 0
CPU_USAGE   : 0
MAX_MEM     : 3857748
MAX_CPU     : 200
FREE_DISK   : 9582
RUNNING_VMS : 0
PUBLIC      : 0

 DSID         FREE_MB
------------------------------

    PCI ADDRESS    CLASS   VENDOR   DEVICE     VMID
-------------------------------------------------------


Fri Sep 23 12:21:14 2016 [Z0][SCHED][D]: Getting VM and Host information. Total time: 0.15s
Fri Sep 23 12:21:14 2016 [Z0][SCHED][D]: Host 0 discarded for VM 15. It does not fulfill SCHED_REQUIREMENTS.
Fri Sep 23 12:21:14 2016 [Z0][SCHED][D]: Match-making results for VM 15:
        Cannot schedule VM, there is no suitable system ds.

Fri Sep 23 12:21:14 2016 [Z0][SCHED][D]: Host 0 discarded for VM 17. It does not fulfill SCHED_REQUIREMENTS.
Fri Sep 23 12:21:14 2016 [Z0][SCHED][D]: Match-making results for VM 17:
        Cannot schedule VM, there is no suitable system ds.

Fri Sep 23 12:21:14 2016 [Z0][SCHED][D]: Match Making statistics:
        Number of VMs:            2
        Total time:               0s
        Total Cluster Match time: 0s
        Total Host Match time:    0.00s
        Total Host Ranking time:  0.00s
        Total DS Match time:      0.00s
        Total DS Ranking time:    0s

Fri Sep 23 12:21:14 2016 [Z0][SCHED][D]: Scheduling Results:

Fri Sep 23 12:21:14 2016 [Z0][SCHED][D]: Dispatching VMs to hosts:
        VMID    Host    System DS
        -------------------------

Fri Sep 23 12:21:14 2016 [Z0][SCHED][D]: Dispatching VMs to hosts. Total time: 0.00s

Dmitry1 · September 26, 2016, 10:15am

Can anyone help with this problem?

ruben · September 26, 2016, 12:36pm

The common reasons are:

You have a cluster and did not added a system ds to the cluster
The cluster is not being monitored

Dmitry1 · September 26, 2016, 12:40pm

On this cluster - some files created already.

/var/lib/one/datastores/109/

How can I debug that?

ruben · September 26, 2016, 12:42pm

onecluster list, will show you the clusters you have

onecluster show <cluster_id> will show the vnets and ds associated to a
given cluster

Dmitry1 · September 26, 2016, 12:52pm

[root@one-sandbox ~]# onecluster list
ID NAME HOSTS VNETS DATASTORES
0 default 2 2 3

[root@one-sandbox ~]# onecluster show 0
CLUSTER 0 INFORMATION
ID : 0
NAME : default

CLUSTER TEMPLATE
RESERVED_CPU="“
RESERVED_MEM=”"

HOSTS
0
4

VNETS
0
1

DATASTORES
0
1
109
[root@one-sandbox ~]#

Dmitry1 · September 29, 2016, 11:43am

Can anyone help with it?

ruben · September 29, 2016, 2:41pm

The scheduler logs are filtering the hosts, you can find the requirements of the VM in its information onevm show

Dmitry1 · October 6, 2016, 1:49pm

[root@one-sandbox ~]# onevm show 15
VIRTUAL MACHINE 15 INFORMATION
ID : 15
NAME : ttylinux - kvm-copy-15
USER : oneadmin
GROUP : oneadmin
STATE : PENDING
LCM_STATE : LCM_INIT
RESCHED : No
START TIME : 09/22 18:05:53
END TIME : -
DEPLOY ID : -

VIRTUAL MACHINE MONITORING

PERMISSIONS
OWNER : um-
GROUP : —
OTHER : —

VM DISKS
ID DATASTORE TARGET IMAGE SIZE TYPE SAVE
0 vz hda ttylinux - kvm-copy-disk-0 -/40M file YES
1 - hdb CONTEXT -/- - -

VM NICS
ID NETWORK BRIDGE IP MAC
0 test br0 10.110.20.194 02:00:0a:6e:14:c2

SECURITY

NIC_ID NETWORK SECURITY_GROUPS
0 test 0

SECURITY GROUP TYPE PROTOCOL NETWORK RANGE
ID NAME VNET START SIZE
0 default OUTBOUND ALL
0 default INBOUND ALL

USER TEMPLATE
LOGO="images/logos/linux.png"
SCHED_MESSAGE="Thu Oct 6 14:48:14 2016 : No system datastores found to run VMs"
SCHED_REQUIREMENTS="ID=“4"”

VIRTUAL MACHINE TEMPLATE
AUTOMATIC_DS_REQUIREMENTS="“CLUSTERS/ID” = 0"
AUTOMATIC_REQUIREMENTS="(CLUSTER_ID = 0) & !(PUBLIC_CLOUD = YES)“
CLONING_TEMPLATE_ID=“5"
CONTEXT=[
DISK_ID=“1”,
ETH0_CONTEXT_FORCE_IPV4=””,
ETH0_DNS=“195.214.232.18”,
ETH0_GATEWAY=“10.110.20.1”,
ETH0_GATEWAY6="",
ETH0_IP=“10.110.20.194”,
ETH0_IP6="",
ETH0_IP6_ULA="",
ETH0_MAC=“02:00:0a:6e:14:c2”,
ETH0_MASK=“24”,
ETH0_MTU="",
ETH0_NETWORK="",
ETH0_SEARCH_DOMAIN="",
ETH0_VROUTER_IP="",
ETH0_VROUTER_IP6="",
ETH0_VROUTER_MANAGEMENT="",
NETWORK=“YES”,
SSH_PUBLIC_KEY="",
TARGET=“hdb” ]
CPU="0.1"
GRAPHICS=[
LISTEN=“0.0.0.0”,
TYPE=“VNC” ]
MEMORY="128"
TEMPLATE_ID="9"
VMID=“15”

Dmitry1 · October 6, 2016, 1:52pm

I don’t see any problems with it, what to do next?

atodorov_storpool · October 6, 2016, 2:26pm

Hi,

Judjing by the image that you have posted the system datastore is disabled. Please enable the SYSTEM datastore and it will deply the VMs. In sunstone: Storage -> Datastores -> select the SYSTEM datastore (0). There is a button with three vertical dots and triangle pointing down. Click there and select Enable.

Kind Regards,
Anton Todorov

Dmitry1 · October 6, 2016, 2:30pm

But I want to place it on datastore 109, and Image for VM is assigned to this datastore.

atodorov_storpool · October 6, 2016, 3:17pm

The image behavior is depending on the technology behind the datastore, the TM_MAD in use for both image and system datastores and so on. The system datastore is needed for the VM to work.

For your use case you should select a datastore technology and TM_MAD that are of shared type. Then the TM_MAD will create symlink to the image in the image datastore instead of placing the file in the SYSTEM one.

Kind Regards,
Anton Todorov

Dmitry1 · October 6, 2016, 3:57pm

Thank you! It works!

Topic		Replies	Views
There is no suitable system ds Community Support	2	1127	March 27, 2017
Cannot schedule VM, there is no suitable host Community Support	11	6167	October 20, 2017
New VMs stuck in PENDING - System datastore has no size Community Support	7	3656	May 8, 2020
SCHED_DS_REQUIREMENTS does not work Community Support	14	1908	December 15, 2016
Datastore (0) / host not in same cluster Community Support	7	1787	January 6, 2017

Cannot schedule VM, there is no suitable system ds

Related Topics