I am a little bit confused on how to interpret the results of pveversion -v in terms of the kernel version. It seems to say both 2.6.32-6-pve and 2.6.32-54. Here are the results from running it.
root@proxmox:~# pveversion -v
pve-manager: 2.0-14 (pve-manager/2.0/6a150142)
running kernel...
Lately (maybe since around beta 2 or 3) my Proxmox VE 2.0 server keeps going off of the network every few days or so. I have to go and press the reset button on the server. Is anyone else having this issue? Is there anything I can do to fix the issue? Thanks in advance.
In proxmox VE 2.0 beta 1, in the list of VMs on the side, after each VM number, the VM name was in parenthesis. Now, the VM name isn't there, so I am forced to distinguish between VMs based solely on number. Is this just me, or did you take away this handy feature? Thanks in advance.
OK, but are you expecting to actually have the overall look and feel be any different? As in, will I be able to take a quick look at the stable version vs the current version and notice any difference? It is good to know that you are steadily adding features though.
Actually, Untangle was the one router distro that worked for me. However, it took forever to boot, was a bit sluggish, and had too many features that you had to pay for. My advice with your issues though: Check the MD5sum of the iso. You might have gotten a corrupted download.
On the network model wiki page, it says, "Physical NIC (eg., eth1) cannot currently be made available exclusively for a particular KVM / Container , ie., without bridge and/or bond." Will this be made possible with 2.0? It would really simplify setting up a virtual router. In particular I am...
I would have to assume that that would work. I can't think of a reason it wouldn't anyways. For cloning, use Clonezilla or Easeus Disk Copy. Good luck!!
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.