@olivierlambert Will do... that VM is running a massive rsync job at the moment, but once it's finished I'll be able to shut it down.

@olivierlambert Ah I was clicking in slightly the wrong area. You have to be pixel perfect I think. Thanks

@olivierlambert When I go into advanced, those fields are not editable? How do I change the values?

Thanks

@olivierlambert Ah I see. Yes, I am familiar with memory ballooning from my VMWare days.

The VM is only a dual core with 4G RAM assigned, as it hosts only some reverse proxy containers (though they are essential). In the advanced tab, it shows the memory limits as:

Static: 2 GiB/7.59Gib
Dynamc: 4 GiB/4 Gib

@olivierlambert Thank you for the reply.

The VM is up to date. I wasn't aware of the xl dmesg command. I'm seeing:

(XEN) [ 5538.751053] p2m_pod_demand_populate: Dom6 out of PoD memory! (tot=1049114 ents=940768 dom6)                                                                                     
(XEN) [ 5538.751056] domain_crash called from p2m_pod_demand_populate+0x4d2/0x8b0         
(XEN) [ 5538.751057] Domain 6 (vcpu#0) crashed on cpu#3:                                                                                                                                 
(XEN) [ 5538.751059] ----[ Xen-4.17.5-4  x86_64  debug=n  Not tainted ]----               
(XEN) [ 5538.751059] CPU:    3                                                              
(XEN) [ 5538.751060] RIP:    0033:[<000000000079a336>]                                    
(XEN) [ 5538.751061] RFLAGS: 0000000000010202   CONTEXT: hvm guest (d6v0)                   
(XEN) [ 5538.751062] rax: 000000c00036e000   rbx: 0000000000400000   rcx: 0000000000294000                                                                                               
(XEN) [ 5538.751063] rdx: 00000000003d0000   rsi: 00000000003d0000   rdi: 00000000002d0000
(XEN) [ 5538.751064] rbp: 000000c00035f410   rsp: 000000c00035f318   r8:  0000000000001032                                                                                               
(XEN) [ 5538.751065] r9:  0000000000001032   r10: 00007ff8fefa9d28   r11: 0000000000000000                                                                                               
(XEN) [ 5538.751065] r12: 000000c00036e000   r13: 0000000000000000   r14: 000000c0000061c0                                                                                               
(XEN) [ 5538.751066] r15: 00ffffffffffffff   cr0: 0000000080050033   cr4: 00000000003706f0
(XEN) [ 5538.751067] cr3: 0000000139c51804   cr2: 00007ff8fdf5e0d8                        
(XEN) [ 5538.751068] fsb: 00007ff94747f740   gsb: 0000000000000000   gss: ffff9c4a6d600000
(XEN) [ 5538.751069] ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: 002b   cs: 0033
(XEN) [ 5538.751234] p2m_pod_demand_populate: Dom6 out of PoD memory! (tot=1049114 ents=940768 dom6)
(XEN) [ 5538.751236] domain_crash called from p2m_pod_demand_populate+0x4d2/0x8b0
(XEN) [ 5538.751420] p2m_pod_demand_populate: Dom6 out of PoD memory! (tot=1049114 ents=940768 dom6)
(XEN) [ 5538.751422] domain_crash called from p2m_pod_demand_populate+0x4d2/0x8b0

Do you know what PoD memory is? This indeed looks to be a candidate for the cause.

Hi all,

I am seeing random reboots on my RockyLinux VM's. In this example, I have a RockyLinux 9 VM running a number of docker containers. I was just SSH'd onto the VM and working, and BOOM.. it's gone again. Bringing up the console, I see it is rebooting. This keeps happening. The VM is not busy and it's not running out of memory.

What can I check..?
Why does it keep rebooting...?

I must get the VM stable or I'm going to have to go back to Proxmox pronto!

Many thanks.

@MathieuRA It does indeed Sir. Thank you very much!

@Danp Yes. Even when I select a local SSD SR it still happens. I'm not able to create any VM's at all, no matter which SR I am selecting.

@Danp I tried removing the second host from the pool but it now still will not allow me to create a VM.

Ah, nice. I did not know that you could drill down into the error. The dump is as follows:

vm.create
{
  "clone": false,
  "existingDisks": {},
  "installation": {
    "method": "cdrom",
    "repository": "8eb59f38-25e2-4486-b7c2-98dc938e1fc6"
  },
  "name_label": "Windows 10 (64-bit)",
  "template": "3d3a2920-24c8-f280-5c27-1e4d4a82253c-7774689b-4ca1-4dea-8545-dddd6b64c17f",
  "VDIs": [
    {
      "bootable": false,
      "device": "0",
      "size": 34359738368,
      "type": "system",
      "SR": "3d615d9a-4b54-cf75-ef43-0d08bbf0a640",
      "name_description": "Created by XO",
      "name_label": "Windows 10 (64-bit)_epunu"
    }
  ],
  "VIFs": [
    {
      "network": "945f1105-893e-becc-35fe-0a97328ee7ac",
      "allowedIpv4Addresses": [],
      "allowedIpv6Addresses": []
    }
  ],
  "CPUs": 2,
  "cpusMax": 2,
  "cpuWeight": null,
  "cpuCap": null,
  "name_description": "",
  "memory": 4294967296,
  "bootAfterCreate": true,
  "copyHostBiosStrings": false,
  "createVtpm": false,
  "destroyCloudConfigVdiAfterBoot": false,
  "secureBoot": false,
  "share": false,
  "coreOs": false,
  "tags": [],
  "hvmBootFirmware": "uefi"
}
{
  "code": "HANDLE_INVALID",
  "params": [
    "SR",
    "OpaqueRef:NULL"
  ],
  "call": {
    "duration": 8,
    "method": "VDI.create",
    "params": [
      "* session id *",
      {
        "name_description": "Created by XO",
        "name_label": "Windows 10 (64-bit)_epunu",
        "other_config": {},
        "read_only": false,
        "sharable": false,
        "SR": "OpaqueRef:NULL",
        "type": "user",
        "virtual_size": 34359738368
      }
    ]
  },
  "message": "HANDLE_INVALID(SR, OpaqueRef:NULL)",
  "name": "XapiError",
  "stack": "XapiError: HANDLE_INVALID(SR, OpaqueRef:NULL)
    at Function.wrap (file:///opt/xo/xo-builds/xen-orchestra-202412191835/packages/xen-api/_XapiError.mjs:16:12)
    at file:///opt/xo/xo-builds/xen-orchestra-202412191835/packages/xen-api/transports/json-rpc.mjs:38:21
    at runNextTicks (node:internal/process/task_queues:60:5)
    at processImmediate (node:internal/timers:454:9)
    at process.callbackTrampoline (node:internal/async_hooks:130:17)"

I have just rebuilt the XO install, and that error has... apparently changed into a different one. Create VM operation still fails, but this time the message is:

HANDLE_INVALID(SR, OpaqueRef:NULL)
This is a XenServer/XCP-ng error

Hmph

@Danp Thanks for that. I built the XO from source a few days back, but maybe it just missed that. I'll rebuild now and see what happens.. Thanks

Hi there.

I am currently testing XCP-NG. I installed onto a server and all has been quite smooth sailing. Now I wanted to see if I can add another host to the pool and migrate the VM's between them. So I added an external NFS server, and have added the NFS SR to the pool. However, after adding the second XCP-NG host to the pool, I am unable to create a VM. When I click the create button it shows an error. Looking in the log it says:

no object with UUID or opaque ref: OpaqueRef:32cbe139-e607-6f84-e29b-a6b1d24f213c

Can anyone suggest where to look for further diagnosis of this issue?

Many thanks