<div dir="ltr"><div>Hi,</div><div> </div><div>no this is the normal forward-slash with "shift+7" on the german keyboard - googlemail messed it up translating it to something else. </div><div></div><div>The URL is normally typed.</div><div> </div><div>This is really weird and I will try to help you as much as I can to get to the bottom of it. </div><div> </div><div>Stefan </div></div> <div class="gmail_quote"><div dir="ltr" class="gmail_attr">Am Do., 17. Nov. 2022 um 10:08 Uhr schrieb Frediano Ziglio <<a href="mailto:freddy77@gmail.com">freddy77@gmail.com</a>>: </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Il giorno gio 17 nov 2022 alle ore 07:57 Stefan Silberstein <<a href="mailto:linuxstony@gmail.com" target="_blank">linuxstony@gmail.com</a>> ha scritto: > > Hello again, > > so - yesterday I worked from home - as I wrote I was able to connect by specifying the user root with "remote-viewer spice://<a href="http://root@192.168.178.51:5900" rel="noreferrer" target="_blank">root@192.168.178.51:5900</a>" > > Today I want to connect the exact same way (yesterday i simply closed the remote-viewer window and the server keept on running so the windows-VM was running the whole night) - and I can not connect. > > Error Message on the console "** (remote-viewer:6146): CRITICAL **: 07:55:52.853: virt_viewer_util_extract_host: assertion 'uri != NULL' failed" > Error Message on the popup says translated: Connectiontype could not be determined by URI. > Hi, That means that the code was not able to parse the URI. > IP of the server itself is 192.168.178.51 > IP of the Virtual Machine is 192.168.178.64 and i pingable > Port 5900 on the server is open: 5900/tcp open vnc > remote-viewer --spice-debug spice:⁄⁄<a href="http://192.168.178.51:5900" rel="noreferrer" target="_blank">192.168.178.51:5900</a> does not produce a more verbose output :( > In this example you are not using ASCII slashes (//), maybe that's the problem. > Update in the meantime > But maybe this is helpful to you: > > I simply started "remote-viewer --spice-debug" > Then i got the GUI (which i wasnt even aware it existed). > > When I choose the same entry on that list - I AM able to connect. > > So the error only exists only when I try to connect via command line?! (This is when I am able to connect tomorrow via GUI ;) ) > > Shouldn't this be the same ? > > I mabe I can help - maybe this is indeed a bug? > > Stefan > Frediano > Am Mi., 16. Nov. 2022 um 09:37 Uhr schrieb Victor Toso <<a href="mailto:victortoso@redhat.com" target="_blank">victortoso@redhat.com</a>>: >> >> On Wed, Nov 16, 2022 at 09:27:21AM +0100, Stefan Silberstein wrote: >> > I appreciate the time to answer me. >> > >> > In the meantime (out of desperation because i needed the virtualmachine for >> > work) I gave it a go with specifying root as user and not the servers >> > username "server". >> > >> > I was able to connect to the virtual Windows10 installation with >> > >> > remote-viewer spice://<a href="http://root@192.168.178.51:5900" rel="noreferrer" target="_blank">root@192.168.178.51:5900</a> >> >> Cool >> >> > But again - then I dont unterstand why it worked as user and >> > later on with specifying the user later on (which doesn't work >> > right now anymore) >> > >> > So it is a permissions problem on my side and I successfully >> > wasted your time. :/ >> > >> > Sorry about that. >> >> Don't worry about that. Happy to hear it worked. >> >> > >> > This happens when "users" try to play with the big boys toys :D >> > >> > Have a nice day you all and thanks for your time. >> >> You too. >> Cheers, >> >> > >> > Stefan >> > >> > Am Mi., 16. Nov. 2022 um 09:21 Uhr schrieb Victor Toso < >> > <a href="mailto:victortoso@redhat.com" target="_blank">victortoso@redhat.com</a>>: >> > >> > > Hi Stefan, >> > > >> > > On Tue, Nov 15, 2022 at 09:53:05PM +0100, Stefan Silberstein wrote: >> > > > Hello developers, >> > > > >> > > > I can imagine that this will be an annoying question for you - >> > > > so I apologize in advance. >> > > > >> > > > I am a user - with a longer history with linux BUT i am >> > > > completely new to virtualization. >> > > > Due to the fact that I got a server donated to me I wanted to >> > > > give it a go and it worked like a charm. >> > > > >> > > > Installed virt-manager, installed Windows10 connected with >> > > > virt-manager - absolutely no problem. >> > > > >> > > > Due to the fact that I need dual monitors I learned that I >> > > > could add another display and connect with spice - and it >> > > > worked immediately. >> > > > >> > > > BUT - without me changing anything (consciously) I wasn't able >> > > > to connect to the virtual machine the next week. >> > > > >> > > > It refuses with "Verbindungstyp konnte nicht von URI ermittelt werden" >> > > > (Connection type could not be determined by URI) >> > > > >> > > > Then i tried to connect with sudo and specifying the user in >> > > > the command line and it once again connected: >> > > > >> > > > sudo remote-viewer spice:⁄⁄<a href="http://server@192.168.178.51:5900" rel="noreferrer" target="_blank">server@192.168.178.51:5900</a> >> > > >> > > Perhaps the URL is the problem. If the IP is 192.168.178.51 and >> > > the port for the VM is 5900, then try >> > > >> > > remote-viewer spice://<a href="http://192.168.178.51:5900" rel="noreferrer" target="_blank">192.168.178.51:5900</a> >> > > >> > > If server is a dns that can be resolved, should be fine to use it >> > > instead of ip address >> > > >> > > remote-viewer spice://server:5900 >> > > >> > > >> > > > And now - again without changing anything - it doesn't connect >> > > > with that command as well. >> > > > >> > > > I have sadly NO clue whatsoever where to even search for a >> > > > solution - the internet didn't help me here... >> > > > >> > > > Do you have any hint at all what I might do wrong here? >> > > > >> > > > The machine is available - the port is open and visible >> > > > PORT STATE SERVICE >> > > > 22/tcp open ssh >> > > > 80/tcp open http >> > > > 3389/tcp open ms-wbt-server >> > > > 5900/tcp open vnc >> > > > >> > > > ufw on the server is shut down. >> > > > >> > > > ANY help would be greatly appreciated. >> > > >> > > You can get more verbose information of issues with --spice-debug >> > > command line option too. >> > > >> > > Cheers, >> > > Victor >> > > </blockquote></div>