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
PACKAGE(1)                                                    General Commands Manual                                                   PACKAGE(1)

NAME
package - register package user via mailagent SYNOPSIS
package address system version patchlevel [ mailpatches | notifypatches ] DESCRIPTION
This command is not intended to be run directly by a user, but may appear in any mail whose subject is set to Command. Such mail will be processed by the mailagent(1), which will extract all lines beginning with @SH, which may specify this command. The mailagent first sets environment variables that will be used by the command. Package is used to notify the author of a package about its users. It is normally generated automatically by the MailAuthor.U unit when the user runs Configure. If the patchlevel specified is not the latest for that system and version, mail is immediately sent suggesting that they upgrade and remindng them how to request the latest patches. The final parameter, if included may be set to mailpatches to specify that the user would like to have future patches mailed to them, or notifypatches to specify that a mail notification of future patches should be sent, rather than the entire patch. The user's address and notification request are saved in the file users in the package's directory. Package performs an approximate address match in order to avoid duplicate entries. Whenever this elimination occurs, a warning message is issued in the logfile. Two addresses will be said equivalent if one of them has an added machine name or if they are really equal. There- fore, the following addresses are equivalent: ram@acri.fr ram@main.acri.fr whereas the following two are not equivalent, unfortunately: ram@acri.acri.fr ram@main.acri.fr When a user is asking to be left alone, it is important to let him know if the request failed, because he will be annoyed when the next set of patches is issued and he still gets them despite his previous request. Therefore, if no approximate match occurs, a warning message is sent back, with a list of addresses that are close to his own e-mail address, but not equivalent. Fortunately, the following addresses are considered close: ram@acri.fr ram@somewhere.com raphael@main.acri.fr manfredi@acri.acri.fr because they either have the same login (important when someone changes company) or share the same domain or sub-domain part. In order to edit the users file, the edusers script should be used. For one thing, it will let you edit the users file from whatever pack- age you name in the command line, but it will also properly lock the file so that the execution of package will stall for the duration of the manual edition (provided you have a strict locking policy defined in your ~/.mailagent configuration file). FORWARDING
Package supports command forwarding as described in the mailhelp(1) page. FILES
~/.mailagent configuration file for mailagent. System/users list of users of that system. This file consists of single line records, one for each registered user. Each record consists of three tab-separated fields. The first field indicates the level of updates requested by the user by a single letter as follows: M Mail future patches directly to the user when they are issued. N Notify the user of future patches. U The users chose to let the author know that they have tried the program, but does not wish to know about future updates. L The user is no longer interested in the program and wants to be left alone. The second field is their last notified patch level, or a dash (-) if it is not known. The third field is the user's Email address. Log/agentlog mailagent's log file AUTHORS
Graham Stoney <greyham@research.canon.oz.au> Raphael Manfredi <Raphael_Manfredi@pobox.com> (minor enhancements) SEE ALSO
edusers(1), mailagent(1), metaconfig(1). PACKAGE(1)