Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The "Auto-boot VM" function not working XCP-ng Center v8 #172

Closed
kbalicki opened this issue Aug 7, 2019 · 30 comments
Closed

The "Auto-boot VM" function not working XCP-ng Center v8 #172

kbalicki opened this issue Aug 7, 2019 · 30 comments
Labels
wontfix This will not be worked on

Comments

@kbalicki
Copy link

kbalicki commented Aug 7, 2019

Boot Options tab for VM: Auto-boot: Yes

After server (re) start VM does not start and has to be started manually.

@borzel
Copy link
Member

borzel commented Aug 8, 2019

Which XCP-ng Center version exactly?

@kbalicki
Copy link
Author

kbalicki commented Aug 8, 2019

Which XCP-ng Center version exactly?

8.0.0

@kbalicki
Copy link
Author

8.0.1 - same problem

@DPerkunas
Copy link

Confirming same issue for 8.0.0, haven't tried 8.0.1 yet.

@borzel borzel added this to the 2020.01 milestone Feb 6, 2020
@borzel
Copy link
Member

borzel commented Feb 6, 2020

Maybe: need to set the general autoboot parameter for the whole server, not only for the VMs itself

@borzel
Copy link
Member

borzel commented Feb 6, 2020

same as here: vatesfr/xen-orchestra#879

@speedy01
Copy link

speedy01 commented Feb 9, 2020

same as here: vatesfr/xen-orchestra#879

This may be the case with v8.0, but 8.1 may be a different issue.

8.0 to 8.1 upgrade via yum went well without an issue, but autostart of the vm does not work. Auto start worked fine with 8.0.
I confirmed that autostart is set to TRUE on the pool and on the vm itself using
xe pool-param-get uuid=<pool_uuid> param-name=other-config param-key=auto_poweron
xe vm-param-get uuid=<vm_uuid> param-name=other-config param-key=auto_poweron

Not sure what else to check...but will be happy to provide any additional information

@borzel borzel removed this from the 2020.01 milestone Mar 11, 2020
@borzel
Copy link
Member

borzel commented Mar 11, 2020

Its relatively difficult to set the autoboot parameter for the pool if I'm in the vm context. More investigation is needed.

@stormi
Copy link
Member

stormi commented Mar 11, 2020

Autostart of VMs in 8.1 updated via yum from 8.0 has been fixed since in XCP-ng directly, if that's the same issue.

@borzel
Copy link
Member

borzel commented Mar 11, 2020

@stormi no, it's an internal one

@kbalicki
Copy link
Author

Is there some solution for this, or still nothing?

@olivierlambert
Copy link
Member

For me, it's working on XCP-ng 8.1 with Xen Orchestra. Are you on 8.0?

@kbalicki
Copy link
Author

For me, it's working on XCP-ng 8.1 with Xen Orchestra. Are you on 8.0?

I do not use Xen Orchestra, and problem is still there :(

@HeMaN-NL
Copy link

What is your xcp-ng version and what steps have you done to enable it?

@Machine22
Copy link

Reporting on the same issue i am using the latest version of XCP-ng with xen center. Am facing the same issue right here, not only does pfsense not auto start on Xen server reboot but as well my other Windows 7 machine running Plex that is attached to Pfsense's LAN. Could it be an issue with Xcp or the VMs in particular are set up wrongly with in xcp though i highly doubt.
Anyone with a solution kindly pass it on. Thanks in Advance

@olivierlambert
Copy link
Member

Can you try with Xen Orchestra? I just tested it here and it works.

@stormi
Copy link
Member

stormi commented Jun 30, 2020

I think this whole bug report is about XCP-ng Center, not XCP-ng or Xen Orchestra. I'm pretty sure it works in Xen Orchestra indeed.

@olivierlambert
Copy link
Member

I'd like to be sure it's purely XCP-ng Center related, that might help to find the root cause 👍

@kbalicki
Copy link
Author

kbalicki commented Jul 2, 2020

What is your xcp-ng version and what steps have you done to enable it?

XCP-ng 8.1 + XCP-ng Center 20.04,00

XCP-ng Center: VM -> Properties -> Boot Options - ? Autostart on server boot
Rebooting server did not help either.

@kbalicki
Copy link
Author

kbalicki commented Jul 2, 2020

I think this whole bug report is about XCP-ng Center, not XCP-ng or Xen Orchestra. I'm pretty sure it works in Xen Orchestra indeed.

Will test it when have some free time. My XCP-ng server is behind NAT, and it will take a moment to reconfigure everything, so it will be publicity available, so I can use XOA quick deploy.

@kbalicki
Copy link
Author

kbalicki commented Jul 2, 2020

I'd like to be sure it's purely XCP-ng Center related, that might help to find the root cause 👍

Confirmed, autostart works ok with Xen Orchestra, so it is XCP-ng issue.

@stormi
Copy link
Member

stormi commented Jul 2, 2020

I'd like to be sure it's purely XCP-ng Center related, that might help to find the root cause +1

Confirmed, autostart works ok with Xen Orchestra, so it is XCP-ng issue.

XCP-ng Center

@olivierlambert
Copy link
Member

I'd like to be sure it's purely XCP-ng Center related, that might help to find the root cause +1

Confirmed, autostart works ok with Xen Orchestra, so it is XCP-ng Center issue.

Ah nice! Thanks 👍

@Alphaprot
Copy link

Also can confirm that it is XCP-ng Center related, see XCP-ng 8.1.0 - vm autostart not working

@steinbitglis
Copy link

Is there any workaround for this, other than installing xen orchestra?

@M-Covrig
Copy link

M-Covrig commented Nov 4, 2021

Perhaps you need to update to the latest xcp-NG center, and it should work. I'm using v20.04.01. I would suggest to use both xcp-ng center and xoa(even the free version is doing the job). Or you can ask for an extension to XOA license, the lads are very helpful. Cheers

@steinbitglis
Copy link

It seems like 'xe pool-param-set' and 'xe vm-param-set' worked. I'm new to XCP-ng, and apart from this auto-boot issue, I like it a lot.

@M-Covrig
Copy link

M-Covrig commented Nov 4, 2021

Yes it is nice and stable, we are using this for our organisation in the last 2 years nearly, and I'm delighted. Still there's a lot to learn... :). Forgot to mention, the only issue encountered was the LVM limitation to max 4TB if I remember correctly.

@borzel
Copy link
Member

borzel commented Jan 5, 2024

we will not work on that

@borzel borzel closed this as completed Jan 5, 2024
@borzel borzel added the wontfix This will not be worked on label Jan 5, 2024
@borzel
Copy link
Member

borzel commented Jan 5, 2024

follow up and information: #211 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests