Project

General

Profile

Actions
Copy link

Bug #1580

closed

Limitiation to create only 32 GB VM

Added by Kevin Fernandes about 12 years ago. Updated over 7 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
Marek Hulán
Category:
VM management
Target version:
1.6.3
Difficulty:
easy
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

While creating VMs via the Foreman UI. Only VMs till 32GB Memory can be created from the dropdown list. This field should be changed, so that VMs of any Memory size could be created.

Files

32GBVM.png View 32GBVM.png 89.1 KB Kevin Fernandes, 05/16/2012 04:28 AM

Related issues 4 (1 open — 3 closed)

Related to Foreman - Bug #2314: Smaller grains for VM memory/RAM choice neededClosedMarek Hulán03/13/2013Actions
Related to Foreman - Feature #10875: Add option to choose between MB and GB when selecting Memory for new virtual machineNew06/18/2015Actions
Related to Foreman - Feature #10395: Compute Profile (oVirt) limited to 8 Cores and 16GB of memoryClosedMarek Hulán05/06/2015Actions
Has duplicate Foreman - Feature #12983: Need Higher Max Core & Max Memory limit for compute profile under Rhev & VmwareDuplicateActions
Actions
Copy link
 #1

Updated by Brian Gupta almost 12 years ago

Kevin,

Any chance you can give me the URL where this field is? (Feel free to obfuscate your actual server). I don't use provisioning so am not familiar with that particular code.

Thanks,
Brian

Actions
Copy link
 #2

Updated by Kevin Fernandes almost 12 years ago

Hi Brian,

I am attaching a screen shot of the fields where the configuration happens. And the link is the following on that page when i select Provision on "and selecting KVM host".

http://foreman.domain.local:7000/hosts/new

Regards,
Kevin

Actions
Copy link
 #3

Updated by Ohad Levy almost 12 years ago

  • Assignee set to Amos Benari
  • Difficulty set to easy
Actions
Copy link
 #4

Updated by Ohad Levy almost 12 years ago

  • Target version deleted (1.0)
Actions
Copy link
 #5

Updated by Ohad Levy over 9 years ago

  • Assignee deleted (Amos Benari)
Actions
Copy link
 #6

Updated by Dominic Cleal over 8 years ago

  • Related to Bug #2314: Smaller grains for VM memory/RAM choice needed added
Actions
Copy link
 #7

Updated by Dominic Cleal over 8 years ago

  • Related to Feature #10875: Add option to choose between MB and GB when selecting Memory for new virtual machine added
Actions
Copy link
 #8

Updated by Dominic Cleal over 8 years ago

  • Has duplicate Feature #12983: Need Higher Max Core & Max Memory limit for compute profile under Rhev & Vmware added
Actions
Copy link
 #9

Updated by Dominic Cleal over 8 years ago

  • Related to Feature #10395: Compute Profile (oVirt) limited to 8 Cores and 16GB of memory added
Actions
Copy link
 #10

Updated by Marek Hulán over 7 years ago

  • Description updated (diff)
  • Target version set to 115
Actions
Copy link
 #11

Updated by Marek Hulán over 7 years ago

  • Target version changed from 115 to 1.6.3
Actions
Copy link
 #12

Updated by Marek Hulán over 7 years ago

  • Status changed from New to Assigned
  • Assignee set to Marek Hulán

This limitation is there for libvirt and oVirt CRs. VMware already exposes text field. As part of this I'll create some basement for related tasks, e.g. same thing should be applied to CPU count.

Actions
Copy link
 #13

Updated by Marek Hulán over 7 years ago

  • Status changed from Assigned to Duplicate

actually all of what's here is already part of #2314 so I'll use that one

Actions
Copy link

Also available in: Atom PDF