Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
We need opinion on how feasibale will it be to work on ubuntu gmnome desktop accessing it remotely running on a virtual machine provided network speed is good compared to physical machine running ubunut desktop?
We tried remote access using xrdp, vnc, nxserver none of them appeared to work good its always hanging copy/paste does not work, refresh rate is slow etc.
I am wondering if remote access ubuntu desktop is a good option ?Please advice.
Your description of what you're attempting is confusing:
Quote:
accessing it remotely running on a virtual machine
What purpose/role does the virtualization serve? It sounds to me like a useless layer, that is possibly responsible for the poor performance. I use remote desktop access to both Linux and Windows hosts successfully on both Linux and Windows clients.
Further, it is unusual to export a desktop to remote hosts. Usually, the remote host logs in with ssh, with its own local desktop. The ssh login can then be used to launch whatever applications are required, including GUI applications whose X connection will be forwarded to the remote host's X server.
What are you trying to accomplish by exporting the remote desktop?
ubuntu will be our new development environemnt, our network guys say its easier for them to provide us VM than a physical machine , we have our windows desktops and we will remote to the ubuntu desktop , if remote option is not friendly I would convey this to my network guys accessing linux desktop remotely for everyday work is a bad idea.
Quote:
Originally Posted by theNbomr
Your description of what you're attempting is confusing:
What purpose/role does the virtualization serve? It sounds to me like a useless layer, that is possibly responsible for the poor performance. I use remote desktop access to both Linux and Windows hosts successfully on both Linux and Windows clients.
Further, it is unusual to export a desktop to remote hosts. Usually, the remote host logs in with ssh, with its own local desktop. The ssh login can then be used to launch whatever applications are required, including GUI applications whose X connection will be forwarded to the remote host's X server.
What are you trying to accomplish by exporting the remote desktop?
ubuntu will be our new development environemnt, our network guys say its easier for them to provide us VM than a physical machine , we have our windows desktops and we will remote to the ubuntu desktop , if remote option is not friendly I would convey this to my network guys accessing linux desktop remotely for everyday work is a bad idea.
Okay, so the remote Linux is Ubuntu, and it is virtual. Now the question becomes whether you actually need a desktop on a remote host to do development. Using an ssh connection from your Windows workstation to the virtual Ubuntu should give you excellent performance, and still provide all of the development environment you need. I have used that model for many years, using both Windows and Linux on the local workstation, and both real and virtual development hosts. What is there on the remote Ubuntu desktop that you consider vital? Exporting an entire remote desktop seems needless & resource-consuming.
--- rod.
I need the entire desktop we are using this like our physical machines unfortunately our network team thinks its good idea to have a vm than a physical machine, I want to convince them its not good idea to use remote access linux compared to physical machine.
Quote:
Originally Posted by jefro
Might even look at 2X.com products.
I think that NX is maybe the fastest or tied with windows RDP.
Do you need to see the entire desktop or can you use other means to display a single application?
Might also consider iscsi type of systems or a ipxe/gpxe boot to a network share virtual machine image or system image.
I need the entire desktop we are using this like our physical machines
Why do you need to do that? If the virtual hosts become real hosts, how will that matter? If you have one virtual (or real) host, how will you share its single desktop concurrently with multiple users? Will all users share one ID on the remote Ubuntu? Wouldn't you want each user to have his/her own login ID? Remote access does not mean remote desktop. That is how Windows remote access works, but it is seldom used to access Linux hosts, which are intended to support multiple users concurrently.
The remote host can be either real or virtual. It's done all the time. Frequently, a shared development host is run completely headless; there is no desktop to be shared.
We were developing in windows machine , now we have to move to machine with operating system ubuntu,our new development machines will be ubuntu desktops.
Every developer who has the windows machine will get a machine which has ubuntu operating system .
We asked our network team to install ubuntu in every developer machine. They say its better to have virtual machine rather than installing ubuntu in every machine and access ur ubuntu machine through vnc client.
The developers when we tried vnc clinet to access our ubuntu machines we felt its refresh rate is slow, no full screen, no dual monitor copy paste from windows to ubuntu did not work etc .
Please advice me what option is the best having a virtual machine access it through vnc client or have it physically installed in our machines replacing windows?
Hope this explains my concern.
Quote:
Originally Posted by theNbomr
Why do you need to do that? If the virtual hosts become real hosts, how will that matter? If you have one virtual (or real) host, how will you share its single desktop concurrently with multiple users? Will all users share one ID on the remote Ubuntu? Wouldn't you want each user to have his/her own login ID? Remote access does not mean remote desktop. That is how Windows remote access works, but it is seldom used to access Linux hosts, which are intended to support multiple users concurrently.
The remote host can be either real or virtual. It's done all the time. Frequently, a shared development host is run completely headless; there is no desktop to be shared.
If you want to use the Ubuntu host from a Windows desktop, then use a Windows ssh client (putty, for instance), and a Windows hosted X server. Login to the remote Ubuntu (doesn't matter whether the Ubuntu is real or virtual), and do your development as a Ubuntu user. Perhaps also, mount the remote Ubuntu filesystem by running a Samba server on the Ubuntu host. Then you can use the local desktop facilities for copy & paste, local editors (but be cognizant of line-terminators), and see all of the files on the Ubuntu host, either as a Windows user with a shared network filesystem, or as a native Ubuntu user logged in via ssh. No need to run any kind of desktop on the development host. In fact, the development host can run completely headless. This will give you good, efficient performance, and provide all of the facilities you need for developing Linux software, either text-mode or GUI.
I suggest that if you are using the Ubuntu platform for team-oriented software development, that you install only one, used by all team members with their own login IDs. Use a code versioning system such as CVS to keep track of source code on the development host, and do backups from the one host only.
I wouldn't recommend vmware player, use server instead (also free), it lets you run the vm's in a more long term back ground server-like state, and is easier to configure for long term usage (start on boot etc). Performance should be "fine" in general, depends on the machine you're using really.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.