January 1, 20197 yr ok background time I'm running a small network lab off my System and as such i have 12 VMS doing various tasks the plan is set and have just finished creating all the VM's and they were all ruining fine together then after shutting all the VM's down to change some network settings on the platform (changing the primary DNS to the internal one) i went to start all my VM's and started to run into issues getting them all going the VM's i have are as follows Database Mail server Web Server NS1 NS2 DHCP/NTP IP - PBX jumpbox GUI - Client analog Glances Manager Dev and right now i have all of the first group except the IP-PABX running and i cant seem to start anything else. OK oddly enough I just tried to start one of the stopped servers to get a copy of the error message i get and i have managed to start two more so it looks like if im paitent ill get them all started again. this is not ideal however as i would like them all to auto start well except perhaps the dev and GUI client. the error i am getting is internal error: qemu unexpectedly closed the monitor: 2019-01-01T17:11:45.632075Z qemu-system-x86_64: -vnc 0.0.0.0:9,websocket=5703: Failed to start VNC server: Failed to find an available port: Address already in use error Screenshot so my question is dose anyone else have these issues with a larger number of VM's. and as they all seem to be related to the VNC ports is there a way i can tell it not to use VNC As only one of these has a GUI and all the others are accessed and maintained over SSH via the bastion jumpbox. or is this just a case of only having the important servers DHCP, NS1, jumpbox, WEB, and perhaps Database set to auto start and then slowly start the others
Archived
This topic is now archived and is closed to further replies.