Recent content by Digdug

Yes, you can even set it to /system/tasks And I assume you added the API tokenas well to the curl command.

Set the permissions to /

Bash to check (using python and JSON so you can get other values as well) result=$(curl -s -k -H 'Authorization: PBSAPIToken=<username>@pam!<tokenname>:<token-secret-value>' "https://<domainname-or-ip>:8007/api2/json/nodes/localhost/tasks?running=true") tasks=$(echo $result | python3 -c "import...

I have a similar problem with one of my Proxmox servers. During the nightly backup the complete system hangs. After a reboot I've to unlock the vm and the backup did not complete. Already changed memory, harddisks. Still same problem, only during nightly backup. The server has two SATA 600 WD...

Today I updated to: pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1) running kernel: 2.6.32-18-pve proxmox-ve-2.6.32: 2.3-88 pve-kernel-2.6.32-10-pve: 2.6.32-63 pve-kernel-2.6.32-18-pve: 2.6.32-88 lvm2: 2.02.95-1pve2 clvm: 2.02.95-1pve2 corosync-pve: 1.4.4-4 openais-pve: 1.1.4-2 libqb: 0.10.1-2...

Had to do the same. To make it work I added the bios_old.bin file to /var/share/kvm and changed the vm.conf to: args: -bios /usr/share/kvm/bios_old.bin cpu: qemu64 FreeBSD is working again! Is the new bios stable enough for other operating systems? Or can we expect other failures (BSOD/Kernel...

Same problem. With pfSense v2.02 i368 and pfSense v2.01 x64 AMD Phenom II X6 1075T host machine FreeBSD 8.1-Release, FreeBSD 8.3-Release AND FreeBSD 9.1-Release won't install. VM Machine has 1 (Default) KVM64 processor, 2 cores 4096Mb static memory adding: set hw.mca.enabled=0 and boot will...

Great! Thanks a lot for the startup-shutdown feature! And the bug-fix for LVM snapshots! Upgrading from 2.0 to 2.1 worked without any issues.

I think it would be a great feature.

Is is possible to start VM machines sequentially instead of parrallel? This way I can load DNS and DHCP servers before any other.

When you remove a backup from the web-gui, it only removes the tar.lzo file, but leaves the log file. I would expect both files to be removed.

This returns "0"

Exactly eth1 is the WAN side and eth0 is the LAN side. Do you use v2.0 of Proxmox, because with v1.9 I did not have this message. I don't have any problems, everything is working like it should, I only get the message.

VM102 is pfSense v2.0.1 64-Bit VM em0 MAC: 02:AA:30:84:F4:52 (vmbr0) VM em1 MAC: 0A:84:5E:B2:A6:A1 (vmbr1) Hmm, shouldn't these be the same as the MAC addresses in tap102i0 and tap102i1?

# brctl show bridge name bridge id STP enabled interfaces vmbr0 8000.f46d04cfb642 no eth0 tap100i0 tap101i0...