error on virtual manager

 
Thread Tools Search this Thread
Operating Systems Linux Red Hat error on virtual manager
# 1  
Old 06-03-2011
error on virtual manager

In red hat linux server 6
I start up virtual manager and I get below error prompt.

Package reuired for KVM usage
The following packages are not installed
qemu-kvm
These are required to create KVM guests locally.
Would you like to install them now .
I press yes but the package cannot located ...
So, I have install the qemu-kvn-0.12.1.2.113.el6_0.8.src.rpm already
I use command rpm -ivh XXX.rpm to install.
So, what I miss and please advice
Login or Register to Ask a Question

Previous Thread | Next Thread

5 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

Providing virtual machine priority in kvm based virtual machines

Hi All, Is there any way I can prioritize my VMs when there is resource crunch in host machine so that some VMs will be allocated more vcpu, more memory than other VMs in kvm/qemu hypervisor based virtual machines? Lets say in my cloud environment my Ubuntu 16 compute hosts are running some... (0 Replies)
Discussion started by: SanjayK
0 Replies

2. SuSE

Xen Virtual Manager

Never used this before, so I just did the simple thing, and tried installing an OS. The only OS that worked is Suse Linux. All the rest hung at the select OS screen. Do other OS's (like Windows/Unix) have to have drivers or a configuration file, etc, installed prior to running the install. Well... (3 Replies)
Discussion started by: jgt
3 Replies

3. Red Hat

My RHEL virtual Machine Does not have Virtual Machine Manager Desktop Tool

My RHEL virtual Machine Does not have Virtual Machine Manager Desktop Tool Hi, I don't seem to have the Virtual Machine Manager Desktop tool set up on my RHEL6 Machine. The Linux machine runs off VMWare player and I'm not sure whether it is a VMWare software issue or a problem with the RHEL6... (2 Replies)
Discussion started by: accipiter1
2 Replies

4. Solaris

Change hostID of Solaris 10 virtual/guest machine installed by Virtual Box 4.1.12 on Windows-XP host

Trying to set or modify the randomly set hostID of a Solaris 10 virtual/guest machine that I installed on a Windows-XP host machine (using Virtual Box 4.1.12). I was able to set/modify the hostname of the Solaris 10 virtual/guest machine during installation as well as via the Virtual Box... (4 Replies)
Discussion started by: Matt_VB
4 Replies

5. Linux

LVM (volume manager) and virtual disks

:eek: Hi guys, I'm pulling my hair out over this one. I am trying to set up a virtual server environment. ( I am using VirtualBox, but I think this is irrelevant to this problem.) I have downloaded a pre-packaged Linux virtual disk, with which I have successfully started a virtual instance of a... (4 Replies)
Discussion started by: otheus
4 Replies
Login or Register to Ask a Question
KVM(3)							   BSD Library Functions Manual 						    KVM(3)

NAME
kvm -- kernel memory interface LIBRARY
Kernel Data Access Library (libkvm, -lkvm) DESCRIPTION
The kvm library provides a uniform interface for accessing kernel virtual memory images, including live systems and crash dumps. Access to live systems is via sysctl(3) for some functions, and mem(4) and kmem(4) for other functions, while crash dumps can be examined via the core file generated by savecore(8). The interface behaves similarly in both cases. Memory can be read and written, kernel symbol addresses can be looked up efficiently, and information about user processes can be gathered. The kvm_open() function is first called to obtain a descriptor for all subsequent calls. COMPATIBILITY
The kvm interface was first introduced in SunOS. A considerable number of programs have been developed that use this interface, making back- ward compatibility highly desirable. In most respects, the Sun kvm interface is consistent and clean. Accordingly, the generic portion of the interface (i.e., kvm_open(), kvm_close(), kvm_read(), kvm_write(), and kvm_nlist()) has been incorporated into the BSD interface. Indeed, many kvm applications (i.e., debuggers and statistical monitors) use only this subset of the interface. The process interface was not kept. This is not a portability issue since any code that manipulates processes is inherently machine depen- dent. Finally, the Sun kvm error reporting semantics are poorly defined. The library can be configured either to print errors to stderr automati- cally, or to print no error messages at all. In the latter case, the nature of the error cannot be determined. To overcome this, the BSD interface includes a routine, kvm_geterr(3), to return (not print out) the error message corresponding to the most recent error condition on the given descriptor. SEE ALSO
kvm_close(3), kvm_getargv(3), kvm_getenvv(3), kvm_geterr(3), kvm_getfiles(3), kvm_getloadavg(3), kvm_getprocs(3), kvm_getswapinfo(3), kvm_nlist(3), kvm_open(3), kvm_openfiles(3), kvm_read(3), kvm_write(3), sysctl(3), kmem(4), mem(4) BSD
April 25, 2010 BSD