[SOLVED] Does Proxmox 8 Work on Modern Computers? YES!

[ubu]

Plaese describe problem better, IS IT with the Installer not booting or IS the system hanging at boot AFTER the installation was successfull?

Have you tried the Text Mode Install from the proxmox iso.

Sorry you have Problems with your Server, i have installed proxmox in dozens of different Machines (mostly Supermicro, but also dell Fujitsu, in Notebooks and Desktops)

 

[LnxBil]

See the link here: Well, found this thread from 2014: https://forum.proxmox.com/threads/s...l-with-dev-to-be-fully-populated-error.20211/

Ah okay. The problem had the same solution as the 7.1+ black boot screen problem - nomodeset and console, so disabling the framebuffer seems to help a lot.

That's why my brother said to run away from Proxmox...I'll keep it with EXT4, then install pfSense VM with ZFS.

Why? What's wrong with ZFS on PVE? It's the same implementation that all systems have nowadays: OpenZFS.

I would suggest that Proxmox next update/upgrade includes support for the Nvidia NVS 310/315 for Intel Xeon processor.

Nvidia is a Nvidia problem ... unless they provide support, Linux is not going to have it. That battle is on for decades and Nvidia still sux big time.
Proxmox VE uses the Ubuntu LTS kernel, so point your blame there ... but nvidia ... so no one will care. Also that card is really OLD ... PCIe 2.0 ... and there are cards that work perfectly like my Quadro K2000 ... as a second GPU of course, I have onboard.

And you always point out Xeon ... you're on the lowest end of Xeon with the W edition. All my workstations have proper Xeons and all of them have onboard video, connected to the onboard management controller. How does that work for off-board nvidia? Is it even possible?

Yes, that's to select advance at the installer menu to install in console mode nomodeset; however, that only makes booting up after the successful install impossible because there is no on-board graphics card on the Dell Precision 5820 and no drivers to accommodate a basic GPU either for whatever card installed.

Edit the kernel command line in Grub or your bootloader of choice. That's why there is a menu always shown for 5 seconds ... exactly for that.

 

[Dunuin]

If Debian 12 doesn't support ZFS, it's not ready for prime time. Wondered when or whether Debian will support PassKey...but that another issue.

Debian is a stability focused distribution. It is and will always be some years behind and that is a good thing if you want stability. And ZFS won't be official part of the linux kernel because people like Linus Torvalds (the guy who invented linux and which after linux is named) don't like ZFS and want to push their own btrfs instead.
I also would like to use ZFS with my Windows machines. But following your argumentation Windows Server is even less production ready because you can't use ZFS at all

 

[Nollimox]

Can your brother elaborate what he dislikes and what software he likes with respect to virtualization?

He didn't elaborate because I was too adamant since I got the recommendation to use Proxmox from pfSense lead developer. If I remember correctly, he had express concern for the choice of using Debian and for what appears the patch job that Proxmox seems to be on top of it.

 

[Nollimox]

But following your argumentation Windows Server is even less production ready because you can't use ZFS at all

Honestly, I never liked Windows...the only reason why I install it on VM (mostly VirtualBox and Parallel) is that Microsoft stop making Project available for Macs...Windows feared losing its business customers who preferred design quality hardware gravitating to Apple.

 

[LnxBil]

If I remember correctly, he had express concern for the choice of using Debian

ah okay. This argument has been made before and - fun fact - previous versions of PVE were based on the RHEL-based kernel with a Debian userland. That changed and it got better ... now we have an Ubuntu LTS Kernel with a Debian userland. Also, Proxmox does not patch anything in Debian, all packages of PVE are additive and only a few packages are mutual exclusive, e.g. qemu binary. PVE uses their own backup system which was rejected upstream, so they need to build it theirselves.

 

[spirit]

And ZFS won't be official part of the linux kernel because people like Linus Torvalds (the guy who invented linux and which after linux is named) don't like ZFS and want to push their own btrfs instead.

That's not the problem.
The problem is that zfs license is incompatible with GPL, so it's impossible of merge it upstream. (but distros can still provide it)

 

