Manage KVM through Cockpit
-
@tim_g said in Manage KVM through Cockpit:
@stacksofplates said in Manage KVM through Cockpit:
CentOS 7 now has the VM console as long as the VM has VNC graphics. You don't need to remove SPICE, you can just add VNC also.
What did you do to be able to see the terminal in Cockpit? When I try I just see "Manual Connection" connection info, and a button to launch Remote Viewer. I do have both SPICE and VNC display added.
When I'm using In-Browser Viewer, I don't get anything.
Oh, it was hidden. When I resized my web browser, it showed the "Password Required" box.
In order for me to see that, I have to resize my web browser every time. If it's maximized, I have to un-maximize it, and then maximize it again, or resize it any way period to get it to show. Weird.
-
If I have the VNC connection passworded, in Cockpit after entering the password, it gives an error: "Failed to connect to server (code: 1006)".
If I do not use a password, it works fine. Anyone else run into this?
-
@tim_g said in Manage KVM through Cockpit:
If I have the VNC connection passworded, in Cockpit after entering the password, it gives an error: "Failed to connect to server (code: 1006)".
If I do not use a password, it works fine. Anyone else run into this?
No I haven't used that function.
-
@tim_g said in Manage KVM through Cockpit:
@tim_g said in Manage KVM through Cockpit:
@stacksofplates said in Manage KVM through Cockpit:
CentOS 7 now has the VM console as long as the VM has VNC graphics. You don't need to remove SPICE, you can just add VNC also.
What did you do to be able to see the terminal in Cockpit? When I try I just see "Manual Connection" connection info, and a button to launch Remote Viewer. I do have both SPICE and VNC display added.
When I'm using In-Browser Viewer, I don't get anything.
Oh, it was hidden. When I resized my web browser, it showed the "Password Required" box.
In order for me to see that, I have to resize my web browser every time. If it's maximized, I have to un-maximize it, and then maximize it again, or resize it any way period to get it to show. Weird.
Hmm. I don't have that issue. That's interesting.
-
Anyone know if Fedora 28 has KVM management built in to the default Cockpit yet, or does it still require additional updates?
-
The KVM management is not 100% & yes you still need to update with "dnf install -y cockpit-machines"
-
@fateknollogee said in Manage KVM through Cockpit:
The KVM management is not 100% & yes you still need to update with "dnf install -y cockpit-machines"
Only an extra package is pretty good. Don't need to go to a beta version or something.
-
@scottalanmiller No beta at all. Either way, you still need virt-manager or virsh for complete control during setup of your vm's.
-
@scottalanmiller said in Manage KVM through Cockpit:
@fateknollogee said in Manage KVM through Cockpit:
The KVM management is not 100% & yes you still need to update with "dnf install -y cockpit-machines"
Only an extra package is pretty good. Don't need to go to a beta version or something.
Not exactly. As of Fedora 27, the default cockpit install, if you select it during the GUI install, is not a complete cockpit install in the first place.
After getting to the root login, you still need to do
dnf install cockpitto get the full package. By default, it only hadcockpit-wsand dependencies.I have not done a clean F28 install and tested tihs.
Let me go spin one up.
-
Will update shortly.
-
Still the same. Cockpit it NOT fully installed.
[jbusch@localhost ~]$ sudo dnf list cockpit* Last metadata expiration check: 0:02:38 ago on Mon 28 May 2018 02:13:56 PM CDT. Installed Packages cockpit-bridge.x86_64 168-1.fc28 @updates cockpit-networkmanager.noarch 168-1.fc28 @updates cockpit-storaged.noarch 168-1.fc28 @updates cockpit-system.noarch 168-1.fc28 @updates cockpit-ws.x86_64 168-1.fc28 @updates Available Packages cockpit.x86_64 168-1.fc28 updates cockpit-dashboard.x86_64 168-1.fc28 updates cockpit-doc.noarch 168-1.fc28 updates cockpit-docker.x86_64 168-1.fc28 updates cockpit-kdump.noarch 168-1.fc28 updates cockpit-kubernetes.x86_64 168-1.fc28 updates cockpit-machines.noarch 168-1.fc28 updates cockpit-machines-ovirt.noarch 168-1.fc28 updates cockpit-ostree.noarch 168-1.fc28 updates cockpit-packagekit.noarch 168-1.fc28 updates cockpit-pcp.x86_64 168-1.fc28 updates cockpit-selinux.noarch 168-1.fc28 updates cockpit-sosreport.noarch 168-1.fc28 updates cockpit-tests.x86_64 168-1.fc28 updatesInstalling
cockpitresults in this.[jbusch@localhost ~]$ sudo dnf install cockpit Last metadata expiration check: 0:04:34 ago on Mon 28 May 2018 02:13:56 PM CDT. Dependencies resolved. ================================================================================================================================== Package Arch Version Repository Size ================================================================================================================================== Installing: cockpit x86_64 168-1.fc28 updates 62 k Installing weak dependencies: cockpit-dashboard x86_64 168-1.fc28 updates 213 k cockpit-packagekit noarch 168-1.fc28 updates 276 k Transaction Summary ================================================================================================================================== Install 3 Packages -
Installing
cockpit-machinesis not dependent oncockpit. So you may not need the full cockpit to make it all work.[jbusch@localhost ~]$ sudo dnf install cockpit-machines Last metadata expiration check: 0:11:34 ago on Mon 28 May 2018 02:13:56 PM CDT. Dependencies resolved. ================================================================================================================================== Package Arch Version Repository Size ================================================================================================================================== Installing: cockpit-machines noarch 168-1.fc28 updates 505 k Installing dependencies: libvirt x86_64 4.1.0-2.fc28 fedora 9.3 k libvirt-daemon-config-nwfilter x86_64 4.1.0-2.fc28 fedora 14 k libvirt-daemon-driver-libxl x86_64 4.1.0-2.fc28 fedora 161 k libvirt-daemon-driver-lxc x86_64 4.1.0-2.fc28 fedora 162 k libvirt-daemon-driver-uml x86_64 4.1.0-2.fc28 fedora 69 k libvirt-daemon-driver-vbox x86_64 4.1.0-2.fc28 fedora 148 k libvirt-daemon-driver-xen x86_64 4.1.0-2.fc28 fedora 131 k Transaction Summary ================================================================================================================================== Install 8 Packages -
@jaredbusch oh weird.
-
@scottalanmiller said in Manage KVM through Cockpit:
@jaredbusch oh weird.
It's been like that since I can remember.
Also, minimal install doesn't install cockpit at all.
-
@obsolesce said in Manage KVM through Cockpit:
@scottalanmiller said in Manage KVM through Cockpit:
@jaredbusch oh weird.
It's been like that since I can remember.
Also, minimal install doesn't install cockpit at all.
That I knew.
-
@obsolesce said in Manage KVM through Cockpit:
@scottalanmiller said in Manage KVM through Cockpit:
@jaredbusch oh weird.
It's been like that since I can remember.
Also, minimal install doesn't install cockpit at all.
When I installed Fedora 28 minimal without LVM, installling cockpit didn’t include cockpit.storaged for some reason.
-
Sorry if this is a dumb question, I'm very new at Linux in general.
When adding a VM, where do you tell it to store the VM at?
-
@ccwtech said in Manage KVM through Cockpit:
Sorry if this is a dumb question, I'm very new at Linux in general.
When adding a VM, where do you tell it to store the VM at?
I don't think you can through Cockpit at this point. You need to either use
virshor Virt-Manager. -
@ccwtech said in Manage KVM through Cockpit:
Sorry if this is a dumb question, I'm very new at Linux in general.
When adding a VM, where do you tell it to store the VM at?
I make another partition and mount it to /data
-
Ok, I have the file system setup with plenty of space in /var
Trying to install using Cockpit:
ERROR internal error: process exited while connecting to monitor: 2018-06-17T23:26:23.767121Z qemu-system-x86_64: -drive file=/run/media/root/DATA/en_windows_server_2012_r2_x64_dvd_2707946.iso,format=raw,if=none,id=drive-ide0-0-1,readonly=on: Could not open '/run/media/root/DATA/en_windows_server_2012_r2_x64_dvd_2707946.iso': Permission denied Domain installation does not appear to have been successful. If it was, you can restart your domain by running: virsh --connect qemu:///system start Server-2012R2 otherwise, please restart your installation.
