1. Home
  2. Popular
Log in to post
  • J

    V2V migrated VMs don't autostart

    Unsolved Migrate to XCP-ng
    4
    1 Votes
    4 Posts
    94 Views
    J
    Further testing: Testing with newer commit: 27882fb1dcd24fc5257835e60b3fa1002e4e885c Still same results. I've tried with both original VM powered on, and off. No change in end-result. The VM imports properly. But it doesn't power on automatically as expected after the import has completed. Manual powering on is then needed to be performed. I'm only importing 1 VM at a time. And I've tried with the field Number of VMs to import in parallel both at the default value of 2 and reduced to 1. No change in behaviour from this either.
  • stormiS

    XCP-ng 8.3 updates announcements and testing

    Pinned News
    682
    1 Votes
    682 Posts
    685k Views
    TeddyAstieT
    @leroyj We already know that our k10temp module doesn't have support beyond Zen 2, and needs to be updated. That's not incredibly complex, but still needs to be done. I was wondering if the amd cpu temp be probed the way you did for the intel cpu. No, AMD temperature infos are not exposed through MSR but through PCIe/MMIO (through various subsystems, like "SMU" and other ones). Like what does https://github.com/torvalds/linux/blob/master/drivers/hwmon/k10temp.c or https://github.com/ocerman/zenpower. (regarding the AI draft, there is no documented MSR 0xc0010292 in neither APM nor public Zen3 PPM) That doesn't require any specific Xen support aside the right Linux drivers in Dom0.