Harvester cluster booted up and ready. Going to try applying the yamll

Do you try this on harvester master or 1.0.3?

It should work on both (kubevirt versions) anyway.

I am using a version of 1.0.3 with my own changes on top

Although I have been running into this nodeaffinity error

(combined from similar events): Error creating pod: Pod "virt-launcher-pcitest2-rt8x4" is invalid: spec.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms: Required value: must have at least one node selector term

There's no PCI device attached yet

In the UI I had it assigned to a specific node, but I keep getting this FailedCreate error

If you don't have a reason to select a specific node, why not let the device plugin do it for you? It looks like a validation error. We haven't come across this.

If on every node the devices of your selector are assigned to

vfio-pci

, you won't have a problem wherever it sits.

Yeah, I was trying to keep it on the one host with gpus, but I can test PCI passthrough on either (the other host in my 2 node cluster has a 10Gb PCI NIC

Thread for Kubevirt hack (to avoid filling up the channel)

I was trying to enable the

vfio-pci

driver through the Harvester configuration, using this:

os:
  modules:
  - vfio-pci

, with no luck. I made it work with:

os:
  write_files:
  - content: |
      vfio-pci
    path: /etc/modules-load.d/vfio-pci.conf

Any thoughts, am I missing sth? Shouldn't the first one work (do the same thing)? I believe that

vfio-pci

should be anyway enabled by default.

Team: I need to build a harvester client in go language which can create VM. Any suggestions pls?

Team: Any idea from where I can download the kubevirt-->VirtualMachine CRD? Thanks in Advance!!

Team: We used to have an API docs in the Harvester Site. I am not finding anymore. Anyone know the new location?

@here: We need to implement the the version management for VM images. Just checking what tool and process you guys are using to store VM images (I.e. git…etc)

You can store VM images in a S3 server that’s local to Harvester cluster. On the Harvester side, internally the VM images are stored in Longhorn.

@Team: Any idea what is the use of the "vip-pools" under "settings" ?

Team: Do we have any production ready harvester-go-client which we can use to create Virtual Machines from my Go Code?

Team: I have a two node cluster. My primary (First) Node went down. However, the secondary node is not picking-up and showing "Not ready" in console. Is this a limitation of harvester? Isn’t a single point of failure? Any suggestion on where to look into logs? Looks like a complete down?

Team, It seems that Harvester doesn’t consider “_*requests.memory*_” param while assigning memory for a VM. It always use the limit memory (minus some overhead) and assign that much of memory to the VM. I am just wondering whether others faced the similar issue. If yes, then any suggestions?

Hello team, I have downloaded the harvesterhci source code. Just wondering whether anyone can direct me to the function which gets called when Harvester UI triggers a create VM call. Thanks in advance.

Team, one of our nodes is keep giving below error. Any advice please? Failed to create pod sandbox: rpc error: code = Unknown desc = failed to get sandbox image "index.docker.io/rancher/pause:3.6": failed to pull image "index.docker.io/rancher/pause:3.6": failed to pull and unpack image "docker.io/rancher/pause:3.6": failed to resolve reference "docker.io/rancher/pause:3.6":

We are using a 3-node cluster for our development. Setup is working fine, however sometime a specific Node is keep getting into “*Cordoned*” state with the message “*Kubelet stopped posting node status*”. I tried a lot but haven't been able to nail down the actual issue with that specific Node. Can someone please help me with some pointers towards the troubleshooting? Do we have any tool I can use for the troubleshooting?

Hi folks, just wondering if I could ask a couple of UI-dev related questions? Having a couple of challenges with Extensions, and trying to follow the harvester extension work. Seems Vue version related. Hoping that some of the harvester dev expertise can help put 2 and 2 together there (there is no channel for extensions yet)

After a few weeks of running Harvester, we started getting Kubelet disk pressure errors. When looking further we noticed that there were >50GBs generated by thousands of tmp directories in the /usr/local/.state/var-lib-rancher.bind/agent/tmp directory. Just checking whether anyone faced the similar issue? Any idea on how to fix this?

@fresh-truck-88697 has left the channel

Hi Harvester！How can I join dev team？

@bland-jackal-11704 has left the channel

@bored-painting-68221 has left the channel

Hey I am trying to create pulumi bridge for the harvester terroform provider: https://github.com/gsuess/pulumi-harvester The compilation is failing with:

/home/cookiecutter/go/pkg/mod/github.com/harvester/terraform-provider-harvester@v0.6.2/internal/provider/virtualmachine/resource_virtualmachine_constructor.go:204:48: cannot use uint(bootOrder) (value of type uint) as type int in argument to vmBuilder.Disk
/home/cookiecutter/go/pkg/mod/github.com/harvester/terraform-provider-harvester@v0.6.2/internal/provider/virtualmachine/resource_virtualmachine_constructor.go:294:15: vmBuilder.Input undefined (type *builder.VMBuilder has no field or method Input)
/home/cookiecutter/go/pkg/mod/github.com/harvester/terraform-provider-harvester@v0.6.2/internal/provider/virtualmachine/schema_virtualmachine_input.go:20:22: undefined: builder.InputTypeTablet
/home/cookiecutter/go/pkg/mod/github.com/harvester/terraform-provider-harvester@v0.6.2/internal/provider/virtualmachine/schema_virtualmachine_input.go:22:13: undefined: builder.InputTypeTablet
/home/cookiecutter/go/pkg/mod/github.com/harvester/terraform-provider-harvester@v0.6.2/internal/provider/virtualmachine/schema_virtualmachine_input.go:28:22: undefined: builder.InputBusUSB
/home/cookiecutter/go/pkg/mod/github.com/harvester/terraform-provider-harvester@v0.6.2/internal/provider/virtualmachine/schema_virtualmachine_input.go:30:13: undefined: builder.InputBusUSB
/home/cookiecutter/go/pkg/mod/github.com/harvester/terraform-provider-harvester@v0.6.2/internal/provider/virtualmachine/schema_virtualmachine_input.go:31:13: undefined: builder.InputBusVirtio

Is this something you recognise?