Hello,

It would be great adding 2 items to the "Task" part:

• Size/Destination of the VDI when moving. As of now, the shown information is:

  Pool Name
  VDI Name - SR Size
  VM Name (Host)

  What I propose is:

  Pool Name
  VDI Name - VDI Size
  Origin SR (Size) -> Destination SR (Size)
  VM Name (Host)

  I guess something similar could be applied to a VDI copy operation.

• Elapsed time in the task. This is shown in XenCenter and XO should be able to show it also. Sometimes is really useful when you're performing migration tasks and need to extrapolate elapsed time in certain tasks.

Also, the "Previous tasks" part, it's quite clogged with unuseful (99.99% of the times) information like:

• "SR.scan"
• VM.update_allowed_operations
• host_call_plugin
• VDI.db_introduce
• Async.SR.update

all of them items that only show the host where they are occurring (except "SR.scan" which shows which SR is being scanned) and nothing else. Maybe those can be useful to debug some situation, but not for a daily working mode. I don't know.. maybe with some filters where those tasks would be hidden by default?

To me, a definition of "Task" is something started on-demand, and not internal operations of Xen.

Thanks for the great job

@olivierlambert said in "global name 'commmand' is not defined" while installing patches:

Hi,

Are you on XOA or XO from the sources? If from the sources, there's no versions for XO or its components.

We might have an issue so you should probably try to rebuild on pierre-fix-rpu branch, and then try again

Well, I report these versions:

Okay

Hello,

xo-server 5.90.2
xo-web 5.95.0

Trying to install patches on a 8.2 host via VM -> Patches -> "Install all patches"

-1(global name 'commmand' is not defined, , Traceback (most recent call last):
  File "/etc/xapi.d/plugins/xcpngutils/__init__.py", line 101, in wrapper
    return func(*args, **kwds)
  File "/etc/xapi.d/plugins/updater.py", line 96, in decorator
    return func(*args, **kwargs)
  File "/etc/xapi.d/plugins/updater.py", line 157, in update
    raise error
NameError: global name 'commmand' is not defined

Sounds like a typo....

Thanks.

@Danp said in Installing patches in pool fails:

Known issue

https://xcp-ng.org/forum/topic/5759/cannot-read-property-sort-of-undefined-while-installing-patches

All good. Thanks.

Hello,

xo-server 5.90.2
xo-web 5.95.0

Pool (choosing the desired one) -> Patches -> "Install pool patches".

Fails with:

Cannot read properties of undefined (reading 'sort')

The pending patches are:

Any idea why?

Thanks.

@olivierlambert said in Migrating from Intel -> AMD:

I don't know, but what I can tell is the fact I myself migration my own production from Intel to AMD without any issue, so I really wonder why your guest can't boot

Well it's weird... because happens with all Ubuntu 16 hosts too.

For this Debian in particular, even after upgrading to bullseye, still won't boot on any AMD host, only on Intel ones. Finally I just reinstalled from scratch on an AMD host and migrated the data.

@olivierlambert said in Migrating from Intel -> AMD:

So this is a guest issue then

Can you try to boot this VM with a live CD? (eg Ubuntu).

Well the guest boots perfectly from any other Intel host. I can certainly boot from a live CD though. Any action I should try once I'm there?

@olivierlambert said in Migrating from Intel -> AMD:

Are you fully up to date on 8.2 and rebooted after all updates?

Yes. And just in case, since there are no other servers there:

uptime:
12:52:12 up 21 min, 1 user, load average: 0.75, 0.22, 0.07

But still not booting.

Also when moving a pfsense VM, I had to do the procedure described here:

https://xcp-ng.org/forum/topic/5706/the-emulator-required-to-run-this-vm-failed-to-start/9

@olivierlambert Yes: