XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. lefty
    L
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 1
    • Posts 5
    • Groups 0

    lefty

    @lefty

    0
    Reputation
    1
    Profile views
    5
    Posts
    0
    Followers
    0
    Following
    Joined
    Last Online

    lefty Unfollow Follow

    Latest posts made by lefty

    • RE: xo-cli vm.create from bash fails

      Solved: you need to use the template id, not the uuid.

      posted in Xen Orchestra
      L
      lefty
    • xo-cli vm.create from bash fails

      I'm trying to piece together a way to deploy VMs using xo-cli. Ansible seems like a sensible choice, but at the moment I'm just trying the basics from shell. Listing object is working fine, but I can't seem to get creating a VM to work.

      This works:
      npx xo-cli --list-objects type=VM-template uuid=d986ea98-09fa-4e9a-9ee6-e6c78119496f

      But this fails:
      npx xo-cli vm.create name_label="test" name_description="dsc" template=d986ea98-09fa-4e9a-9ee6-e6c78119496f bootaftercreate=false VIFs="json:[{\"network\":\"$NETUUID\"}]"
      with error:
      ✖ no such VM-template d986ea98-09fa-4e9a-9ee6-e6c78119496f JsonRpcError: no such VM-template d986ea98-09fa-4e9a-9ee6-e6c78119496f

      This might be related to me doing stuff in bash, but escaping the dashes or adding quotes around the string does not help.

      Any ideas?

      posted in Xen Orchestra
      L
      lefty
    • RE: xo-cli data limit ??

      I'm just guessing here, but maybe something like this?
      xo-cli --list-objects type=VM power_state=Halted | jq -r ".[].name_label"

      posted in Xen Orchestra
      L
      lefty
    • RE: "CROSSTalk" CPU vulnerabilty (cross-core data leak)

      Thanks for the clarification. No Skylake present, so I will proceed.

      posted in News
      L
      lefty
    • RE: "CROSSTalk" CPU vulnerabilty (cross-core data leak)

      @stormi said in "CROSSTalk" CPU vulnerabilty (cross-core data leak):

      Intel just released updated microcode (actually it's a revert) for some models: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases

      I'll update the microcode_ctl package. The "older" microcode that is used instead is still recent enough to contain the fixes against CROSSTalk / SRBDS. Or so I had understood, but I can't find evidence about it.

      So should I wait applying these updates? You seem to be unsure of which microcode version to distribute.

      posted in News
      L
      lefty