Trouble Creating Ubuntu VM on FreeNAS 11

Status
Not open for further replies.

Grinas

Contributor
Joined
May 4, 2017
Messages
174
I had the same problem and TightVNC was the only VNC viewer that would work. It also worked on windows very well
 

siddmon

Cadet
Joined
Jul 15, 2017
Messages
3
I have this same issue.
I'm running FreeNas 11 RC
I created a ZVol under my ZPol, I can see a VNC port.
When I click start vm, says VM started and once the page refreshes it stays as STOPPED and VNC or TightVNC cannot connect.


Console:
Jul 18 20:20:15 myfreenas tap0: Ethernet address: 00:bd:4b:80:17:00
Jul 18 20:20:15 myfreenas kernel: em0: link state changed to DOWN
Jul 18 20:20:15 myfreenas kernel: em0: link state changed to DOWN
Jul 18 20:20:15 myfreenas kernel: bridge0: link state changed to DOWN
Jul 18 20:20:15 myfreenas kernel: bridge0: link state changed to DOWN
Jul 18 20:20:15 myfreenas kernel: tap0: promiscuous mode enabled
Jul 18 20:20:15 myfreenas kernel: bridge0: link state changed to UP
Jul 18 20:20:15 myfreenas kernel: bridge0: link state changed to UP
Jul 18 20:20:15 myfreenas bridge0: can't disable some capabilities on em0: 0x1
Jul 18 20:20:19 myfreenas dhclient: New IP Address (em0): 192.168.1.175
Jul 18 20:20:19 myfreenas dhclient: New Subnet Mask (em0): 255.255.255.0
Jul 18 20:20:19 myfreenas dhclient: New Broadcast Address (em0): 192.168.1.255
Jul 18 20:20:19 myfreenas dhclient: New Routers (em0): 192.168.1.1
Jul 18 20:20:19 myfreenas kernel: em0: link state changed to UP
Jul 18 20:20:19 myfreenas kernel: em0: link state changed to UP
Jul 18 20:21:17 myfreenas tap0: Ethernet address: 00:bd:88:72:18:00
Jul 18 20:21:17 myfreenas kernel: em0: link state changed to DOWN
Jul 18 20:21:17 myfreenas kernel: em0: link state changed to DOWN
Jul 18 20:21:17 myfreenas kernel: bridge0: link state changed to DOWN
Jul 18 20:21:17 myfreenas kernel: bridge0: link state changed to DOWN
Jul 18 20:21:17 myfreenas kernel: tap0: promiscuous mode enabled
Jul 18 20:21:17 myfreenas kernel: bridge0: link state changed to UP
Jul 18 20:21:17 myfreenas kernel: bridge0: link state changed to UP
Jul 18 20:21:17 myfreenas bridge0: can't disable some capabilities on em0: 0x1
Jul 18 20:21:21 myfreenas dhclient: New IP Address (em0): 192.168.1.175
Jul 18 20:21:21 myfreenas dhclient: New Subnet Mask (em0): 255.255.255.0
Jul 18 20:21:21 myfreenas dhclient: New Broadcast Address (em0): 192.168.1.255
Jul 18 20:21:21 myfreenas dhclient: New Routers (em0): 192.168.1.1
Jul 18 20:21:21 myfreenas kernel: em0: link state changed to UP
Jul 18 20:21:21 myfreenas kernel: em0: link state changed to UP
Jul 18 20:24:25 myfreenas tap0: Ethernet address: 00:bd:6e:50:1b:00
Jul 18 20:24:25 myfreenas kernel: em0: link state changed to DOWN
Jul 18 20:24:25 myfreenas kernel: em0: link state changed to DOWN
Jul 18 20:24:25 myfreenas kernel: bridge0: link state changed to DOWN
Jul 18 20:24:25 myfreenas kernel: bridge0: link state changed to DOWN
Jul 18 20:24:25 myfreenas kernel: tap0: promiscuous mode enabled
Jul 18 20:24:25 myfreenas kernel: bridge0: link state changed to UP
Jul 18 20:24:25 myfreenas kernel: bridge0: link state changed to UP
Jul 18 20:24:25 myfreenas bridge0: can't disable some capabilities on em0: 0x1
Jul 18 20:24:29 myfreenas dhclient: New IP Address (em0): 192.168.1.175
Jul 18 20:24:29 myfreenas dhclient: New Subnet Mask (em0): 255.255.255.0
Jul 18 20:24:29 myfreenas dhclient: New Broadcast Address (em0): 192.168.1.255
Jul 18 20:24:29 myfreenas dhclient: New Routers (em0): 192.168.1.1
Jul 18 20:24:29 myfreenas kernel: em0: link state changed to UP
Jul 18 20:24:29 myfreenas kernel: em0: link state changed to UP
Jul 18 20:24:40 myfreenas tap0: Ethernet address: 00:bd:db:8b:1b:00
Jul 18 20:24:40 myfreenas kernel: em0: link state changed to DOWN
Jul 18 20:24:40 myfreenas kernel: em0: link state changed to DOWN
Jul 18 20:24:40 myfreenas kernel: bridge0: link state changed to DOWN
Jul 18 20:24:40 myfreenas kernel: bridge0: link state changed to DOWN
Jul 18 20:24:40 myfreenas kernel: tap0: promiscuous mode enabled
Jul 18 20:24:40 myfreenas kernel: bridge0: link state changed to UP
Jul 18 20:24:40 myfreenas kernel: bridge0: link state changed to UP
Jul 18 20:24:40 myfreenas bridge0: can't disable some capabilities on em0: 0x1
Jul 18 20:24:44 myfreenas kernel: em0: link state changed to UP
Jul 18 20:24:44 myfreenas kernel: em0: link state changed to UP
Jul 18 20:24:44 myfreenas dhclient: New IP Address (em0): 192.168.1.175
Jul 18 20:24:44 myfreenas dhclient: New Subnet Mask (em0): 255.255.255.0
Jul 18 20:24:44 myfreenas dhclient: New Broadcast Address (em0): 192.168.1.255
Jul 18 20:24:44 myfreenas dhclient: New Routers (em0): 192.168.1.1
Jul 18 20:25:00 myfreenas tap0: Ethernet address: 00:bd:5c:db:1b:00
Jul 18 20:25:00 myfreenas kernel: em0: link state changed to DOWN
Jul 18 20:25:00 myfreenas kernel: em0: link state changed to DOWN
Jul 18 20:25:00 myfreenas kernel: bridge0: link state changed to DOWN
Jul 18 20:25:00 myfreenas kernel: bridge0: link state changed to DOWN
Jul 18 20:25:00 myfreenas kernel: tap0: promiscuous mode enabled
Jul 18 20:25:01 myfreenas kernel: bridge0: link state changed to UP
Jul 18 20:25:01 myfreenas kernel: bridge0: link state changed to UP
Jul 18 20:25:01 myfreenas bridge0: can't disable some capabilities on em0: 0x1
Jul 18 20:25:04 myfreenas kernel: em0: link state changed to UP
Jul 18 20:25:04 myfreenas kernel: em0: link state changed to UP
Jul 18 20:25:04 myfreenas dhclient: New IP Address (em0): 192.168.1.175
Jul 18 20:25:04 myfreenas dhclient: New Subnet Mask (em0): 255.255.255.0
Jul 18 20:25:04 myfreenas dhclient: New Broadcast Address (em0): 192.168.1.255
Jul 18 20:25:04 myfreenas dhclient: New Routers (em0): 192.168.1.1


Ubuntu iso: ubuntu-16.04.2-desktop-amd64.iso

The issue is with the VM not starting at all, I know I have to do some extra configuration with grub to be able to install it after the VM starts.

TIA
 

mike360x1

Contributor
Joined
Dec 25, 2012
Messages
107
How much ram did you allocate to your virtual machine? Did you enter it in assuming it was GB rather than MB?
 

siddmon

Cadet
Joined
Jul 15, 2017
Messages
3
How much ram did you allocate to your virtual machine? Did you enter it in assuming it was GB rather than MB?
I did read the whole thread, the number seems to be in MB, I assigned 3000MB which is close to 3GB from the 16GB available.
 

Grinas

Contributor
Joined
May 4, 2017
Messages
174
have you tired running the vm via the command line and seeing the error you get. i cant remeber the exact command off the top of my head to run via cmdline but its something like below.

Code:
bhyve --run --vm=<vmName>


use the man pages to find the exact command
 

siddmon

Cadet
Joined
Jul 15, 2017
Messages
3
have you tired running the vm via the command line and seeing the error you get. i cant remeber the exact command off the top of my head to run via cmdline but its something like below.

Code:
bhyve --run --vm=<vmName>


use the man pages to find the exact command
Here is the output:

Code:
[root@myfreenas ~]# bhyve --run --vm=<ubuntu>																					   
bash: syntax error near unexpected token `newline'																				 
[root@myfreenas ~]#																												 


[root@myfreenas ~]# bhyve --run --vm=ubuntu																						 
bhyve: illegal option -- -																										 
Usage: bhyve [-abehuwxACHPSWY] [-c vcpus] [-g <gdb port>] [-l <lpc>]																
			 [-m mem] [-p vcpu:hostcpu] [-s <pci>] [-U uuid] <vm>																   
	   -a: local apic is in xAPIC mode (deprecated)																				 
	   -A: create ACPI tables																									   
	   -c: # cpus (default 1)																									   
	   -C: include guest memory in core file																						
	   -e: exit on unhandled I/O access																							 
	   -g: gdb port																												 
	   -h: help																													 
	   -H: vmexit from the guest on hlt																							 
	   -l: LPC device configuration																								 
	   -m: memory size in MB																										
	   -p: pin 'vcpu' to 'hostcpu'																								 
	   -P: vmexit from the guest on pause																						   
	   -s: <slot,driver,configinfo> PCI slot config																				 
	   -S: guest memory cannot be swapped																						   
	   -u: RTC keeps UTC time																									   
	   -U: uuid																													 
	   -w: ignore unimplemented MSRs																								
	   -W: force virtio to use single-vector MSI																					
	   -x: local apic is in x2APIC mode																							 
	   -Y: disable MPtable generation 



Code:
[root@myfreenas ~]# bhyve --run ubuntu																							
bhyve: illegal option -- -																										
Usage: bhyve [-abehuwxACHPSWY] [-c vcpus] [-g <gdb port>] [-l <lpc>]																
			 [-m mem] [-p vcpu:hostcpu] [-s <pci>] [-U uuid] <vm>																  
	   -a: local apic is in xAPIC mode (deprecated)																				
	   -A: create ACPI tables																									  
	   -c: # cpus (default 1)																									  
	   -C: include guest memory in core file																						
	   -e: exit on unhandled I/O access																							
	   -g: gdb port																												
	   -h: help																													
	   -H: vmexit from the guest on hlt																							
	   -l: LPC device configuration																								
	   -m: memory size in MB																										
	   -p: pin 'vcpu' to 'hostcpu'																								
	   -P: vmexit from the guest on pause																						  
	   -s: <slot,driver,configinfo> PCI slot config																				
	   -S: guest memory cannot be swapped																						  
	   -u: RTC keeps UTC time																									  
	   -U: uuid																													
	   -w: ignore unimplemented MSRs																								
	   -W: force virtio to use single-vector MSI																					
	   -x: local apic is in x2APIC mode																							
	   -Y: disable MPtable generation	 
 

Brer

Explorer
Joined
Mar 2, 2017
Messages
63
Here is the output:

Code:
[root@myfreenas ~]# bhyve --run --vm=<ubuntu>																					  
bash: syntax error near unexpected token `newline'																				
[root@myfreenas ~]#																												


