Search results

It is the same screen from what I remember, though I did not do an exhaustive test yesterday I will dive into it more this week and report back.

I just updated to the latest kernel and the problem is back again, this time even trying to load an older kernel has not helped.

You were correct somehow that flag got switched to disabled and once it rebooted with it enabled the test VM fired up no problem.

Just updated to the latest version of Proxmox VE and still getting this error: kvm: warning: host doesn't support requested feature: CPUID.80000001H:EDX.nx [bit 20] kvm: Host doesn't support requested features TASK ERROR: start failed: QEMU exited with code 1 Here is the VM configuration, it...

I have my nodes setup that vmbr0 is the interface used by VMs, they are then divided using a VLAN tag (default untagged VLAN is the testing and development network) on the particular interface assigned to a VM and then my storage network is vmbr1 and my management is assigned to vmbr2.

@Dunuin -- The only way to get HA from TrueNAS is to purchase their hardware and they use an active-passive type HA using multiple nodes in a single chassis that both have access to all the disks though only the master is actively using them. These servers are also way out of my budget.

I am wanting to know if this is currently possible or if this would even be worth implementing if it is not possible with the current ProxmoxVE release. This will, unfortunately, be a bit of a long post but ill try and be as concise as possible. Server Background: I have ProxmoxVE (currently...

The way that I did my setup for HA pfSense while only running a single pfSense VM is to make use of my managed switches VLAN and LACP abilities. I'll simplify my install a little for the length of my post but it won't change the design. So for this post, I have 1 managed switch (called MAIN), a...

kvm: warning: host doesn't support requested feature: CPUID.80000001H:EDX.nx [bit 20] kvm: Host doesn't support requested features

I have 7 nodes in my cluster and 6 of them are running older Intel CPUs, with each node having 2 sockets. The problem is the 1 node that I have that is running an AMD CPU. This node will not start a VM unless the processor type is set to max or to host. These of course can cause issues if the VM...

So I ended up getting things working by having a valid certificate on both my mail gateway and my mail server and have also setup all the appropriate supporting DNS entries as well the only part that I have not setup is DIKM.

I wanted to update and close this thread off as I just updated today (Dec 4, 2021) to the lastest set of packages and I was able to load the new kernel. For the record and to help others later here is the package versions that worked for this old Dell. proxmox-ve: 7.1-1 (running kernel...

Just updated the server that was causing issues and it stuck at the same spot as shown in image 2 of my previous post. I'll try and look into it more later this week or next and see if it is the same error or if it is changed at all.

If you are using a single NIC virtual or otherwise to pass tagged and untagged traffic you will need to have a base interface in pfSense. as they are all technically going over a single connection between pfSense and the switch. You would then add the VLANs to pfSense as well as the switch your...

I use pfSense and run in on a VM in my ProxmoxVE cluster, I have 3 bridges set up on each of my Proxmox nodes and none of them are set to be VLAN aware. vmbr0 is set as my virtual machine traffic where all of my LAN-based VLANs will travel. vmbr1 is for communicating with other Proxmox nodes...

In the interest of full disclousre, I have been Proxmox VE and Proxmox MG for a while now but I defiantly am much more versed in the Virtual Environment than the Mail Gateway. While in the process of completely overhauling the hardware in my home data center and setting things up again from...

I restarted the machine having the boot issues and took a video and extracted the following images from it with the various errors and other output.

Here are the CPU models that I have in use if this helps, I am hoping to get a chance to restart the Dell server today and get more from the output just have to get some work-related tasks done before I can tinker with it again. Node 1 = Supermicro X8DTi-LN4F with dual X5670 which is running...

Yes, the CPU was released in Q4 of 2007 and the HPs from my quick check on one of them was Q1 of 2008. I will try and grab a screenshot of the output it seems to repeatedly try to keep going but states similar or the same errors again and again. I just double-checked and I have the latest BIOS...

I updated my cluster of Proxmox nodes to 7.1 and everything went smoothly except for 1 machine. I am running on older hardware but all from the same generation more or less. My updates on my 5 HP DL380 G5 servers went without a hitch though 1 of them did need a second reboot after the upgrade to...