VM Started but State:stopped

Status
Not open for further replies.

vincent_y79

Cadet
Joined
Jul 19, 2017
Messages
6
I'm trying to create a VM, it says vm started but state never runs and stays stopped (tried with Wait to boot enabled and disabled) . I don't know if my cpu is too old but I think I remember running a windows VM on a previous version (9.3? maybe I'm remembering wrong). Not sure what else to provide or how else to describe the problem.

System Information
Hostname freenas.local Edit
Build FreeNAS-11.0-U4 (54848d13b)
Platform AMD Phenom(tm) 9950 Quad-Core Processor
Memory 8154MB
System Time Sun Nov 26 13:57:18 EST 2017
Uptime 1:57PM up 14:46, 2 users
Load Average 1.06, 1.00, 1.08

/var/log/messages, the only thing that shows up when I attempt to start is below
Nov 26 13:16:17 freenas tap0: Ethernet address: 00:bd:2b:37:fc:00
Nov 26 13:16:17 freenas kernel: tap0: promiscuous mode enabled

Result of grep POPCNT /var/run/dmesg.boot
Features2=0x802009<SSE3,MON,CX16,POPCNT>
 
D

dlavigne

Guest
Were you able to resolve this? If not, upgrading to 11.1 when it's released may resolve it as it has a lot of VM fixes and improvements.
 

maconde

Cadet
Joined
Feb 1, 2018
Messages
7
I have the same error with 11.1-U1

Feb 1 13:02:40 das-freenas tap1: Ethernet address: 00:bd:35:e3:10:01
Feb 1 13:02:40 das-freenas kernel: tap1: promiscuous mode enabled
 
D

dlavigne

Guest
If you create a report at bugs.freenas.org, post the issue number here.
 

maconde

Cadet
Joined
Feb 1, 2018
Messages
7
If you create a report at bugs.freenas.org, post the issue number here.

I have not reported the error because I think it is a problem with the network configuration of my server, I am trying to see what it is, to avoid it being an error on my part. I reinstalled the FreeNAS and after configuring the network by the console using the wizard that brings FreeNAS when starting, the VM that I created now does run, but they do not have a network connection.
 
Last edited by a moderator:
Status
Not open for further replies.
Top