[SOLVED] Messed with grub and broke proxmox web interface

Timusius

New Member
Feb 3, 2024
2
0
1
I am running proxmox on a Lenovo Tiny m900 and trying to make GPU passthrough.

I am by no means a Linux wizard, so today I simply googled around and tried to follow this guide: https://wiki.andeljan.cz/en/public/Proxmox-passthrough
I thought, "Ok this is just some option that will enable the sharing of the GPU, and I can easily go back."

So I changed the grub line to: GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on i915.enable_gvt=1" , did "update-grub" and rebooted.

The first thing I noticed was that proxmox web interface did not respond :-(
SSH also does not respond. (I am not sure if it's even enabled, so it could just be this.)

So I physically connect a screen and keyboard to the machine, and log in.
I am met by the screen simply telling me to go to 192.168.1.40:8006, that I just tried. (This matches the static IP I set for the machine during proxmox install, and where I am trying to reach proxmox web interface.)
Proxmox seems to think that it is running just fine I guess?

I revert the change to grub (the line is set back to GRUB_CMDLINE_LINUX_DEFAULT="quiet" ), did another "update-grub" and restarted. Proxmox is still broken.
Full shutdown... reboot.. still broken?

Where should I look to fix this?


Misc Info:

At first I thought the network was completely dead on the machine, so i did :
cat /etc/network/interface
and is sort of confused that the only ip address I can see, is for vmbr0 which seems to have 192.168.1.51 which is an address for a LXC container, that is not running at the moment.

The VM's and containers seem to run just fine. (I run Home assistant and try to run Frigate NVR, and their pages show up just as they should.)

cat /etc/hosts look just fine with the correct entry for the proxmox host:
127.0.0.1 localhost.localdomain localhost
192.168.1.40 tiny.local Tiny

# The following lines are desirable for IPv6 capable hosts

::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts


systemctl status pveproxy.service responds just fine with: active (running)
 
Last edited:
I am met by the screen simply telling me to go to 192.168.1.40:8006, that I just tried. (This matches the static IP I set for the machine during proxmox install, and where I am trying to reach proxmox web interface.)
cat /etc/hosts look just fine with the correct entry for the proxmox host:
127.0.0.1 localhost.localdomain localhost
192.168.1.40 tiny.local Tiny
cat /etc/network/interface
and is sort of confused that the only ip address I can see, is for vmbr0 which seems to have 192.168.1.51 which is an address for a LXC container, that is not running at the moment.

Change the address for vmbr0 in /etc/network/interfaces back to 192.168.1.40 and reboot the PVE-host.
 
Change the address for vmbr0 in /etc/network/interfaces back to 192.168.1.40 and reboot the PVE-host.
Thanks! It worked perfectly!

I thought it was only related to the virtual bridge, so I did not think about changing it.

Now I just wonder how my kernel parameter attempt ended up changing that network related thing... and what else it may have messed up :-D
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!