KVM/Qemu allocated memory not showing in guest


 
Thread Tools Search this Thread
Operating Systems Linux Red Hat KVM/Qemu allocated memory not showing in guest
# 1  
Old 12-07-2018
KVM/Qemu allocated memory not showing in guest

So we have a RHEL 7.6 workstation with 128 gigs of ram. The OS sees all the ram and 80 cors (40 HT)


We have 1 guest with 8 CPUs and 32gigs of ram running RHEL 7.6 workstation as well. We are trying to create another guest with 64 CPUs and 80 gigs of ram. We setup the system using virt-manager and PXE boot the system to install the OS.


All this goes without a hitch, but when we log in after the system is build with PXE and do a free -g it only shows 2 gigs instead of 80 gigs.


I have tried many variation of memory including 64gigs, but each time we try something above 32gigs, its only shows 2gigs.


Any ideas?
Thanks!

Joe
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Linux

Unable to connect guest VM to internet (QEMU via both 'User-mode networking' and 'TUN/TAP')

Hello, I installed FreeBSD 10.3 on AQEMU. I can't connect to internet in none of the modes of "Default, User-Mode Networking" and "TUN/TAP Networking". I am able to ping my host in the TAP networking mode (192.168.1.33 which is my IP addr in guest), but getting 'no route to host' for any... (1 Reply)
Discussion started by: temp-usr
1 Replies

2. Red Hat

KVM - VM Guest

Background : - Need to create addition 40G storage for VM guest. 1. I have created new KVM - VM guest on RHEL 5.8 server hosting server. 2. Hosting server has occupied all size with LV and there is not space to create new LV. 3. I tried to achieve this requirement by creating 40G file size and... (1 Reply)
Discussion started by: Nats
1 Replies

3. UNIX for Advanced & Expert Users

Need commands to fetch Guest VM OS version from Xen and KVM

Im looking for the commands that can be executed to fetch the OS Version of the VMs running on the below Hypervisors. Xen (Not the citrix Xen server, but the Xen Sever hosted on a ubuntu Machine) KVM (0 Replies)
Discussion started by: ranvirsingh
0 Replies

4. UNIX for Dummies Questions & Answers

Qemu Problems: OpenBSD(host) Kali Linux(guest)

As the title suggests I ran into a little problem trying to create a virtual machine of Kali Linux usign Qemu inside OpenBSD. I edited the example Kali Linux gave on their website here to the following for BSD: qemu-system-i386 -hda ./kali.qcow2 -boot d -cdrom ./kali-linux-1.0.5-i386.iso -m... (0 Replies)
Discussion started by: Azrael
0 Replies

5. UNIX for Advanced & Expert Users

NFS3 over KVM-Guest don't map UnixACLs

Hi, I have an problem with ACLs over NFS3. The Problem is, when i mount a nfsshare from an KVMguest, the UnixACLs were not mapped too. I don't know why. But this is only when i have the NFSshares on an virtulamachine. When i do the same with ein real machine, ACLs work well. You can see that:... (4 Replies)
Discussion started by: darktux
4 Replies

6. UNIX for Advanced & Expert Users

[Solved] Cannot install KVM guest on CentOS/RedHat

Hi, I've a CentOS Server and I need to create KVM guest machine without X. /usr/sbin/virt-install --name server1 --ram 4000 --vcpus=8 --file=/srv/virtual/server1.img --file-size=20 --cdrom /tmp/server1.iso --mac=52:54:00:fd:48:7c The iso was created with cobbler... So, now the machine is... (5 Replies)
Discussion started by: hiddenshadow
5 Replies

7. Red Hat

help about qemu-kvm boot with initrd

I used the redhat RHEL6 boot with initrd but it failed, can sb help me # /usr/libexec/qemu-kvm --enable-kvm -smp 8 -m 1024 -net nic,model=virtio -net tap,script=/etc/qemu-ifup -initrd /boot/initramfs-2.6.32-279.el6.x86_64.img -kernel /boot/vmlinuz-2.6.32-279.el6.x86_64 -append "root=/dev/ram... (4 Replies)
Discussion started by: yanglei_fage
4 Replies

8. Red Hat

Could not see virtual fc in KVM guest OS

Hi All, I have RHEL 5u4 physical system with 2 Qlogic fc cards. It hosts 2 KVM virtual machines which are also running RHEL 5u4 OS. After all these I have created a virutal HBA (refered in google) successfully on the base OS. But the same is not visible to guest OS. My question here is, ... (1 Reply)
Discussion started by: Vichu
1 Replies

9. Virtualization and Cloud Computing

KVM FC12 guest save not working ??

Howdy I am using Fedora12 with KVM, with XP64pro as a guest. Everything seems to be working just fine, BUT I can't Save. When I do instruction KVM to save, I get a continuing Saving display, but it continues for a long time until I finally terminate it due to boredom :) I have let it run for... (0 Replies)
Discussion started by: TJMan
0 Replies

10. Red Hat

Filesystems disappear on KVM guest machine after reboot.

