I just upgraded a server from proxmox 1.2 (kernel 2.24) to proxmox 1.9 (kernel 2.6.32-7)
Everything seemed to go well. However some of our applications do not work properly.
Upon looking at the startup logs of the openvz containers I noticed the following issues.
Starting iSCSI daemon...
Could you please provide references supporting your statement?
A few notes:
- HT on pre-nehalem are different than HT from nehalem and newer processors.. (ours at the time was a nehalem 5520).
- Some do not recommend because they do not see measurable performance gains
- Some say that some...
Good point except that I don't fall under the developer's category of open source contributors.
The question is:
Whether you can find a fix to this in a matter of days, in which case I would not mind even paying for a support ticket. But provided that you feel confident that you guys can nail...
Diermar I see your point and that is expected.
However I would like to balance it with my thoughts.
1. You probably won't get much support contact in general unless on production servers. So if someone can't go to production with proxmox, your chance of selling a support contract to that...
Thank you spirit,
The issue is that we are not trying to find a way to escape the issue here because we do not understand what this means and the impact.
We would rather have a real solution. Why would other OS install find without this issue but not proxmox? Clearly something is missing. We...
Ok guys:
We were supposed deploy a new production server tomorrow with Proxmox 2.0.
However with this new issue we cannot deploy Proxmox 2.0.
We have decided to delay the production server release by a few days while waiting to receive a fix from you guys.
I am available every day to test...
APEI: Can not request iomem region <00000000bf7b85ea-00000000bf7b85ec> for GARs.
I have a feeling that Proxmox is get able to read all the memory.
APEI: Can not request iomem region <00000000bf7b85ea-00000000bf7b85ec> for GARs.
I am attaching some logs if that could help.
Guys this is definitely a Proxmox Issue.
1. I installed proxmox 1.9 on the same system and i did not get this issue.
2. I contacted supermicro and they said:
Please contact operating system company you installed. This issue may not release to BIOS issue...
This is the hardware I use:
"Supermicro SYS-1026T-6RF+ 1U Intel Xeon5600/5500 DDR3 PCIE2 750W Black
"
Intel CPU BX80614X5650 Xeon 6 Core X5650 2.66GHz LGA1366 12MB 6.40GT Retail
See specs attached.
Can someone shed some light on how Proxmox utilizes the disk space at installation?
- I start with a 445GB RAID 10 storage,
- set pve root to use 45GB at installation
- swap ends up being total memory 24GB (does swap take actual physical extra space?)
And I end up with pve local storage of...
APEI: Can not request iomem region <00000000bf7b85ea-00000000bf7b85ec> for GARs.
I just installed proxmox 2.0rc1 on an Intel Xeon X5650 @ 2.67GHz with 24GB of RAM.
And set the maxroot to 45G
The main storage is on LSI Megaraid RAID10 with 8 drives - total 445GB.
The first boot message I get...
Just to bring a correction to the last post's command.
To set the maxroot for pve the enter the max size without the letter "G".
e.g. maxroot=20 (not maxroot=20G)
This will set pve root to use only 20GB.
Thanks Dietmar,
I guess what I am trying to figure out is whether I should do a phased upgrade into multiple versions to get to 2.0 or if I should simply do a single command upgrade?
And in the worst case scenario if I just install a fresh 2.0 can I import without an issue all the VZ...
We still have a couple of servers running Proxmox 1.2.
1. How would you recommend we go about upgrading them to Proxmox 2.0 without breaking anything?
2. would we have to re-install or upgrade?
3. if we export all containers from Proxmox 1.2, would they import fine and work fine directly in...
Thanks for reaching out.
I paid $4400 for the Z-drive this past october.. at the time their linux drivers were not ready yet. So I ended up buying an LSI card as I could not wait. I wanted to return the item but they said that they cannot accept a return because it is not defective.
I was one...
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.