In the github issue referenced above, I read:

live migration from e.g. xeon v3 to xeon v4 fails because of cpu mismatch.. xe vm-migrate command line with force it mostly works fine...

Ok. It seems to be like If you checked it to work manually you can force it

This is a quite ancient thread, but I'm answering anyway.

I've done some tests with the Force-Migration Wizard in XCP-NG 8.1.

Expected/Desired behaviour:

VM is running during migration and after migration. Reboot is done after migration had finished, to activate the new cpu feature mask.

In no case it worked as desired. The outcomes of the tries:

• the vm crashed, was halted on source server
• the migration was logged as successful, but the vm was halted on the target server

I have 3 different cpu models, with which I tested Force-Migration:

• Intel(R) Xeon(R) CPU E5506 @ 2.13GHz (oldest)
• Intel(R) Xeon(R) CPU E5620 @ 2.40GHz
• Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz(newest)

Maybe this feature is only useful, if the cpu features differ only very slightly?

a) Just want to mention the proxmox way of doing what I suggested:

https://www.proxmox.com/en/proxmox-ve/pricing

The have a community subscription - the lowest price subscription. Would be interesting how many "community" subscribers they have. (They probably won't tell if asked )

b) The top result in google search for xcp-ng and "donations" points to this thread

https://www.google.com/search?q="xcp-ng"+"donations"

@olivierlambert said in Nag-Screens:

I prefer to use my time to contribute if I need or to build myself an Open Source thing

Ok. Thanks again for your time.

I'm not understood by you mostly and I won't follow my current agenda being understood any longer to get to a mutual understanding with the goal of contribution while respecting both sides needs.

I'll respect your doing business your way and some of the thoughts you wrote seems plausible to me while I completely disagree with others. I leave that by this comment and stop here to save your time.

My last question on that is to repeat in other words what I already wrote:

You said I could have improved XCP-NG with the time I invested in writing the remove-disclaimer snippets. I checked the bugtracker of xcp-ng to see if I can
do something and realized that it'll probably take several days/weeks to get familiar with the code before being able to contribute something useful.

I'd like to contribute to xcp-ng with my scripting skills.

Can you or some other person suggest what I - a seasoned sysadmin with scripting capabilities(lua,php,perl,shell,ruby,...) - can do by writing/improving/checking scripts with a a budget of some varying amount of hours per week/month? (See my github repo for the past small scripting examples of what I've shared so far: https://github.com/megabert/)

Ok. If you like to drop out of this conversation at any time, a conversation which you may consider a useless waste of time, it's ok for me.

I thought about if this concern is important enough before starting into that direction. I decided it absolutely was and still is. And I still think it is a great contribution once my thoughts are actually understood - which is not the case currently.

The following benefits are realistic to me if the suggestions are adopted:

• Additional money as donations from home users/small company users(100k+ €/annually medium term worldwide)
• Increased User satisfaction
• Increased encouragement and participation in xcp-ng and maybe xo
• Increased efficiency in communication

If you're not interested in that, I'll gladly stay away from further consuming your time and just may look on my own on how to contribute to xcp-ng in a way it contributes to your needs as stated by you so far.

So, do you have needs for ...

• ... financial support to keep Vates running and growing and to have the resources to be able to further support XCP-NG development?
• ... other kinds of support for XCP-NG?
• ... a balance between giving and taking and you request some giving back for your huge efforts to bring forward xcp-ng and xo?

I have needs for ...

• ... trust, that software I use, will be developed in a direction that I appreciate and not into ways i hate(because I do want to avoid the needed efforts to abandon a software and migrate to another software):
  • maximize usability
  • keep free features free
  • request reasonable and fair prices
  • keeping ways to migration to other products open
• ... efficiency and tidyness
  • clean and tidy interfaces
  • easy ways to contribute with my competence(scripting skills). (I checked out the bugtracker and worry about having to need at least weeks to dive into the software before being able to do anything)
• ... a balance between giving and taking(giving something back for what I got)
• ... autonomy (deciding what and how much I give back in order to help)
• ... recognition of what I have gave to support others
• ... practise and development my compentences (scripting skills, ...)
• ... contribute to the world community for shared values, knowledge and tools

Suggestions for strategies about how our both needs can be met:

• Vates offers a sponsorship license: An easy way(web page) to pay a regular payment with an amount of the donators choice. All donators have the option to be listed with their preferred Name(company,private name, fantasy name) on a web page of donators(maybe sorted form hightest donation amount to lowest).
• Someone shows easy ways to help to improve XCP-NG with a time budget of hours instead of weeks or month for persons with scripting skills or maybe for various other needed/existent skills.
• Similar to the above: A task list is being created, where people with a limited time budget can contribute. This will serve as possibility for minor contributions and as a possible easy entry point for long term participation within the xcp-ng project
• Getting needs met is important: Think more about what needs exist and figure out strategies how to meet one ore more of those needs on both sides

What's regarding me, I'm a user of mostly Citrix XenServer at the moment. I personally decided to head for proxmox because performance is better. But never the less as stated above it would meet my needs to support xcp-ng.

Update:

Of course I knew you probably wouldn't be very fond of my action of supporting the prevention of the disclaimer. But I'm impressed that you didn't start to fight me and still stay in contact and communicate your needs! In my experience in IT forums that's a rare personal competence and I want to say thank you for that!

I thought several times about buying a starter subscription of xo, but I decided against it, because ~1000 EUR per year seamed to much for my company budget. (Yes, there are many other companies for which this amount of money is ridiculous, but not here). I definitely would pay a lower rate if I keep using XCP-NG for the companies virtualization.

Open Source is not just taking, it's also giving.

Yes, I totally agree. I'll have a look at the bugtracker to see what's to be done.

Are there any open tasks for a person like me with some scripting skills?

Open Source is also not about fighting against its users, I thought!

Link to the descriptions to patch the disclaimer away:

https://github.com/FoxieHazmat/xenorchestraSourceBannerFix/issues/1

and to the script that does it for you(tested with XO 5.44.1):

https://github.com/megabert/xenorchestraSourceBannerFix

pageb018 created this issue in FoxieHazmat/xenorchestraSourceBannerFix

open anychance you have an update to make this work with newer versions? #1

task list: constantly flipping blue bar / hard to read

Observations:

• Regarding the task in the left menu. I have a pool of ~12 smaller Servers.
• The number next to the Tasks Menu-Item is constantly changing between 1-4.
• When I click on it, I see regular appearances of tasks like: "myserver-1.mydomain.tld SR.scan" which appear and disappear in short intervals.
• The thick blue bar(with label "previous tasks") dances up and down on my screen quickly.
• The width of the columns change constantly supposedly in adapting to the servername length, so there's even more motion on this page.
• There is a message/task Connection to VM console (on de-f1-xs03....) 0% which I can not delete(A hover icon states that this message/task can not cancelled).

User Experience:

• I can hardly inspect a task which is in my focus to get details about, because the different lines are moving up and down quickly
• It's hard for me to get the information when so much motion is on the page
• I do not understand why I can not delete the task "Connection to VM console..." and how I get rid of it.
• It's annoying to have a constantly visible and changing number of tasks in the menu, when there in fact is absolutely no user task running(Storage Repository scans are completely irrelevant for me).

Thoughts about possible improvements:

• place the label/button "previous tasks" above the head of the tasks, so the very visible bar stops moving
• use fixed column length, so this source for this type of motion is eliminated
• Add an explanation via hover, why a task can not be cancelled
• Hide Storage Repository Scans, as these are continuous system jobs and not user jobs.(An administrator may want be informed about errors for those jobs, but I see no sense in seeing those jobs running)

Thanks Olivier for your clear feedback. I so experienced you are open to - even critical feedback - and realize you tried to understand my point of view. So I'm motivated to provide the feedback to the other points where I think things can be improved(in a new thread).

Impact: Yes, it's the red circle. I just dislike alarm symbols when situation is normal. I try to remove it myself from the code as long as I do not intend to buy a subscription.

@olivierlambert said in Nag-Screens:

Not sure to understand: what's not solved? The top banner than you can remove now?

I just read the information about that in the mentioned github issue. I haven't tried so far. Probably this is solved.

There is another presentation detail which I consider annoying and which I would like to disable:

The red circle with a question mark at "XOA" menu entry, showing, that update
information is not available.

This one is still open.

Also, why reviving such an old topic just for that?

Because I firstly installed XO from source, got annoyed and this is the matching forum and the matching post for the issue. Lastly because you invited anyone to continue the discussion in the github issue. (https://github.com/vatesfr/xen-orchestra/issues/4430)

We are open to continue the discussion on the forum, which seems the best place to do so.

For me the issue isn't resolved. So I'm asking you for reconsidering as stated. That's why I shared my opinion about it. If you do not like my opinion nor discussion on this topic, just say a word, and I'll never bother the forum with my presence again.

declanmarks created this issue in vatesfr/xen-orchestra

closed Disable built from sources warning. #4430

@smschumacher said in Nag-Screens:

I have to be quite honest but this motivates me much more to have a look at oVirt than to buy XCP-NG. I already gave Proxmox a try but this is, but it suffered from the exact same problem. Oh Sure, we are 100% open source, but if you want PREMIUM features you need to pay a few hundred dollars a month.

Same goes for me here. In the beginning I directly went away from XOA appliance, because of the many pages

That feature is unavailable in this version, if you like that, it's available in Version {Starter|Premium|Enterprise}.

Having realized that XenOrchestra is Open Source at last after 2(?) years it was started, I baked it myself(Many thanks for the installation guide hereby!). The message

This version is not bundled with any support nor updates. Use it with caution.

which is displayed on every f****** page is very annoying. I saw there's possibly a fix for it in this github issue: https://github.com/vatesfr/xen-orchestra/issues/4175

There is another presentation detail which I consider annoying and which I would like to disable:

• The red circle with a question mark at "XOA" menu entry, showing, that update information is not available.

What is acceptable / not annoying for me is...

• the yellow triangle with the words no support at the left, lower down the menu.
• an information about the version(open source, no support, bla ...) when updating or in monthly intervals

I read that is very import for Vates to inform the users about the possibility that there is commercial support available. I can understand that need to inform users so that nobody who wants support and has the budget just do not know.

But for me it's annoying and with the current state, I do not like the interface and won't recommend it to others and I kindly ask you to consider changing the policy on that topic.

When I look at the situation, I can imagine, that you really get some new customers by informing them constantly that there's support available. On the other side, you possibly loose a lot enthusiasts because of the nagging. Enthusiasts that are from the tech layer, who may have great influence on what software is being used and what not. Tech people who recommend software they like the to other users. If you have great software, anybody wants to use it. Tech people like me.

For me for example the monitoring solution check_mk is one of those software products. I got a recommendation for it and at the shared office space everyone is using it and I'm fascinated to talk to anyone interested about it and share my knowledge on the topic, because it's really great software.

I think Vates and you Olivier have earned great respect for me by starting up XCP-NG and I think you enriched the world by doing so. Thanks for that!

What regards Xen-Orchestra so far: Currently I have no strong preference for it. But that may change in future...

What regards the compare with proxmox: I think one message at a login is acceptable for me.

Regards,
fork

FoxieHazmat created this issue in vatesfr/xen-orchestra

closed Permanent banner when running XOA from the sources #4175