Search results

could this be happening because the storage isn't on LVM? currently it's using just a ext4 mounted folder.

basically the VM was offline, all my sites on it were down, couldn't ssh/ping, nothing was working.

so i just rebooted and this time snapshot worked. but during the time to snapshot, server was un-responsive for the whole 2-3 minutes. is this how it's supposed to be?

i just tried snapshot again, but same result. but to give you some more insights, after i upgraded from 2.1 to 2.2, i didn't reboot. could that be the problem? also, i don't see anyway to cancel this, even in tasks,

it's a 72k rpm sata. hit2tb:100/vm-100-disk-1.qcow2,cache=writethrough,size=320G

hm, i just did a smartctl test and everything was fine on that drive /storage/hit2tb (it is a mounted drive btw). it's formatted as ext4. what could the problem be? anyway to find out?

now after waiting a bit longer it finally timed out with this message: Formatting '/storage/hit2tb/images/100/vm-100-state-first.raw', fmt=raw size=17553162240 TASK ERROR: VM 100 qmp command 'snapshot-drive' failed - got timeout any ideas? and btw, VM is responsive again.

it's almost over 15 minutes now, seems it just froze. with no abort button, what can i do? on top of that, i'm looking at /var/lib/vz/images/100, and i see nothing there! did snapshot feature somehow delete it?

hi so i just upgraded from 2.1 to 2.2 w/o a problem and i created a new KVM w/ qcow2, installed cpanel, and then went to proxmox to try out the new snapshot. now it's been over 5 mins and still says: Task: VM 100 - Snapshot w/ the progress bar looping over and over. and I see that the VM is not...

hi when i add new hard drive, normally i partition them using fdisk/parted and then format it as ext4, then i just mount them via /etc/fstab. but if i wanted to take advantage of fast backups, i heard someone say it should be in LVM. whats the correct procedure to do this? format as LVM and then...

root@server1:~# pveversion -v pve-manager: 2.1-1 (pve-manager/2.1/f9b0f63a) running kernel: 2.6.32-11-pve proxmox-ve-2.6.32: 2.0-66 pve-kernel-2.6.32-11-pve: 2.6.32-66 lvm2: 2.02.95-1pve2 clvm: 2.02.95-1pve2 corosync-pve: 1.4.3-1 openais-pve: 1.1.4-2 libqb: 0.10.1-2 redhat-cluster-pve: 3.1.8-3...

okay so backup just took a long time, 50 mins and now its done and everything is back to normal. i'm surprised though, that it knocked out my VM (all sites down) during this backup process.

ahh finally! thought this day would never come! now the hard part, upgrading 2.1 to 2.2. how safe is it to upgrade?

i've just took a snapshot backup and my VM stopped responding: INFO: starting new backup job: vzdump 101 --remove 0 --mode snapshot --compress lzo --storage hit2tb --node server1 INFO: Starting Backup of VM 101 (qemu) INFO: status = running INFO: mode failure - unable to detect lvm volume group...

how is this new snapshot any different from what we had? as we speak, i've just created a snapshot on one of my VM, and VM is not responding at all. i'm on 2.1 btw. for me, snapshot usually takes half hour or longer, so you could say, it's not really snappy.

hi guys anyone know of any insights to how much performance hit one should expect when going virtualization? i have a bare-metal server which is performing well for a site that gets over 10mil+ requests per day, hovering at avg load of 30-40, with almost zero io wait. but i want the flexibility...

yes, something like OnApp interface we can offer to our clients so we can resell, that'd be huge.

I like to have all my servers virtualized for variety of reasons, such as backups, portability, cloning, revert/snapshots, etc ... Why, are there any known problems for running SAN under virtualization?

can it also be installed inside openvz/kvm?

Thanks milkwerm, that was very helpful. But one more question, if I were to run this off virtualization, can this run off of proxmox or xenserver? or does it have to be on VMWare only?