@olivierlambert I found it. It is an option, again, available only through XO!
I have a VM in halted state and it does not provide an option to delete it in XCPNG Center. In XO I have an active button to delete it but I get a warning saying 'Removing the VM is a blocked operation. Would you like to remove it anyway?'
Why is that happening? I don't have any snapshots of this machine. I don't remember whether I cloned any new VMs from it. Even if I did - is there a risk of breaking something by deleting this VM?
I have my own share of problems with HAProxy on pfSense as all my webservers fall off and I can't figure out why. Testing anything on pfSense without guest utilities is counterproductive, that's why this subject came up since I can't install guest tools because FreeBSD received a major upgrade and repos have changed.
@jedimarcus No, I don't have os-xen in the list of installed packages.
In fact I have another VM with pfSense which I have been using for a few months and in that VM I have xen utilities installed. So, this instance of pfSense also does not have os-xen package showing in the list of installed packages.
I have tried to install xe-guest-utilities into a fresh VM with pfSense 2.4.4 and got a message:
pkg: Newer FreeBSD version for package php74-shmop: To ignore this error set IGNORE_OSVERSION=yes - package: 1202504 - running kernel: 1102000 pkg: repository pfSense contains packages for wrong OS version: FreeBSD:12:amd64 Processing entries: 100% Unable to update repository pfSense Error updating repositories!
Tried a few things and can't figure out how to work around this. Can someone from the XCP-NG team suggest what to do? Thanks.
I only yesterday got my hands on Xen Orchestra. Installation went on fine. XO is fast! And it tells me what XCP-NG Center does not. When I logged in I noticed there were 5 patches available. I installed the patches and XO did not tell me anything like I had to restart the host to apply the patches. What makes me itching is that shortly after the installation of the patches the host seemingly crashed. Or just rebooted by itself? Until I installed the patches my XCP host was rock-solid and stable. It did not run for too long, just 19 days, but this is when I started this deployment and migration from Hyper-V and there was no a single crash. All of a sudden the server goes AWOL.
A newbie question - does applying patches normally require a restart? Does XCP notify me that I need to restart the host? Does it restart itself without telling an admin that it is doing so? Finally, if my host actually crashed - is there a way to see why it did? I am checking the logs area in XO and I see there only 3 messages about one VM lacking a feature.
Thanks in advance for any advice
There is no discrepancy between the OS in the VM and the template I used. My operating system is Windows Server 2012R2. I chose the corresponding template. However I noticed now, when re-creating the VM, that when this template is selected - the UEFI options are grayed out.
So, what I did now - I made a new VM and selected 'Other Install Media'. UEFI was selectable - I chose UEFI and to boot over network and made a diskless machine. Before powering it up I attached the disk and voila - the machine came up!
Thank you for your hunch
I agree about the best practices like using XO, however I am at an initial stage and I need to get a few things done before delving into the Orchestra
Thanks for the UEFI suggestion, let me try that.
Thank you very much.
Please help with advice. I am currently migrating virtual machines from Hyper-V. I have been able to move all Linux machines without trouble. Windows Server 2008 migration also worked without a hitch.
Windows Server 2012R2 is giving me trouble. This is my sequence of action:
Unlike all other machines this one says there is hard disk, but there is no bootable device. I tried booting off the DVD and running bootsec /fixboot and bootsec /fixmbr commands, however this did not help.
What else can I do to fix the boot issue?
Thanks very much