Hi!

I am having a strange issue:

When I update XenTools (Citrix-ones) from e.6. 9.3.2 to 9.4.2, there are two NICs visible in Windows 2022 after the first reboot.

After the second reboot, there is only one (as in XOA).

Do you see the same issue?
Is there anything, I can do to avoid the second reboot?

Best wishes
KPS

@Pilow
My migration speed is a bit lower than yours. I am at about 350MiB. What is your setup?

But: I think, the "migration time" is not as important, as the freeze-time... (at least for me)

@olivierlambert
Yes, it's 37s for the migration of a VM with 8GB RAM.
For large VMs, that is critical (5:20 min for 96GB RAM).

...but the core-issue is the freeze, as everything above 4s can leads to disconnects, etc.

Hi!

When I migrate VMs between hosts (with shared storage), the migration takes significantly longer compared to VMware.

Environment:

AMD EPYC 9374F

768 GB RAM

6 × 10 GbE

Observation:

Migrating a VM with 8 GB RAM takes 0:37 min.
Migrating a VM with 96 GB RAM takes around 5:20 min.

Additionally, during the final step of the migration, large VMs experience a noticeable freeze of about 8-10 seconds although they are nearly idle, which makes live pool upgrades during business hours impractical.

Is there anything, I can do to speed this up - especially the freeze?

Best wishes
KPS

@icompit
Did you ever solve this? I am having exactly the same problem...

@GuillaumeHullin
That was the trick!

GRUB_TIMEOUT_STYLE="menu" did solve it!

@GuillaumeHullin said in Linux VM (Ubuntu 22.04) - Grub-Menu invisible:

GRUB_TIMEOUT_STYLE

I did change GRUB_TIMEOUT_STYLE from "hidden" to "timeout".
Now, the system is counting down from 5 to 1 (on a screen, where the rest is black), but the menu is still missing

@GuillaumeHullin
This was just something, I found while googeling...
I did use your config, but still:

• Black screen instead of the boot-menu.

@GuillaumeHullin said in Linux VM (Ubuntu 22.04) - Grub-Menu invisible:

Hi,
Have you run sudo update-grub after changing your configuration?

Yes, I did

Hi!

I am having a problem with linux VMs, that are not showing grub.
The console of the VM is black until the VM does really start.

What I tried:

Changed grub-config to:

GRUB_TIMEOUT=5
GRUB_TERMINAL=console

and

GRUB_TERMINAL="serial"
GRUB_CMDLINE_LINUX="console=tty0 console=ttyS0,115200"
GRUB_SERIAL_COMMAND="serial --speed=115200 --unit=0 --word=8 --parity=no --stop=1"

Can you give me a hint on how to solve this?

Best wishes

@DustinB
When a browser is open for some days, the process is using more and more memory, until it reaches the memory limit. If nobody is logged in, that is happening much slower.
Currently, my limit is 8GB:

When that limit is reached, strange things begin to happen:

• API-requests are timing out
• Backup-jobs are failing
  ...until the process is restarted.

About the original question:

sessionCookieValidity = '12 hours'

should fit?

Hi!

I want to have an auto-logout in Xen-Orachestra. I can see, that logged-on sessions, that are lasting over days are filling the memory of the XOA VM, until issues are starting.

What I found in your git is:

 [authentication] 
 # Default to `maxTokenValidity` 
 #permanentCookieValidity = '30 days' 
  
 # Default to `undefined`, ie as long as the browser is not restarted 
 # 
 # https://developer.mozilla.org/fr/docs/Web/HTTP/Headers/Set-Cookie#Session_cookie 
 #sessionCookieValidity = '10 hours' 

...but I do not really understand the difference between permanentCookieValidity and sessionCookieValidity. Which one do I have to set, to force user logoffs after 12h, when a user does keep the browser open, when leaving the office?

Thank you for your help
KPS

You can easily add some firewall rules as an additional layer and/or restrict to ssh-forwarded sessions

Are there any UUIDs for a remote, that are saved in the meta-files on the remote?

Hi!

I am using XOA on lates stable 5.98.1.
The "Performance-Plugin" seems to have a problem on the resolution of alerts:

First Mail: SR-fill >80%: iSCSI-SR1: 80.1% used
Resolution Mail: END OF ALERT: localstorage: 0.0% used

--> When iSCSI-SR1 did fall below 80% I received the mail about a totally different SR, that is currently empty

Are you having the same issue?

Regards
KPS

@Danp
Thank you!
There is an entry with (i am at least thinking) is reflecting the overall-status. It does not show, which part has failed, IF it has failed, but success should be success

@olivierlambert said in Problem with differential restore:

No, because it's a planned feature. In short, XOA will act as an temporary SR so you can instantly start the backup VM, then migrate it to the target storage.

That’s great get InstantRestore!!!!

@olivierlambert
I want to have the option to introduce ZFS snapshots of the remote if I want to restore from them as:

• They are immutable
• They can be sent offsite

So, I would add an „older version“ of RemoteA as RemoteB

@olivierlambert
Thank you for your answer. IMHO there should be a log, as it is really hard to monitor.

You have to wait some minutes/hours for the short moment, when the VM starts up, until it is deleted. Only the restore status is logged

Hi!

I just did start my first "manual" health check of a restore-point.
The VM was imported and did start, but: Where can I find the result of the check?

• As it was not part of a scheduler, i did not get a mail
• Backup-Restores does just show the import, but nothing about the health check
• Overview does only show backup/mirror/replication-jobs

Thank you for your help
KPS