KVM/Qemu allocated memory not showing in guest

Login or Register to Reply

Thread Tools Search this Thread
# 1  
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?

Login or Register to Reply

Thread Tools Search this Thread
Search this Thread:
Advanced Search

More UNIX and Linux Forum Topics You Might Find Helpful
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...... Red Hat
Red Hat
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...... UNIX for Dummies Questions & Answers
UNIX for Dummies Questions & Answers
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...... Red Hat
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, ...... Red Hat
Red Hat
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...... Virtualization and Cloud Computing
Virtualization and Cloud Computing
XBDBACK(4)						 BSD/xen Kernel Interfaces Manual						XBDBACK(4)

xbdback -- Xen backend paravirtualized block device interface
pseudo-device xbdback
The xbdback interface forms the backend part of the paravirtualized drivers used by Xen domains to offer a block device interface, similar to a hard disk. xbdback interfaces are backed either by a physical device directly, or an image file mounted through vnd(4). All xbdback interfaces follow the ``xbdbackXiY'' naming convention, where 'X' represents the guest domain identifier, and 'Y' an arbitrary identifier. This identifier is usually associated to the device node as seen by the guest using major(3) and minor(3) numbers. For example, identifier ``769'' (0x301) means major 3 and minor 1, identified as ``hda1'' under Linux convention. For NetBSD, the guest device name spec- ified in the guest configuration file does not matter, and can be chosen arbitrarily. A xbdback interface will appear as a xbd(4) block device inside a NetBSD guest domain. In the XenStore, xbd and xbdback are identified by ``vbd'' (virtual block device) entries.
xbd backend: attach device %s (size %d) for domain %d Gives the device used as xbdback interface for the given guest domain, and its size, in bytes. xbd backend 0x%x for domain %d using event channel %d, protocol %s Gives the backend identifier, guest domain ID, event channel ID, and pro- tocol used for block level communication. xbdback %s: can't VOP_OPEN device 0x%x: %d When this message appears in the system message buffer with error 16 (EBUSY), the device is likely to be already mounted. It must be unmounted first, as the system will refuse to open it a second time.
vnd(4), xbd(4), xenbus(4)
The xbdback driver first appeared in NetBSD 4.0.
The xbdback driver was written by Manuel Bouyer <bouyer@NetBSD.org>.
June 7, 2011 BSD

Featured Tech Videos