Just a quick note and warning is that if you are testing to see if EFIPXE booting works on a VM, MAKE SURE it actually works. For example Iinitially tested using my Distro's QEMU 2.5+dfsg-5ubuntu10.46 and ovmf BIOS firmware (OVMF supports EFI). However, I found on old versions of QEMU (like 2.5), EFIbooting with GRUB NEVER works so it may appear that you have made a mistake when everything is fine when you boot a physi........
This is only really necessary in the case you don't want DHCP. If you are dealing with an encrypted LUKS server on the internet, you will often want to have a static IP so you know which IP to connect to (or if you have a semi-static IP assigned by DHCP).
SET IP Address by /etc/initramfs-tools/initramfs.conf
Subnet Mask: 255.255.255.0
By default at least on Centos 7 nfs only allows 8 connections and starts 8 nfsd daemons.
To fix this edit this file:/etc/sysconfig/nfs
Edit the line "RPCNFSDCOUNT" (uncomment it so it looks like this:
In the example above we are setting 30 nfsd daemons to run (or in other words 30 connections are possible this way).........
systemd is like the service manager for your Centos and other modern Linux distributions (including Debian/Mint/Ubuntu) allows you to enable services, stop them, restart them, check their status and even reboot your system.
The key commands or arguments you will use with systemctl are the following:
list-units [PATTERN...] List loaded units
Proxmox at the root of your storage creates and "images"and "templates/iso" folder for VM images and iso's respectively. It ignores files in any other location.........
yes it does create its own json
cat /tmp/vcsaUiInstaller/ovftool-20180809-175238948-20180809-175603497.log |grep -i json
2018-08-09T17:56:04.238-07:00 verbose OVFTool [Originator@6876 sub=Default] Manifest file entry: SHA1(VMware-vCenter-Server-Appliance-184.108.40.20600-8832884_OVF10-file1.json) = 1deb658c724767697587d5909c4051c01813e6a1
Server Side Config
1.) First install nfs-utils
yum -y install nfs-utils
2.) Configure nfs share
Create a directory for your NFS share
Create your NFS share in /etc/exports
echo "/datastore 10.220.101.0/24(rw,sync,no_root_squash)" >> /etc/exports
systemctl restart nfs........
nfs mount failed:
mount 10.10.2.20:/tmp/nfsmount /mnt/nfs/
mount: wrong fs type, bad option, bad superblock on 10.10.2.20:/tmp/nfsmount,
missing codepage or helper program, or other error
(for several filesystems (e.g. nfs, cifs) you might
need a /sbin/mount. helper program)
sudo apt-get install nfs-kernel-server #oops there are no exports so it won't startsudo /etc/init.d/nfs-kernel-server start* Not starting NFS kernel daemon: no exports.
#we will use the /tmp/nfstestshare directory for our NFS share
#add it to /etc/exports (basically what NFS checks to determine what to make an NFS share)
I get the following error "Installer Crashed" on 18.1 MATE 64-bit when installing by NFS/PXE. Yet it was able to at least detect and use my NIC (perhaps the driver was only activated because of PXE/NFS being used)?
When using 18.1 Cinnamon on CD the NIC does not work but the installer did succeed. However it doesn't work right, I can't login graphically and get some Cinnamon OOMerror but how can this be with 8GB of RAM straight from login?........
*Update so this doesn't work it must be something to do with the path of nfs or something else but the installer fails with "Installer crashed" at the end whereas with the CD/USB it works.
This assumes you've already installed and configured a separate PXE/DHCP server somewhere else and your /tftpboot directory is setup.
This is for Linux Mint 18.1 but generally applies to most versions although you may have tro change things like "casper"........
Add the following to fstab where 192.168.1.125/Media is the samba share and where /home/homeuser/Downloads is where you want to mount.
Change user and pass to what is needed (if no pass is required it still works fine with the below).
//192.168.1.125/Media /home/homeuser/Downloads cifs user=guest,pass=bla 0 0
mount: wrong fs type, bad option, bad superblock on //192.168.1.125/Media,
This is what fixed it:
[root@box13 ~]# dd if=/dev/zero of=/dev/md160 bs=512 count=500
Basically you need to wipe out more than just the 512 byte partition table so 512 bytes * 500 is more than enough to make DRBD happy and think the partition is now empty.
The reason this happens is because it gets confused when there is a previous partition with data on the device you are using.
root@box13 ~]# d........
pxe-32 tftp open timeout
The solution was to enable tftp in xinetd with "chkconfig tftp on".
See the troubleshooting below:
NetworkManager 0:off 1:off 2:off 3:off 4:off 5:off 6:off
I had a system running a 128MB live CD image with 2.8 gigs of available RAM and the OOM kernel killer went crazy when using dd for more than 8 minutes and kept killing everything. I've read that this is due to a low-memory issue and paging in the kernel and 32-bit systems with lots of RAM.
I even enabled swapspace on my LiveCD and the issue happened 25 minutes into dd rather than 8 minutes, so what gives?
Also no swap space was ever used!
I've never understood how to enable and disable services for different run levels in Debian based distros, it's just weird, annoying and doesn't make sense. I much prefer chkconfig from RHEL.
Just install the package called 'rcconf' and be done with it. rcconf makes things easy for you.
apt-get install rcconf
Reading package lists... Done
Building dependency tree
Reading state information... Done........
Here are the results, it is Sempron 3000+ AMD Mobile, 500Gig HDD, 512MB RAM with shared ATI Radeon graphics.
# # # # # # # ##### ###### # # #### # #
# # ## # # # #&nb........
Basic Port ListingHopefully someone finds this useful or at least interesting.
Name Port Protocol Description
Small services ........