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...
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...
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?
Hello Dietmar,
Changed the setting to "on" and the error still occurs...
Strange thing is eth1 doesn't have an ip address, or is it the ip6 address that sends the packet?
I have a host with two interfaces eth0 and eth1
eth0 has a local ip
eth1 has no ip
Since Proxmox 2.0 I recieve this message:
eth1 received packet with own address as source address
Why do I get this message?
My interfaces:
# network interface settings
auto lo
iface lo inet loopback
iface...
Ok, think I "fixed" it with a workaround from 2010...
CPU is set to QEMU64
In the virtual machine added:
vm.pmap.pg_ps_enabled="0"
to /boot/loader.conf
Now the system boots properly, time will tell...
Hi, thanks for the reply. I found the same and tried KVM CPU to mode host and opteron_Gx.
FreeBSD correctly sees the host, halts with a "fatal trap 9: general protection fault while in kernel mode"
When I set the cpu back to QEMU64 it boots, but as soon as the login prompt display's, it reboots...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.