A Look at Virt-Manager (KVM/QEMU) GUI
Вставка
- Опубліковано 6 січ 2020
- In this episode of the CyberGizmo we explore the graphical user interface for QEMU/KVM. I am moving off Open VirtualBox, it is just getting slower and slower for me. Gnome Boxes is a quick fast way to create VM, but lacks the options I think I will need going down the road to replace VirtualBox.
I say in this video that AMD invented virtualization support in hardware that is true, but most people credit IBM with the first operating system to support Virtualization. And even this isn't completely true. Atlas was the first to support virtual memory (without which virtualization would have never been possible)
The Burroughs B5500 had rudimentary virtual segmentation in its early MCP (a very primitive form of virtualization way back in the mid 1960's almost 10 years before IBM "invented" OS/VS1
Finally the Intel 80286 had a form of software emulated virtualization that was slow, terrible and clunky
Intel did not really support hardware assisted virtualization until the Hazwell series of chips.
Follow me:
Twitter @djware55
Facebook: / don.ware.7758
Music Used in this video
"NonStop" Kevin MacLeod (incompetech.com)
Licensed under Creative Commons: By Attribution 3.0 License - Наука та технологія
![Lp. Последняя Реальность #97 ЧЁРНАЯ МАТЕРИЯ [Анти Скинт] • Майнкрафт](http://i.ytimg.com/vi/k4MjXCzKsYw/mqdefault.jpg)
I have been using Virt-manager for 15 years or more. Virt-manger supports Xen,Lcx, and KVM. I started using it on Suse Enterprise Linux 10 and Xen virtualization. It works great. Today I have many KVM/qemu virtualization. It is more flexible with hardware than VMware ESXi and does not require a lot of RAM that a lot of other KVM front ends use/require.
1. Linux reads and writes ntfs too, so you can skip the FAT partition. I used ntfs on Linux already 10 years ago.
2. Maybe you want to run your banking stuff for safety in an encrypted VM and block all inbound traffic for that VM.
3. I did use vdi files directly in QEMU/KVM.
4. The GUI of Virt-manager is relative primitive compared to Virtualbox and not all functions work.
5. Most Windows drivers are based on old stuff from 2014 and I doubt, whether they contain all the security updates.
6. If I run the Windows-VM on the original off-lease PC, I can activate Windows using the sticker on that PC in Virtualbox. That is why I have all Windows version from 1.04 till 10 nicely activated and I could run all upgrades till their end-of life dates. In virt-manager it is impossible, maybe because of the very limited list of supported CPUs.
Yes, the disk IO of QEMU/KVM is faster, but I compensate it by running the Virtualbox VMs with ext4/ntfs on top of the Host's OpenZFS. Consequently ~98% of all disk IO is served from my 4GB L1ARC (lz4 compressed memory cache). You could say, it is like running my VMs from a RAM disk. Linux VMs boot in ~10 seconds. The CPU is the bottleneck and it is one of the cheapest and slowest Ryzen CPUs (Ryzen 3 2200G; $95; 4C4T; 14nm; clocked at 3.5 GHz boosting till 3.7 GHz).
Thank you! 👍 Recently i updated my pc from Win7 to Debian10 but I need to run some programs that limited to Windows. Your video helped me a lot to understand how it works in Linux.
BenitoF tyou are welcome and glad it helped you :)
@@CyberGizmo :-) What i've learned in the past is, that the Linux community is more supportive to new users and much more into finding solutions for all kinds of problems than the residents of the Windows-Universe.
I've got a question to you about virtualisation. Wich is better for running certain Win-Apps: KVM/Qemu or Docker/Container. Sorry, if that sound silly but i'm not got really into it yet. I've used VirtualBox on my Win7-PC and you're right -that sucks a lot. ;-) I understand the principles of docker+containers (and that it is less hungry for hardware resources) but i but haven't found any useful instructions on how to really run Windows 7 or Win7 programs -with GUI - yet. Now i wonder what i should do best to get these apps running on Linux. For example i've got an architectural Program wich i need for work and use quite often. And that's the main reason i've stayed so long on Win7. Maybe you can shine some light on it for me. Thank you! (And sorry for any misspelling, english isn't my native language)
That is a great video, thanks for taking the time to explain the “why” as well as the “how”. The bit about the root being the only permission to creating VMs and the .conf settings is the missing piece of the puzzle! Thanks.
Super video. Nice job!
Thanks Datapioneer appreciate that
Great video, thank you.
Thank you Faisal and glad you liked it
Great stuff !
Thanks, Kevin :)
Thanks DJ
Welcome D Naya and thank you for the comment
Something that works fine for me is using the super simple gnome-boxes to creat the VM and then if I need to tweak it , I'll use virt-manager to do the fine tuning or add some some device
Did virtual-manager handle all the selinux contexts automatically when you added your own folder for the iso’s?
As far as I know, WINE does NOT use QEMU. WINE translates the Windows API into Linux calls. However, there's nothing to stop anyone from running WINE inside of a QEMU Instance.
Thank you for the video.
Can you please share if there is method to share a physical hard drive between the host and guest machine that are bidirectional and one system/machine doesn't lock the files (permissions) for the other system/machine. Would greatly appreciate it. Have looked almost everywhere and they are not what I am looking for.
Thank you for your time.
Hello,is it possible to create a vga pass through when using a laptop with iGPU and dGPU?
15:20 Setup
18:45 Troubleshooting
I have a "fuzzy" look today because I was up most of the night preparing the next video...not this one :)
Well Intel was slow to virtualize the protected mode (32-bit) instruction set. 386 and higher virtual Real mode x86 support. This what made many 386 memory managers and multitaskers work under DOS. I twisted Dos into running stuff better suited to Windows or Linux using the crude VM hooks in the 386 class machines. Late model OS/2 multitasked traditional DOS programs and its own protected mode programs. Window 3.1 and 9xran over it, of course.
I installed this setup on my PopOS 19.10, it worked the first 2 times properly but now the host won't shutdown correctly and I can't even get the virtmanager to connect. KVM/QEMU is great but the setup is harder than something like virtual box.
I like virt manager but cant seem to get copy-paste function to work. Any ideas?
Hi, I wanted to try to follow your advice and I installed VM, but I had a problem, trying to install Whonix which as you know is .ova does not recognize it while Virtualbox recognizes it.
Is there maybe a solution to this problem that I don't know?
Greetings
Worked OK for ArcoLinux Xfce and OpenBox, but for i3 it wouldn't go above 800x600, and due to lack of patience for software that isn't friendlier, I turfed it. VB works like I like it to, so that's what I'm sticking with.
At 28:03 you show that window that shows "migrate" about the VM, but it is greyed out. Also at 31:27 you show the advanced options, and the path to where the image is stored is shown, but it seems there is no option to move the VM images to another hard drive, that is what I want. Could you make a video about how to set the path for the VM images on another hard of my system, so they are not stored on my SSD? Thanks in advance for another wonderful video, your channel is awesome, you provide many insights on your videos that I do not find elsewhere.
Nice, but since your host was ubuntu, what about lxd/lxc solution. Any comment on that?
Thanks Hans, yep will get to those as well. One host was Ubuntu but video was made on Fedora
I heard boxes is very good now with VM's have you tried it recently, I hear that multi VM's now talk to one another really easy now without problems
Yes, have been using boxes when I do not need additional configuration for the VMs
GNU/Linux native dude! QEMU-KVM rocks. Why wouldn't you!? But yeah, I remember that dual-boot dance..LOL
Linux reads windows files systems. You can mount a windows partition in linux and transfer file through a simple file manager.
VM Manager is much better than Virtualbox. You can lot many things [ passthrough etc ] which Virtual box can't do. But if you need bare metal virtulisation experience, Proxmox is the way to go. Its free, opensource and can be installed in less than 5 mins.
Sounds like another one to try as well. I didn't want to cover type 1 Hypervisors today, but an idea for a future video and will take a look at VM Manager as well. Thanks, mithub for the comment and great suggestions.
Thanks for the comment about Proxmox, it is very interesting.
Proxmox is running KVM for virtual machines, so the performance is the same as for QEMU/KVM. For Proxmox you basically need a second PC as Proxmox server.
The VM Manager is intended for enterprises and it runs in the Cloud. You need a Google Cloud Billing Account, so for home users it is an expensive and complex overkill.
@@bertnijhof5413 " The VM Manager is intended for enterprises and it runs in the Cloud. You need a Google Cloud Billing Account," Please do not misguide any one. Whatever you said is 100 % wrong. You can have VM manager running any standard Linux Box supporting virtulisatin [ VT-X support ]
@@mithubopensourcelab482 I'm talking about Googles VM manager, maybe there are more than one and I checked Google WEB site for the VM-Manager. Just google "Google VM Manager" and learn something new.
Do you still have a copy of the x86 AT&T UNIX you've used back then? I would love it, if you made a video on that!
I do actually, not sure it will run, but I still have it, but would need to find a reader for the media :). Off to the junk dealers to find one :)
@@CyberGizmo 🌞 Sorry for making your comment section into my wishlist, but your retrospect view on all the different init-systems in *nix would also be very much appreciated!
DJ, I have replicated this process on FerenOS December 2019 Build on bare metal. Was thinking of doing a video on the subject similar to yours but didn't want to step on any toes. Do you have any objections? To be clear, I'm not stealing any of your content, just the concept which should be okay, but wanted to run it by you. Please let me know.
Datapioneer, No objections at all. Will check out your video when you are done would love to hear your take on this as well.
The more quality content on the topic, the better.
So how would I add virtual storage to a separate drive? I want to install the windows vm permanently on a separate 1Tb drive divided into 2 partitions. The second partition I will use to test mac stuff. Do I need to add the entire drive as a pool option? I'm sort of new so please forgive the ignorance of the newbie
Atziluth, you need to create a pool in the menu dialog when you attach the ISO to load from, then when creating virtual hard drive, choose manage storage and create the file store on the pool you created before. I will be showing this today if I get the video done for ZFS part 2. (Also make sure your user can read/write to the volume or director which holds your new pool
@@CyberGizmo yes thank you! I figured it out just last night. Had to do chmod 777. Also if you do vfio the drive wont show up in the windoes installation. To fix that, download the vfio driver from fedora for windows and click "browse" during the windows installation to find the x64 folder and then win10 inside that (Assuming win10 x64). Then install it and your unallocated drive will show up
@@atziluth5198 Thanks for that additional info!
@@CyberGizmo no problem. Also, i just booted up my pc and ran the vm. It gave me a permission error after i had already been in and created it. The drive was unmounted so i had to remount it. I believe that is what is creating the issue. I gotta find a way to keep the drive mounted when i shutdown and see if it fixes it
@@CyberGizmo it worked. i followed this guide: forum.manjaro.org/t/wiki-howto-permanent-mount-for-partition/26187
Everything works great
unable to complete install: cannot access storage file '/media/mike/savehere/machine/ubuntu.qcow2
that's the error i'm getting when creating a new vm. do you know what can be done?
Did you move/delete the ISO you used to create the virtualization?
What are you doing with all those hard drives behind you?
Its a glusterfs cluster (storing videos and home directories)
Warning: Wall of text!
a) 7th Jan 2020? Superblocks are a historic artefact of BIOS firmware. These days, you have to be in fairly extreme circumstances to be using such firmware, or even simulating it's boot process through the CSM (compatibility support module) in your UEFI firmware. If your OS breaks UEFI standard and changes the boot OS in an update, (rather than an install) you can just change it back in your firmware configuration. The worst case, is when fastboot makes it an arse to get into your firmware config utility because it doesn't enable the keyboard driver until it's passed the hotkey check. 🙄️ Windows _and_ Linux have a way to reboot to the firmware configuration... I usually have no issues with the hotkeys on Macs but I read that nvram "recovery-boot-mode=unused" will make it start in recovery mode. I've not tried on BSD OSs, and more exotic OS (ReactOS, Haiku, AROS etc.) may well _not_ have such a system, and that would be bad. (If you have this, disconnecting the mains for a good 5min, or full capacitor discharge, reconnecting and powering on with the hotkey often forces a regular boot, instead of fastboot... That's not possible on mobile devices, which increasingly don't even let you take the battery out ☹️) Mostly, such exotic OS are prime examples where you'd want to give them dedicated hardware, or isolate them in a VM.
b) Well, your EFI boot partition will be FAT-compatible formatted anyway, (maybe just extend that a bit?) but in all honesty, Windows, Mac OS, Linux and Unix can all read and write an NTFS partition, or (with a 3rd party tool, in Windows) an ext2fs (or ext3fs, with caveats... I think UFS is also possible, and that would be "nicer" for BSD/MacOS) so I've never had an issue with that, and my user directories (C:\Users or /home) have always been on a volume readable by all OS on my machine, and I've been using multi-boot on my main machine (whatever that is) since the '90s. This is _preferable_ because FAT doesn't support hardlinks (or junctions / reparse points) which proves very useful to map the configuration for Google Chrome / Firefox / HexChat / GIMP / Krita / LibréOffice / VMWare and VirtualBox or whatever, that you have installed natively on both OS to the same home folder for each user on both OS... So it's often in ~/.local/share or ~/.config on Linux / Unix where it's in %UserProfile%\AppData\Local or %UserProfile%\AppData\Roaming on Windows... You can just junction the two locations together, then when you add a bookmark in one OS, it's automatically there in the other, even if you don't "sync" your browser with Google / Mozilla, and chat-logs from a session on Linux / BSD will still be present in Windows etc.
Though, I recently switched to hosting them on a NAS, and Windows will mount it through SMB, while Linux or Unix will mount it through NFS, with WebDav and ftp available as a fallback for anything. (it's on zfs, on a Unix box) Though, I've already noticed that this has _disadvantages_, struggling to login to any OS on my main machine if I have networking issues, which makes _resolving_ those networking issues harder, as I have to use a backup computer / mobile device. However, having the power of zfs keeping my user data safe, and not having to root through old backups when something goes wrong (I can't use Windows snapshots on anything I can access from other OS) has already proven useful several times. 😁️ I also found Windows Explorer displays large directories faster over the SMB network when that share isn't stored on a local NTFS filesystem!!? (like, the "Documents" folder... Mine is at _least_ a messy as yours 😉️) So... Worth the hassle, and I should really just have an emergency local-only user on each OS... But how do I keep it safe, and not forget the password I never use?.. (TBA)
I built my own from dumpster diving hardware, (because it doesn't matter... New RAM and drives, if the rest dies I'll move them into a new trash PC... That's why software RAID rocks!) but if you're less adventurous, a bespoke NAS box is pretty cheap, and I'd highly recommend doing this. You can then mount your home / profile folders on your guest OS (virtual machines) as well, and can access your documents and media and such from your _phone_ over the WiFi as well. It's _really_ great! (or, maybe you _already_ put your trust in a cloud provider?)
Did you delete a reply @DJ Ware, or is UA-cam being very odd? It says I have a reply I can't find. The start of it is correct. I should've been clearer about superblocks. They're not gone, but they don't play the crucial role in booting the system that they used to. Wiindows, and Linux used to keep the "boot sector/block" in there, so they'd modify it if there was a known exploit in the old code, but that's just not the case with UEFI, where multiboot configurations were a design consideration, and the major change between UEFI, and the plain EFI standard Apple had been using before that. They can just update their .efi file, and would be being _very_ naughty if they replaced some other OS' .efi file. Effectively, they tend to keep different EFI boot partitions anyway, and the "active" partition and .efi file is controlled by the NVM (sometimes still, and usually incorrectly, termed CMOS) of the firmware. There is usually an OTB (one-time boot) hotkey in most firmware too. It should pick up any EFI partition, on any volume the firmware can see, find all the .efi files valid for this architecture, and let you select which one your want to boot _this time_. (sadly, what volumes a firmware can identify is a little less "standard" than _the_ standard would like, but still)
Wine does not use qemu!
I have played with Aqemu when I want a gui for qemu. Aqemu is a Qt frontend to qemu that has many of the same features.
github.com/tobimensch/aqemu/
Don't remove Virtualbox yet. Red Hat has deprecated virt-manager, time to find another frontend. Red Hat suggests Cockpit.
uh huh, that's why its still in Fedora 31, you do know that Fedora is where Redhat pulls its code base right? Also cockpit is an admin tool not a virtual machine, 2nd in a server environment you do not have a GUI which is what virt-manager is, and 3rd you would probably be running RedHats commercial engine for KVM/QEMU anyway.
@@CyberGizmo Virt-manager is also an admin tool. Qemu/kvm handle the vitualization. The virt-manager - cockpit switch is since rhel 8. As per Red Hat blog post www.redhat.com/en/blog/managing-virtual-machines-rhel-8-web-console . Fedoramagazine also recommends switching to Cockpit: fedoramagazine.org/create-virtual-machines-with-cockpit-in-fedora/
@@CyberGizmo The above comment made by another user is unfortunately correct as I found out last week.....
I love Virt-Manager, and I don't feel like cockpit is a suitable replacement, but theres nothing stopping someone from forking the git repo of Virt-Manager and continuing to support it for the thousands of people that use it.
I have never personally done any kind of forking, but the idea is tempting. Anything to not just keep the project alive but also to improve it, modernise the UI further.
@@longnamedude3947 I stand corrected then, Its still in the git repo and yep nothing stopping someone from forking it.. But its just a front end to KVM/QEMU so can always do the configuration files manually or use Vagrant to set them up, but will continue to use it. Last build date on github is Jan 2020 so someone is still working on it.
@@CyberGizmo I find it strange that Red Hat have decided to take such a route. But I guess that's there choice, and being open-source we can happily fork it if we need to :)
Virt manager is far better than Oracle Virtualbox
Please stop saying “libe”. /lib rhymes with rib 😂
Thanks for the great explanations.
Shawn, that's how i learned it from Dennis Ritchie one the creators of UNIX and been calling it that for 30 years, so not likely to change.
DJ Ware I learned about black hole radiation from Stephen Hawking, but didn’t keep his pronunciation 😅❤️
lib is short for library. lib != rib
libe would be the correct way to pronounce it if you want to be technical
Heads up: as of now your website is disfunctional - all links are dead.
Thanks Guntberi will check out what's going on with it