-
Notifications
You must be signed in to change notification settings - Fork 257
How do you get this working in Realease 18.04 #27
Comments
@dankseman - it almost worked without change for me; I had to comment out
in install.sh from the ~/xrdp-init/ubuntu/18.04 directory; ran the script again, rebooted the Hyper-V and then did the usual I did completely shutdown the VM and start and stop the Hyper-V management service as well before I could get it to prompt for Enhanced but I don't remember doing that before. Still don't get any drives even with printers unchecked like other suggested. Login Screen is xrdp default but works none the less. |
Do you need to run git clone etc or just go straight to install.sh? |
Yep, I installed git first (but I used git for lots of things) and cloned it into a directory but I think you could just grab the file if you wanted too. |
I really not sure what you are saying. Can you just write commands I need
to use if not too much trouble (it seems less than before)?
I understand if you do not wish to of course if too much trouble.
…On Sun, 29 Apr 2018, 14:19 John Kattenhorn, ***@***.***> wrote:
Yep, I installed git first (but I used git for lots of things) and cloned
it into a directory but I think you could just grab the file if you wanted
too.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#27 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AjkSfnNiKJGy9DSwJrr_AL2b8GrKHWncks5ttb3cgaJpZM4TrVKm>
.
|
I just saw that about printers. It worked for me on 18.04 beta. |
No problem - I use this as reference https://www.tenforums.com/virtualization/107147-guide-how-run-ubuntu-18-04-enhanced-mode-hyper-v.html |
Well that is the guide I used as well but it fell over in git clone phase.
…On Sun, 29 Apr 2018, 14:40 John Kattenhorn, ***@***.***> wrote:
No problem - I use this as reference
https://www.tenforums.com/virtualization/107147-guide-how-run-ubuntu-18-04-enhanced-mode-hyper-v.html
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#27 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AjkSfr1-4n2ssrRKhoKGEoiKX9afqVtaks5ttcLogaJpZM4TrVKm>
.
|
What did you get back from |
I have partly sussed it. That link has somehow converted the git clone
into a hyperlink and it falls over. When I use command from original
source it works.
I removed the line as you said, and redid powershell. I then shut down vm
stopped and started service but it just point blank refuses to kick to xrdp.
…On 29 April 2018 at 14:45, John Kattenhorn ***@***.***> wrote:
What did you get back from sudo apt install git ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#27 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AjkSfkD5PZtZtO0TgjOImOA-JVTKPpwxks5ttcQRgaJpZM4TrVKm>
.
|
I get a xrdp "Just connecting" screen with a login dialog with several session options (Xorg, X11rdp, Xvnc, console, vnc-any, sesman-any, neutrinordp-any). If I choose Xorg, the dialog disappears and times out after about 5 mins. If I choose X11rdp, RDP says that it got disconnected and attempts to reconnect. I've tried removing the line suggested above Thanks! |
I had to comment out both rmmod vsock and rmmod vmw_vsock_vmci_transport in the install.sh script for ubuntu 18.04 to get it working. |
Thanks @stijnv1. I've tried that but still no luck. Which session should I use? XOrg or X11rdp? And do I need to rebuild the VM or just rerun the script? |
I started from scratch, editing install.sh commenting out the two rmmod lines, got to the end of the setup and got this error: Job for XRDP service failed because the control process exited with error code. Amy ideas. |
Steps I did:
|
@matthewturner does your VM log you in automatically? I am able to log in to an enhanced session using the Xorg option after disabling automatic login. |
I am sure this is actually a Hyper-v issue. Even if you have a Windows
guest, it does not connect properly unless the guest has a password. Always
been like that.
…On Wed, 2 May 2018, 22:27 Charlie Billen, ***@***.***> wrote:
@matthewturner <https://github.com/matthewturner> does your VM log you in
automatically?
I am able to log in to an enhanced session in using the Xorg option after
disabling automatic login.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#27 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AjkSfg7pM8CBgaV0KuuBv8IbV6WA193Kks5tuiTMgaJpZM4TrVKm>
.
|
Thanks @charliebillen, @stijnv1 and @dankseman. I had to comment out both lines ( The performance isn't quite what I'd hoped but close. Could those two lines affect performance? |
@matthewturner may be wrong but I don't think they'd affect performance. My potentially incorrect understanding is that those kernel modules allow communication between VMWare guests and hosts, and are removed and replaced with There is another issue (#28) with reports of slow performance on HiDPI screens. If you're running on your Surface Pro maybe you're seeing the same thing? |
@matthewturner - |
So explain to me why it bloody worked perfectly on a beta 1804 but is
complete garbage on release version?
I am so disappointed that the originator of the 16.04 web article has
failed to respond. Sad!
…On Thu, 3 May 2018, 23:33 Justin, ***@***.***> wrote:
@matthewturner <https://github.com/matthewturner> - vsock is the AF_VSOCK
protocol for tcp/ip between virtual machines and any hypervisor.
vmw_vsock_vmci_transport is the VMWare implementation of vsock when
running on a VMWare hypervisor and hv_sock is the Hyper-V implementation
for running on the Windows hypervisor. So the goal is that you are using
hv_sock + vsock to enable the Hyper-V socket connections between
host/guest.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#27 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AjkSfmOTZLFcfiHeFzIWZJ9kghjRjT2iks5tu4WfgaJpZM4TrVKm>
.
|
I think he must of just missed it. @cwilhit - Is very much on top of responses in other instances. I will work on getting this script fixed today for release 18.04. |
Beta releases of 18.04 had the vwmare module loaded by default, so we had that line included in the script because it must be unloaded in order to load hv_sock. I would like to note that these errors complaining about rmmod failing when a module is not loaded is not fatal. It should still continue to work :) Nevertheless, we'll remove those lines since they're not needed anymore. We're in the final stages of working with Canonical to get an image pre-configured in our Hyper-V Quick Create gallery, which means users don't even have to mess with manually configuring. Thanks for working with us on this! |
Even though I removed those lines, it still fails with an error about the
xrdp service as I said earlier, and then xrdp does not work. I believe the
issue is more complicated.
…On Fri, 4 May 2018, 20:09 Craig Wilhite, ***@***.***> wrote:
Beta releases of 18.04 had the vwmare module loaded by default, so we had
that line included in the script because it must be unloaded in order to
load hv_sock. I would like to note that these errors complaining about
rmmod failing when a module is not loaded is *not* fatal. It should still
continue to work :)
Nevertheless, we'll remove those lines since they're not needed anymore.
We're in the final stages of working with Canonical to get an image
pre-configured in our Hyper-V Quick Create gallery, which means users don't
even have to mess with manually configuring. Thanks for working with us on
this!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#27 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AjkSfkGZHLtXEgo5gLYbYcSOErDOJyAtks5tvKd3gaJpZM4TrVKm>
.
|
Is this a stock 18.04 release .iso you're using from Canonical and did this occur on your first attempt at running the script? My most recent attempt at running this script was this morning with an .iso from Canonical's website and it ran with no issues. After all, virtual machines are supposed to be reproduceable. |
Well, I finally got it working. I restarted from scratch and did full installation rather than the minimal installation as well. I actually typed all the commands and this time it worked. I do not know if this is relevant but I did the edit to install.sh before the chmod command this time, and I also did initial reboot using reboot command rather than shutting down via Hyper-V Taskbar and restarting. I copied these from cerberus script on www.tenforums.com Get the scripts from GitHub $ sudo apt-get update $ sudo apt install git $ git clone https://github.com/jterry75/xrdp-init.git ~/xrdp-init Make the scripts executable and run them... $ cd ~/xrdp-init/ubuntu/18.04/ Now edit the install.sh file using whatever editor you like (nano, vi etc) rmmod vmw_vsock_vmci_ttransport i.e. #rmmod vmw_vsock_vmci_ttransport Save file. $ sudo chmod +x install.sh $ sudo ./install.sh Reboot VM $ reboot Run script again to finish setting up VM $ cd ~/xrdp-init/ubuntu/18.04/ $ sudo ./install.sh Shutdown VM completely (I do this from Hyper-V Taskbar) On Host Windows, run following powershell command (with admin rights) Set-VM -VMName Ubuntu -EnhancedSessionTransportType HvSocket Restart VM to kick in to XRDP In popup box, deselect printers, and choose which drive you want to see. Login with xorg, and name, password. Now it is in enhanced mode. |
Seems like there might be multiple issues at play here. For whats is worth I also had issues with stock 18.04. After entering credentials afer xrdp login I just got a blank screen. I followed the microsoft blog documentation and decided to run the 16.04/config-user.sh script which I don't think works right on 18.04. I think I tracked it down to ~/.xsession being out of date--calling unity which got replaced by gnome. I replaced 'unity' on the last line with: Now I'm able to log in. |
Good to see it is working for you! You do not need to run the 16.04's config-user.sh for 18.04. |
Yeah -my instructions reflect that.
…On Thu, 10 May 2018, 16:15 Craig Wilhite, ***@***.***> wrote:
Good to see it is working for you! You do not need to run the 16.04's
config-user.sh for 18.04.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#27 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AjkSfmo30FosRhOntKKgZV1ktLwWuE14ks5txFmagaJpZM4TrVKm>
.
|
Any news on this? My quick create gallery isn't showing an Ubuntu option, just Windows 10 dev environment. |
@Ephesos mine doesn't either. Neither enterprise or professional had it available. I just installed it from the iso and installed this library. |
Still working through a few things to get the experience we want for the user. When it does go live, we'll post a new update on our blog and I'll tweet it out. |
Waiting anxiously for ubuntu 18.04 on quick start. |
@felipedeveza it's not that difficult to install yourself. Why wait. |
@sregister Your solution worked! |
Dealt with similar issues as you guys and tried the various remedies suggested here and other places. What worked for me, however, was installing the full version of Ubuntu; I sweated it out with the minimalist version. Someone somewhere said to run the VM on Gen 1 than Gen 2 but i was adamant on running it on Gen 2. The minimalist installation on Gen 2 was apparently missing some important driver/s and/or process/es which i didn't get the time to figure out; i hope someone does so that we get to make it work with the minimalist version. |
Don't see any shared-drives in the Ubuntu session. |
You have to be running normal version 1803 to do this as 1709 does not have the powershell upgrade needed. I am almost certain the same is true of Server 2016. |
Probably, well just from the MS doc (may 31) How does someone know that he is in EnhancedSessionMode, its just not by getting full-screen and Auto-Login? |
It just works i.e. you get the xrdp login screen. It will not work with 2016 - you will just get the normal linux login screen. Also, it does not work if you use linux autologin. |
@dankseman Don't quite understand whats the difference linux autologin vs RDP autologin could be? |
@pudknocka you need to be running a Windows version of 1803 or newer, like a recent Insider build. That means builds 17134+. Versions earlier than this (like 14393) do not have this feature--you'd need to upgrade to get it. As for your question about knowing you're in enhanced session mode: you'll have to login through an xrdp login, which has a very distinct baby blue background. Alternatively, in a Hyper-V VMConnect window, hovering over the icons in the toolbar you will see an icon that reads either "Basic Session" or "Enhanced Session" |
@cwilhit why is this issue closed without a fix in the Microsoft VM tools/scripts? As of 10/16/2018, linux auto-login is still kills enhanced sessions upon connecting. This happens on a fresh install and what's worse, the setup wizard happily presents the option to enable auto-login ("It's a trap!"). On a side note, Ubuntu 18.04's memory usage is really bloated, apparently due to Gnome (6.5GB idle at login). Do you support enhanced sessions with other desktop managers? If yes, how? For others seeing this and this issue broke gnome terminal, you can disable auto-login by "Show applications" (bottom-left) -> Details -> Users -> [Unlock] (top right) -> Automatic Login -> Off Or if terminal is working, by
|
@SidShetye this issue was opened to track generally getting enhanced mode to work with Ubuntu 18.04 release. If you want to track auto-login, I'd recommend following #22 instead. |
Hi! Posting because I ended up here trying to get Enhanced mode working. If you're stuck on an older release of Windows 10 and can't use HvSocket, just configure xrdp to listen on tcp, configure networking (make sure your machine can reach the VM over the network), and connect with Remote Desktop Connection (you can add Drive sharing before you connect). What worked for me: Matt |
I was able to get beta versions working with the scripts here (omitting a couple of commands) but it does not work at all on the release version. It falls over at this step
git clone https://github.com/jterry75/xrdp-init.git ~/xrdp-init
The text was updated successfully, but these errors were encountered: