Recent content by notfixingit

I had the same issue last week, however like Vactis, mine was with kvm_intel not kvm_amd and specifically with kernel 5.11.x. (proxmox 7) I spent the better part of the other night researching it and unfortunally I did not bookmark where I found the info, but someone in a Ubuntu kernel thread...

Raid 1 requires pairs of drives aka mirror. The ZFS link posted above by Dietmar covers how to do a raid 1.

That appears to have worked, thanks =)

It looks like corosync 2 does have support for 2 node? totem { version: 2 secauth: off cluster_name: mycluster transport: udpu } nodelist { node { ring0_addr: pcmk-1 nodeid: 1 } node { ring0_addr: pcmk-2 nodeid: 2 } } quorum {...

Really it depends on your bandwidth and cpu requirements, if it's heavy mySQL instance for example, you could easly use 100% of the box. We honestly though run into max nic cards and memory issues though before CPU problems. But unless your running heavy VM's, it should be more than enough. On...

Gotcha, but the CPU in this particular case is a Broadwell (Atom C2750), so is the check looking for all possible features of Broadwell and some of the same type cpu's just do not have all those features? Just confused as the host CPU is a Broadwell On another system having the same issue with...

Package upgrade scripts would make sense or a post install script. I'll leave the system that upgraded successfully but still has these files untouched for now, if you guys come up with a method that you want to do I would be happy to test or something you would like me to try, let me know.

Setting a KVM VM CPU to type Broadwell on C2750 worked in 3.4 but not in 4.0, also having this same issue with other systems where the type was set to match the host CPU. Error when trying to start warning: host doesn't support requested feature: CPUID.01H:ECX.fma [bit 12] warning: host...

FYI doing purge still leaves /etc/init.d/rgmanager for some reason?? I've also noticed a bunch of other files left after upgrade in /etc/init.d Items in /etc/init.d after upgrade that's not in a fresh install: clvm cman cpglockd openvswtich-switch pvebanner pvenetcommit qemu-server rbdmap...

Made it a little farther... time-sync.target tsort: -: input contains a loop: tsort: apparmor.service tsort: sysinit.target tsort: uuidd.socket tsort: sockets.target tsort: basic.target tsort: openvswitch-switch.service tsort: networking.service tsort: network.target tsort...

Check for bios and LSI firmware updates?

I was able to successfully install 4.0 into a new VM inside Fusion without issue setting the OS type to Ubuntu x64 since my version does not have debian 8 listed.

Got a little further by doing the below (I did a fresh install on another box and did not see these enabled): systemctl disable qemu-server systemctl disable vz systemctl disable rgmanager Maybe there is a better way to clean these up? Now I'm at this: Oct 24 00:47:52 pve1...

Finally found what I think is the issue using journalctl -b (still getting use to systemd) Oct 23 20:33:00 pve1 systemd-sysv-generator[277]: Ignoring creation of an alias umountiscsi.service for itself Oct 23 20:33:00 pve1 systemd[1]: [/run/systemd/generator.late/qemu-server.service:7] Failed...