@scottalanmiller said in P2V Windows 2000 on KVM: So this is ridiculous, but we just found out that it is actually 2003 R2, not 2000. So I assume that this will be way better. I had a ton of issues getting mine to work - I had to run chkdsk like 15 times before it finally booted... I don't recall what migration tool I used.

In the interests of "closure", the plethora of libvirt updates which came down the line yesterday from fedora seem to have fixed the problem. I can now create virtual networks again. Yay!

@JaredBusch said in Converting Hyper-V to KVM: pages on daerma.com load slow. No idea why, it is a basic WP site. Removed an old IP from the router, and it all works faster. That makes no sense. But it was something that needed cleaned up.

For Fedora you can just do sudo dnf install vagrant-libvirt

@fuznutz04 said in KVM networking & teaming: @DustinB3403 said in KVM networking & teaming: @fuznutz04 no he's saying you can only assign it in VM or via CLI. You still create your team. I think he is actually saying, you can create the NIC team in Cockpit. (You can, I did it already), but you then just assign that team, via the VM Guest settings. ...I think. For what's it's worth, that is what I said.

1 .So can ovirt be run with only 2 nodes? 2. With those 2 nodes, do you need a separate shared storage device for live migrations, etc, or can you have local storage (Like "vsan")?

@kamidon said in Run virt-manager on Windows 10: Why Virt-manager over Hyper-V? For Windows 10 Home users? It’s about managing KVM hosts.

@Francesco-Provino said in virt-manager for Windows: @scottalanmiller you don’t want a GUI on the virtualization host, ever. Just spin a VM with virt-manager and launch it on your local machine with xming or one of the other solutions in the other comments. Right, bypassing Windows can be an option, but it's a crappy one. But I got it working directly on Windows, so no need for a heavy VM for one app.

it relies on DNS (or hosts files) to resolve itself and generate SSL certs, this has to work before you install the engine. If it did work, and you still get this error, this is a bug

@dyasny said in KVM/QEMU DNS: libvirt has dnsmasq built in, to serve DHCP. It can also be configured to serve DNS to the libvirt NAT network, and the host. This is an example of a working configuration: https://fabianlee.org/2018/10/22/kvm-using-dnsmasq-for-libvirt-dns-resolution/ Pretty cool. Thanks.

@FATeknollogee said in KVM host: refusing connection on ports 22 & 9090: Still looking for a fix!! Can you ping out from it? Is the gateway missing or wrong? Subnet missing or wrong?

Yeah, sorry misread you where looking for how to do it from windows that why I added the exe

@dyasny said in Virt-manager: IDE disks: @scottalanmiller said in Virt-manager: IDE disks: They need to just get off of my lawn. LOL, funny how I'd never have understood the joke before moving to NA and buying a house HAHAHA

@dyasny said in Virt-Manager on multiple pc's: if you have an ovirt-engine somewhere central, that can reach to all the other locations, you can create a datacentre per location and place standalone hosts in there, using local storage. Never thought about that. That's a great idea.

@stacksofplates said in Kvm network troubleshooting: @scottalanmiller said in Kvm network troubleshooting: Your server has an IP address of 192.168.122.1? Is that correct? Nothing wrong with that technically, but it would be exceptionally unusual. That's almost always the gateway address. What is the address of your gateway? That's libvirts virtual bridge address for the NAT network. Oh, duh, I missed the bridge. Carry on.

@atahaynah said in Cockpit: @DustinB3403 it was stopped But fortunately i got it resolved i had to downgrade one packege and after that restarted the service and it worked What did you downgrade to fix the issue?

@scottalanmiller RHV now, after a rebrand in 2016-ish

@DustinB3403 said in How to Install Desktop Environment to a Fedora Server: @Pete-S I was the person to mention creating a desktop environment on the system to use as the management domain, and run virt-manager there. And I've repeated it numerous times, across several topics. As for using virsh, that is an option too. Sorry, I didn't follow the other previous thread(s).

@Dashrender think of this as XOCE to XenServer/XCP-ng but with a desktop instead of a web interface. Literally nothing different and is completely normal.

So following on from the Other thread. Looks like i'm heading to the Install KVM, setup a Linux VM and use that to manage the KVM server from that.

@FATeknollogee the install itself has been covered too many times to mention Maybe if he runs into a specific issue and solves it, that would be a good thing to share

I have it restored and going again with a nice starting area (big castle and useful things). realmc.minecraftr.us (that's my free afraid.org domain name for it specifically) Or if you prefer, tgserv.timothygruber.com. Oh, it's version 1.12.2. I didn't update it yet because there's a couple plugins I run that haven't updated yet.

@StorageNinja said in Why I Feel KVM Is the Easiest HyperVisor to Learn the Basics On: @Dashrender said in Why I Feel KVM Is the Easiest HyperVisor to Learn the Basics On: The question is - why is the quality so bad? Isn't the process supposed to catch bad quality? Their process is consider the windows insider group (extreme power users) to be a good enough replacement for proper QE teams, and writing automated build tests. Right, the new process isn't to catch bad things, it's actually to see bad things as "not all that bad." Presumably because a shift from viewing their products as being for business to being for entertainment. Remember when Windows 95 was a key tool for businesses, but by Windows 98 they had made sure to put a "for entertainment purposes only" label on the product to make sure no one confused it with something that was intended for business use? I feel like that's where they are now. At least internally, no one is really thinking of this as a business tool.

@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.

@scottalanmiller said in KVM with Cockpit on Fedora 29 Network Type Options Greyed Out: When building a new VM using Cockpit's web interface to KVM on Fedora 29, the Network Type option leaves most options like Bridge to LAN, Generic ethernet connections, and Direct attachment greyed out. Anyone know why? Did you try with network manager? Any missing package?

@obsolesce said in Fedora 28 KVM Cockpit Doesn't Show All VMs: Everyone is always waiting for someone else to report bugs and issues, that's why they take so long to get fixed. Not as bad with FOSS, but a big reason with MS for example. But I don't know that it is a bug. It's reasonable that it might be, but it's just one possibility.

@scottalanmiller said in Delete All Snapshots on KVM with Virsh: Is this a personal alias to Remove-VMSnapshot perhaps? No I had that first but edited it incorrectly. Missed the VM in front. But ya I thought vmcheckpoint was an alias but it's not. Remove-VMSnapshot is correct. So weird, they renamed it to checkpoint, but never changed the PS commands.

@stacksofplates I can imagine. Good luck!

PS. I had a look on the guest side of thing just now because that is what Microsoft talked about. Most OSs are virtualization aware. I had a look at debian running as guest under Xen with a clean install without any Xen guest tools. Debian installation automatically sense it's running on virtualized hardware and sets it's I/O scheduler to "none", thereby letting the host handle whatever I/O scheduling needed. This also makes sense because the guest doesn't know what kind of storage the host is using.