How to Install Fedora 25 Minimal

black3dynamite

@StrongBad said in How to Install Fedora 25 Minimal:

Why ext4 as a default? Feels like they are moving backwards there. They made the move to XFS from ext4 already.

Fedora Server uses EXT4 (/boot) and XFS (/root). Fedora Workstation uses EXT4.

black3dynamite

@JaredBusch

guest-agents installs packages of open-vm-tools and qemu-guest-agent.

Typing this command will so those packages:
dnf groupinfo "guest-agents"

JaredBusch

@black3dynamite said in How to Install Fedora 25 Minimal:

@JaredBusch

guest-agents installs packages of open-vm-tools and qemu-guest-agent.

Typing this command will so those packages:
dnf groupinfo "guest-agents"

yeah finally back to this. so yup, no Hyper-v agents. Fixed that. Let's see what Hyper-V thinks of it.

[root@jrd-nc ~]# dnf -y install hyperv-daemons
Last metadata expiration check: 2:26:36 ago on Fri Apr 28 09:18:21 2017.
Dependencies resolved.
===============================================================================================================
 Package                          Arch             Version                             Repository         Size
===============================================================================================================
Installing:
 hyperv-daemons                   x86_64           0-0.17.20170105git.fc25             updates           8.7 k
 hyperv-daemons-license           noarch           0-0.17.20170105git.fc25             updates            16 k
 hypervfcopyd                     x86_64           0-0.17.20170105git.fc25             updates            15 k
 hypervkvpd                       x86_64           0-0.17.20170105git.fc25             updates            23 k
 hypervvssd                       x86_64           0-0.17.20170105git.fc25             updates            15 k

JaredBusch

Hyper-V still shows degraded, but it now shows the IP address in the console.
0_1493399297907_upload-d0dc1ab1-e951-4599-9b3d-79191b511196
0_1493399322234_upload-09cbd3d9-b1c3-45ee-b506-7b934d86ed1f

JaredBusch

This is a Fedora 25 VM without the hyperv-daemon

0_1493399383460_upload-a64dc56a-957d-4c9a-a6f4-d7c5426a3c3d
0_1493399401331_upload-605ba1b5-5fd2-4842-a0a7-cbbd5c678254

JaredBusch

first post updated with a note to install hyperv-daemons if running under Hyper-V

FATeknollogee

@JaredBusch said in How to Install Fedora 25 Minimal:

Hyper-V still shows degraded, but it now shows the IP address in the console.

I installed 2 "minimal install" vm's on Win Serv 2016 (Fedora 25 & CentOS).
On the Fedora vm, I checked the "guest agen" add-on but not on the CentOS.
Under Status, they both show ok, I didn't have to add hyperv-daemons

JaredBusch

@FATeknollogee said in How to Install Fedora 25 Minimal:

@JaredBusch said in How to Install Fedora 25 Minimal:

Hyper-V still shows degraded, but it now shows the IP address in the console.

I installed 2 "minimal install" vm's on Win Serv 2016 (Fedora 25 & CentOS).
On the Fedora vm, I checked the "guest agen" add-on but not on the CentOS.
Under Status, they both show ok, I didn't have to add hyperv-daemons

You mean under heartbeat on the summary tab? Yeah. it always does.
Or you mean on the networkig tab? well there it show ok, but not any IP info until you install the hyper-v daemons and reboot.

FATeknollogee

@JaredBusch Networking tab. In that case, let me go ahead & install the daemons

stacksofplates

@travisdh1 said in How to Install Fedora 25 Minimal:

@FATeknollogee said in How to Install Fedora 25 Minimal:
@JaredBusch said in How to Install Fedora 25 Minimal:
@FATeknollogee said in How to Install Fedora 25 Minimal:

@JaredBusch Let's say you want to use this VM as a file server.
Is it better to create 2 disks (1 for o/s + 1 for storage) or just one big ass disk?

As this example showed, I had a 127GB disk because I let Hyper-V Server 2016 use its default.

Fedora only took 17GB of it. 2GB for swap and 15GB for root.

The rest is sitting there waiting to be used however you want.

So all you have to do is make the space usable.
#create a logical volume named data
lvcreate -l 100%FREE -n data fedora

#format it to ext4
mkfs.ext4 /dev/fedora/data

#make a directory to mount it
mkdir /data

#mount it
mount /dev/fedora/data /data
Obviously you will want to have this mounted on reboot, so add it to /etc/fstab
nano /etc/fstab

