Proxmox VE 2.0 rc1 released!
- Thread starter martin
- Start date
Please read Tom's post above, as I think that he answered that.
I've used 2.0 testing since it first came out, but not for any production data. We use version 2 for servers which have data we can recover elsewhere like approx, dhcp server, etc. We run weekly pve backups and hourly backups using rsnapshot for things like /etc . So using 2.0 rc1 in production totally depends on how well you know you know your data. After all protection of data is the number one priority .
For our order entry and accounting systems, we'll wait for 2.1 .
Hi Guys,
today i have tried to install the Proxmox RC1 on Debian Squeeze (http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Squeeze)
My Problem begin after the packages unzipping and by the settings of the packages.
Some problems with the dependency !! I have no more idea !!
Have a look on my logs !!
today i have tried to install the Proxmox RC1 on Debian Squeeze (http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Squeeze)
My Problem begin after the packages unzipping and by the settings of the packages.
Some problems with the dependency !! I have no more idea !!
Have a look on my logs !!
Please make sure that your hostname is resolvable via /etc/hosts, i.e you need an entry in /etc/hosts which assigns an IP address to that hostname.
This is not the case with the ISO install. I have these open ports 22 (ssh),25 (mail), 80, 443 and 8006 (apache), 85 (pvedaemon) + portmap (111) and rpc.statd port (1732 here) for NFS.
Can't speak for the standalone install on top of an existing OS as I've never used that.
Best regards,
Koen
Last edited:
I think that the official installation-manual contains an incorrect order.
I would like to present my way of installation for Proxmox 2.0 RC1 on Debian Squeeze
INSTALLATION FINISHED
In this way i could perform an error-free installation
I would like to present my way of installation for Proxmox 2.0 RC1 on Debian Squeeze
INSTALLATION FINISHED
In this way i could perform an error-free installation
Thnx, I think you are right. Installing postfix beforehand resolved the issue.
Although one could simply remove the citadel stuff after going through the official install guide I prefer a more perfect clean install
user stuff looks quite nice - though i seem to have a little issue; trying to add a user based on PAM, i only and always get
create user failed: command '/usr/sbin/usermod -p '$5$eoeBVGSZ$mppiCb2wN3CCMZOsY8gYQcRSltGvoWOnEWAG07z1XM/' gnagna' failed: exit code 6 (500)
(which makes somehow sense since there is no user yet for 'usermod'...)
another small glitch - updating from last beta was only possible after doing a manual
update-rc portmap defaults
otherwise, dependency "nfs-common" broke, and all pve* packages subsequently...
create user failed: command '/usr/sbin/usermod -p '$5$eoeBVGSZ$mppiCb2wN3CCMZOsY8gYQcRSltGvoWOnEWAG07z1XM/' gnagna' failed: exit code 6 (500)
(which makes somehow sense since there is no user yet for 'usermod'...)
another small glitch - updating from last beta was only possible after doing a manual
update-rc portmap defaults
otherwise, dependency "nfs-common" broke, and all pve* packages subsequently...
I saw the same thing with the usermod error, then switched to Proxmox VE authentication.
Didn't have to do the NFS stuff though (beta3 installed through ISO).
/K
Didn't have to do the NFS stuff though (beta3 installed through ISO).
/K
[root@freebsd ~]# pciconf -lv
hostb0@pci0:0:0:0: class=0x060000 card=0x11001af4 chip=0x12378086 rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '440FX - 82441FX PMC [Natoma]'
class = bridge
subclass = HOST-PCI
isab0@pci0:0:1:0: class=0x060100 card=0x11001af4 chip=0x70008086 rev=0x00 hdr=0x00
vendor = 'Intel Corporation'
device = '82371SB PIIX3 ISA [Natoma/Triton II]'
class = bridge
subclass = PCI-ISA
atapci0@pci0:0:1:1: class=0x010180 card=0x11001af4 chip=0x70108086 rev=0x00 hdr=0x00
vendor = 'Intel Corporation'
device = '82371SB PIIX3 IDE [Natoma/Triton II]'
class = mass storage
subclass = ATA
none0@pci0:0:1:3: class=0x068000 card=0x11001af4 chip=0x71138086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = '82371AB/EB/MB PIIX4 ACPI'
class = bridge
vgapci0@pci0:0:2:0: class=0x030000 card=0x11001af4 chip=0x11111234 rev=0x00 hdr=0x00
vendor = 'Technical Corp.'
class = display
subclass = VGA
virtio_pci0@pci0:0:3:0: class=0x020000 card=0x00011af4 chip=0x10001af4 rev=0x00 hdr=0x00
vendor = 'Red Hat, Inc'
device = 'Virtio network device'
class = network
subclass = ethernet
virtio_pci1@pci0:0:4:0: class=0x050000 card=0x00051af4 chip=0x10021af4 rev=0x00 hdr=0x00
vendor = 'Red Hat, Inc'
device = 'Virtio memory balloon'
class = memory
subclass = RAM
virtio_pci2@pci0:0:5:0: class=0x010000 card=0x00021af4 chip=0x10011af4 rev=0x00 hdr=0x00
vendor = 'Red Hat, Inc'
device = 'Virtio block device'
class = mass storage
subclass = SCSI
[root@freebsd ~]# uname -a
FreeBSD freebsd.xxx.xxx 9.0-STABLE FreeBSD 9.0-STABLE #0: Wed Feb 22 13:34:16 EET 2012 root@freebsd.xxx.xxx:/usr/obj/usr/src/sys/fbsd amd64
between two guests ( freebsd - linux )
[root@freebsd ~]# iperf -s
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 64.0 KByte (default)
------------------------------------------------------------
[ 4] local yy.yy.yy.yy port 5001 connected with xx.xx.xx.xx port 45727
[ ID] Interval Transfer Bandwidth
[ 4] 0.0-10.0 sec 13.5 GBytes 11.6 Gbits/sec
Since the upgrade to RC1 i've lost VNC connectivity, the console popup appears but no content, apache error log complains:
File does not exist: /usr/share/pve-manager/root/com.tigervnc.vncviewer.VncViewer, referer: https://192.168.178.3:8006/?console=shell&node=proxmox
File does not exist: /usr/share/pve-manager/root/com.tigervnc.vncviewer.VncViewer, referer: https://192.168.178.3:8006/?console=shell&node=proxmox