06-06-2011
I had a similar problem.
Are you logged on locally to the box or are you exporting the virt-manager display to a remote server?
The reason I ask, is because it should work if you are logged on locally. If you are logged on remotely via ssh -X have a look for bug 512253 - Virt Manager (not allowed to post liks yet!)
There is a work-around is to use virt-install instead.
Let me know how you get on. I'm using Fully Virtualised VM's installed from an ISO local to the Host.
8 More Discussions You Might Find Interesting
1. Debian
Is there a way to configure the gnome file manager to open each directory in the same window instead of opening a new one? (Debian 5.0.0) (5 Replies)
Discussion started by: snorkack59
5 Replies
2. Solaris
hi all
i am a newbie to solaris and i am doing some R&D in veritas volume manager. This is my first day with veritas. I downloaded and installed Veritas storage foundation 5.1 package in my sun solaris 5.10 sparc machine. When i try to create disk group in vxvm, it giving one error message. I am... (6 Replies)
Discussion started by: kingston
6 Replies
3. Solaris
Hello,
There once was a disk. Veritas thought it wasn't happy, but it really was.
The disk was all alone on a plex. There was another plex, in the same volume, that was fine and happy with its own single disk.
I removed the plex with the unhappy disk. Then I went into vxdiskadm, removed... (2 Replies)
Discussion started by: kity1kity
2 Replies
4. Emergency UNIX and Linux Support
Hi guys.
I have installed debian 6.0.1a. I have install all XEN stuff. including xen kernel, libvirtd, ...
but when i want to connect xend virt-manager shows me this:
Verify that:
- A Xen host kernel was booted
- The Xen service has been started
details:
Unable to open connection to... (0 Replies)
Discussion started by: majid.merkava
0 Replies
5. UNIX for Advanced & Expert Users
Hi,
I am trying to setup KVM virtulization under CentOS6.0x32 and installed all the required rpm's as per the installation guidelines.
# rpm -qa | grep libvirt
libvirt-cim-0.6.1-4.el6.i686
fence-virtd-libvirt-qpid-0.2.1-5.el6.i686
libvirt-qpid-0.2.22-3.el6.i686... (0 Replies)
Discussion started by: boby.kumar
0 Replies
6. UNIX for Advanced & Expert Users
Hello Dears,
I am up to install configuration manager as the number of Linux systems are growing alot in my company.
can please advise any of them?
Puppet, spicewalk ansilble etc.. please share you opinion.
My aim is to have config manager to automate/provision systems and to have inventory... (1 Reply)
Discussion started by: Vit0_Corleone
1 Replies
7. Linux
Hello Dears,
I am up to implement cnfiguration manager as the number of Linux systems are growing alot in my company.
can please advise any of them?
Puppet, spicewalk ansilble etc.. please share you opinion.
My aim is to have config manager to automate/provision systems and to have inventory... (5 Replies)
Discussion started by: Vit0_Corleone
5 Replies
8. UNIX for Beginners Questions & Answers
I have downloaded RHEV-H 4.2 Red Hat Virtualization - Red Hat Customer Portal (RHVirtualization 4.2 Host and Manager iso). I uploaded the image and installed on an HP G9 server baremetal.
I found I dont have a WAN/net connectivity later on HPG9 server. How can I still install virt-manager on... (1 Reply)
Discussion started by: Paras Pandey
1 Replies
LEARN ABOUT ULTRIX
elcsd.conf
elcsd.conf(5) File Formats Manual elcsd.conf(5)
Name
elcsd.conf - error logging configuration file
Description
The file contains information used by the daemon to configure error logging for the system. The system manager maintains this file. The
error logging daemon is dependent on the current order of the entries in the file. Do not change the order.
The information in the file shows any defaults and describes what you can enter. A newline is used to delimit each entry in the file, a
null entry consists of a newline alone, and comments begin with #.
#
# elcsd - errlog configuration file
#
{ # delimiter DON'T remove or comment out!
1 # status 1-local,2-logrem,4-remlog,5-remlog+priloglocal
# errlog file size limit num. of blocks
/usr/adm/syserr # errlog dir. path
# backup errlog dir. path
/ # single user errlog dir. path
/usr/adm/syserr # log remote hosts errlog dir. path
# remote hostname to log to
} # delimiter DON'T remove or comment out!
# hosts to log :S - separate file or :R - remotes file (together)
remote1:S
remote2:S
#remote3:S # disabled
remote4:S
.
.
.
The status line of the file describes where you can log error packets, also called error messages:
Logs error packets locally =
1, the default.
Logs error packets from a remote system or systems to the local machine =
2.
Logs local and remote error packets locally =
3.
Logs error packets from the local system to a remote system =
4.
Logs error packets from the local system remotely and logs high
priority messages locally = 5.
The errorlog file size defines the maximum size of an errorlog file. If disk space is limited, you can specify the maximum number of
blocks (512 bytes each) you want the errorlog file to be. If you do not specify the maximum number of blocks, the system will notify you
when the file system is 98% full.
The default errorlog directory path is You can direct error packets to a different directory; if you do, you must change the default for
also. For further information, see
If the error-logging daemon cannot write to the primary errorlog directory path, it attempts to log to the backup errorlog directory path
automatically.
The root directory is the default for the single-user errorlog directory path. When the system makes the transition to multiuser mode,
errors logged in single-user mode are transferred to the default errorlog directory path You can direct single-user error packets to
another directory.
To log error packets from a remote system locally, set up an errorlog directory path on the local system. The default is
Errorlog packets from remote systems can be logged to separate files or to one file. S sets up a separate errorlog file for each remote
system that logs locally. R logs packets from the corresponding remote system to the file syserr.remotes. The default is S.
Restrictions
You must have superuser privileges to change the file. However, anyone can view the file.
Files
elcsd daemon messages
See Also
elcsd(8), eli(8), uerf(8)
Guide to the Error Logger System
elcsd.conf(5)