XCP-ng

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    1. Home
    2. dave.opc
    D
    • Profile
    • Following 0
    • Followers 0
    • Topics 1
    • Posts 9
    • Best 0
    • Controversial 0
    • Groups 0

    dave.opc

    @dave.opc

    8
    Reputation
    5
    Profile views
    9
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    dave.opc Unfollow Follow

    Latest posts made by dave.opc

    • RE: XCP-ng 8.0.0 Release Candidate

      @olivierlambert
      Of course i will try that, but can't install 8.0 on production pc yet. Will wait for 8.0 release.
      I just posted this issue, so maybe you or someone will try to do CR 7.6 -> 8.0RC1 and see if the issue still exists.

      posted in News
      D
      dave.opc
    • RE: XCP-ng 8.0.0 Release Candidate

      @olivierlambert
      from 7.6 to 8
      P.S. just checked. the other way from 8 to 7.6 CR is working fine.
      Also copying VM from 7.6 to 8 is working. - problem with CR 7.6 -> 8

      posted in News
      D
      dave.opc
    • RE: XCP-ng 8.0.0 Release Candidate

      Got another issue with RC1:

      I got 2 xcp ng servers. 1st at home on 8.0rc1 and 2nd remote on 7.6
      When i had at home 7.6 (before upgrade) my continuous replication task in XOA was working fine. Every night copying VM to home server.
      After upgrading to 8.0RC1 XOA starts copying. I can see [importing....] in xcp center, but after transfering the file, xoa ends with error XOA.JPG
      I thought i had a problem with iscsi drive, connected to xcp, but i also tried copying to my main sr (nvme) and got the same error.

      posted in News
      D
      dave.opc
    • RE: XCP-ng 8.0.0 Release Candidate

      kern.log.txt

      Kern log file shows that it booted at that time, at least i don't see any errors. (file attached)
      It looks like it was just reset and started booting, but i doubt there was an electricity outage, as my xcp is powered by ippon back basic 1050.

      posted in News
      D
      dave.opc
    • RE: XCP-ng 8.0.0 Release Candidate

      @r1
      I thought it's obvious if i am asking in 8.0RC1 thread, that i have this verison.

      posted in News
      D
      dave.opc
    • RE: XCP-ng 8.0.0 Release Candidate

      Today i found out, that my xcp was restarted at 3.51AM. There is no crash dump in xcp center. Where do i look to find out what happened?

      posted in News
      D
      dave.opc
    • RE: XCP-ng 8.0.0 Release Candidate

      Is there any possibility to make installer nonGUI?
      On my Ryzen 2400G can't load, it boots up, and after choosing installer the screen is just blank. Tried the same image on VM it starts the installer, but with some graphics.

      Addon: ok, i changed 8192M to 2048M in grub.cfg and was able to install the system. Everything is working fine. Now, i got a question: i did yum update and system told me that there is a new kernel with newer xcp-ng:

      kernel x86_64 4.19.19-5.0.9.xcpng8.0 xcp-ng-base 30 M
      xcp-ng-release x86_64 8.0.0-12 xcp-ng-base 15 k
      xcp-ng-release-config x86_64 8.0.0-12 xcp-ng-base 350 k
      xenserver-firstboot noarch 1.0.11-1.1.xcpng8.0 xcp-ng-base 20 k

      After installing and rebooting, it still shows that kernel is 4.19.0 - any idea how to fix? (not sure if xcp-ng itself updated to 8.0.0-12, in xsconsole it shows as 8.0.0)

      posted in News
      D
      dave.opc
    • RE: Strange autostart VMs

      Got that, thanks.

      What about the Debian server VM which didn't start? It's enabled in XOA.

      posted in Development
      D
      dave.opc
    • Strange autostart VMs

      Hi.

      Currently running xcp-ng 7.6
      I have also xoa running as one of the vm's
      Today i restarted the xcp-ng server, and here is how VM's started:

      1. XOA VM. autostart=on. Start order=2 (in xcp-ng center). Started 1st
      2. FreeNAS VM. autostart=on. Start order=1. Started 2nd
      3. PfSense VM. autostart=on. Start order=0. Started 3rd
      4. Debian Server VM. autostart=on. Start order=2. Didn't start at all.

      As i understand from description, VM's with starting order = 0 should start with priority. In my case it went wrong. And one of the VMs didn't start at all...

      posted in Development
      D
      dave.opc