Start: no host available?

[nasheayahu]

Afternoon, I have not started this VMs for a long while, but after login, I basically had no control of the OS, I tried "hostnamectl" and got this messages:

failed to connect to system scope bus via local transport: Connection refused?

then a moment later the OS freezes up, then I did a force-shutdown, but when trying to start it again, I get this messages:

How do I trouble shot and fix this?

Thanks!...

[DustinB]

@nasheayahu What is listed under logs?

What do you see on the VM console when it is running?

From the error message, it's possible that this VM is unable to start on your host because you may not have the CPU, RAM or disk space.

[probain]

Last time I saw that error. The resources on the host weren't enough to start the additional VM.

[nasheayahu]

@probain said:

Last time I saw that error. The resources on the host weren't enough to start the additional VM.

I believe your right, but here is the states of what is running now before I to started the idM and NTP VMs:

Here is the settings for the IdM (started first):

Here is the settings for the NTP (started second):

after losing control of the NTP, then I just discovered I lost control of the IdM, and my pfSenseLab console:

however, I still have control over the pfSenseLab WebGUI via Remmina, but I can not ssh into the console from my Workstation:

All the other VMs still have functionality.

[john.c]

This post is deleted!

[probain]

Other ideas I get are:

PCI passthrough on any of these?
Are they cloned from each other, or setup from scratch?
Afinity host / load balancing?

What happens if you migrate to the other pool?

[olivierlambert]

Start the VM with xe vm-start uuid=<VM UUID> and see the error message there.