Install Proxmox VE on Debian Stretch

Z

zustudios

Renowned Member
Dec 13, 2015
86
0
71
I'm doing the tutorial:
https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Stretch
What could I be doing wrong?
When I do apt update && apt dist-upgrade I get:
root@pve:/home/XX# apt-get update && apt-get upgrade -y
Ign:1 http://ftp.us.debian.org/debian stretch InRelease
Hit:2 http://security.debian.org/debian-security stretch/updates InRelease
Hit:3 http://ftp.us.debian.org/debian stretch-updates InRelease
Hit:4 http://ftp.us.debian.org/debian stretch Release
Hit:6 http://download.proxmox.com/debian/pve stretch InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
9 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up pve-cluster (5.0-12) ...
Job for pve-cluster.service failed because the control process exited with error code.
See "systemctl status pve-cluster.service" and "journalctl -xe" for details.
invoke-rc.d: initscript pve-cluster, action "start" failed.
● pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2017-08-28 18:13:44 CDT; 6ms ago
Process: 6679 ExecStart=/usr/bin/pmxcfs $DAEMON_OPTS (code=exited, status=255)

Aug 28 18:13:44 pve systemd[1]: Starting The Proxmox VE cluster filesystem...
Aug 28 18:13:44 pve pmxcfs[6679]: [main] crit: Unable to get local IP address
Aug 28 18:13:44 pve systemd[1]: pve-cluster.service: Control process exited, code=exited status=255
Aug 28 18:13:44 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Aug 28 18:13:44 pve systemd[1]: pve-cluster.service: Unit entered failed state.
Aug 28 18:13:44 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
dpkg: error processing package pve-cluster (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of pve-firewall:
pve-firewall depends on pve-cluster; however:
Package pve-cluster is not configured yet.

dpkg: error processing package pve-firewall (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libpve-guest-common-perl:
libpve-guest-common-perl depends on pve-cluster; however:
Package pve-cluster is not configured yet.

dpkg: error processing package libpve-guest-common-perl (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of qemu-server:
qemu-server depends on pve-cluster; however:
Package pve-cluster is not configured yet.
qemu-server depends on pve-firewall; however:
Package pve-firewall is not configured yet.
qemu-server depends on libpve-guest-common-perl; however:
Package libpve-guest-common-perl is not configured yet.

dpkg: error processing package qemu-server (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-manager:
pve-manager depends on qemu-server (>= 1.1-1); however:
Package qemu-server is not configured yet.
pve-manager depends on pve-cluster (>= 1.0-29); however:
Package pve-cluster is not configured yet.
pve-manager depends on pve-firewall; however:
Package pve-firewall is not configured yet.

dpkg: error processing package pve-manager (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libpve-access-control:
libpve-access-control depends on pve-cluster; however:
Package pve-cluster is not configured yet.

dpkg: error processing package libpve-access-control (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-container:
pve-container depends on libpve-guest-common-perl; however:
Package libpve-guest-common-perl is not configured yet.
pve-container depends on pve-cluster (>= 4.0-8); however:
Package pve-cluster is not configured yet.

dpkg: error processing package pve-container (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-ha-manager:
pve-ha-manager depends on pve-cluster (>= 3.0-17); however:
Package pve-cluster is not configured yet.
pve-ha-manager depends on qemu-server; however:
Package qemu-server is not configured yet.

dpkg: error processing package pve-ha-manager (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of librados2-perl:
librados2-perl depends on libpve-access-control; however:
Package libpve-access-control is not configured yet.

dpkg: error processing package librados2-perl (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
pve-cluster
pve-firewall
libpve-guest-common-perl
qemu-server
pve-manager
libpve-access-control
pve-container
pve-ha-manager
librados2-perl
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@pve:/home/xx#
 
zustudios said:
When I do apt update && apt dist-upgrade I get:
root@pve:/home/XX# apt-get update && apt-get upgrade -y
Click to expand...
Please do not use upgrade.
dist-upgrade and upgrade are not the same.

Proxmox need dist-upgrade to be proper upgraded.
The reason is some packages like the kernel will not be upgrade with upgrade only.
 
That problem was solved with a reinstall. Now my problem is setting up the bridged network. How do I set up a bridged network with static information?
My host computer uses the public gateway, netmask,and main IP. If I use the same information for the bridge both the host and VM have no connection.
I have no internal information says my ISP.
Everything worked fine with proxmox ISO but the bridge was created automatically so I don't have the settings information.
I'm installing proxmox on top of Debian 9.

Virtual Environment 5.0-30
Logs
bridge 'vmbr0' does not exist
kvm: -netdev type=tap,id=net0,ifname=tap101i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown: network script /var/lib/qemu-server/pve-bridge failed with status 512
TASK ERROR: start failed: command '/usr/bin/kvm -id 101 -chardev 'socket,id=qmp,path=/var/run/qemu-server/101.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -pidfile /var/run/qemu-server/101.pid -daemonize -smbios 'type=1,uuid=809490d8-4d85-4876-8544-ea3ef155d3c5' -name server.example.com -smp '2,sockets=2,cores=1,maxcpus=2' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vga std -vnc unix:/var/run/qemu-server/101.vnc,x509,password -cpu kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce -m 4096 -k en-us -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:af2150b67018' -drive 'if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -device 'virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5' -drive 'file=/var/lib/vz/images/101/vm-101-disk-1.raw,if=none,id=drive-scsi0,cache=writeback,format=raw,aio=threads,detect-zeroes=on' -device 'scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap101i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=6A:E0:B1:E3:84:80,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'' failed: exit code 1
 
Last edited:
I've the same problem, if I delete the vmbr0 from the interfaces file the host has connection to internet, if I configure the vmbr0 I've only local network connection on both, host machine and vms....
This is my interfaces file, any suggestion?
Thanks.

Code: 
auto lo
iface lo inet loopback

allow-hotplug enp5s0f0

auto enp5s0f0
iface enp5s0f0 inet manual

iface enp5s0f0 inet6 manual

auto vmbr0
iface vmbr0 inet static
        address  192.168.1.236
        netmask  255.255.255.0
        gateway  192.168.1.1
        broadcast  192.168.1.255
        bridge_stp off
        bridge_ports enp5s0f0
        network 192.168.1.1
        bridge_maxwait 0
        dns-nameservers 8.8.8.8
        bridge_fd 0

iface vmbr0 inet6 auto
        accept_ra 1

iface enp5s0f1 inet manual
 
That "network 192.168.1.1" entry looks wrong to me ...

Also, what for is the 'broadcast' setting (the default should be good for both setting).
 
ok, I removed the "broadcast and network lines" and... same story...
Code: 
root@host:/home/massi# nano /etc/network/interfaces
root@host:/home/massi# /etc/init.d/networking restart
[ ok ] Restarting networking (via systemctl): networking.service.
root@host:/home/massi# ping google.com
PING google.com (216.58.205.110) 56(84) bytes of data.
From 192.168.1.2 (192.168.1.2): icmp_seq=2 Redirect Host(New nexthop: modemtim.homenet.telecomitalia.it (192.168.1.1))
From 192.168.1.2 (192.168.1.2): icmp_seq=3 Redirect Host(New nexthop: modemtim.homenet.telecomitalia.it (192.168.1.1))
From 192.168.1.2 (192.168.1.2) icmp_seq=1 Destination Host Unreachable
From 192.168.1.2 (192.168.1.2): icmp_seq=5 Redirect Host(New nexthop: modemtim.homenet.telecomitalia.it (192.168.1.1))
From 192.168.1.2 (192.168.1.2): icmp_seq=6 Redirect Host(New nexthop: modemtim.homenet.telecomitalia.it (192.168.1.1))
From 192.168.1.2 (192.168.1.2) icmp_seq=4 Destination Host Unreachable
From 192.168.1.2 (192.168.1.2): icmp_seq=8 Redirect Host(New nexthop: modemtim.homenet.telecomitalia.it (192.168.1.1))
From 192.168.1.2 (192.168.1.2): icmp_seq=9 Redirect Host(New nexthop: modemtim.homenet.telecomitalia.it (192.168.1.1))
From 192.168.1.2 (192.168.1.2) icmp_seq=7 Destination Host Unreachable
From 192.168.1.2 (192.168.1.2): icmp_seq=12 Redirect Host(New nexthop: modemtim.homenet.telecomitalia.it (192.168.1.1))
From 192.168.1.2 (192.168.1.2) icmp_seq=10 Destination Host Unreachable
From 192.168.1.2 (192.168.1.2): icmp_seq=14 Redirect Host(New nexthop: modemtim.homenet.telecomitalia.it (192.168.1.1))
From 192.168.1.2 (192.168.1.2) icmp_seq=13 Destination Host Unreachable
From 192.168.1.2 (192.168.1.2) icmp_seq=14 Destination Host Unreachable
^C
--- google.com ping statistics ---
16 packets transmitted, 0 received, +6 errors, 100% packet loss, time 15067ms
pipe 3
root@host:/home/massi#
 
Yep, no in the gateway but in one switch...sorry, I forgot to save parameters... now works all correctly, thanks
 
You must log in or register to reply here.
Top Bottom