New openmediavault-kvm plugin

Thanks for your patience ...

Extending the sources.list had no effect for me (propably you missed my post #999).

Anyway in the meanwhile I did a new clean install - taking care that the Internet/Ethernet connection is running and I end up in the situation that the Guest OS don`t get its own IPAddress.

What I did

- Fresh Install OMV6

- apt-get update + apt-get upgrade + apt-get dist-upgrade

- installing OMV-EXTRAS

- apt-get update + apt-get upgrade + apt-get dist-upgrade

- Changing Sytem Network Adapter to Bridge br0

- Creating ISO and Pool folder for KVM

- Creating KVM VM (OS: Debian10, Network bound to Bridge br0)

- Starting VM successfully (can access via VNC), but no valid IP (because no Ethernet Adapter?) in the guest OS, see snapshots below:

OMV Version:

uname -a
Linux homenas1 6.0.0-0.deb11.2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.0.3-1~bpo11+1 (2022-10-29) x86_64 GNU/Linux

Is the Version now correct?

VM Settings:

GuestOs Network Status (only Local Loopback)

I didn't configured any KVM Network (default is inactive) in addition to bind the VM to br0. Is that correct?

Zitat von ryecoaaron

... Maybe I might see something if you post the VM's xml ...

Should be this here:

<domain type='kvm'>
  <name>MLDServer55</name>
  <uuid>0d46610e-1fc5-46e9-b200-7170a7f7ed40</uuid>
  <metadata>
    <libosinfo:libosinfo xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0">
      <libosinfo:os id="http://debian.org/debian/10"/>
    </libosinfo:libosinfo>
  </metadata>
  <memory unit='KiB'>2097152</memory>
  <currentMemory unit='KiB'>2097152</currentMemory>
  <vcpu placement='static'>2</vcpu>
  <os>
    <type arch='x86_64' machine='pc-q35-7.1'>hvm</type>
    <boot dev='hd'/>
    <boot dev='cdrom'/>
  </os>
  <features>
    <acpi/>
    <apic/>
    <vmport state='off'/>
  </features>
  <cpu mode='host-passthrough' check='none' migratable='on'>
    <topology sockets='1' dies='1' cores='2' threads='1'/>
  </cpu>
  <clock offset='utc'>
    <timer name='rtc' tickpolicy='catchup'/>
    <timer name='pit' tickpolicy='delay'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>destroy</on_crash>
  <pm>
    <suspend-to-mem enabled='no'/>
    <suspend-to-disk enabled='no'/>
  </pm>
  <devices>
    <emulator>/usr/bin/qemu-system-x86_64</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2' cache='none' io='native'/>
      <source file='/srv/dev-disk-by-uuid-a3d5448f-44e6-4c76-9145-101ba4dade08/pool/MLDServer55.qcow2'/>
      <target dev='vda' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/srv/dev-disk-by-uuid-a3d5448f-44e6-4c76-9145-101ba4dade08/isos/MLD-5.5_netinstall_2022.11.12-183+1465_amd64.iso'/>
      <target dev='sda' bus='sata'/>
      <readonly/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <controller type='usb' index='0' model='qemu-xhci' ports='15'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
    </controller>
    <controller type='sata' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pcie-root'/>
    <controller type='pci' index='1' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='1' port='0x10'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/>
    </controller>
    <controller type='pci' index='2' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='2' port='0x11'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/>
    </controller>
    <controller type='pci' index='3' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='3' port='0x12'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/>
    </controller>
    <controller type='pci' index='4' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='4' port='0x13'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/>
    </controller>
    <controller type='pci' index='5' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='5' port='0x14'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/>
    </controller>
    <controller type='pci' index='6' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='6' port='0x15'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/>
    </controller>
    <controller type='pci' index='7' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='7' port='0x16'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x6'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:e9:f3:00'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <target type='virtio' name='org.qemu.guest_agent.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <channel type='spicevmc'>
      <target type='virtio' name='com.redhat.spice.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='2'/>
    </channel>
    <input type='tablet' bus='usb'>
      <address type='usb' bus='0' port='1'/>
    </input>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <graphics type='vnc' port='-1' autoport='yes' listen='0.0.0.0'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>
    <graphics type='spice' autoport='yes' listen='0.0.0.0'>
      <listen type='address' address='0.0.0.0'/>
      <image compression='off'/>
    </graphics>
    <sound model='ich9'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/>
    </sound>
    <audio id='1' type='spice'/>
    <video>
      <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </video>
    <redirdev bus='usb' type='spicevmc'>
      <address type='usb' bus='0' port='2'/>
    </redirdev>
    <redirdev bus='usb' type='spicevmc'>
      <address type='usb' bus='0' port='3'/>
    </redirdev>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
    </memballoon>
    <rng model='virtio'>
      <backend model='random'>/dev/urandom</backend>
      <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/>
    </rng>
  </devices>
</domain>

The e1000 had the result that the Guest is getting an IPAddress from the Guest-Network Subrange, what is not exactly what I wanted ...

Zitat von ryecoaaron

you will have to ask the minidvb people what is supported

Seems true, that this is a kvm supporting problem.

I Finally solved the issue for me (without really understanding the problem):

The minidvb distribution has the service to create an pre-configured ISO for specific purposes (here setting up MLD as Server). If I use one of that self-customized ISOs with aloready included kvm-virtio package, the Network-Bridge works perfectly ==> I get the IP via DHCP as intended.

Originally I used the Network installation ISO, which doesn't seem to have that kvm-virtio package activated.

ryecoaaron, again many thxs for your support and patience.

Hi,

maybe someone here can help me with this?

Thema

Boot OMV4 on a physical disk in a kvm guest

Hi,

was away for a long time and didn’t have the time for omv. I am still using omv4.

I am in a stuck situation because of my home automation software (FHEM). I installed a lot of custom FHEM modules via apt/curl/npm/git.

Now I want to get out of this situation and am thinking about how to proceed.

OMV now has a KVM module. Great! With this I can go the route without Proxmox now.

I will not be able to do the migration in one step, so I have the following idea:

1. Install omv6 to a new SSD
2. Install

…

hoppel118

20. Dezember 2022

Thanks Hoppel

Hey,

Can someone walk me through how i install home assistant on a VM please? first time doing this and I'm not sure what I'm doing at all.

I tried this https://www.home-assistant.io/installation/linux

but i kept getting this

Failed to create VM.
error: Failed to define domain from /tmp/CaretakerHA.xml
error: unsupported configuration: 'directory' storage format is not directly supported by QEMU, use 'dir' disk type instead
virsh define --file /tmp/CaretakerHA.xml

OMV\Exception: Failed to create VM.
error: Failed to define domain from /tmp/CaretakerHA.xml
error: unsupported configuration: 'directory' storage format is not directly supported by QEMU, use 'dir' disk type instead
virsh define --file /tmp/CaretakerHA.xml in /usr/share/openmediavault/engined/rpc/kvm.inc:2851
Stack trace:
#0 /usr/share/openmediavault/engined/rpc/kvm.inc(1223): OMVRpcServiceKvm->virshCommand(Array, 'Failed to creat...')
#1 [internal function]: OMVRpcServiceKvm->setVm(Array, Array)
#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('setVm', Array, Array)
#4 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Kvm', 'setVm', Array, Array, 1)
#5 {main}

Hi STUKguy

I did this yesterday. I decided to setup Home Assistant Operating System in KVM.

Here is a good general KVM HowTo: [How-To] Use the Openmediavault-KVM plugin

• install openmediavault-kvm
• create two folders (pool and isos) -> chapter 3.1
• configure pool and isos as storage group -> chapter 3.2
• network configuration -> chapter 3.3 (If you want to do it right, you want a bridge interface in OMV)

Zitat

If we want a network interface that has an IP in our LAN and at the same time can access the shared resources of the host, we must create a bridge interface in OMV (in the Network>Interfaces section) as follows. Warning: This method will remove the current network interface configuration and replace it with a jumper. If you have services configured on the host with this network interface (for example, Wireguard), you will need to reconfigure them to work with the bridge:

• Go to Network>Interfaces> Make a note of the network interface name that appears under the Device column. Select this interface and click delete, BUT do not apply changes yet.
• Without applying the changes of the previous point, click on + Create then on Bridge. In the Interfaces field, find the name of our newly removed interface and select it. Enter the necessary data for the Ipv4 protocol with static IP, for this in Method select Static. Fill in the fields:
  • IP: Your OMV IP
  • Netmask: 255.255.255.0
  • Gateway: IP of your DHCP server (your router)
  • DNS: For example 1.1.1.1
• Press Save and now you can apply the changes. Now your OMV network interface will have a name similar to br0. This is the bridge-type interface that you should select on your VM.
• Add the newly created network interface (br0) to your VM. You should not create an interface in KVM, macvtap or any other.
  • If you already have a VM created:
    • stop it, remove the current interface assigned and simply select your VM and click on Network and then Add Network. In Model change virtio to bridge. In Bridge look for the network interface created in OMV, it will be br0 (or similar). Press Add.
  • If you are creating a new VM:
    • In the VM creation window, go to the Network section and change virtio to bridge. In the next field select your network interface br0.

  
  

• download the .qcow2 file from here: https://www.home-assistant.io/installation/linux and copy it to your pool folder
• configure your VM the following way:

• configure the access to the vm -> chapter 3.5

This is how it works for me.

ryecoaaron According to the HA documentation, we should select "Generic Default" for the operating system. However, this does not exist in the list. I decided to try Debian 10 and it worked. Do you think there is anything wrong with this? Is it possible to add "Generic Default" to the list? Debian 11 is also missing.

I´m lost.

I created a bridge interface in OMV settings (br0). I then created a VM running Windows 10. Network config for this is bridge and the interface is br0. After setting up Windows 10 (100x times) there is no network interface available.

This is the bridge in OMV network config:

This is the current network setup in KVM:

And here is the network adapter for the Win10 machine:

But Windows is like:

This is the relevant part of the xml file:

<interface type='bridge'>

<mac address='52:54:00:4c:75:53'/>

<source bridge='br0'/>

<model type='virtio'/>

<address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>

What am I missing?

Zitat von hoppel118

Hi STUKguy

I did this yesterday. I decided to setup Home Assistant Operating System in KVM.

Here is a good general KVM HowTo: [How-To] Use the Openmediavault-KVM plugin

• install openmediavault-kvm
• create two folders (pool and isos) -> chapter 3.1
• configure pool and isos as storage group -> chapter 3.2
• network configuration -> chapter 3.3 (If you want to do it right, you want a bridge interface in OMV)

• download the .qcow2 file from here: https://www.home-assistant.io/installation/linux and copy it to your pool folder
• configure your VM the following way:

• configure the access to the vm -> chapter 3.5

This is how it works for me.

ryecoaaron According to the HA documentation, we should select "Generic Default" for the operating system. However, this does not exist in the list. I decided to try Debian 10 and it worked. Do you think there is anything wrong with this? Is it possible to add "Generic Default" to the list? Debian 11 is also missing.

Alles anzeigen

Hey hoppel118 ,

i still get the same error

Failed to create VM.
error: Failed to define domain from /tmp/haos.xml
error: unsupported configuration: 'directory' storage format is not directly supported by QEMU, use 'dir' disk type instead
virsh define --file /tmp/haos.xml

OMV\Exception: Failed to create VM.
error: Failed to define domain from /tmp/haos.xml
error: unsupported configuration: 'directory' storage format is not directly supported by QEMU, use 'dir' disk type instead
virsh define --file /tmp/haos.xml in /usr/share/openmediavault/engined/rpc/kvm.inc:2851
Stack trace:
#0 /usr/share/openmediavault/engined/rpc/kvm.inc(1223): OMVRpcServiceKvm->virshCommand(Array, 'Failed to creat...')
#1 [internal function]: OMVRpcServiceKvm->setVm(Array, Array)
#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('setVm', Array, Array)
#4 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Kvm', 'setVm', Array, Array, 1)
#5 {main}

I am assuming i download the zip for .qcow2 and extract to the the folder on the OMV server

Zitat von STUKguy

I am assuming i download the zip for .qcow2 and extract to the the folder on the OMV server

Yes, you have to unzip the file to use it. At least this is what I did.

Who is the owner of the qcow2 file?

ls -l /data/vm/haos_ova-9.4.qcow2
-rw-r--r-- 1 libvirt-qemu libvirt-qemu 7561936896 24. Dez 00:28 /data/vm/haos_ova-9.4.qcow2

Is it libvirt-qemu?

Can you describe (maybe with screenshots) how you created your pools? On which filesystem is your pool? Which architecture is your server?

Zitat von hoppel118

Yes, you have to unzip the file to use it. At least this is what I did.

Who is the owner of the qcow2 file?

Code

ls -l /data/vm/haos_ova-9.4.qcow2
-rw-r--r-- 1 libvirt-qemu libvirt-qemu 7561936896 24. Dez 00:28 /data/vm/haos_ova-9.4.qcow2

Is it libvirt-qemu?

Can you describe (maybe with screenshots) how you created your pools? On which filesystem is your pool? Which architecture is your server?

Alles anzeigen

Hey hoppel118

This is how i created the pool folders

First went Storage>Shared Folders then clicked on the plus

Then setup like this

Then clicked on the tick (apply) on the "Pending configuration changes"

Then shared the isos folder in SMB (so i can move the qcow2 file over)

Then in Services > KVM > pools

How do i find the owner of qcow2? and how do i change this?

Sorry just re-read the last bit my OMV is built on a HP Elite 800 G1 so i think that is a x86 cpu

Hi hoppel118 ,

Its the machine it self that is causing the problem, i just installed HAOS on the machine i wanted to get rid of and installed fine.

Now i got to figured out what i haven't checked in the bios of the machine i need a VM of HAOS on (HP 800 G1)

Zitat von STUKguy

Now i got to figured out what i haven't checked in the bios of the machine i need a VM of HAOS on (HP 800 G1)

Ok, good luck.

Zitat von STUKguy

i just installed HAOS on the machine i wanted to get rid of and installed fine.

Bare metal or in a vm?

Good night! 😉

Zitat von hoppel118

Bare metal or in a vm?

VM my friend,

Good night to you too

Zitat von ryecoaaron

It makes very little difference which one you pick

Ok, this what I wanted to „hear“.

Zitat von ryecoaaron

but while Generic Default doesn't exist, Generic Linux 2016, Generic Linux 2018, Generic Linux 2020 do exist.

I don’t see this „Generic Linux 20xx“ options:

Zitat von ryecoaaron

This list is populated by the osinfo-query command which gets its data from the osinfo-db package. If you want to update it, use the package from bookworm (I use the updated package on all of my servers):

Thanks for this hint. But I am unsure, if I really want to install packages manually after my omv4 situation… 😉