[root@myfreenas ~]# bhyve --run --vm=ubuntu																						
bhyve: illegal option -- -																										
Usage: bhyve [-abehuwxACHPSWY] [-c vcpus] [-g <gdb port>] [-l <lpc>]																
			 [-m mem] [-p vcpu:hostcpu] [-s <pci>] [-U uuid] <vm>																  
	   -a: local apic is in xAPIC mode (deprecated)																				
	   -A: create ACPI tables																									  
	   -c: # cpus (default 1)																									  
	   -C: include guest memory in core file																						
	   -e: exit on unhandled I/O access																							
	   -g: gdb port																												
	   -h: help																													
	   -H: vmexit from the guest on hlt																							
	   -l: LPC device configuration																								
	   -m: memory size in MB																										
	   -p: pin 'vcpu' to 'hostcpu'																								
	   -P: vmexit from the guest on pause																						  
	   -s: <slot,driver,configinfo> PCI slot config																				
	   -S: guest memory cannot be swapped																						  
	   -u: RTC keeps UTC time																									  
	   -U: uuid																													
	   -w: ignore unimplemented MSRs																								
	   -W: force virtio to use single-vector MSI																					
	   -x: local apic is in x2APIC mode																							
	   -Y: disable MPtable generation



Code:
[root@myfreenas ~]# bhyve --run ubuntu																							
bhyve: illegal option -- -																										
Usage: bhyve [-abehuwxACHPSWY] [-c vcpus] [-g <gdb port>] [-l <lpc>]																
			 [-m mem] [-p vcpu:hostcpu] [-s <pci>] [-U uuid] <vm>																 
	   -a: local apic is in xAPIC mode (deprecated)																				
	   -A: create ACPI tables																									 
	   -c: # cpus (default 1)																									 
	   -C: include guest memory in core file																						
	   -e: exit on unhandled I/O access																							
	   -g: gdb port																												
	   -h: help																													
	   -H: vmexit from the guest on hlt																							
	   -l: LPC device configuration																								
	   -m: memory size in MB																										
	   -p: pin 'vcpu' to 'hostcpu'																								
	   -P: vmexit from the guest on pause																						 
	   -s: <slot,driver,configinfo> PCI slot config																				
	   -S: guest memory cannot be swapped																						 
	   -u: RTC keeps UTC time																									 
	   -U: uuid																													
	   -w: ignore unimplemented MSRs																								
	   -W: force virtio to use single-vector MSI																					
	   -x: local apic is in x2APIC mode																							
	   -Y: disable MPtable generation	 

There is no --run option which is clear from the Usage options, you need to run something similar to this, I got my VM up and running from the following command, replace <nasrootfolder> and <pathtodataset> with your nas root folder and dataset holding your VM image.

Code:
bhyve -A -P -H -c 1 -m 2000 \
	-s 0:0,hostbridge \
	-s 31,lpc \
	-l com1,/dev/nmdm1A \
	-l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd \
	-s 3,virtio-net,tap1 \
	-s 29,fbuf,tcp=0.0.0.0:5902,w=1024,h=768,wait \
	-s 30,xhci,tablet \
	-s 4,ahci-hd,/dev/zvol/<nasrootfolder>/<pathtodataset> Ubuntu
 
Status
Not open for further replies.
Top