Hi currently running xcp-ng 8.2 and within my small form factor I have 4 VMs. One of the VMs is currently virtualized pfsense. When xcp-ng boots I'd actually like the pfsense VM to start first. Is it possible to assign in XO or through the xcp-ng CLI itself the proposed boot order of the various VMs?

Hey thanks for working on XCP-ng Center -- I find it a really useful tool.

Is this a README that describes how your project differs from XenCenter.

Hey do you have actual instructions on how to compile from source? I trying to work with someone creating an arch linux AUR package and was looking for a little more input.

FWIW -- I had a similar problem with VMs going randomly down -- it wasn't windows but various BSD and Linux VM's. Sometimes they would run a few days, other times they would lock up every other day. Logs didn't help because when the VM locked, logs were not written. I even had the xcp-ng installation lock a few times, although it was usually on of the VMs. I started searching for faulty hardware and eventually SMART tested all the drives and mem86 the RAM. Turns out I had some bad RAM modules which I later RMA'd. With new RAM (after after thoroughly testing it), I haven't had any lock ups. I'm not sure this will help you at all.

@julien-f Thanks for explanation. Thank you

@olivierlambert

Well damn -- you're right.

Well VM now up and running. Just have to figure out how networking works in this new copied VM. Thanks for help.

Not that you actually needed this reply, but confirmed patch works after upgrade this morning.

Thanks for update and the patch.

@nikade Hey thanks for for the link. I ended up just using a LetsEncrypt cert rather than self signed. I think had to add a DNS host override on my router to associate the Local LAN address of the xo server with the domain name of the server contained in the certificate -- Like 10.0.1.50 ---> xo.example.com. Thanks for pointing me in the right direction on this one.

So I managed to build with Cargo on arch (which also required clang as a dependency). Moved xen-guest-agent/target/debug/xen-guest-agent to /usr/sbin and also copied the basic xen-guest-agent/startup/xen-guest-agent.service file to /etc/systemd/system and enable/started the service.

And ahh -- success --

I guess my project for week is to figure out how to write a PKGBUILD file for this particular project. We'll see how that goes

I'm assuming since building from git repository (https://gitlab.com/xen-project/xen-guest-agent) there aren't going to be any file signatures to check against. I'm looking at cargo, clang, python-setuptools and xen as dependencies?

When using this toolset, what network interface names does this match against? For example it will match against interface names starting with eth and I think enpS. I looked in the source code within the main branch but couldn't find the file where this search occurs.

@gskger Why don't you install acme.sh or something similar on XO host and deploy from there. No need to use pfSense.

@yann Yes I tried compiling with cargo. Got along some of the way until I reached this:

  Failed to locate xenstore library:
  pkg-config exited with status code 1
  > PKG_CONFIG_ALLOW_SYSTEM_LIBS=1 PKG_CONFIG_ALLOW_SYSTEM_CFLAGS=1 pkg-config --libs --cflags xenstore

  The system library `xenstore` required by crate `xenstore-sys` was not found.
  The file `xenstore.pc` needs to be installed and the PKG_CONFIG_PATH environment variable must contain its parent directory.
  The PKG_CONFIG_PATH environment variable is not set.

  HINT: if you have installed the library, try setting PKG_CONFIG_PATH to the directory containing `xenstore.pc`.

Where do I get the xenstore library? I've searched the AUR and pacman official archives and I can't seem to find.

Hey do you have actual instructions on how to compile from source? I trying to work with someone creating an arch linux AUR package and was looking for a little more input.

@olivierlambert Hey thanks a lot for that tip.

@Andrew Your link doesn't really address the question. xoa would be the username and the password is the same as what was setup during xoa creation -- or as your link helpfully pointed out -- you could reset the xoa system user password and go from there.

I need to become the root user in xoa. What is the root password? I've tried root/root but it doesn't work and it isn't in the documentation. I need to change the network interface for xoa.

@Danp Aww. see that box. Let me look into this problem a bit more. Learning some new things here.

@DustinB Didn't know about the health check drivers to be honest. My VM not working is a pfSense VM. I looked at the link posted and didn't see BSD drivers. Looking my XO installation for pfSense I dont even see anything in the GUI regarding healthchecks. Weird. Not sure how this option was even turned on in the first place.

Been using XO with delta backups for a while however one of my VMs is now receiving an error and I'm not sure how to rectify. I'll post what I have below. Looks like there might be two errors -- VHD check error and WaitObjectState Error. Not sure how to actually fix any of these errors.

Thanks for help.

     Clean VM directory
    VHD check error
        path
        "/xo-vm-backups/a8a20272-aaef-0bc9-82c8-d5ba96d1e725/vdis/fed92d10-c8a0-4587-a018-8a6b6c050453/60e7144d-ea34-4cf7-b798-c0bfd17134c2/.20240204T075759Z.vhd"
        error
        {"generatedMessage":false,"code":"ERR_ASSERTION","actual":false,"expected":true,"operator":"=="}
    Start: Mar 4, 2024, 01:00:02 AM
    End: Mar 4, 2024, 01:00:02 AM
    Snapshot
    Start: Mar 4, 2024, 01:00:02 AM
    End: Mar 4, 2024, 01:00:04 AM
    Backups for XO
        transfer
        Start: Mar 4, 2024, 01:00:06 AM
        End: Mar 4, 2024, 01:18:53 AM
        Duration: 19 minutes
        Size: 4.34 GiB
        Speed: 3.94 MiB/s
        health check
            transfer
            Start: Mar 4, 2024, 01:19:00 AM
            End: Mar 4, 2024, 05:34:33 AM
            Duration: 4 hours
            Size: 9.3 GiB
            Speed: 635.79 KiB/s
            vmstart
            Start: Mar 4, 2024, 05:34:33 AM
            End: Mar 4, 2024, 05:44:33 AM
            Error: waitObjectState: timeout reached before OpaqueRef:214f572e-ed48-4f80-a9c7-6f984129a2f7 in expected state
        Start: Mar 4, 2024, 01:19:00 AM
        End: Mar 4, 2024, 05:44:37 AM
        Error: waitObjectState: timeout reached before OpaqueRef:214f572e-ed48-4f80-a9c7-6f984129a2f7 in expected state
    Start: Mar 4, 2024, 01:00:04 AM
    End: Mar 4, 2024, 05:44:37 AM
    Duration: 5 hours
    Error: waitObjectState: timeout reached before OpaqueRef:214f572e-ed48-4f80-a9c7-6f984129a2f7 in expected state

Start: Mar 4, 2024, 01:00:02 AM
End: Mar 4, 2024, 05:44:37 AM
Duration: 5 hours
Error: waitObjectState: timeout reached before OpaqueRef:214f572e-ed48-4f80-a9c7-6f984129a2f7 in expected state
Type: delta
code_text