[Nollimox]

So, I did the Debian 12.1 install, now getting this:



So, it appears i definitely doesn't like UEFI despite the drive formatted Ext4...what a dilemma, indeed. It did appear as if it was doing some clean, by the drive flashing light indicator; however, a reboot produced the same exact result.

Could one install Ubuntu server...it's supposedly the same as Debian?

 

[Dunuin]

Could one install Ubuntu server...it's supposedly the same as Debian?

No, not the same.

 

[Nollimox]

No, not the same.

Hello Dunuin, do you have any solution to the issues I face? I tried legacy mode to install Debain 12.1 but notice when Grub was added to the hard drive, the drive still had UEFI despite formatted EXT4. Then, ended up cleaning /dev/sda...never getting to the root prompt.

 

[Nollimox]

What's really sad is Debian doesn't respond to alt + F2 or any other combination of keys...what a dilemma indeed. Tried wireless as well as wired keyboard...nothing just stuck.

Tried pinging, then, SSH:

-mac-pro ~ % ping 10.8.27.13
PING 10.8.27.13 (10.8.27.13): 56 data bytes
64 bytes from 10.8.27.13: icmp_seq=0 ttl=64 time=0.488 ms
64 bytes from 10.8.27.13: icmp_seq=1 ttl=64 time=0.434 ms
64 bytes from 10.8.27.13: icmp_seq=2 ttl=64 time=0.338 ms
64 bytes from 10.8.27.13: icmp_seq=3 ttl=64 time=0.416 ms
64 bytes from 10.8.27.13: icmp_seq=4 ttl=64 time=0.398 ms
64 bytes from 10.8.27.13: icmp_seq=5 ttl=64 time=0.372 ms
64 bytes from 10.8.27.13: icmp_seq=6 ttl=64 time=0.451 ms
64 bytes from 10.8.27.13: icmp_seq=7 ttl=64 time=0.413 ms
64 bytes from 10.8.27.13: icmp_seq=8 ttl=64 time=0.399 ms
64 bytes from 10.8.27.13: icmp_seq=9 ttl=64 time=0.337 ms
64 bytes from 10.8.27.13: icmp_seq=10 ttl=64 time=0.430 ms
64 bytes from 10.8.27.13: icmp_seq=11 ttl=64 time=0.512 ms
^C
--- 10.8.27.13 ping statistics ---
12 packets transmitted, 12 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.337/0.416/0.512/0.051 ms
-mac-pro ~ % ssh root@10.8.27.13
The authenticity of host '10.8.27.13 (10.8.27.13)' can't be established.
ED25519 key fingerprint is SHA256:MQaajvI8OpRGdWqYSomTgd7Kzf0v1X2/QchuvZu5rwQ.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '10.8.27.13' (ED25519) to the list of known hosts.
root@10.8.27.13's password:
Permission denied, please try again.
root@10.8.27.13's password:

No luck, then tried other user:

-mac-pro ~ % ssh administrator@10.8.27.13
administrator@10.8.27.13's password:
Linux server1 6.1.0-11-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.38-4 (2023-08-08) x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
administrator@server1:~$

Wipe off sweat...halfway there; now, wondering whether I really like Proxmox!

 

[Nollimox]

To me, it seems that the login is still governed by systemd...maybe graphics drivers are missing, please see below:

Do see any problem?

administrator@server1:~$ systemctl status
● server1
State: running
Units: 255 loaded (incl. loaded aliases)
Jobs: 0 queued
Failed: 0 units
Since: Wed 2023-09-06 14:21:11 CDT; 43min ago
systemd: 252.12-1~deb12u1
CGroup: /
├─init.scope
│ └─1 /sbin/init
├─system.slice
│ ├─cron.service
│ │ └─518 /usr/sbin/cron -f
│ ├─dbus.service
│ │ └─519 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
│ ├─ifup@eno1.service
│ │ └─495 dhclient -4 -v -i -pf /run/dhclient.eno1.pid -lf /var/lib/dhcp/dhclient.eno1.leases -I -df /var/lib/dhcp/dhclient6.eno1.le>
│ ├─ssh.service
│ │ └─569 "sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups"
│ ├─system-getty.slice
│ │ ├─getty@tty1.service
│ │ │ └─524 /sbin/agetty -o "-p -- \\u" --noclear - linux
│ │ └─getty@tty2.service
│ │ └─647 /sbin/agetty -o "-p -- \\u" --noclear - linux
│ ├─systemd-journald.service
│ │ └─345 /lib/systemd/systemd-journald
│ ├─systemd-logind.service
│ │ └─522 /lib/systemd/systemd-logind
│ ├─systemd-timesyncd.service
│ │ └─504 /lib/systemd/systemd-timesyncd
│ └─systemd-udevd.service
│ └─udev
│ └─367 /lib/systemd/systemd-udevd
└─user.slice
└─user-1000.slice
├─session-3.scope
│ ├─718 "sshd: administrator [priv]"
│ ├─732 "sshd: administrator@pts/0"
│ ├─733 -bash
│ ├─737 systemctl status
│ └─738 pager
└─user@1000.service
└─init.scope
├─721 /lib/systemd/systemd --user
└─722 "(sd-pam)"

administrator@server1:~$

 

[Nollimox]

Well, my hostname seems to be unable to edit and hostname --ip-address returns 127.0.1.1, how to change?

administrator@server1:~$ hostname --ip-address
127.0.1.1

 

[BobhWasatch]

Non root can't edit /etc/hosts, use sudo or su to become root. But hostname isn't set that way, use hostname command as root.

 

[Nollimox]

Non root can't edit /etc/hosts, use sudo or su to become root. But hostname isn't set that way, use hostname command as root.

Okay...I had tried sudo but bash said no such command.

That (su) worked, thank you.
root@server1:/home/administrator# hostname --ip-address
10.8.27.13
root@server1:/home/administrator#

 

[Dunuin]

-mac-pro ~ % ssh root@10.8.27.13

For security reasons Debian by default forbids to login as root without pub priv keys.
Options are to ssh as an unprivileged user and then run su - or to set AllowRootLogin yes in /etc/ssh/sshd_config.
"sudo" isn't working because Debian isn't coming with the sudo package by default.

 

[Nollimox]

@Dunuin

update-grub...no such command: another stuck point so close to finishing, why?

root@server1:/home/administrator# update-grub
bash: update-grub: command not found
root@server1:/home/administrator#

 

[Nollimox]

Can anyone explain why update-grub not working?

root@server1:/home/administrator# ls /sbin/update*
/sbin/update-ca-certificates /sbin/update-default-wordlist /sbin/update-grub2 /sbin/update-passwd /sbin/update-smart-drivedb
/sbin/update-catalog /sbin/update-dictcommon-aspell /sbin/update-initramfs /sbin/update-pciids
/sbin/update-default-aspell /sbin/update-dictcommon-hunspell /sbin/update-locale /sbin/update-rc.d
/sbin/update-default-ispell /sbin/update-grub /sbin/update-mime /sbin/update-shells
root@server1:/home/administrator# ~
bash: /root: Is a directory
root@server1:/home/administrator# cd /sbin
root@server1:/sbin# update-grub
bash: update-grub: command not found
root@server1:/sbin# ls -l update-g*
-rwxr-xr-x 1 root root 64 Feb 8 2023 update-grub
lrwxrwxrwx 1 root root 11 Apr 23 14:55 update-grub2 -> update-grub
root@server1:/sbin# update-grub
bash: update-grub: command not found
root@server1:/sbin#

 

[ubu]

So, I did the Debian 12.1 install, now getting this:

View attachment 55125

So, it appears i definitely doesn't like UEFI despite the drive formatted Ext4...what a dilemma, indeed. It did appear as if it was doing some clean, by the drive flashing light indicator; however, a reboot produced the same exact result.

Could one install Ubuntu server...it's supposedly the same as Debian?

The Power fault message seems like a hardware problem to me

 

[BobhWasatch]

/sbin/update-gtub
Linux does not add current directory to the search path as you may be used to from other systems.