Fedora CockPit (with KVM) Copy and Paste
-
One of the goals of the lab being, testing the hell out of Fedora Cockpit and KVM from multiple OS's and seeing how it all works and behaves.
Not the "use <insert alternative>" to achieve X" when I want to use "<built-in tools>".
-
@DustinB3403 said in Fedora CockPit (with KVM) Copy and Paste:
One of the goals of the lab being, testing the hell out of Fedora Cockpit and KVM from multiple OS's and seeing how it all works and behaves.
Not the "use <insert alternative>" to achieve X" when I want to use "<built-in tools>".
I don't access any hypervisor in this way. You are locked on a stupid silly little thing.
For Hyper-V, once installed, I install ScreenConnect and then use that interface for everything. To put the initial ISO files on there, I download them from my workstation and then copy them to
C:\ISO_Filesvia\\uncname\c$\ISO_FilesFor KVM, as soon as it is setup and online, I never log in to the local console via any means. Cockpit or otherwise. I use
sshfrom my workstation.While cockpit is a cool GUI, it is just that. A GUI. It will never be able to do everything that you need to do. Just like any other GUI.
-
@JaredBusch and do you also manage your VM's via SSH and instinctively know all of the KVM commands (or look them up constantly?)
This is one tiny issue to the overall, learning KVM portion of my lab that I was struggling to determine why it wasn't working the way I expected it to.
There is nothing to say I can't use putty, or SSH via powershell or VNC or any other tools. This is just one part of the "nice to know" things that if ever used in the wild would be great to know exists as a possible issue.
-
This entire topic is about a lab, is about learning. Finding issues or solutions to things that may occur. While generally speaking using a GUI or a piece of software like WinSCP will likely be the go-to solution, I guarantee that there would be a time when those tools aren't available for some reason.
Thus the test, and find the weird issues so they can be offset or worked around.
-
@DustinB3403 said in Fedora CockPit (with KVM) Copy and Paste:
@JaredBusch and do you also manage your VM's via SSH and instinctively know all of the KVM commands (or look them up constantly?)
I generally manage my VM's via VMM (which uses SSH) or Cockpit.
@DustinB3403 said in Fedora CockPit (with KVM) Copy and Paste:
This is one tiny issue to the overall, learning KVM portion of my lab that I was struggling to determine why it wasn't working the way I expected it to.
No, you were not struggling, you were refusing to do anything else. This is not even managing your VMs. This is a simple early setup step of the hypervisor itself.
@DustinB3403 said in Fedora CockPit (with KVM) Copy and Paste:
There is nothing to say I can't use putty, or SSH via powershell or VNC or any other tools. This is just one part of the "nice to know" things that if ever used in the wild would be great to know exists as a possible issue.
Terminal access via a webpage is always shit for features. Why? Because every single OS affects every single browser in different ways. Even before user configuration of said browsers comes in to play.
This is not unique to cockpit.
-
With that, I want to start with the Cockpit GUI and see what issues are encountered and what it can and cannot do. Where other solutions are better (many of which I already know) and learn the tools and system.
-
@DustinB3403 said in Fedora CockPit (with KVM) Copy and Paste:
This entire topic is about a lab, is about learning. Finding issues or solutions to things that may occur. While generally speaking using a GUI or a piece of software like WinSCP will likely be the go-to solution, I guarantee that there would be a time when those tools aren't available for some reason.
Thus the test, and find the weird issues so they can be offset or worked around.
Cockpit IS the GUI.....
-
@JaredBusch said in Fedora CockPit (with KVM) Copy and Paste:
@DustinB3403 said in Fedora CockPit (with KVM) Copy and Paste:
This entire topic is about a lab, is about learning. Finding issues or solutions to things that may occur. While generally speaking using a GUI or a piece of software like WinSCP will likely be the go-to solution, I guarantee that there would be a time when those tools aren't available for some reason.
Thus the test, and find the weird issues so they can be offset or worked around.
Cockpit IS the GUI.....
I could use the Desktop console (that also has a GUI). Cockpit is a tool to be used.
-
Honestly, this is all kinda silly.
You are "creating" a problem that simply doesn't exist!!Cockpit terminal tab, Copy & paste in a Windows 10 vm works.
I just tried it again in v1809 (OS Build 17763.107) -
The last time I tried copy and paste it worked.
-
@FATeknollogee said in Fedora CockPit (with KVM) Copy and Paste:
Honestly, this is all kinda silly.
You are "creating" a problem that simply doesn't exist!!Cockpit terminal tab, Copy & paste in a Windows 10 vm works.
I just tried it again in v1809 (OS Build 17763.107)I've already agreed this is likely an issue with the system I was using.
Hence there is no "creating a problem". I'm not even at the lab. I simply wanted to see if others were having the same issue when I made this post. You're not having this issue, therefore I have to look at either my Windows system or use alternative solutions which are known to work.
-
@FATeknollogee said in Fedora CockPit (with KVM) Copy and Paste:
Honestly, this is all kinda silly.
You are "creating" a problem that simply doesn't exist!!Cockpit terminal tab, Copy & paste in a Windows 10 vm works.
I just tried it again in v1809 (OS Build 17763.107)No, he is not. Also, no, it does not "just work" as you say. If it did, the post would never have been made.
I consistently have random issues using copy and paste into a web interface terminal. Both Cockpit and UNMS. Sometimes it works, sometimes it does not.
I do it little enough, that i never care to toubleshoot it.
-
@JaredBusch said in Fedora CockPit (with KVM) Copy and Paste:
@FATeknollogee said in Fedora CockPit (with KVM) Copy and Paste:
Honestly, this is all kinda silly.
You are "creating" a problem that simply doesn't exist!!Cockpit terminal tab, Copy & paste in a Windows 10 vm works.
I just tried it again in v1809 (OS Build 17763.107)No, he is not. Also, no, it does not "just work" as you say. If it did, the post would never have been made.
I consistently have random issues using copy and paste into a web interface terminal. Both Cockpit and UNMS. Sometimes it works, sometimes it does not.
I do it little enough, that i never care to toubleshoot it.
I'll second this - The troubles in pasting into a web based console are real - and sometimes seemingly random.
I am willing to blame Windows on this problem - but the problem is real.
