I would suggest an improvement on your b options to be c: change from a text input box to selection list, and only offer valid choices. On 4/24/2014 11:20 AM, Rodrigo Trujillo wrote: > Hi all, > > we have recently merged the patches that allow user to change guest > memory and cpu. > When user change this parameters, we have some problems: > > 1- If user assigned more virtual cpus than the amount in the host > and start the VM, VM will start normally, but the host server will > have the performance heavily declined. > > 2- If user assigned more virtual memory than the physical amount > in the host, the VM does not start and qemu throws an exception like > "Cannot allocate memory." > > Solutions: > > 1a - Show the number of host physical CPUs in edit Template and > edit Guest windows, then warn the user if he assigns a higher number > 1b - Show the number of host physical CPUs in edit Template and > edit Guest windows, then does not allow to set up a higher number > (generate a error during edition) > > 2a - Show the host MEMORY amount in edit Template and edit Guest > windows, then warn the user if he assigns a higher number > 2b - Show the host MEMORY amount in edit Template and edit Guest > windows, then does not allow to set up a higher number (generate a > error during edition) > > - A third option would be check the numbers before start a guest > and warn the user, or does not allow the vm to be started. > > > I would like to implement 1a and 2b. > Do you have any thoughts or concerns/suggestions ? > > Rodrigo Trujillo > > _______________________________________________ > Kimchi-devel mailing list > Kimchi-devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/kimchi-devel >

We probably also need a warning message in the event a user tries to start a VM that the host can't accommodate. The user can alter the VM settings outside kimchi, or they could alter the physical hardware of the host. On 4/24/2014 1:35 PM, Adam King wrote: > I would suggest an improvement on your b options to be c: change from > a text input box to selection list, and only offer valid choices. > > > On 4/24/2014 11:20 AM, Rodrigo Trujillo wrote: >> Hi all, >> >> we have recently merged the patches that allow user to change guest >> memory and cpu. >> When user change this parameters, we have some problems: >> >> 1- If user assigned more virtual cpus than the amount in the >> host and start the VM, VM will start normally, but the host server >> will have the performance heavily declined. >> >> 2- If user assigned more virtual memory than the physical amount >> in the host, the VM does not start and qemu throws an exception like >> "Cannot allocate memory." >> >> Solutions: >> >> 1a - Show the number of host physical CPUs in edit Template and >> edit Guest windows, then warn the user if he assigns a higher number >> 1b - Show the number of host physical CPUs in edit Template and >> edit Guest windows, then does not allow to set up a higher number >> (generate a error during edition) >> >> 2a - Show the host MEMORY amount in edit Template and edit Guest >> windows, then warn the user if he assigns a higher number >> 2b - Show the host MEMORY amount in edit Template and edit Guest >> windows, then does not allow to set up a higher number (generate a >> error during edition) >> >> - A third option would be check the numbers before start a guest >> and warn the user, or does not allow the vm to be started. >> >> >> I would like to implement 1a and 2b. >> Do you have any thoughts or concerns/suggestions ? >> >> Rodrigo Trujillo >> >> _______________________________________________ >> Kimchi-devel mailing list >> Kimchi-devel(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/kimchi-devel >> >