New openmediavault-kvm plugin

Zitat von ryecoaaron

Either remove it by editing the xml or use virt-manager.

how can i use virt-manager if omv doesn't have desktop version?

Zitat von ryecoaaron

virt-manager can run on any system running Linux (maybe other ways with Windows but I don't know) and connect to libvirtd running on OMV. I do it every day.

yes thanks, I was able to connect remotely via

virt-manager -c qemu+ssh://user@192.168.1.131/system

Zitat von rudder

how can i use virt-manager if omv doesn't have desktop version?

Hi! plz google this - virt-manager and Xming(virtmanager throught ssh)

Thank you so much for all of the hard work with this plugin! I can't tell you how much I appreciate it.

I followed the guide to create a windows 10 instance. I am using an old rack-mounted server from my former employer and it has 2 network cards. I deleted the interface for the 2nd card as per the instructions and created a bridge with the same IP address.

I continued to follow the directions to and was able to get the VM running. I added a second ISO to populate the drivers and this solved many of my problems. My current issue is that I have the "Unidentified network" when I remote into the VM. I found solutions to many of my other questions in other forums but I thought that I would post this question here as it might be related to the network setup in ovm 5.

I have tried all of the usual windows tricks to get this to work - running the troubleshooting tool, renewing IPconfig, winsock, etc. The problem appears to be somewhere else, I think. Any help would be GREATLY appreciated!

<domain type='kvm' id='8'>
<name>windows10</name>
<uuid>ed3484c2-ba5e-4e5d-a6d4-8ffe1930516c</uuid>
<memory unit='KiB'>4194304</memory>
<currentMemory unit='KiB'>4194304</currentMemory>
<vcpu placement='static'>2</vcpu>
<resource>
<partition>/machine</partition>
</resource>
<os>
<type arch='x86_64' machine='pc-i440fx-5.2'>hvm</type>
<boot dev='hd'/>
<boot dev='cdrom'/>
<boot dev='network'/>
</os>
<features>
<acpi/>
<apic/>
<hyperv>
<relaxed state='on'/>
<vapic state='on'/>
<spinlocks state='on' retries='8191'/>
</hyperv>
</features>
<cpu mode='host-passthrough' check='none'>
<topology sockets='1' cores='2' threads='1'/>
<feature policy='disable' name='smep'/>
</cpu>
<clock offset='localtime'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<devices>
<emulator>/usr/bin/qemu-system-x86_64</emulator>
<disk type='file' device='disk'>
<driver name='qemu' type='qcow2'/>
<source file='/srv/dev-disk-by-label-Windows/kvm/pool/windows10.qcow2'/>
<backingStore/>
<target dev='vda' bus='virtio'/>
<alias name='virtio-disk0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
</disk>
<disk type='file' device='cdrom'>
<driver name='qemu' type='raw'/>
<source file='/srv/dev-disk-by-label-Windows/kvm/ISOS/Windows10.iso'/>
<backingStore/>
<target dev='hda' bus='ide'/>
<readonly/>
<alias name='ide0-0-0'/>
<address type='drive' controller='0' bus='0' target='0' unit='0'/>
</disk>
<disk type='file' device='cdrom'>
<driver name='qemu' type='raw'/>
<source file='/srv/dev-disk-by-label-Windows/kvm/ISOS/virtio-win-0.1.217.iso'/>
<backingStore/>
<target dev='hdb' bus='ide'/>
<readonly/>
<alias name='ide0-0-1'/>
<address type='drive' controller='0' bus='0' target='0' unit='1'/>
</disk>
<disk type='file' device='cdrom'>
<driver name='qemu' type='raw'/>
<source file='/srv/dev-disk-by-label-Windows/kvm/ISOS/virtio-win-0.1.217.iso'/>
<backingStore/>
<target dev='hdc' bus='ide'/>
<readonly/>
<alias name='ide0-1-0'/>
<address type='drive' controller='0' bus='1' target='0' unit='0'/>
</disk>
<disk type='file' device='cdrom'>
<driver name='qemu' type='raw'/>
<source file='/srv/dev-disk-by-label-Windows/kvm/ISOS/Windows10.iso'/>
<backingStore/>
<target dev='hdd' bus='ide'/>
<readonly/>
<alias name='ide0-1-1'/>
<address type='drive' controller='0' bus='1' target='0' unit='1'/>
</disk>
<controller type='usb' index='0' model='piix3-uhci'>
<alias name='usb'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
</controller>
<controller type='pci' index='0' model='pci-root'>
<alias name='pci.0'/>
</controller>
<controller type='virtio-serial' index='0'>
<alias name='virtio-serial0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
</controller>
<controller type='ide' index='0'>
<alias name='ide'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
</controller>
<interface type='bridge'>
<mac address='52:54:00:23:2e:d6'/>
<source bridge='br0'/>
<target dev='vnet0'/>
<model type='virtio'/>
<alias name='net0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
</interface>
<channel type='spicevmc'>
<target type='virtio' state='disconnected'/>
<alias name='channel0'/>
<address type='virtio-serial' controller='0' bus='0' port='1'/>
</channel>
<input type='tablet' bus='virtio'>
<alias name='input0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
</input>
<input type='mouse' bus='ps2'>
<alias name='input1'/>
</input>
<input type='keyboard' bus='ps2'>
<alias name='input2'/>
</input>
<graphics type='vnc' port='5900' autoport='yes' listen='0.0.0.0'>
<listen type='address' address='0.0.0.0'/>
</graphics>
<graphics type='spice' port='5901' autoport='yes' listen='0.0.0.0'>
<listen type='address' address='0.0.0.0'/>
<gl enable='no'/>
</graphics>
<video>
<model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
<alias name='video0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
</video>
<memballoon model='virtio'>
<stats period='10'/>
<alias name='balloon0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
</memballoon>
</devices>
<seclabel type='dynamic' model='dac' relabel='yes'>
<label>+64055:+64055</label>
<imagelabel>+64055:+64055</imagelabel>
</seclabel>
</domain>

Zitat von ryecoaaron

Because it is a Windows VM and you added a virtio network adapter, Windows needs virtio drivers. That is why there is a "Download virtio iso" button on the Pools tab. This has the drivers you need if you attach it to the VM.

Thank you for the response. Yeah, I came to that realization well before this when my pool didn't show up in windows during installation. I googled the error and then came across the virtio iso on another forum. That was enough to get me to where I am now.

That said, the "download" button is greyed out in my pool tab. Is it possible I have the wrong driver? I have a Red Hat network driver.

UPDATE

I deleted the virtio iso that I had found online and downloaded through the UI - it looks like it was the same disk. I deleted and re-added the driver from this iso - same result. I ran the windows troubleshooter - it was not able to fix the issue.

I can't ping the router or the host.

Zitat von ryecoaaron

You have to select a pool to download it to.

That is windows stuff. Not my specialty.

Thank you again for the response. I did update my post as you were responding with more information - I was able to get the pool loaded (it turns out I had the right iso already).

From within the windows vm I can't ping my router or the host. Does that tell us anything? I set up the bridge as per the guide and that bridge is selected as the only network in the kvm settings.

Zitat von muchgooder

Thank you again for the response. I did update my post as you were responding with more information - I was able to get the pool loaded (it turns out I had the right iso already).

From within the windows vm I can't ping my router or the host. Does that tell us anything? I set up the bridge as per the guide and that bridge is selected as the only network in the kvm settings.

I thought I would post something here in case someone else had the same issue. I let this go for a few days and then I decided I would come back here and post something in the general forum. As luck would have it, it is now working for some reason. I don't really know what changed to make it work. I did re-apply the drivers ISO and refreshed the adapters several times in device manager. I also had the windows network set to be dhcp, although I have since made it static and that is working fine.

Can someone point me in the right direction for getting USB to work? I was able to get a windows 10 vm created and running. Earlier in this forum there were mentions of USB working but I haven't yet found a way to add it in the admin console. Thanks!

Zitat von ryecoaaron

What do you mean? What are you trying to do with usb? Did you install the virtio drivers

Ah, I had updated drivers using that disk but I had not run the actual program. I now have the following:

However, I do not have any usb options in "My Computer". I have two thumb drives plugged in to my server but nothing shows in the Windows vm. Last year when I was using OMV4 / Virtualbox this worked fine. What threw me off a bit is that in the virtualbox I could see USB in the admin console so I was expecting to see that in this admin panel.

I figured out the problem. In my original post I had assumed that I needed to add the USB somewhere. I did not realize that there is a spot for the plugin on the main admin page of OMV and the usb needs to be added there and not the cockpit admin console.

i have a feature request for the vm backup schedule. As i'm running several vms, it is difficult to time the backups with hours and minutes. So it would be great to have some sequential approach like: start VM2 script only, if VM1 script has finished, because if the backups are overlapping, the IO is going down because of hardware limits

perhaps it's a lack of understanding on my side....how do you prevent that your many vms not run at the same time?

I've just backed up 100 GB nd it took almost an hour.....

so if i calculate 1 hour for ten vms, i have ten hours, which could be only 3 hours in realtime and the 1 hour approach has 7 hours "slacktime", because other vms need less time.

An other solution would be a access option to some logging files, so i can calculate the whole timing