Search results

Hi, I have three nodes in a cluster with Proxmox ve 2.1 installed. An external SAS storage is used as the main shared storage in LVM mode. Everything seems to work almost fine. The migration works fine. The problem is that sometimes (once or twice a week) one of the nodes (the same one) becomes...

Hi, I have some VM's installed on three nodes with Proxmox VE 2.1. The problem is that the VM's won't shutdown when I click the button "shutdown" in the main interface. I would say it didn't worked in proxmox ve 1.9 as well without opening the console window of the VM. But the VM DOES shutdown...

I have Proxmox VE 1.9, not 2.0 I added these options according to this post: forum.proxmox.com/threads/6964-Change-NFS-mount-options Now it looks like this: nfs: O_NFS path /mnt/pve/O_NFS server 172.16.10.200 export /nfs options udp content backup Seems...

I already solved the problem. I added "option udp" to the storage.cfg where my nfs shares are mentioned and now it works fast in and out. Strange but it seems that Debian and OpenBSD aren't very friendly to each other when nfs with tcp protocol is used. Although scp between them works fast...

I have two proxmox nodes in a cluster with directly attached shared storage (HP MSA 2000) where VMs are running. I also set up an NFS share on a separate OpenBSD machine as a storage for vzdump images. The backup process seems to run properly. According to backup logs it takes from 30...

Tha additional question to that topic is: how do I stop the vzdump process correctly if I suppose it hang? Should I simply kill the processes with corresponding PIDs and issue the command qm unlock VMID?

It is complicated to do a check with no load on the servers. I can try it later. Now it shows the following (20 KVM guests on the storage): CPU BOGOMIPS: 14932.37 REGEX/SECOND: 585656 HD SIZE: 2.21 GB (/dev/mapper/pve-root) BUFFERED READS: 65.20 MB/sec AVERAGE SEEK TIME...

Hi, the situation is this. During the backup process, when the snapshot method is used, the process may hang (while the VM itself functions properly more or less). I noticed that it happens when a VM (Windows guest only. It NEVER happened with Linux KVM guests) reboots. This occurs when I VM...

I try to issue the command "/etc/init.d/networking restart" but it has no effect on the changes I made in the web interface. The second bridge device doesn't appear in the network configuration.

Hi, When I add a bridge device in the web interface of a physical server it says to me that I must reboot the server to apply changes. Why is it so? It is very complicated to reboot the physical server with a couple of VMs that MUST run in uninterruptible mode. Any ideas? Or do I miss anything?

The partition is OK. I just followed somebody's advice to make a partition across the whole disk to make sure that no other OS would try to initialize the disk as an empty one. Then I made the same VG and continued working on it. Another try with pvmove failed with the same result: pvmove -v...

pvscan PV /dev/block/104:178 VG pve lvm2 [8.80 GB / 1.11 GB free] PV /dev/block/104:481 VG VGONVD3 lvm2 [2.00 TB / 1.82 TB free] (This is what I need) PV /dev/block/104:449 VG VGONVD3 lvm2 [1.59 TB / 1.59 TB free] pvdisplay "/dev/block/104:481" --- Physical volume --- PV...

Hi. I have an LVM storage on a proxmox server with some virtual disks on it. I want to move them all to another storage. The storage was created so: pvcreate /dev/cciss/c0d8p1 (adding a disk with 2TB space) vgcreate VGONVD3 /dev/cciss/c0d8p1 What I do now: pvcreate /dev/cciss/c0d6p1 (adding a...

The result is the same: pvmove /dev/block/104\:480 Physical volume /dev/block/104 not found Run `pvmove --help' for more information. The same result with pvmove "/dev/block/104\:480" (in quotes) Here is the result of "ls": ls 104:0 104:19 104:245 104:352 104:421 104:51 104:592...

I'm trying to move a volume group to another physical storage issuing a command: pvmove /dev/cciss/c0d8 and get an answer: Physical Volume "/dev/cciss/c0d8" not found in Volume Group "VGONVD4" But I am sure I created a physical volume using this device name like this: pvcreate /dev/cciss/c0d8...

No, no, no! I think it is not a way to move the storage online! I expect something with commands "pvmove" and "vgreduce" The question was: which disk name should I use in these commands. I expected to use "pvmove /dev/cciss/c0d8", but now it must be something different.

I'm trying to move a volume group to another physical storage issuing a command: pvmove /dev/cciss/c0d8 and get an answer: Physical Volume "/dev/cciss/c0d8" not found in Volume Group "VGONVD4" But I am sure I created a physical volume using this device name like this: pvcreate /dev/cciss/c0d8...

Ok, thank you. I will try it. But is there a way to move them between machines or move them to another storage like simple disk files in backup purposes? And one more question remains: can i use physical storage as LUN's, so as I can see a single physical disk and not four related to four fault...

I set up a shared storage for proxmox ve using an external sas controller HP 2012MSA and I think I do something wrong because my kvm's disks on the shared storage get corrupted when used by the secont server in the cluster. Here is what I did to make a shared volume: pvecreate /dev/cciss/c0d8...

Re: Proxmox 1.8 fails to install (unable to create volume group at /usr/bin/proxinsta Yes. This works! Thank you! It was so obvious and simple! Stupid me :-)