https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# harvester
a
This message was deleted.
f
s
@full-plastic-79795 Thank you, for your reply. Would you say, the host is not able to deploy any vms, since Harvester thinks KVM is not enabled? I can't deploy any VMs: "1. 0/1 nodes are available: 1 Insufficient memory. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod."
b
if you're on AMD, you need to wait for 1.2.0
s
Yeah, AMD...
Any plany when 1.2.0 will be released?
b
for testing, you can try 1.2.0-rc2, but the releases page says
We don't support upgrading from this version to a later version either.
s
Sure, didnt upgrade Harvester before. 😄
Installed it last night for the first time.
b
the issue list for the label 
required-for-rc/v1.2.0
makes me think we're likely still at least a couple of months out from a final 1.2.0 release, but that's just a blind guess from a random user. 😁 https://github.com/harvester/harvester/issues?page=2&q=is%3Aissue+is%3Aopen+label%3Arequired-for-rc%2Fv1.2.0
s
Hmm, having this bug in a production release for months, not having any release to fix, does not speak for Harvester.
b
i get the impression that the bug was there for quite some time before anyone noticed though. there just aren't that many AMD users (at least on servers) apparently. 😞
s
I've had Harvester running on AMD for years - but not AMD servers, just on NUC-alike machines
s
I tried it on an AMD Ryzen 5700G.
s
Mine are AMD Ryzen 4700U (which work fine running Harvester)
b
We run a bunch of Epyc hosts in our cluster without issue (though the message is present)
s
Unfortunately our cluster is not able to start any vm.
168 Views
Open in Slack
PreviousNext
Powered by