#add this
/dev/fedora/data /data                    ext4    defaults        1 2
Anyone have a simple "how to do this" guide on /dev/xvdb or /dev/sdb ? (I read some guides on the 'net, thy all seem long & winded)
Off the top of my head even, let's go!
pvcreate /dev/xvdb
vgcreate vgname /dev/xvdb
lvcreate -n 'lvname' vgname -l 100%FREE
mkfs.xfs /dev/vgname/lvname
mount /dev/vgname/lvname /mountpoint
If you add an xfs volume to fstab, it's recommended to make the last two options (dump and fsck) zero. Yeah, xfs can really speed up boot times if you're switching from another file system that needs to run an fsck at boot.

https://mangolassi.it/topic/11302/travis-hershberger-linux-lvm-storage

If you're doing -l 100%FREE it doesn't necessarily matter. But if you are ever going to have more than one volume, I'd do vgcreate -s 1G (or more depending on volume size). 4M chunks become annoying to manage, especially when you can do vgcreate -l 1 vs vgcreate -l $((1024000 / 4096)).

travisdh1

@stacksofplates said in How to Install Fedora 25 Minimal:

@travisdh1 said in How to Install Fedora 25 Minimal:
@FATeknollogee said in How to Install Fedora 25 Minimal:
@JaredBusch said in How to Install Fedora 25 Minimal:
@FATeknollogee said in How to Install Fedora 25 Minimal:

@JaredBusch Let's say you want to use this VM as a file server.
Is it better to create 2 disks (1 for o/s + 1 for storage) or just one big ass disk?

As this example showed, I had a 127GB disk because I let Hyper-V Server 2016 use its default.

Fedora only took 17GB of it. 2GB for swap and 15GB for root.

The rest is sitting there waiting to be used however you want.

So all you have to do is make the space usable.
#create a logical volume named data
lvcreate -l 100%FREE -n data fedora

#format it to ext4
mkfs.ext4 /dev/fedora/data

#make a directory to mount it
mkdir /data

#mount it
mount /dev/fedora/data /data
Obviously you will want to have this mounted on reboot, so add it to /etc/fstab
nano /etc/fstab

#add this
/dev/fedora/data /data                    ext4    defaults        1 2
Anyone have a simple "how to do this" guide on /dev/xvdb or /dev/sdb ? (I read some guides on the 'net, thy all seem long & winded)
Off the top of my head even, let's go!
pvcreate /dev/xvdb
vgcreate vgname /dev/xvdb
lvcreate -n 'lvname' vgname -l 100%FREE
mkfs.xfs /dev/vgname/lvname
mount /dev/vgname/lvname /mountpoint
If you add an xfs volume to fstab, it's recommended to make the last two options (dump and fsck) zero. Yeah, xfs can really speed up boot times if you're switching from another file system that needs to run an fsck at boot.

https://mangolassi.it/topic/11302/travis-hershberger-linux-lvm-storage
If you're doing -l 100%FREE it doesn't necessarily matter. But if you are ever going to have more than one volume, I'd do vgcreate -s 1G (or more depending on volume size). 4M chunks become annoying to manage, especially when you can do vgcreate -l 1 vs vgcreate -l $((1024000 / 4096)).

I have to ask, how do the 4M chunks become annoying to manage?

The -l 100%FREE should really be a lower percentage anyway, so you can take a snapshot on the volume when you want to run a backup.

stacksofplates

@travisdh1 said in How to Install Fedora 25 Minimal:

@stacksofplates said in How to Install Fedora 25 Minimal:
@travisdh1 said in How to Install Fedora 25 Minimal:
@FATeknollogee said in How to Install Fedora 25 Minimal:
@JaredBusch said in How to Install Fedora 25 Minimal:
@FATeknollogee said in How to Install Fedora 25 Minimal:

@JaredBusch Let's say you want to use this VM as a file server.
Is it better to create 2 disks (1 for o/s + 1 for storage) or just one big ass disk?

As this example showed, I had a 127GB disk because I let Hyper-V Server 2016 use its default.

Fedora only took 17GB of it. 2GB for swap and 15GB for root.

The rest is sitting there waiting to be used however you want.

So all you have to do is make the space usable.
#create a logical volume named data
lvcreate -l 100%FREE -n data fedora

#format it to ext4
mkfs.ext4 /dev/fedora/data

#make a directory to mount it
mkdir /data

#mount it
mount /dev/fedora/data /data
Obviously you will want to have this mounted on reboot, so add it to /etc/fstab
nano /etc/fstab

#add this
/dev/fedora/data /data                    ext4    defaults        1 2
Anyone have a simple "how to do this" guide on /dev/xvdb or /dev/sdb ? (I read some guides on the 'net, thy all seem long & winded)
Off the top of my head even, let's go!
pvcreate /dev/xvdb
vgcreate vgname /dev/xvdb
lvcreate -n 'lvname' vgname -l 100%FREE
mkfs.xfs /dev/vgname/lvname
mount /dev/vgname/lvname /mountpoint
If you add an xfs volume to fstab, it's recommended to make the last two options (dump and fsck) zero. Yeah, xfs can really speed up boot times if you're switching from another file system that needs to run an fsck at boot.

https://mangolassi.it/topic/11302/travis-hershberger-linux-lvm-storage
If you're doing -l 100%FREE it doesn't necessarily matter. But if you are ever going to have more than one volume, I'd do vgcreate -s 1G (or more depending on volume size). 4M chunks become annoying to manage, especially when you can do vgcreate -l 1 vs vgcreate -l $((1024000 / 4096)).
I have to ask, how do the 4M chunks become annoying to manage?

The -l 100%FREE should really be a lower percentage anyway, so you can take a snapshot on the volume when you want to run a backup.

You get both performance gains from using larger chunks and you don't need to do math when you grow your volume. If you only grow your volume to what you need at the time, it's much easier to just type the size in GB vs the number of extents / 4M.

travisdh1

@stacksofplates said in How to Install Fedora 25 Minimal:

@travisdh1 said in How to Install Fedora 25 Minimal:
@stacksofplates said in How to Install Fedora 25 Minimal:
@travisdh1 said in How to Install Fedora 25 Minimal:
@FATeknollogee said in How to Install Fedora 25 Minimal:
@JaredBusch said in How to Install Fedora 25 Minimal:
@FATeknollogee said in How to Install Fedora 25 Minimal:

@JaredBusch Let's say you want to use this VM as a file server.
Is it better to create 2 disks (1 for o/s + 1 for storage) or just one big ass disk?

As this example showed, I had a 127GB disk because I let Hyper-V Server 2016 use its default.

Fedora only took 17GB of it. 2GB for swap and 15GB for root.

The rest is sitting there waiting to be used however you want.

So all you have to do is make the space usable.
#create a logical volume named data
lvcreate -l 100%FREE -n data fedora

#format it to ext4
mkfs.ext4 /dev/fedora/data

#make a directory to mount it
mkdir /data

#mount it
mount /dev/fedora/data /data
Obviously you will want to have this mounted on reboot, so add it to /etc/fstab
nano /etc/fstab

#add this
/dev/fedora/data /data                    ext4    defaults        1 2
Anyone have a simple "how to do this" guide on /dev/xvdb or /dev/sdb ? (I read some guides on the 'net, thy all seem long & winded)
Off the top of my head even, let's go!
pvcreate /dev/xvdb
vgcreate vgname /dev/xvdb
lvcreate -n 'lvname' vgname -l 100%FREE
mkfs.xfs /dev/vgname/lvname
mount /dev/vgname/lvname /mountpoint
If you add an xfs volume to fstab, it's recommended to make the last two options (dump and fsck) zero. Yeah, xfs can really speed up boot times if you're switching from another file system that needs to run an fsck at boot.

https://mangolassi.it/topic/11302/travis-hershberger-linux-lvm-storage
If you're doing -l 100%FREE it doesn't necessarily matter. But if you are ever going to have more than one volume, I'd do vgcreate -s 1G (or more depending on volume size). 4M chunks become annoying to manage, especially when you can do vgcreate -l 1 vs vgcreate -l $((1024000 / 4096)).
I have to ask, how do the 4M chunks become annoying to manage?

The -l 100%FREE should really be a lower percentage anyway, so you can take a snapshot on the volume when you want to run a backup.
You get both performance gains from using larger chunks and you don't need to do math when you grow your volume. If you only grow your volume to what you need at the time, it's much easier to just type the size in GB vs the number of extents / 4M.

It's LVM, so it really doesn't care if you tell it the number of extents to use or the size in GB. Two different ways of telling it the same thing. Mix and match to your hearts content.

stacksofplates

@travisdh1 said in How to Install Fedora 25 Minimal:

@stacksofplates said in How to Install Fedora 25 Minimal:
@travisdh1 said in How to Install Fedora 25 Minimal:
@stacksofplates said in How to Install Fedora 25 Minimal:
@travisdh1 said in How to Install Fedora 25 Minimal:
@FATeknollogee said in How to Install Fedora 25 Minimal:
@JaredBusch said in How to Install Fedora 25 Minimal:
@FATeknollogee said in How to Install Fedora 25 Minimal:

@JaredBusch Let's say you want to use this VM as a file server.
Is it better to create 2 disks (1 for o/s + 1 for storage) or just one big ass disk?

As this example showed, I had a 127GB disk because I let Hyper-V Server 2016 use its default.

Fedora only took 17GB of it. 2GB for swap and 15GB for root.

The rest is sitting there waiting to be used however you want.

So all you have to do is make the space usable.
#create a logical volume named data
lvcreate -l 100%FREE -n data fedora

#format it to ext4
mkfs.ext4 /dev/fedora/data

#make a directory to mount it
mkdir /data

#mount it
mount /dev/fedora/data /data
Obviously you will want to have this mounted on reboot, so add it to /etc/fstab
nano /etc/fstab

#add this
/dev/fedora/data /data                    ext4    defaults        1 2
Anyone have a simple "how to do this" guide on /dev/xvdb or /dev/sdb ? (I read some guides on the 'net, thy all seem long & winded)
Off the top of my head even, let's go!
pvcreate /dev/xvdb
vgcreate vgname /dev/xvdb
lvcreate -n 'lvname' vgname -l 100%FREE
mkfs.xfs /dev/vgname/lvname
mount /dev/vgname/lvname /mountpoint
If you add an xfs volume to fstab, it's recommended to make the last two options (dump and fsck) zero. Yeah, xfs can really speed up boot times if you're switching from another file system that needs to run an fsck at boot.

https://mangolassi.it/topic/11302/travis-hershberger-linux-lvm-storage
If you're doing -l 100%FREE it doesn't necessarily matter. But if you are ever going to have more than one volume, I'd do vgcreate -s 1G (or more depending on volume size). 4M chunks become annoying to manage, especially when you can do vgcreate -l 1 vs vgcreate -l $((1024000 / 4096)).
I have to ask, how do the 4M chunks become annoying to manage?

The -l 100%FREE should really be a lower percentage anyway, so you can take a snapshot on the volume when you want to run a backup.
You get both performance gains from using larger chunks and you don't need to do math when you grow your volume. If you only grow your volume to what you need at the time, it's much easier to just type the size in GB vs the number of extents / 4M.
It's LVM, so it really doesn't care if you tell it the number of extents to use or the size in GB. Two different ways of telling it the same thing. Mix and match to your hearts content.

You can do a -L and pass the size in GB but if you don't know exactly how many extents you have left you have to calculate that before you can pass a size. You also gain performance in using larger chunks.

stacksofplates

For example a volume with 4041 free extents in 4MB chunks.

>$ sudo lvcreate -L 20G -n test rhel
Volume group "rhel" has insufficient free space (4041 extents): 5120 required.

So now if you can't grow your volume group, you have to calculate how much space 4041 extents is.

vgdisplay will show you PE size, but you still have to calculate how much free space to leave so you don't over commit.

stacksofplates

So if you're working with 400M volumes, sure leave it at 4M. But anything in the normal sizes today (hundreds of GB), it saves time, mistakes, and gains performance by setting a larger chunk size.

black3dynamite

Unlike installing Linux Integration Services, Hot-Add support is not enabled by default after installing hyperv-daemons.

Create a file /etc/udev/rules.d/100-balloon.rules. You may use any other desired name for the file.

Add the following content to the file: SUBSYSTEM=="memory", ACTION=="add", ATTR{state}="online"

Reboot the system to enable Hot-Add support.

See Note 8 on Supported CentOS and Red Hat Enterprise Linux virtual machines on Hyper-V

JaredBusch

@black3dynamite said in How to Install Fedora 25 Minimal:

Unlike installing Linux Integration Services, Hot-Add support is not enabled by default after installing hyperv-daemons.

Create a file /etc/udev/rules.d/100-balloon.rules. You may use any other desired name for the file.

Add the following content to the file: SUBSYSTEM=="memory", ACTION=="add", ATTR{state}="online"

Reboot the system to enable Hot-Add support.

See Note 8 on Supported CentOS and Red Hat Enterprise Linux virtual machines on Hyper-V

You mean for dynamic memory to work?

black3dynamite

@JaredBusch said in How to Install Fedora 25 Minimal:

@black3dynamite said in How to Install Fedora 25 Minimal:

Unlike installing Linux Integration Services, Hot-Add support is not enabled by default after installing hyperv-daemons.

Create a file /etc/udev/rules.d/100-balloon.rules. You may use any other desired name for the file.

Add the following content to the file: SUBSYSTEM=="memory", ACTION=="add", ATTR{state}="online"

Reboot the system to enable Hot-Add support.

See Note 8 on Supported CentOS and Red Hat Enterprise Linux virtual machines on Hyper-V

You mean for dynamic memory to work?

Yes, dynamic memory for ballooning and hot-add.