On 4/28/11, Gleb Natapov gleb@redhat.com wrote:
So why don't you use virt-manager?
The original intention was to run the host without any graphical desktop or anything not necessary to host the guests. That was based on reading and such which recommends not having anything beyond the necessary to minimize potential security problems and maximize resources available.
Then there were those pages which warn that virt-manager didn't work too well if bridged networking was required.
Last but not least, when I finally gave up and installed the desktop, virt-manager couldn't find the hypervisor. Checking up, it appears that the user needed additional permissions to certain files, which after given and tested via CLI, I still get errors.
Starting up X as root gave me this ominous warning that I really shouldn't be doing this and since I didn't think it was wise in the first place to have the desktop with root access running on what's supposed to be a production machine, I stopped trying that route and went back to figuring how to get virt-install to work.
Emmanuel Noobadmin wrote:
On 4/28/11, Gleb Natapov gleb@redhat.com wrote:
So why don't you use virt-manager?
The original intention was to run the host without any graphical desktop or anything not necessary to host the guests. That was based on reading and such which recommends not having anything beyond the necessary to minimize potential security problems and maximize resources available.
Then there were those pages which warn that virt-manager didn't work too well if bridged networking was required.
Last but not least, when I finally gave up and installed the desktop, virt-manager couldn't find the hypervisor. Checking up, it appears that the user needed additional permissions to certain files, which after given and tested via CLI, I still get errors.
Starting up X as root gave me this ominous warning that I really shouldn't be doing this and since I didn't think it was wise in the first place to have the desktop with root access running on what's supposed to be a production machine, I stopped trying that route and went back to figuring how to get virt-install to work.
I log in as root and setup KVM guest, set it to boot automatically and next login as root is only if something is wrong.
Ljubomir
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 04/28/2011 06:46 AM, Emmanuel Noobadmin wrote:
On 4/28/11, Gleb Natapov gleb@redhat.com wrote:
So why don't you use virt-manager?
The original intention was to run the host without any graphical desktop or anything not necessary to host the guests. That was based on reading and such which recommends not having anything beyond the necessary to minimize potential security problems and maximize resources available.
Then there were those pages which warn that virt-manager didn't work too well if bridged networking was required.
Last but not least, when I finally gave up and installed the desktop, virt-manager couldn't find the hypervisor. Checking up, it appears that the user needed additional permissions to certain files, which after given and tested via CLI, I still get errors.
Starting up X as root gave me this ominous warning that I really shouldn't be doing this and since I didn't think it was wise in the first place to have the desktop with root access running on what's supposed to be a production machine, I stopped trying that route and went back to figuring how to get virt-install to work.
You don't have to run an entire X desktop on the server to use virt-manager there.
If you have a graphical linux workstation on the same network (x can be slow across a WAN, so I would only do it locally), you can just do this from the workstation with X running:
ssh -XY -l root <server_name>
then from the server do this:
virt-manager
This will run just the application "virt-manager" on the server and push the video display back to your machine.
You may need to run this on the workstation before you ssh to the server machine:
xhost +
On 4/28/11, Johnny Hughes johnny@centos.org wrote:
You don't have to run an entire X desktop on the server to use virt-manager there.
If you have a graphical linux workstation on the same network (x can be slow across a WAN, so I would only do it locally), you can just do this from the workstation with X running:
ssh -XY -l root <server_name>
then from the server do this:
virt-manager
This will run just the application "virt-manager" on the server and push the video display back to your machine.
You may need to run this on the workstation before you ssh to the server machine:
xhost +
Thanks a lot for this tip, it'll probably come in very useful for me since it sounds a lot easier/efficient than having VNC (freenx never worked for me) on every CentOS machine in my office. Although maybe not in this particular case since my usual access to this particular server is through WAN.
Emmanuel Noobadmin wrote:
On 4/28/11, Johnny Hughes johnny@centos.org wrote:
You don't have to run an entire X desktop on the server to use virt-manager there.
If you have a graphical linux workstation on the same network (x can be slow across a WAN, so I would only do it locally), you can just do this from the workstation with X running:
ssh -XY -l root <server_name>
then from the server do this:
virt-manager
This will run just the application "virt-manager" on the server and push the video display back to your machine.
You may need to run this on the workstation before you ssh to the server machine:
xhost +
Thanks a lot for this tip, it'll probably come in very useful for me since it sounds a lot easier/efficient than having VNC (freenx never worked for me) on every CentOS machine in my office. Although maybe not in this particular case since my usual access to this particular server is through WAN.
It's SSH, it' safe from the internet also.
Ljubomir
On 4/28/2011 11:02 AM, Emmanuel Noobadmin wrote:
If you have a graphical linux workstation on the same network (x can be slow across a WAN, so I would only do it locally), you can just do this from the workstation with X running:
ssh -XY -l root<server_name>
then from the server do this:
virt-manager
This will run just the application "virt-manager" on the server and push the video display back to your machine.
You may need to run this on the workstation before you ssh to the server machine:
xhost +
Thanks a lot for this tip, it'll probably come in very useful for me since it sounds a lot easier/efficient than having VNC (freenx never worked for me) on every CentOS machine in my office. Although maybe not in this particular case since my usual access to this particular server is through WAN.
Freenx is worth taking the time to solve whatever problem you had with it. It should 'just work' from a yum install as long as you install the /etc/nxserver/client.id_dsa.key into your NX client and have the default ssh access. You don't need to install it on every machine, just one that you use as your management desktop using the approach above to open windows for GUI programs from nearby machines. You can run the NX client->freenx connection over a WAN and get much better performance than you will with ssh-forwarded windows direct to your remote location - plus you can disconnect the NX session and pick it up elsewhere with all your windows still open and programs still running.
-
Emmanuel Noobadmin -
Johnny Hughes -
Les Mikesell -
Ljubomir Ljubojevic