Fedora 27 install log

installing Fedora 27 on my laptop, some notes on qemu/libvirt and rpmfusion

rpmfusion is still needed for vlc and other goodies although it gets less important

qemu/virt-manager can now nicely run windows 10, just keep a few things in mind:
from: https://pve.proxmox.com/wiki/Windows_10_guest_best_practices


To obtain a good level of performance, we will install the Windows VirtIO Drivers during the Windows installation.

Create a new VM, select “Microsoft Windows 8/2012” continue and mount your Windows 10 ISO in the CDROM drive
For your virtual hard disk select “VirtIO” as bus and “Write back” as cache option for best performance (the No cache default is safer, but slower)
Configure your memory settings as needed, continue and set “VirtIO (paravirtualized)” as network device, finish your VM creation.
For the VirtIO drivers, upload the driver ISO (use the stable VirtIO ISO, get it from here) to your storage, create a new CDROM drive (use “Add -> CD/DVD drive” in the hardware tab), and load the Virtio Drivers ISO in the new virtual CDROM drive
Now your ready to start the VM, just follow the Windows installer.

Launch Windows install using DVD .iso

After starting your VM launch the console
Follow the installer steps until you reach the installation type selection where you need to select “Custom (advanced)”
Now click “Load driver” to install the VirtIO drivers for hard disk and the network. (successfully tested with “virtio-win-0.1.118.iso”)
hard disk: Browse to the CD drive where you mounted the VirtIO driver and select folder “viostor\w10\amd64” and confirm. Select the “Red Hat VirtIO SCSI controller” and click next to install it. Now you should see your drive.
Network: Repeat the steps from above (click again “Load driver”, etc.) and select the folder “NetKVM\w10\amd64”, confirm it and select “Redhat VirtIO Ethernet Adapter” and click next.
Memory Ballooning: Again, repeat the steps but this time select the “Balloon\w10\amd64” folder, then the “VirtIO Balloon Driver” and install it by clicking next. With these three drivers you should be good covered to run a fast virtualized Windows 10 system.
Choose the drive and continue the Windows installer steps.

Now, Cortana will chat, mute her or talk to her, this installs windows 10.

Once the install is done, make sure to check device manager for missing drivers, use the ISO to install them.

4 GB RAM and 2 CPUs work reasonably fine for me. 3D acceleration is.. I didn’t get SPICE to work properly with my intel integrated graphics.

The normal display driver however works quite well when installing the qxldod driver
from the CD: viostor\w10\amd64\ right-click the .inf file and install

also, install the 64 bit version of the guest-agent.

change is good

I forgot how good it feels to change, to be active.

Life is changing and I am part of it. I am not afraid anymore.

I must not fear.
Fear is the mind-killer.
Fear is the little-death that brings total obliteration.
I will face my fear.
I will permit it to pass over me and through me.
And when it has gone past I will turn the inner eye to see its path.
Where the fear has gone there will be nothing.
Only I will remain.

Fedora 23 TRIM SSDs

running fedora 23 with full-disk encryption on an SSD – no TRIM support?

fstrim: /home: the discard operation is not supported

now.. it is not in fstab because we run crypto so let’s do this the right way: (I think)
sources: neutrino.es
and christophersmart.com

1) in /etc/crypttab add “discard” to your crypto partition
<target name> <source /> <key> <options>
luks UUID=4aa302cb-4b9a-413b-a862-9856ed5ddbba none discard

2) in /etc/lvm/lvm.conf, at the end of the ‘devices’ section, set “issue_discards = 1

3) rebuild initramfs and reboot
grubby --update-kernel=ALL --args=rd.luks.options=discard
dracut -f

now it should work, check with fstrim –verbose –all

# fstrim –verbose –all
/home: 53,9 GiB (57874288640 bytes) trimmed
/boot: 324,6 MiB (340356096 bytes) trimmed
/: 21,9 GiB (23504187392 bytes) trimmed

4) use systemctl to run a weekly job for that
systemctl ebable fstrim.timer
systemctl start fstrim.timer
systemctl status fstrim.timer


# systemctl status fstrim.timer
‚óŹ fstrim.timer – Discard unused blocks once a week
Loaded: loaded (/usr/lib/systemd/system/fstrim.timer; enabled; vendor preset: disabled)
Active: active (waiting) since Do 2016-06-16 07:27:27 CEST; 15min ago
Docs: man:fstrim

Jun 16 07:27:27 anakin systemd[1]: Started Discard unused blocks once a week.
Jun 16 07:27:27 anakin systemd[1]: Starting Discard unused blocks once a week.

UPDATE: Seems Fedora 24 understands the kernel boot argument so:
edit /etc/default/grub and add rd.luks.options=discard to the end

GRUB_DISTRIBUTOR=”$(sed ‘s, release .*$,,g’ /etc/system-release)”
GRUB_CMDLINE_LINUX=”rd.lvm.lv=fedora/root rd.luks.uuid=luks-4aa302cb-4b9a-413b-a862-9856ed5ddbba rd.lvm.lv=fedora/swap r
hgb quiet rd.luks.options=discard

now just rebuild grub and the initramfs step should not be neccessary, anymore… (you do need the lvm part and the systemd timer)
grub2-mkconfig -o /boot/grub2/grub.cfg

owncloud ubuntu 16.04 and logwatch

log of installing owncloud on ubuntu server 16.04 with logwatch

following the default install manual

decide for root webserver or subdomain
(cloud.[domain].[tld]) or just my homeserver

moving data dir elsewhere and setting permissions

set up letsencrypt

open firewall for https

adding logwatch scripts

ownCloud log in Logwatch deel 1

ownCloud log in Logwatch deel 2

Ubuntu 16.04 LTS / firewalld/systemd and fail2ban

just before Fedora 24 I wanted to check out Ubuntu 16.04 LTS and the Gnome flavor.. basically same as last time it feels like 3 years in the past from fedora.
anyway, SystemD is now default and let’s see if I can get it to work as before

One Bummer: Fail2Ban doesn’t work with default settings!
it says in the log that it blocked but I could still connect…

solution: (in jail.local)
backend = systemd

this re-enables the functionality and I verified it works!

Continue reading

O2 micro sdcard reader doesn’t work with kernel 4.2/4.4 on DELL latitude

all of a sudden (don’t know when) my sdcard reader stopped working…

seems there is a bug report and discussion since 4.1.8

this guy seems to have fixed it:
Continue reading