I've created an Centos7 VM in this updated Fedora-20 box. NFS always works without a hitch however I can't mount the server from the VM.
[root@localhost bobg]# mount 192.168.1.8:/home/bobg/ /mnt/HOME1/ mount.nfs: access denied by server while mounting 192.168.1.8:/home/bobg/
Nothing changes, the hardware is a constant, but it says the server "denies access" and I can't see why, where can I be going wrong? Ssh, sftp, and ping all work from the VM, I just can't mount it from NFS.
Any help appreciated,
Bob
Once upon a time, Bob Goodwin - Zuni, Virginia, USA bobgoodwin@wildblue.net said:
I've created an Centos7 VM in this updated Fedora-20 box. NFS always works without a hitch however I can't mount the server from the VM.
[root@localhost bobg]# mount 192.168.1.8:/home/bobg/ /mnt/HOME1/ mount.nfs: access denied by server while mounting 192.168.1.8:/home/bobg/
Possibly NFSv4 vs. NFSv3? RHEL/CentOS 6 and earlier (and Fedora before around 17 IIRC) default to NFSv3 mounts, while newer stuff defaults to NFSv4.
Try adding "-o nfsvers=3".
On 23.07.2014 20:21, Chris Adams wrote:
Once upon a time, Bob Goodwin - Zuni, Virginia, USA bobgoodwin@wildblue.net said:
I've created an Centos7 VM in this updated Fedora-20 box. NFS always works without a hitch however I can't mount the server from the VM.
[root@localhost bobg]# mount 192.168.1.8:/home/bobg/ /mnt/HOME1/ mount.nfs: access denied by server while mounting 192.168.1.8:/home/bobg/
Possibly NFSv4 vs. NFSv3? RHEL/CentOS 6 and earlier (and Fedora before around 17 IIRC) default to NFSv3 mounts, while newer stuff defaults to NFSv4.
Try adding "-o nfsvers=3".
/etc/sysconfig/nfs RPCNFSDARGS="-d -s"
systemctl restart nfs-server journalctl -f --full
nfsd fan club
On 07/23/14 15:06, poma wrote:
/etc/sysconfig/nfs RPCNFSDARGS="-d -s"
systemctl restart nfs-server journalctl -f --full
nfsd fan club
Ok, not sure what that did but now it's mounted. Hopefully it will work after a reboot.
Thank you,
Bob
On 23.07.2014 22:59, Bob Goodwin - Zuni, Virginia, USA wrote:
On 07/23/14 15:06, poma wrote:
/etc/sysconfig/nfs RPCNFSDARGS="-d -s"
systemctl restart nfs-server journalctl -f --full
nfsd fan club
Ok, not sure what that did but now it's mounted. Hopefully it will work after a reboot.
Thank you,
Bob
First you adjust the debug logging directed to syslog, then it is applied, and with the journalctl, you can monitor server events. ;)
poma
On 07/23/14 17:28, poma wrote:
First you adjust the debug logging directed to syslog, then it is applied, and with the journalctl, you can monitor server events. ;)
poma
Well this appears to be the area of interest however I don't know how to interpret it?
Jul 23 16:51:45 localhost.localdomain systemd[1]: Starting NFS Mount Daemon... Jul 23 16:51:45 localhost.localdomain systemd[1]: Started NFS Mount Daemon. Jul 23 16:51:45 localhost.localdomain systemd[1]: Starting NFS Server... Jul 23 16:51:45 localhost.localdomain rpc.mountd[5596]: Version 1.3.0 starting Jul 23 16:51:45 localhost.localdomain kernel: NFSD: starting 90-second grace period (net ffffffff819a09c0) Jul 23 16:51:45 localhost.localdomain systemd[1]: Started NFS Server. Jul 23 16:51:45 localhost.localdomain systemd[1]: Starting NFSv4 ID-name mapping daemon... Jul 23 16:51:45 localhost.localdomain systemd[1]: Starting NFS Remote Quota Server... Jul 23 16:51:45 localhost.localdomain systemd[1]: Started NFS Remote Quota Server. Jul 23 16:51:45 localhost.localdomain systemd[1]: Started NFSv4 ID-name mapping daemon. Jul 23 16:54:04 localhost.localdomain dhclient[1081]: DHCPREQUEST on eth0 to 192.168.122.1 port 67 (xid=0xa15c2e7) Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: DHCPREQUEST on eth0 to 192.168.122.1 port 67 (xid=0xa15c2e7) Jul 23 16:54:04 localhost.localdomain dhclient[1081]: DHCPACK from 192.168.122.1 (xid=0xa15c2e7) Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: DHCPACK from 192.168.122.1 (xid=0xa15c2e7) Jul 23 16:54:04 localhost.localdomain dhclient[1081]: bound to 192.168.122.14 -- renewal in 1474 seconds. Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: bound to 192.168.122.14 -- renewal in 1474 seconds. Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: <info> (eth0): DHCPv4 state changed renew -> renew Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: <info> address 192.168.122.14 Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: <info> plen 24 (255.255.255.0) Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: <info> gateway 192.168.122.1 Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: <info> server identifier 192.168.122.1 Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: <info> lease time 3600 Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: <info> nameserver '192.168.122.1' Jul 23 16:54:04 localhost.localdomain dbus[665]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher Jul 23 16:54:04 localhost.localdomain dbus-daemon[665]: dbus[665]: [system] Activating via systemd: service name='org.freedes Jul 23 16:54:04 localhost.localdomain systemd[1]: Starting Network Manager Script Dispatcher Service... Jul 23 16:54:04 localhost.localdomain dbus-daemon[665]: dbus[665]: [system] Successfully activated service 'org.freedesktop.n Jul 23 16:54:04 localhost.localdomain dbus[665]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
On 07/23/2014 04:14 PM, Bob Goodwin - Zuni, Virginia, USA issued this missive:
On 07/23/14 17:28, poma wrote:
First you adjust the debug logging directed to syslog, then it is applied, and with the journalctl, you can monitor server events. ;)
poma
Well this appears to be the area of interest however I don't know how to interpret it?
Jul 23 16:51:45 localhost.localdomain systemd[1]: Starting NFS Mount Daemon... Jul 23 16:51:45 localhost.localdomain systemd[1]: Started NFS Mount Daemon. Jul 23 16:51:45 localhost.localdomain systemd[1]: Starting NFS Server... Jul 23 16:51:45 localhost.localdomain rpc.mountd[5596]: Version 1.3.0 starting Jul 23 16:51:45 localhost.localdomain kernel: NFSD: starting 90-second grace period (net ffffffff819a09c0) Jul 23 16:51:45 localhost.localdomain systemd[1]: Started NFS Server. Jul 23 16:51:45 localhost.localdomain systemd[1]: Starting NFSv4 ID-name mapping daemon... Jul 23 16:51:45 localhost.localdomain systemd[1]: Starting NFS Remote Quota Server... Jul 23 16:51:45 localhost.localdomain systemd[1]: Started NFS Remote Quota Server. Jul 23 16:51:45 localhost.localdomain systemd[1]: Started NFSv4 ID-name mapping daemon. Jul 23 16:54:04 localhost.localdomain dhclient[1081]: DHCPREQUEST on eth0 to 192.168.122.1 port 67 (xid=0xa15c2e7) Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: DHCPREQUEST on eth0 to 192.168.122.1 port 67 (xid=0xa15c2e7) Jul 23 16:54:04 localhost.localdomain dhclient[1081]: DHCPACK from 192.168.122.1 (xid=0xa15c2e7) Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: DHCPACK from 192.168.122.1 (xid=0xa15c2e7) Jul 23 16:54:04 localhost.localdomain dhclient[1081]: bound to 192.168.122.14 -- renewal in 1474 seconds. Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: bound to 192.168.122.14 -- renewal in 1474 seconds. Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: <info> (eth0): DHCPv4 state changed renew -> renew Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: <info> address 192.168.122.14 Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: <info> plen 24 (255.255.255.0) Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: <info> gateway 192.168.122.1 Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: <info> server identifier 192.168.122.1 Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: <info> lease time 3600 Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: <info> nameserver '192.168.122.1' Jul 23 16:54:04 localhost.localdomain dbus[665]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher Jul 23 16:54:04 localhost.localdomain dbus-daemon[665]: dbus[665]: [system] Activating via systemd: service name='org.freedes Jul 23 16:54:04 localhost.localdomain systemd[1]: Starting Network Manager Script Dispatcher Service... Jul 23 16:54:04 localhost.localdomain dbus-daemon[665]: dbus[665]: [system] Successfully activated service 'org.freedesktop.n Jul 23 16:54:04 localhost.localdomain dbus[665]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Bob, get on the NFS server and verify that it's allowing mounts from the DHCP domain. It appears your VM is using DHCP to get an IP and it may be that your NFS server isn't exporting to the network or IP your client got via DHCP.
The fact you got it mounted this time may just indicate that THIS TIME you got an IP allowed by the server. Next time, you may not be so lucky. :-/ ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - Millihelen (n): The amount of beauty required to launch one ship. - ----------------------------------------------------------------------
On 24.07.2014 01:23, Rick Stevens wrote:
On 07/23/2014 04:14 PM, Bob Goodwin - Zuni, Virginia, USA issued this missive:
On 07/23/14 17:28, poma wrote:
First you adjust the debug logging directed to syslog, then it is applied, and with the journalctl, you can monitor server events. ;)
poma
Well this appears to be the area of interest however I don't know how to interpret it?
Jul 23 16:51:45 localhost.localdomain systemd[1]: Starting NFS Mount Daemon... Jul 23 16:51:45 localhost.localdomain systemd[1]: Started NFS Mount Daemon. Jul 23 16:51:45 localhost.localdomain systemd[1]: Starting NFS Server... Jul 23 16:51:45 localhost.localdomain rpc.mountd[5596]: Version 1.3.0 starting Jul 23 16:51:45 localhost.localdomain kernel: NFSD: starting 90-second grace period (net ffffffff819a09c0) Jul 23 16:51:45 localhost.localdomain systemd[1]: Started NFS Server. Jul 23 16:51:45 localhost.localdomain systemd[1]: Starting NFSv4 ID-name mapping daemon... Jul 23 16:51:45 localhost.localdomain systemd[1]: Starting NFS Remote Quota Server... Jul 23 16:51:45 localhost.localdomain systemd[1]: Started NFS Remote Quota Server. Jul 23 16:51:45 localhost.localdomain systemd[1]: Started NFSv4 ID-name mapping daemon. Jul 23 16:54:04 localhost.localdomain dhclient[1081]: DHCPREQUEST on eth0 to 192.168.122.1 port 67 (xid=0xa15c2e7) Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: DHCPREQUEST on eth0 to 192.168.122.1 port 67 (xid=0xa15c2e7) Jul 23 16:54:04 localhost.localdomain dhclient[1081]: DHCPACK from 192.168.122.1 (xid=0xa15c2e7) Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: DHCPACK from 192.168.122.1 (xid=0xa15c2e7) Jul 23 16:54:04 localhost.localdomain dhclient[1081]: bound to 192.168.122.14 -- renewal in 1474 seconds. Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: bound to 192.168.122.14 -- renewal in 1474 seconds. Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: <info> (eth0): DHCPv4 state changed renew -> renew Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: <info> address 192.168.122.14 Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: <info> plen 24 (255.255.255.0) Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: <info> gateway 192.168.122.1 Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: <info> server identifier 192.168.122.1 Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: <info> lease time 3600 Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: <info> nameserver '192.168.122.1' Jul 23 16:54:04 localhost.localdomain dbus[665]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher Jul 23 16:54:04 localhost.localdomain dbus-daemon[665]: dbus[665]: [system] Activating via systemd: service name='org.freedes Jul 23 16:54:04 localhost.localdomain systemd[1]: Starting Network Manager Script Dispatcher Service... Jul 23 16:54:04 localhost.localdomain dbus-daemon[665]: dbus[665]: [system] Successfully activated service 'org.freedesktop.n Jul 23 16:54:04 localhost.localdomain dbus[665]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Bob, get on the NFS server and verify that it's allowing mounts from the DHCP domain. It appears your VM is using DHCP to get an IP and it may be that your NFS server isn't exporting to the network or IP your client got via DHCP.
The fact you got it mounted this time may just indicate that THIS TIME you got an IP allowed by the server. Next time, you may not be so lucky. :-/
192.168.122.1 could be DHCP server on Tomato, 192.168.122.14 could be DHCP client & NFS server on Fedora 20 host machine, not NFS client on Centos7 VM. However Bob can set up a Static DHCP on Tomato if it is, http://en.wikibooks.org/wiki/Tomato_Firmware/Menu_Reference#Static_DHCP so DHCP can be excluded from the context.
nfsd fan club
On 07/23/14 19:23, Rick Stevens wrote:
Bob, get on the NFS server and verify that it's allowing mounts from the DHCP domain. It appears your VM is using DHCP to get an IP and it may be that your NFS server isn't exporting to the network or IP your client got via DHCP.
The fact you got it mounted this time may just indicate that THIS TIME you got an IP allowed by the server. Next time, you may not be so lucky. :-/
- Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com -
I have a Cisco E3000 router using the Tomato version of DD-WRT which is set up to assign dhcp addresses to everything in the 192.168.1 xxx range.
However the VM shows 192.168.122.14, what is that, how would I deal with it with the present net assignments, I have a ton of devices assigned by dhcp as it is? Obviously things are happening that I haven't seen before and don't understand.
Everything appears to have survived a reboot this morning so for the moment I have no recognized problems ...
Tnx,
Bob
[root@localhost Downloads]# ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.122.14 netmask 255.255.255.0 broadcast 192.168.122.255 inet6 fe80::5054:ff:fedc:de35 prefixlen 64 scopeid 0x20<link> ether 52:54:00:dc:de:35 txqueuelen 1000 (Ethernet) RX packets 36637 bytes 47030975 (44.8 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 20354 bytes 2160974 (2.0 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 0 (Local Loopback) RX packets 8 bytes 764 (764.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 8 bytes 764 (764.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
On 24.07.2014 17:00, Bob Goodwin - Zuni, Virginia, USA wrote:
I have a Cisco E3000 router using the Tomato version of DD-WRT which is set up to assign dhcp addresses to everything in the 192.168.1 xxx range.
However the VM shows 192.168.122.14, what is that, how would I deal with it with the present net assignments, I have a ton of devices assigned by dhcp as it is? Obviously things are happening that I haven't seen before and don't understand.
So after all, it was a journal from Centos7 VM - NFS client, while I expected to be from Fedora 20 host - NFS server? :)
unexpected fan club
On 07/24/14 11:23, poma wrote:
So after all, it was a journal from Centos7 VM - NFS client, while I expected to be from Fedora 20 host - NFS server? :)
unexpected fan club
Ok, then I suppose the question is how do I make the VM conform to the present network assignments scheme? Or can't I, maybe don't need to? It seems to be working despite my confusion!
Bob
On 24.07.2014 17:36, Bob Goodwin - Zuni, Virginia, USA wrote:
On 07/24/14 11:23, poma wrote:
So after all, it was a journal from Centos7 VM - NFS client, while I expected to be from Fedora 20 host - NFS server? :)
unexpected fan club
Ok, then I suppose the question is how do I make the VM conform to the present network assignments scheme? Or can't I, maybe don't need to? It seems to be working despite my confusion!
Bob
As Chris mentioned, are you running Centos7 VM by VirtualBox, Virtual Machine Manager/libvirt/KVM/QEMU or VMware Workstation?
poma
On 07/24/14 11:48, poma wrote:
As Chris mentioned, are you running Centos7 VM by VirtualBox, Virtual Machine Manager/libvirt/KVM/QEMU or VMware Workstation?
poma
I am ashamed to admit that I could not get VirtualBox to install the Centos7 I had. VMware was a waste of money for someone running Fedora since the ordinary user would find it impossible to keep up with the kernel updates, that still irks me!
Virt-manager installed in F-20 via yum worked without any trouble.
Part of my earlier problem was that due to a slow connection the night I wanted to download Centos I had to give up on the full version and took the smaller Centos Live, next night things were running at full speed and I got the 4 GB DVD version that I have running now. My Viasat usage is limited except between midnight and five so that's the optimal time for such things, it depends on where I stand in usage for the month.
Bob
On 24.07.2014 18:20, Bob Goodwin - Zuni, Virginia, USA wrote:
On 07/24/14 11:48, poma wrote:
As Chris mentioned, are you running Centos7 VM by VirtualBox, Virtual Machine Manager/libvirt/KVM/QEMU or VMware Workstation?
poma
I am ashamed to admit that I could not get VirtualBox to install the Centos7 I had. VMware was a waste of money for someone running Fedora since the ordinary user would find it impossible to keep up with the kernel updates, that still irks me!
Won't get fooled again, lessons learned, right. ;)
Virt-manager installed in F-20 via yum worked without any trouble.
Super duper.
Part of my earlier problem was that due to a slow connection the night I wanted to download Centos I had to give up on the full version and took the smaller Centos Live, next night things were running at full speed and I got the 4 GB DVD version that I have running now. My Viasat usage is limited except between midnight and five so that's the optimal time for such things, it depends on where I stand in usage for the month.
Bob
Eine kleine Nachtmusik. :)
Bob, this way you'll be able to set your network in Fedora 21 host, with slight differences in the configuration with respect to the systemd version. Make note, networkd - bridge!
~~ /etc/systemd/network/bridge0.netdev [NetDev] Name=bridge0 Kind=bridge ~~ /etc/systemd/network/bridge0dhcp4.network [Match] Name=bridge0
[Network] DHCP=v4 ~~ /etc/systemd/network/eth2bridge0.network [Match] Name=eth2
[Network] Bridge=bridge0 ~~
# brctl show bridge name bridge id STP enabled interfaces bridge0 8000.001234567890 no eth2
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# journalctl -b -u systemd-networkd -o cat | grep -v DBus Starting Network Service... timestamp of '/usr/lib/systemd/network' changed bridge0 : loaded bridge sd-rtnl: discarding 20 bytes of incoming message eth2 : link 4 added lo : link 1 added bridge0 : created bridge0 : link state is up-to-date bridge0 : found matching network '/etc/systemd/network/bridge0dhcp4.network' eth2 : found matching network '/etc/systemd/network/eth2bridge0.network' bridge0 : enslaving link 'eth2' lo : unmanaged lo : added address: ::1/128 lo : added address: 127.0.0.1/8 bridge0 : flags change: +UP eth2 : flags change: +UP eth2 : flags change: +LOWER_UP +RUNNING DHCP CLIENT (0x927e3a57): T2 expires in 8min 44.389451s bridge0 : setting addresses bridge0 : added address: 192.168.2.40/24 bridge0 : addresses set bridge0 : setting routes bridge0 : routes set bridge0 : link configured eth2 : added address: fe80::212:34ff:fe56:7830/64 bridge0 : added address: fe80::212:34ff:fe56:7890/64
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/etc/libvirt/qemu/centos7.xml
... <interface type='bridge'> ... <source bridge='bridge0'/> <model type='virtio'/> ... </interface> ...
fedora fan club
On 07/24/14 18:09, poma wrote:
On 24.07.2014 18:20, Bob Goodwin - Zuni, Virginia, USA wrote:
On 07/24/14 11:48, poma wrote:
As Chris mentioned, are you running Centos7 VM by VirtualBox, Virtual Machine Manager/libvirt/KVM/QEMU or VMware Workstation?
poma
I am ashamed to admit that I could not get VirtualBox to install the Centos7 I had. VMware was a waste of money for someone running Fedora since the ordinary user would find it impossible to keep up with the kernel updates, that still irks me!
Won't get fooled again, lessons learned, right. ;)
Virt-manager installed in F-20 via yum worked without any trouble.
Super duper.
Part of my earlier problem was that due to a slow connection the night I wanted to download Centos I had to give up on the full version and took the smaller Centos Live, next night things were running at full speed and I got the 4 GB DVD version that I have running now. My Viasat usage is limited except between midnight and five so that's the optimal time for such things, it depends on where I stand in usage for the month.
Bob
Eine kleine Nachtmusik. :)
Bob, this way you'll be able to set your network in Fedora 21 host, with slight differences in the configuration with respect to the systemd version. Make note, networkd - bridge!
~~ /etc/systemd/network/bridge0.netdev [NetDev] Name=bridge0 Kind=bridge ~~ /etc/systemd/network/bridge0dhcp4.network [Match] Name=bridge0
[Network] DHCP=v4 ~~ /etc/systemd/network/eth2bridge0.network [Match] Name=eth2
[Network] Bridge=bridge0 ~~
# brctl show bridge name bridge id STP enabled interfaces bridge0 8000.001234567890 no eth2
# journalctl -b -u systemd-networkd -o cat | grep -v DBus Starting Network Service... timestamp of '/usr/lib/systemd/network' changed bridge0 : loaded bridge sd-rtnl: discarding 20 bytes of incoming message eth2 : link 4 added lo : link 1 added bridge0 : created bridge0 : link state is up-to-date bridge0 : found matching network '/etc/systemd/network/bridge0dhcp4.network' eth2 : found matching network '/etc/systemd/network/eth2bridge0.network' bridge0 : enslaving link 'eth2' lo : unmanaged lo : added address: ::1/128 lo : added address: 127.0.0.1/8 bridge0 : flags change: +UP eth2 : flags change: +UP eth2 : flags change: +LOWER_UP +RUNNING DHCP CLIENT (0x927e3a57): T2 expires in 8min 44.389451s bridge0 : setting addresses bridge0 : added address: 192.168.2.40/24 bridge0 : addresses set bridge0 : setting routes bridge0 : routes set bridge0 : link configured eth2 : added address: fe80::212:34ff:fe56:7830/64 bridge0 : added address: fe80::212:34ff:fe56:7890/64 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /etc/libvirt/qemu/centos7.xml ... <interface type='bridge'> ... <source bridge='bridge0'/> <model type='virtio'/> ... </interface> ... fedora fan club
And if I get that to work I get an FFC certificate, right?
I keep lots of notes ...
Tnx
On 25.07.2014 02:23, Bob Goodwin - Zuni, Virginia, USA wrote:
On 07/24/14 18:09, poma wrote:
On 24.07.2014 18:20, Bob Goodwin - Zuni, Virginia, USA wrote:
On 07/24/14 11:48, poma wrote:
As Chris mentioned, are you running Centos7 VM by VirtualBox, Virtual Machine Manager/libvirt/KVM/QEMU or VMware Workstation?
poma
I am ashamed to admit that I could not get VirtualBox to install the Centos7 I had. VMware was a waste of money for someone running Fedora since the ordinary user would find it impossible to keep up with the kernel updates, that still irks me!
Won't get fooled again, lessons learned, right. ;)
Virt-manager installed in F-20 via yum worked without any trouble.
Super duper.
Part of my earlier problem was that due to a slow connection the night I wanted to download Centos I had to give up on the full version and took the smaller Centos Live, next night things were running at full speed and I got the 4 GB DVD version that I have running now. My Viasat usage is limited except between midnight and five so that's the optimal time for such things, it depends on where I stand in usage for the month.
Bob
Eine kleine Nachtmusik. :)
Bob, this way you'll be able to set your network in Fedora 21 host, with slight differences in the configuration with respect to the systemd version. Make note, networkd - bridge!
~~ /etc/systemd/network/bridge0.netdev [NetDev] Name=bridge0 Kind=bridge ~~ /etc/systemd/network/bridge0dhcp4.network [Match] Name=bridge0
[Network] DHCP=v4 ~~ /etc/systemd/network/eth2bridge0.network [Match] Name=eth2
[Network] Bridge=bridge0 ~~
# brctl show bridge name bridge id STP enabled interfaces bridge0 8000.001234567890 no eth2
# journalctl -b -u systemd-networkd -o cat | grep -v DBus Starting Network Service... timestamp of '/usr/lib/systemd/network' changed bridge0 : loaded bridge sd-rtnl: discarding 20 bytes of incoming message eth2 : link 4 added lo : link 1 added bridge0 : created bridge0 : link state is up-to-date bridge0 : found matching network '/etc/systemd/network/bridge0dhcp4.network' eth2 : found matching network '/etc/systemd/network/eth2bridge0.network' bridge0 : enslaving link 'eth2' lo : unmanaged lo : added address: ::1/128 lo : added address: 127.0.0.1/8 bridge0 : flags change: +UP eth2 : flags change: +UP eth2 : flags change: +LOWER_UP +RUNNING DHCP CLIENT (0x927e3a57): T2 expires in 8min 44.389451s bridge0 : setting addresses bridge0 : added address: 192.168.2.40/24 bridge0 : addresses set bridge0 : setting routes bridge0 : routes set bridge0 : link configured eth2 : added address: fe80::212:34ff:fe56:7830/64 bridge0 : added address: fe80::212:34ff:fe56:7890/64 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /etc/libvirt/qemu/centos7.xml ... <interface type='bridge'> ... <source bridge='bridge0'/> <model type='virtio'/> ... </interface> ... fedora fan clubAnd if I get that to work I get an FFC certificate, right?
Perhaps for network.service :)
http://jjkuhn.com/images/logo_networkd.gif Ra-ra-ra-ra-ra-ra-ra-ra-ra-ra ra BATMAN!!!!!
I keep lots of notes ...
Tnx
batman fan club
Once upon a time, Bob Goodwin - Zuni, Virginia, USA bobgoodwin@wildblue.net said:
However the VM shows 192.168.122.14, what is that, how would I deal with it with the present net assignments, I have a ton of devices assigned by dhcp as it is? Obviously things are happening that I haven't seen before and don't understand.
192.168.122.0/24 is what libvirtd sets up by default as a local-only network that is NATted to the host system's IP for network access. Does your host system have access to the desired NFS share?
Alternantely, you can configure libvirtd to just bridge your host's network interface to the VM, so that the VM has the same network access as any physical host on the local LAN (it would get an address from your LAN's DHCP, not the private libvirtd-configured DHCP server).
On 07/24/14 11:33, Chris Adams wrote:
Once upon a time, Bob Goodwin - Zuni, Virginia, USA bobgoodwin@wildblue.net said:
However the VM shows 192.168.122.14, what is that, how would I deal with it with the present net assignments, I have a ton of devices assigned by dhcp as it is? Obviously things are happening that I haven't seen before and don't understand.
192.168.122.0/24 is what libvirtd sets up by default as a local-only network that is NATted to the host system's IP for network access. Does your host system have access to the desired NFS share?
Yes, I think everything does.
Alternantely, you can configure libvirtd to just bridge your host's network interface to the VM, so that the VM has the same network access as any physical host on the local LAN (it would get an address from your LAN's DHCP, not the private libvirtd-configured DHCP server).
Ok, then if that is the case it should just work. Everything in the house is assigned in the range 192.168.1.0/24.
I have had the NFS running without a hitch for more than a year, routinely keep data on it, others on the LAN can access the freenas server. It all works and now it appears the VM is working also.
Thanks for the help,
Bob
On 07/23/14 14:21, Chris Adams wrote:
Once upon a time, Bob Goodwin - Zuni, Virginia, USA bobgoodwin@wildblue.net said:
I've created an Centos7 VM in this updated Fedora-20 box. NFS always works without a hitch however I can't mount the server from the VM.
[root@localhost bobg]# mount 192.168.1.8:/home/bobg/ /mnt/HOME1/ mount.nfs: access denied by server while mounting 192.168.1.8:/home/bobg/
Possibly NFSv4 vs. NFSv3? RHEL/CentOS 6 and earlier (and Fedora before around 17 IIRC) default to NFSv3 mounts, while newer stuff defaults to NFSv4.
Try adding "-o nfsvers=3".
No, that's not it,
[root@localhost bobg]# mount -o nfsvers=3 192.168.1.8:/home/bobg/ /mnt/HOME1/ mount.nfs: access denied by server while mounting 192.168.1.8:/home/bobg/
But it does connect to my freenas server,
# mount 192.168.1.48:/mnt/nasdata/box48bobg /mnt/BOX48
[root@localhost BOX48]# ll total 88 drwxr-xr-x. 4 1001 root 1024 Apr 23 14:39 Apps drwxr-xr-x. 2 1001 root 512 Jul 12 10:43 AvStuff drwxr-xr-x. 2 1001 root 512 Apr 19 16:25 BookCLI drwxr-xr-x. 2 1001 root 4096 Jun 13 17:09 digicam drwxr-xr-x. 7 1001 root 512 Apr 15 18:21 gramps drwxr-xr-x. 2 1001 root 2048 Apr 23 14:40 icons drwxrwxr-x. 2 root root 512 Apr 23 14:17 notecase drwxrwxrwx. 2 1001 root 1536 Jul 19 14:19 oocalc
..... snip .......
Thanks, Bob
-
Bob Goodwin -
Chris Adams -
poma -
Rick Stevens