OracleLinux 7.9 ISO boots fine, OracleLinux 8.10 ISO won't boot

[dipr]

Hi guys!
I'm just beginning to try and understand proxmox (8.2) . Initially I was astonished the installer offerend to select ONE of the 8 Disks in the machine as installation location, ignoring all other disks. I gave him /dev/sda, around 300GB. Next it could not create the swap partition. Hence I limited "hdsize" to 30 GB and installation went fine.
I managed to increase the root filesystem by: Setting up /dev/sda4 , creating a LVM pv , adding it to LVM vg "pve" , lvresize the root lv to max size, and resize2fs the root fs while online (isn't ext4 a great fs )

Setting up VMs:
I created a 30GB VM for oracle linux. I specified cdrom=real cdrom. The metal is an old DL380 thus I used HP-ILO to define the virtual-DVD drive to be the iso Image of OracleLinux, just as i did specify the virtual-DVD drive to be the Proxmox8.2 Image. So HP-ILO virtual DVD setting does work, otherwise I would have not been aber to install proxmox.
My reasoning was that the VM cdrom setting "cdrom = real cdrom" woudl Connect the VM's cdrom to whatrever the metal (DL380) thinks its cdrom is.
However booting did not work.

Then I found the "boot ISOs" section in proxmox (that was the reason to increase the pve lv) and "uploaded" the iso file. Worked nicely.
Now if I point the VM's cdrom to the ISO-image of Oracle Linux 7.9 and restart the VM the Installscreen of OL7.9 shows up.
But if I point the VM's cdrom to the ISO-image of Oracle Linux 8.10 and restart the VM i get :

Booting from DVD/CD ...
ISOLINUX 6.04 ....
Faild to load ldlinux,c32
Boot failed: press any key

Any idea why ? Should i change the BIOS Setting of the VM?

Aside from that, some general questions:
- am I correct that I should add all other diskst to LVM-VG "pve" if I want more/bigger VMs ?
- am I correct that such operation are expected to be done not via proxmox web interface but as root via ssh?
- what is the difference between local(pve) and local-lvm(pve) ?
- where will the RAM Image be stored when hibernating a VM ?

edit: forget the boot question, the OEL 8.10 DVD iso won't boot directly on the DL380 as well
so it appears NOT to be a proxmox issue but something in the OEL8.10 ISO image seems to be off.
my bad fro not checking befor posting, sry

 

[LnxBil]

- am I correct that I should add all other diskst to LVM-VG "pve" if I want more/bigger VMs ?

Depends on what you want ... without any involved RAID controller, you will create a RAID0 of all your drives ... I cannot recommend such a setup.

My reasoning was that the VM cdrom setting "cdrom = real cdrom" woudl Connect the VM's cdrom to whatrever the metal (DL380) thinks its cdrom is.

Why don't you just upload your ISO to your PVE and use it like it was designed to do? Your cdrom-passthrough although technically possible, seems overly complicated and error prone.

am I correct that such operation are expected to be done not via proxmox web interface but as root via ssh?

That gives you an indication that this is normally not the way you want to configure your storage

- what is the difference between local(pve) and local-lvm(pve) ?

The first is a filesystem in which you can put your iso files and container templates and the latter is the block storage in which you can put your VMs.

- where will the RAM Image be stored when hibernating a VM ?

On the same storage on which your VM data resists.

 

[dipr]

Thx for the fast an accurate response!
That old DL380 server is just a test environment, in a production environment mirroring would be a good idea.

You third respone insinuates, that one should refrain from command line LVM commands and
limit ones actions to what the proxmox webinterface provides, am I correct?

 

[dipr]

I 've got a very basic installation of proxmox and have a hard time finding my way through LVM and proxmox webinterface display.

As root I see:
root@pve:~# pvscan
PV /dev/sdf2 VG VolGroup01 lvm2 [142.66 GiB / 0 free]
PV /dev/sdg2 VG VolGroup01 lvm2 [<142.34 GiB / 0 free]
PV /dev/sda3 VG pve lvm2 [<29.00 GiB / 0 free]
PV /dev/sda4 VG pve lvm2 [249.36 GiB / <207.12 GiB free]
PV /dev/sdb3 lvm2 [<135.70 GiB]
Total: 5 [<699.06 GiB] / in use: 4 [<563.36 GiB] / in no VG: 1 [<135.70 GiB]
root@pve:~# vgscan
Found volume group "VolGroup01" using metadata type lvm2
Found volume group "pve" using metadata type lvm2
root@pve:~# lvscan
ACTIVE '/dev/VolGroup01/LogVol02' [285.00 GiB] inherit
ACTIVE '/dev/pve/data' [10.74 GiB] inherit
ACTIVE '/dev/pve/swap' [3.50 GiB] inherit
ACTIVE '/dev/pve/root' [55.00 GiB] inherit
ACTIVE '/dev/pve/vm-100-disk-0' [32.00 GiB] inherit

e.g. two VolumeGroups, "VolGroup01" ~284 GB and the infamous "pve", where all appears to be happening, sized 280 GB
(after I've added /dev/sda4).
In the Webinterface shows "local (pve)" is rather static 58GB of which 22GB are in use.
But "local-lvm (pve)" allegedly is only 12GB in size of which the growing virtual hard disk of the Oracle Linux being installed is currently consuming 7.7GB (in the VM it claims the virtual disk should be 32GB)

Thus I take it I'm overprovisioning the hard disk space, putting a 32 GB virtual Disk into a storage of 12GB size.

Questions:
- why is "local-lvm(pve)" shown in the webinterface as 12GB when the VM virtual disk it contains is set up to (grow up to) 32 GB ?
- what is "local-lvm(pve)" ? Clearly it is neither a LVM-VolumeGroup nor a LVM-LogicalVolume nor the sum of all virtual-Disk LVM-LogcialVolumes
- where do I adjust/resize "local-lvm(pve)"
- how do I put the 300GB VolumeGroup01 to use? I me it looks as if it has one lv "LogVol02" which appear to be unused .
- who/what is (should be) using the 10GB of /dev/pve/data ?

 

[LnxBil]

You third respone insinuates, that one should refrain from command line LVM commands and
limit ones actions to what the proxmox webinterface provides, am I correct?

No, not at all. I just wanted to say that there is IMHO no way to do this via the GUI, because it is not a good idea to do that. Other ways, e.g. via ZFS are available via the GUI, so they are implemented.

As this is a test environment, just create a physical volume and add it to your volume group. This is totally fine for a test environment. Please be aware that LVM does not automatically redistribute the physical extends over the disks, so you will end up with a RAID0 with the performance of one disk.

 

[dipr]

The fog begins to receed.
The Volume Group "VolGroup01" has noting to do with the proxmox installation, it is a leftover from the pervious usage of the metal as oracle server. The logical volume it contains can be mounted peerlessly and contains old database files. Sorry for that mixup, my bad.