As my original post says this is only an issue on my new hardware, I have other older boxes that work just fine. Does anyone know of a possible BIOS setting that would cause FreeBSD 64bit to hang?
Running 32 bit version works.
I do have 64 bit pfsence 2.0.1 running on different box no issues. Guess I'll just have to migrate to 32 bit for now.
Thanks
I figured it might be something about hardware and kernels.
I just remembered that the recent hang was a migrate from a 2.6.32-14-pve host and a 2.6.32-12-pve host, where the 2.6.32-12-pve host hung. I'm just testing some new hardware so once I'm happy I'll purchase more so all nodes are...
With the following hardware:
MB: Gigabyte GA-Z77X-D3H
BIOS: F11
CPU: i5-3570K
Mem: 32Gb
and a fresh install of Proxmox VE 2.1, I am unable to install FreeBSD in a VM or boot an existing FreeBSD VM. Starting the VM gets into the bootloader but once I select a boot option it freezes with the \...
Thanks, I didn't know that. I have been using vzmigrate for years now and assumed it was the same under 2.x. I'll use pvectl instead.
That worked kinda... The destination box hung. I've noticed that since upgrading to 2.1, online migration hangs destination host quite a bit.
Exactly same issue. Brand new install from promox ve 2.x cd did apt-get grade and can't run vzmigrate
root@proxmox16:~# vzmigrate proxmox4 2012
Starting migration of CT 2012 to proxmox4
Preparing remote node
Error: Failed to copy config file
I modified copy of the vzmigrate script and...
I'm having this issue with vzmigrate commandline under Proxmox VE 2.1 latest updates. I like to migrate boxes from commandline so is this going to be fixed? This appears to be an issue with the clustered filesystem /etc/pve.
As badaboom had mentioned the mv command appears to work under the...
I have the exact same issue every time I try and run backups to a central NFS share. Backups hang and I have to kill the processes, delete the storage in GUI, unmount the shared mounts manually and restart the pve daemons to get things working again. I didn't have this issue with 1.9 only...
I as about to post that an OpenVZ container doesn't work because ZFS handles quotas differently OpenVZ just doesn't work when quota's are enabled. That was my experience last month when I first tested things under ZFS on Linux rc6. I was able to get a container running by disabling disk...
For the hard drive I have setup IDE raw and it works on my 2.0 and 1.9 installs. I basically accept the defaults for both disk and network.
I did a quick test install and virtio disks/network don't work for pfsense.
You don't need anything extra on your proxmox host (shorewall, forwarding)...
I have been using pfsense in a KVM as a production router for more than a year and it works very well. No need to assign IP addresses to physical interfaces eth0 or eth1. Given your setup here's a valid interfaces file below, that will work. Notice I have the proxmox host's IP assigned to...
Thanks for the great work. I used the Upgrade_from_1.9_to_2.0 process on my highly modified 1.9 box and it worked, well kinda.
The command that fixed almost all my errors was to run: apt-get -f install, to manually get the issues resolved and then simply re-run the upgrade script. After a few...
That's what I figured... but it's always good to get more feedback.
You wouldn't know of any good cheap hardware firewall/routers that can handle 20 WAN IPs with various NAT rules? My current ISP provided router supports the IPs, but isn't really configurable when it comes to NAT rules. And...
I'm thinking about migrating from a hardware firewall/router to pfSense a software solution. So, I setup a test environment using KVM in proxmox to benchmark things and once I'm happy with pfSense I'll purchase dedicated hardware to put in front of the other hardware. So now my problem is that...
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.