Search results

I found no way to get pfSense working after complete update to 2.3 on pvetest. But a complete reinstall of pfSense worked perfectly. I'm using Proxmox from the beginning (may 2008). It is my feeling that Proxmox was very, very stable for such a complex system in quick development. Untill 2.0...

Re: AW: Updates for Proxmox VE 2.2 - including QEMU 1.3 Same problem with Nas4free. Tried to reinstall, same problem. Tried to install Freenas 7 same problem. Erk's trick with shutdown worked but is to complicated for reliable use. Peter

That's right, Tom. I get the console but I can't login. I will use the workarounds. Thank you for your support. proxmox rocks!! Peter

Thank you villain666. i tried your proposal on a openvz container ubuntu 10.04.4 LTS. But I found no way to make the console work.

I mean Turnkey openvz before they turned from ubuntu to debian. Openvz containers based on ubuntu downloaded at the time from the Proxmox website either don't have the inittab file. In that case: where do I put your line to be able to use the console. Peter

Thank you Tom. It works. But on older openvz ct's based on turnkey ubuntu versions I can't find /etc/inittab. What now, dear Tom? Peter

Yes, it was on the command line. It's just a not correctly formulated error message. Peter

I got the following error message using qmrestore: dos not lock like a QemuServer vzdump backup I guess this should be: does not look like a QuemuServer vzdump backup. Peter

Turnkey (http://www.turnkeylinux.org/) offers more than 30 ready made linux servers. I use them to install them on Proxmox under KVM. Now they bring them also as Openvz containers. On their website you find in the forum a howto to install them as easy as the Openvz containers offered by Proxmox...

My syslog is full of the WARNING: Cannot encode 'meminfo' element as 'hash'. Will be encoded as 'map' instead What does this mean? I have some strange issues, like a backup not being able to restore. proxmox1:~# pveversion -v pve-manager: 1.7-12 (pve-manager/1.7/5490) running kernel...

When removing a VM I get the message: Weet u zeker dat u VM %? wilt verwijderen? Dit zal de opgeslagen data permanent verwijderen The number of the VM is not presented. This is not a new bug. Maybe only in the dutch translation. pveversion: pve-manager: 1.7-12 (pve-manager/1.7/5490) running...

very good news. Computers are one of my hobbies since 1985. Two years ago I stopped having all kind of troubles with microsoft and paying for crap software or searching the internet for illegal keys. I turned to linux. Quite a relief. For my web, ftp, dns, mail, music, wordpress, genealogy...

Thanks Clipcarl. It works fine. Just two remarks. I had to restart openbsd-inetd by proxmox2:~# /etc/init.d/openbsd-inetd restart. In a cluster you need to change /etc/inetd.conf for the vm in the node where the vm is placed and use the IP of that node!! As a client I use Remmina on Linux...

Since virtio is a better choice on kvm for the hdd interface I want to change that for my vm's. It works without a problem for the nic. But it is unclear to me whether it is possible for de hdd interface. So: is it possible en howto? I'm very happy with my proxmox servers. Great work. seen...

Hello, I have two proxmox in a cluster. On proxmox1 I added a second hdd (LVM) to a kvm vm with Freenas. Works perfect. But on proxmox2 I get the following error when opening the tab hardware on every kvm vm: [4513]ERR: 24: Error in Perl code: command '/sbin/vgchange -aly hdd101-c' failed...

hello Tom , Hello Dietmar To Tom: proxmox2:/var/lib/vz/images/105# ls -l totaal 3517440 -rw-r--r-- 1 root root 3598340096 nov 20 10:03 vm-105-disk.qcow2 To Dietmar: /etc/qemu-server/105.conf: name: joomla sockets: 1 vlan0: rtl8139=56:A5:B7:8A:97:95 bootdisk: ide0 ide0: vm-105-disk.qcow2...

Hallo Tom, On both nodes is 1.4 installed. With the latest updates of yesterday The log (migration of running vm): /usr/bin/ssh -t -t -n -o BatchMode=yes 192.168.0.102 /usr/sbin/qmigrate --online 192.168.0.101 105 Nov 20 10:03:46 starting migration of VM 105 to host '192.168.0.101' Nov 20...

I migrated vm 105 from proxmox 2 to proxmox1. Not running. It said that the migration was succesfull. The vm would not start. Then I tried your command: proxmox1:~# qm start 105 volume 'local:105/vm-105-disk.qcow2' does not exist proxmox1:~# When I migrate it back it will work again. Peter

Hallo Dietmar, The file exists because the VM works fine. I also managed to restore a backup of it on the other Proxmox server in the cluster, but that VM could also not be migrated. I had a broken memory on this server and had to reinstall. It all seemed to work, only migrating the kvm vm's...

When I migrate a running kvm vm I get the error: volume 'local:103/vm-103-disk.qcow2' does not exist When I migrate it not running, the vm will be migrated, but will not start. openvz containers will be migrated without a problem. proxmox2:~# pveversion -v pve-manager: 1.4-10...