Proxmox won't allow access to VMs via ping or http (browsing)?

[eiger3970]

Proxmox loads and runs itself and VMs, however doesn't allow access to ping/browse the VMs.
Proxmox can access IPs in the LAN and WAN.
If I try to shutdown via the Proxmox GUI or comand line, the VMs don't shutdown and a Proxmox error states: Time out.

 

[reflex]

Can you ping the VMs from the node?

We need more info, network setup for instance.

 

[eiger3970]

Thank you for the reply.
I cannot ping the VMs from the node.
The network setup is Proxmox with VMs > Cat6e > router > Cat6e > My computer.

 

[reflex]

Not talking about cables, I mean the network config on the node and the VMs.

 

[eiger3970]

So I think this is the network config for the Proxmox node.

root@proxmox:/# ifconfig
eth0 Link encap:Ethernet HWaddr c8:3a:35:d5:5b:17
inet6 addr: fe80::ca3a:35ff:fed5:5b17/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:26847 errors:0 dropped:0 overruns:0 frame:0
TX packets:15661 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3184747 (3.0 MiB) TX bytes:3512280 (3.3 MiB)
Interrupt:23 Base address:0x4c00


lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:5156 errors:0 dropped:0 overruns:0 frame:0
TX packets:5156 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2261522 (2.1 MiB) TX bytes:2261522 (2.1 MiB)


tap163i0 Link encap:Ethernet HWaddr 56:63:cd:e2:07:d6
inet6 addr: fe80::5463:cdff:fee2:7d6/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:5461 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 (0.0 B) TX bytes:332954 (325.1 KiB)


tap164i0 Link encap:Ethernet HWaddr 1e:50:f5:36:ea:f1
inet6 addr: fe80::1c50:f5ff:fe36:eaf1/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:5449 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 (0.0 B) TX bytes:332234 (324.4 KiB)


venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet6 addr: fe80::1/128 Scope:Link
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:3 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)


vmbr0 Link encap:Ethernet HWaddr c8:3a:35:d5:5b:17
inet addr:192.168.1.160 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::ca3a:35ff:fed5:5b17/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:26749 errors:0 dropped:0 overruns:0 frame:0
TX packets:15619 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2797238 (2.6 MiB) TX bytes:3509484 (3.3 MiB)


Not quite sure how to access the network config for the VMs, which I have set with different IP addresses.

 

[reflex]

Do you route the VM IPs?

What about /etc/network/interfaces on proxmox node

VMs: /etc/sysconfig/network, /etc/sysconfig/network-scripts/ifcfg-venet* or /etc/sysconfig/network-scripts/ifcfg-eth*

 

[eiger3970]

root@proxmox:/etc/network nano interfaces gives error:
-bash: /usr/bin/nano: Input/output error.

The paths: /etc/sysconfig/network, /etc/sysconfig/network-scripts/ifcfg-venet* or /etc/sysconfig/network-scripts/ifcfg-eth* is not available under root@proxmox:/etc#
root@proxmox:/etc# ls
adduser.conf cron.daily gai.conf insserv login.defs motd.tail profile resolv.conf ssl
aliases cron.hourly groff insserv.conf logrotate.conf mtab profile.d resolv.conf.lock sysctl.conf
aliases.db cron.monthly group insserv.conf.d logrotate.d Muttrc protocols rmt sysctl.d
alternatives crontab group- iproute2 lsb-base Muttrc.d pve rpc terminfo
apache2 cron.weekly grub.d iscsi lvm nanorc python rsyslog.conf texmf
apt debconf.conf gshadow issue lynx-cur network python2.6 rsyslog.d timezone
at.deny debian_version gshadow- issue.net magic networks qemu-server samba ts.conf
bash.bashrc default gssapi_mech.conf kernel magic.mime nsswitch.conf rc0.d securetty ucf.conf
bash_completion defoma host.conf ksmtuned.conf mailcap ntp.conf rc1.d security udev
bash_completion.d deluser.conf hostname kvm mailcap.order opt rc2.d sensors3.conf ufw
bindresvport.blacklist dhcp hosts ldap mail.rc pam.conf rc3.d sensors.d updatedb.conf
ca-certificates dhcp3 hosts.allow ld.so.cache manpath.config pam.d rc4.d services vga
ca-certificates.conf dpkg hosts.deny ld.so.conf mediaprm pango rc5.d shadow vim
calendar environment idmapd.conf ld.so.conf.d mime.types passwd rc6.d shadow- vz
cluster fdmount.conf init.d locale.alias mke2fs.conf passwd- rc.local shells vzdump.conf
console fonts initramfs-tools locale.gen modprobe.d perl rcS.d skel w3m
console-tools fstab inittab localtime modules postfix reportbug.conf snmp wgetrc
cron.d fuse.conf inputrc logcheck motd ppp resolvconf ssh X11

 

[reflex]

root@proxmox:/etc/network nano interfaces gives error:
-bash: /usr/bin/nano: Input/output error.

You have more serious things to worry about than the network config. If you know Linux well: you can try to fix it, otherwise I'd suggest to start over with a new Proxmox install.

 

[eiger3970]

Thanks for your reply.
Yes, I have begun a new HDD with new Proxmox install, however Proxmox is not restoring this faulty Proxmox/HDD backup.
Here's my Proxmox forum thread re Proxmox restore http://forum.proxmox.com/threads/14360-New-Proxmox-install-won-t-restore-old-Proxmox-backups

 

[eiger3970]

As I can't restore from Proxmox backups onto a new Proxmox I'm building due to this Proxmox problem, I have tested this faulty Proxmox on another computer.
Seems to load the GRUB.
However I cannot ping the gateway?
$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 vmbr0
0.0.0.0 192.168.1.180 0.0.0.0 UG 0 0 0 vmbr0

So the computer seems to find the gateway, but no pinging?
Any ideas, because if I can use this Proxmox HDD, it will be easier as my rebuild isn't working yet and I can't restore any backups?

 

[reflex]

That table per se looks good.

Can you ping the proxmox machine from the gateway?

Also: 192.168.1.0 does look awfully like a network identifier. Try with 192.168.1.1

 

[eiger3970]

The router (192.168.1.180) cannot ping Proxmox's HDD 192.168.1.160.
The router's results from route -n are:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.0.50 0.0.0.0 UG 0 0 0 vlan2
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 br0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 vlan2
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 br0
239.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 br0

 

[eiger3970]

So also tested another computer that works and the results are similar for route -n:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.1.180 0.0.0.0 UG 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0

I have put a 2nd HDD with proxmox in the computer and same fault.
Tried Ethernet cable in MOBO Ethernet port and on NIC Ethernet port and same error.
Tried different HDD SATA data cable and same error.
Checking RAM and MOBO now as now many other factors apart from the unusual route -n results. I didn't change any settings when Proxmox stopped working, so any further suggestions welcome.

 

[eiger3970]

Summary:
Original HDD with original Proxmox doesn't work in new server or original server.
New HDD with new Proxmox works in new server, but not in office server.

Old server's hardware checked and working:
Ethernet cable from server to router
RAM
HDD
HDD SATA data cable
MOBO Ethernet port
NIC

Maybe I have to reconfigure the virtualisation software in such a way that it permits access from the physical network card to the VM?
Although this works on original Proxmox build, so not sure how any Proxmox network settings have changed?