Search results

I am going to assume this is a Windows VM running in Proxmox. You can use the disk management utility to expand the C drive onto the other disk. The best way would be to create a new larger disk and image the C drive to this new disk, then replace the old disk with the new larger one. Also...

I just use a simple mail filter to move the successful backups elsewhere, and the failed ones stay in my inbox.

I just wanted to let everyone know who still might be running VE 1.x. There seems to be an issue with networking in CentOS 6.5 with the OpenVZ kernel 2.6.18, which PVE 1.x runs. PVE 2.x & 3.x are not affected by this, they run the 2.6.32 RHEL6 kernel. The recommended permanent fix is to...

Debian has not set a end of life for squeeze yet, everyone is estimating early 2014. Proxmox has EOL'ed version 2.x. The last update from the Proxmox team was a kernel update back in May. I doubt there will be any other updates. (from Proxmox) Debian will continue to release security updates as...

443 is a privileged port, only root can open any ports under 1024.

Re: Hardware Recommendation / Raid controller with operational web interface on proxm I use LSIs 3ware line of cards, their web based interface (3DM2) is available in a deb package. Not to mention it is very very easy to use.

You could use the sudo command and the sudoers file to allow other users to run vzctl, but they would be able to use the entire command, vzctl destroy for example.

You can also run the installer in text mode, you will have to check the CentOS documentation for how to do that.

You could use the tab key to select the button, I have done that before. Can you increase the screen resolution on your computer?

Just use the templates from the OpenVZ team, they are kept more current then the Proxmox provided templates. I have also noticed the naming restrictions on 1.x don't seem to apply anymore, I can use the default filename from openvz, and they work. Here is the URL...

He also has a Windows 2003 SBS system I want to transfer to a virtual machine as well, what would be the best tool to do that?

I am going to be setting up a dual Xeon E5620 based supermicro system for a client, he is wanting to use Windows 2008, I wanted to know if anyone had any recommended settings for that OS, like disk storage type, drivers, etc. The system has 8 drives with a 3ware 9650SE raid card, I am most...

Nobody should be doing new installs of Proxmox 1.9, it is end of life. Any new/old servers are just sitting around waiting for some security bug/flaw/hack to appear in postfix/apache2/etc.

The most common problems I see are: 1) No reverse DNS on the IP the server is using. 2) Invalid hostname (proxmox.localdomain) Add "myhostname = proxmox.mydomain.com" to /etc/mail/main.cf 3) No valid DNS setup for proxmox hostname (proxmox.mydomain.com A 1.2.3.4)

I don't know if your aware of the Rackable line of servers. They all come with a built in card called the roamer, it allows remote console access, power control, and limited monitoring over a telnet connection. I was wondering what would be involved in getting this working as a fencing device...

Does the processor in this second machine support virtualization technology? and is it enabled in the BIOS?

Sounds like you clicked the "all" checkbox in the backup configuration screen, then deleted something, even though the cron job just stays "--all" somehow it remembers the VEIDs of the deleted machines. Just reopen the backup job, uncheck "all" .... save ... recheck "all" .... fixed.

bingo! This was the problem ERROR: unable to parse config line: DISK_QUOTA=yes#012 ----- DISK_QUOTA=yes ----- I added quotes to yes, and that fixed it ----- DISK_QUOTA="yes" ----- The settings were all screwey, the machine had 7mb ram allocated and 7162 mb of swap. had 449.6 GB of disk...

Yes, that is one of the first things I looked at. I just checked again, I had the setting as "pve-auto", its supposed to be "pve.auto". It is still not showing up in the web interface list. I restarted vz & pvedaemon again just to be sure (after the pve-auto/pve.auto change) Here is the...

I moved a OpenVZ container from a CentOS based OpenVZ system to proxmox, I can see it if I run "vzlist", but it doesn't show up in the web interface. Is there something I need to do? (I restarted the vz, pvedaemon, apache2 services already)