Search results

I have similar situation, this time with IBM x3650 M3 (14 x 600GB HDD). Hardware raid /dev/sda is in RAID10 and it's size is 3.8 TB When trying to install Proxmox 1.8 I've got an error pointing that fdisk is unable to create partition larger than 2TB, because disk label is msdos. BUT! :) I...

I need to disable "relatime" option inside openvz VM. It causes my software to "timeout" user connections (strange, but this is our strong guess). Inside openvz VM mount command gives: /dev/simfs on / type simfs (rw,relatime) proc on /proc type proc (rw,relatime) sysfs on /sys type sysfs...

This procedure worked for me: From shell: 1. vconfig add eth0 100 # create vlan 100 > eth0.100 2. ifconfig eth0.100 up # enable this interface 3. brctl addbr vmbr1 # create bridge vmbr1 (for future binding with eth0.100) 4. ifconfig vmbr1 up # enable bridge 5. brctl addif vmbr1...

Hi, OpenVZ VE root block device is /dev/simfs. Unfortunately I need to provide UUID of it for licencing purposes. UUID is "connected" with udev which is not used inside OpenVZ VEs so this may be a problem. There is no /etc/blkid.tab, I tried to create one manualy just for test if blkid will...

I think You missed the volume group creation with vgcreate after pvcreate.

AFAIK lenny 64 stable has no ServeRaid M5015 support. I remember I tested an unstable "sid" (latest night build) and it was OK. Please use lastest stable Proxmox 1.5 ISO, it has full x3650 M2 support. I'm running five machines in a cluster since the release of PVE 1.5 and there is no even...

I just rebooted Hardware Node on which I've manually shell-typed above changes and they persisted. The entry in /etc/network/interfaces, /proc/net/vlan/config and brctl show are still showing eth0.100, vlan100 and vmbr1 bridged with eth0.100. I assume it would be rather easy to implement...

Hi, I'm not sure I understood You correctly but after I manually typed all the settings (using the shell), they immediately appeared in www, under "System" tab. No reboot was necessary. I'm not sure about the stability nor the correctness of these steps, though.

Is the reboot really necessary? What I tried was to manually create the VLAN 100 interface and bridge: 1. vconfig add eth0 100 2. ifconfig eth0.100 up 3. brctl addbr vmbr1 4. brctl addif vmbr1 eth0.100 5. (vi /etc/network/interfaces): auto vmbr1 iface vmbr1 inet manual...

I tested this issue on two hardware nodes, both have Proxmox 1.5 installed but different kernels. The problems exists in both configurations. 1: pve-manager: 1.5-5 (pve-manager/1.5/4627) running kernel: 2.6.18-1-pve proxmox-ve-2.6.18: 1.5-4 pve-kernel-2.6.18-1-pve: 2.6.18-4 qemu-server: 1.1-11...

This issue still exists in version 1.5 of Proxmox. If you remove the dvd-rom drive in hardware tab of vm config, when starting the kvm machine the qemu dvd-rom is still visible in bios bootup screen and later in windows xp. Also I created the kvm container and removed immediately dvd-rom. After...

It works! Flawless and quick installation on all hardware nodes and cluster setup. Thank you very much for such a quick solution and keep up the good work. Best regards!

Great! Any ISO image to download from any location will do :D. Since the x3650 M2 had replaced the older x3650, there is a significant increase in usage of this fine piece of equipment in terms of virtualization.

Thanks for a quick reply! Indeed, Centos 5.4 x86_64 properly recognized sda drive. There was explicit information in the installer that detected controller is ServeRAID M5015. Is there a chance that M5015 drivers/modules from Centos 5.4 installation can be of any use to you in proxmox kernel...

During the installation of latest release of Proxmox 1.4 (build 4390) on x3650 M2 the installer complains that it cannot find any hard disk installed in the system. This server has ServeRAID M5015 Controller, which is pretty new and supported only on few operating systems yet the latest weekly...