Set fixed values like the emulator in virt-handler instead of virt-controller about kubevirt

[rmohr]

Additional fields which do not really make sense to expose:

os:
  type:
    os: hvm
type: qemu

We only support qemu and full virtualization (at the moment).

[rmohr]

As @mpolednik suggested some time ago, we can probably also move the spec.domain subsection up to spec and merge it with the fields there.

[fabiand]

Mh - I do like that we keep the domain part separate form the complete VM spec.
It might become valuable if we start thinking about HA. i.e.

spec:
   ha-stand-by-instances-foo: 2
   domain:
      ...

thus - I can currently imagine that we get to a state where we need to keep non-domain specific, but cluster wide infos and then it makes sense to have the domain specification in a subsection.

@mpolednik ?

[fabiand]

Note on the original comment: In oVirt we know that some users want to set the specific emulator - there it's solved by using a hook.