I'm using Proxmox 1.6 on a Debian Squeeze Host. I have the following issue. The IP of eth0 and vmbr0 is different, and the hostname is mapped in /etc/hosts to the vmbr0 IP (which is a "private" IP, just for the VE) instead of the eth0 IP, which is a public Internet IP. I want the mapping to be fixed, so I can put my servers into a cluster. I decided against "fixing" the Proxmox scripts, because I would be back to square one after a Proxmox update. So I fixed /etc/hosts manually but it gets modified again at boot, which I have just found out. Since there didn't seem to be an obvious fix (after searching the forum), I decided to just make the file read-only, in the hope that it would be left untouched, but now the server won't even come back online after a reboot or react to a Remote Reset command, so I had to pay a technician to do a hardware reset (still waiting for it). This is about the last thing I would have expected...
IMHO, not booting anymore because a perfectly correct /etc/hosts is read-only is a critical bug, and should be fixed. Either just overwrite it, or log an error message and move on, but don't simply jam forever.
IMHO, not booting anymore because a perfectly correct /etc/hosts is read-only is a critical bug, and should be fixed. Either just overwrite it, or log an error message and move on, but don't simply jam forever.