Search results

not that i heard of. my personal interest faded, since we're not using OpenVZ in favor for KVM.

hi, the --all option of vzdump is handy, if you're migrating VMs a lot between servers. however - i also have a lot of VMs in 'stopped' state, i only use every once in a while. these should not be backed up regularly, since they don't change. (they may in between) i suggest a new option...

just put nfs in /etc/modules.

probably a hiccup in your DNS server. everything's working fine for me at this time.

feature request: something reasonable like FQDN should be set during install.

there's an unofficial repository for PVE1.4: http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Lenny_on_32-Bit_Processor

you can join them in a vpn.

from the wiki:

you can (should) join them in a virtual tunneled network and cluster them. this may make sense, if you are well connected.

make sure both net-devices (public ip / private ip) are bridges configured the same way on all 3 nodes. do the same virtually for the 4th node.

they cannot resize the LUN without data loss. then please take the time to answer that one specific question from above: will anything of the information requested change in PVE2.x? (is the storage model stable between 1.x and 2.x or will i have to reimplement patches to a completly different...

did so. for cross-reference: http://bugs.debian.org/580380

hi dietmar, would be nice to know in advance. if i hear LVM i think of all the features. this limitation should be worth mentioning in the wiki. that limits the whole concept of LVM. VGs weren't invented as an additional useless layer. i have no direct access to the SAN, as it's maintained...

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32) i'm using 2.6.18, as i have problems with live-migration using 2.6.32 (see thread: http://forum.proxmox.com/threads/3334) what are the differences to the current stable 2.6.32? was the issue above addressed? is there a changelog?

this would be hard i guess, since the java applet simply does its own stuff.

hi, i'm playing with ISCSI storage at the moment and have multiple targets. i want to join them to a volume group that is used as shared storage. in future i want to add more targets to the VG, as i need/buy more storage. this setup doesn't seem to be possible with the web-gui. i can only...

no, /dev/sdb is correct. see my lsscsi output above.

nothing at all. return code was 1.

this did the trick. but one step later i hit the udev-missing-symlink-bug in another script, so symlinking by hand would be a workaround but no solution. don't know. /etc/udev/rules.d/60-persistent-storage.rules looks debian standard (SHA1: 5f8c2cc014940cc88910bbcb05c5cc5628d1f96c) rules for...

hi dietmar, thanks for this hint. i managed to debug the problem, but don't understand its cause. it didn't manage to get $blockdev. up until $bdev all goes well, but in my /dev/disk/by-id my ISCSI targets don't show up. however they do in /dev/disk/by-path, so i exchanged the function call to...