Hello, I have a KVM system running on RHEL 5.4. It hosts 4 guest VMs. One of the guest host fails to get back the mounted filesystems after the system reboots. Does anyone have any idea what the issue could be? Regards, Mahive. (1 Reply)
Discussion started by: mahive
1 Replies
Login or Register to Ask a Question
VIRT-IMAGE(1)						   Virtual Machine Install Tools					     VIRT-IMAGE(1)

NAME
virt-image - create virtual machines from an image descriptor SYNOPSIS
virt-image [OPTION]... IMAGE.XML DESCRIPTION
virt-image is a command line tool for creating virtual machines from an XML image descriptor "IMAGE.XML" (virt-image(5)). Most attributes of the virtual machine are taken from the XML descriptor (e.g., where the files to back the virtual machine's disks are and how to map them into the guest), though certain information must be added on the command line, such as the name of the guest. The XML descriptor defines most attributes of the guest, making it possible to bundle and distribute it together with the files backing the guest's disks. OPTIONS
Most options can be omitted, in which case virt-image will use defaults from the XML descriptor. When defaults are taken from the XML descriptor, they are indicated below as a path. --name is the only required command line option. -h, --help Show the help message and exit --connect=CONNECT Connect to a non-default hypervisor. See virt-install(1) for details General Options General configuration parameters that apply to all types of guest installs. -n NAME, --name=NAME Name of the guest instance -r MEMORY, --ram=MEMORY Memory to allocate for guest instance in megabytes. Defaults to "/image/devices/memory" in the XML descriptor. -u UUID, --uuid=UUID UUID for the guest; if none is given a random UUID will be generated. If you specify UUID, you should use a 32-digit hexadecimal number. --vcpus=VCPUS Number of vcpus to configure for your guest. Defaults to "/image/devices/vcpu" in the XML descriptor. --check-cpu Check that vcpus do not exceed physical CPUs and warn if they do. --os-type=OS_TYPE Optimize the guest configuration for a type of operating system (ex. 'linux', 'windows'). This will attempt to pick the most suitable ACPI & APIC settings, optimally supported mouse drivers, virtio, and generally accommodate other operating system quirks. See virt-install(1) for valid values. --os-variant=OS_VARIANT Further optimize the guest configuration for a specific operating system variant (ex. 'fedora8', 'winxp'). This parameter is optional, and does not require an "--os-type" to be specified. See virt-install(1) for valid values. Full Virtualization specific options Parameters specific only to fully virtualized guest installs. --noapic Disables APIC for fully virtualized guest (overrides value in XML descriptor) --noacpi Disables ACPI for fully virtualized guest (overrides value in XML descriptor) Networking Configuration -m MAC, --mac=MAC This is deprecated in favor of "--network ...,mac=MAC,..." -b BRIDGE, --bridge=BRIDGE This is deprecated in favor of "--network bridge=BRIDGE" -w NETWORK, --network=NETWORK Connect the guest to the host network. See virt-install(1) for details Graphics Configuration If no graphics option is specified, "virt-install" will default to --vnc if the DISPLAY environment variable is set, otherwise --nographics is used. --vnc Setup a virtual console in the guest and export it as a VNC server in the host. See virt-install(1) for details --vncport=VNCPORT Request a permanent, statically assigned port number for the guest VNC console. See virt-install(1) for details --vnclisten=VNCLISTEN Address to listen on for VNC connections. See virt-install(1) for details. -k KEYMAP, --keymap=KEYMAP Request that the virtual VNC console be configured to run with a non-English keyboard layout. --sdl Setup a virtual console in the guest and display an SDL window in the host to render the output. See virt-install(1) for details --nographics Do not attach a graphical device to the guest. See virt-install(1) for details Miscellaneous Options -p, --print Print the libvirt XML, but do not start the guest. --boot=BOOT The zero-based index of the boot record to use. The XML descriptor can contain multiple "/image/domain/boot" elements for use on different hypervisors. By default, the one that is most appropriate for the current hypervisor is selected. --replace Shutdown and remove any existing guest with the passed "--name" before installing from the image. --skip-checksum Do not check disk images against checksums (if they are listed in the image xml). -d, --debug Print debugging information --force Prevent interactive prompts. If the intended prompt was a yes/no prompt, always say yes. For any other prompts, the application will exit. EXAMPLES
Create and start a guest called "example" with a VNC console from "image.xml": # virt-image --name example --vnc -i image.xml Print the libvirt XML for a guest called "example" without graphics, but do not create or start a virtual machine: # virt-image --print --name example --nographics --image image.xml AUTHOR
Written by David Lutterkort. See the AUTHORS file in the source distribution for the complete list of credits. BUGS
Please see http://virt-manager.org/page/BugReporting COPYRIGHT
Copyright (C) 2006-2007 Red Hat, Inc, and various contributors. This is free software. You may redistribute copies of it under the terms of the GNU General Public License "http://www.gnu.org/licenses/gpl.html". There is NO WARRANTY, to the extent permitted by law. SEE ALSO
virt-image(5), virt-install(1), the project website "http://virt-manager.org" 2009-12-10 VIRT-IMAGE(1)