Hi, Oh, I see then. I suggest using this RAW workaround then until the ticket is solved (we are solving it anyway since the overwritting wasn't the intended behavior).
Regards, -Tino -- Constantino Vázquez Blanco, MSc OpenNebula Major Contributor www.OpenNebula.org | @tinova79 On Fri, Apr 1, 2011 at 12:35 PM, <kna...@gmail.com> wrote: > Tino Vazquez wrote on 01/04/11 14:52: >> >> the problem i see with the workaround is how to relate the RAW section >> to DISK in case there is more than one DISK. > > Hi Tino, > > There is no way and sense to have more then one disk in VMs (aka containers) > based on OpenVZ [1]. You can't assign\attach more disks to OpenVZ VM in > principle. The only thing you can do with VM disk resources is to change > disk quota for particular VM on the host node. Thus such OpenVZ VM > parameters for disk resources management as DISKSPACE and DISKINODES are > unique per each VM and in principle can be passed in RAW section although > it's not quite proper way to do that. > > [1] http://wiki.openvz.org/WP/What_are_containers#Disk > > Regards, > Nikolay. > _______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org