SOLVED Weird. I can't ping from the Truenas Scale server a Windows VM hosted by the server itself

titust1

Explorer
Joined
May 10, 2022
Messages
66
The Truenas Scale server is hosting a Windows VM. The VM obtains a DHCP address from my router, and is able to ping all the machines on the local network, except the Truenas Scale server. From the Truenas Scale server I can ping all machines on the LAN except the IP of the VM machine.
I don't get it...
Do I have to enable something on the Truenas Scale server network?
Please help
 

Samuel Tai

Never underestimate your own stupidity
Moderator
Joined
Apr 24, 2020
Messages
5,399

titust1

Explorer
Joined
May 10, 2022
Messages
66
Yes thanks
This is the short form of the above documentation:
  1. Go To Network / Edit the main Interface (NIC) / Uncheck DHCP or remove the IP from the NIC -> Apply (don't worry it's OK)
  2. In Network Interfaces Click Add to create a bridge
    1. Specify the Type: Bridge
    2. Name: br0 (if it's the first one)
    3. Uncheck DHCP
    4. Select the primary NIC as only member to that bridge
    5. Assign to the bridge the IP formerly owned by the NIC
    6. Apply
  3. Test Network Changes
  4. Important Don't forget to save changes
  5. Click on Virtualization
    1. Select VM
      1. Device / NIC Edit
      2. Bind to br0 (instead of the NIC)
      3. Apply
 

tsr966

Dabbler
Joined
Nov 12, 2019
Messages
16
I have a VM for ubuntu plex and have a similar issue. I can't mount a drive on the same Truenas Scale server. I have 4 nics on my server so can I use a different nic for this VM and solve this issue?
 

jwong858

Dabbler
Joined
Nov 25, 2022
Messages
28
Following the instructions provided by titust1, the network changes were removed after testing the network. I guess the test failed and changes were reverted. I see the errors in the syslog:

Dec 11 16:31:50 truenas ntpd[6210]: bind(19) AF_INET6 2603:8001:4f40:81:223:a4ff:fe0e:274#123 flags 0x11 failed: Cannot assign requested address
Dec 11 16:31:50 truenas ntpd[6210]: unable to create socket on enp5s0 (50) for 2603:8001:4f40:81:223:a4ff:fe0e:274#123
Dec 11 16:31:50 truenas ntpd[6210]: failed to init interface for address 2603:8001:4f40:81:223:a4ff:fe0e:274
Dec 11 16:31:50 truenas ntpd[6210]: Listen normally on 51 enp5s0 [fe80::223:a4ff:fe0e:274%3]:123
Dec 11 16:31:50 truenas ntpd[6210]: Listen normally on 52 macvtap2 [fe80::2a0:98ff:fe33:bbd6%18]:12
Dec 11 16:31:50 truenas avahi-daemon[8200]: Leaving mDNS multicast group on interface enp5s0.IPv6 with address fe80::223:a4ff:fe0e:274.
Dec 11 16:31:50 truenas avahi-daemon[8200]: Joining mDNS multicast group on interface enp5s0.IPv6 with address 2603:8001:4f40:81:223:a4ff:fe0e:274.
Dec 11 16:31:50 truenas avahi-daemon[8200]: Registering new address record for 2603:8001:4f40:81:223:a4ff:fe0e:274 on enp5s0.*.
Dec 11 16:31:50 truenas avahi-daemon[8200]: Withdrawing address record for fe80::223:a4ff:fe0e:274 on enp5s0.

Any ideas?
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703

ric

Contributor
Joined
Dec 22, 2013
Messages
180
After rebooting my Linux system, and changed the NIC to bridge, I received some error messages as shown below.

CallError​

[EFAULT] VM will not start as NIC Device: br0 device(s) are not available.

Error: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/middlewared/main.py", line 177, in call_method result = await self.middleware._call(message['method'], serviceobj, methodobj, params, app=self) File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1294, in _call return await methodobj(*prepared_call.args) File "/usr/lib/python3/dist-packages/middlewared/schema.py", line 1272, in nf return await func(*args, **kwargs) File "/usr/lib/python3/dist-packages/middlewared/schema.py", line 1140, in nf res = await f(*args, **kwargs) File "/usr/lib/python3/dist-packages/middlewared/plugins/vm/vm_lifecycle.py", line 39, in start await self.middleware.run_in_thread(self._start, vm['name']) File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1209, in run_in_thread return await self.run_in_executor(self.thread_pool_executor, method, *args, **kwargs) File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1206, in run_in_executor return await loop.run_in_executor(pool, functools.partial(method, *args, **kwargs)) File "/usr/lib/python3.9/concurrent/futures/thread.py", line 52, in run result = self.fn(*self.args, **self.kwargs) File "/usr/lib/python3/dist-packages/middlewared/plugins/vm/vm_supervisor.py", line 62, in _start self.vms[vm_name].start(vm_data=self._vm_from_name(vm_name)) File "/usr/lib/python3/dist-packages/middlewared/plugins/vm/supervisor/supervisor_base.py", line 138, in start raise CallError( middlewared.service_exception.CallError: [EFAULT] VM will not start as NIC Device: br0 device(s) are not available.
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
[EFAULT] VM will not start as NIC Device: br0 device(s) are not available.
Is that device available? (is it considered "UP" in ifconfig)
 
Top