XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. hoerup
    3. Posts
    H
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 1
    • Posts 14
    • Groups 0

    Posts

    Recent Best Controversial
    • RE: First SMAPIv3 driver is available in preview

      From the blog post

      Size: grow a VDI in size. It's fully thin provisioned!

      Does this mean we finally have live/hot disk expansion ?

      posted in Development
      H
      hoerup
    • RE: XCP-ng 8.3 public alpha 🚀

      What is current status? What is the rough expectation of next alpha/beta release

      posted in News
      H
      hoerup
    • v8.3

      If you should come with a highly insecure guess - when would you estimate that we see the first 8.3 alpha/beta release

      posted in Development
      H
      hoerup
    • RE: FYI - Applying 11/3/2022 and 11/4/2022 Commits in XO from Sources

      When I (re)build on my 3 GB vm i use this before in order to keep nodejs at bay

      export NODE_OPTIONS='--max-old-space-size=3072'
      

      And then it runs smoothly

      posted in Xen Orchestra
      H
      hoerup
    • RE: Mac OS on xcp-ng

      @AlexanderK
      before you spend more time on this i just want to make you aware of the fact that installing OSX on any non-apple hardware will breach Apple's EULA

      posted in Compute
      H
      hoerup
    • RE: XCP-NG vm's extremly slow

      @Andi79
      Is the problem occurring both when the vm's are on HDD and on SSD storage or only on HDD ?

      posted in Compute
      H
      hoerup
    • RE: kernel NULL pointer

      Seems like it's also reported upstream
      https://bugs.xenserver.org/projects/XSO/issues/XSO-1021

      posted in Compute
      H
      hoerup
    • RE: DNS queries during backup job

      Although it is nice that there is work arounds for the DNS spikes with either nscd or the in-process DNS cache, i think the DNS spikes are a symptom of a whole different issue.

      I think we can safely assume that each DNS lookup is corresponding to one attempt at establishing a TCP connection then there is some code somewhere that spawns an awfull lot of short lived connections instead of reusing / pooling them - with all the issues that follows in that area (insufficient ulimit NOFILE, connections in TIME_WAIT/exhausting of client ports etc)

      posted in Xen Orchestra
      H
      hoerup
    • RE: IPv6 support in XCP-ng for the management interface - feedback wanted

      @lematz
      In the first picture of "hostname and dns configuration":
      It doesn't look like you have any double colon '::' in the first 2 entries but you have them in all fields on the last picture

      posted in News
      H
      hoerup
    • RE: is Xo Proxy available in community version

      https://github.com/ronivay/XenOrchestraInstallerUpdater has just added experimental support for provisioning a XO proxy

      posted in Xen Orchestra
      H
      hoerup
    • RE: XO Lite: building an embedded UI in XCP-ng

      @tiner1442 The other responses are technically correct, but a bit un-nuanced
      xcp-ng Center can do vm exports as a sort of backup - but they are entirely manual and only the whole VM

      XOA on the other hand can do scheduled backup and a whole range of various backup methods such as Rolling snapshots, delta backups, continous replication etc

      posted in XO Lite
      H
      hoerup
    • RE: XCP-ng 8.2.0 beta now available!

      @jmccoy555 Could I pursuade you to make a post, describing your setup and summarizing any findings ?

      posted in News
      H
      hoerup
    • RE: XCP-ng 8.2.0 beta now available!

      @stormi whats the opinion on using the new gluster & ceph drivers for a hyper converged solution? Ok / should be ok but not tested / not recommended ??

      posted in News
      H
      hoerup
    • RE: XO Sources - yarn build - javascript heap out of memory

      You do need a lot of virtual memory for build but you can get by with 2GB ram + 4 GB swap if you tell nodejs to limit it self, by setting

       export NODE_OPTIONS='--max-old-space-size=3072'            
      

      before starting the build process

      posted in Xen Orchestra
      H
      hoerup