Recent content by Admiral

Update : This seems to work . Non-hpet also enables Debian 10 to work in Epicmode However : Ubuntu desktop gives a garbled desktopscreen when booting

Ok , i am testing now

Can that be put in the configfile (101.conf) as well?

i posted that with your pgrep-command .. :)

Update : FreeBSD 11 does work , FreeBSD 12 hangs with the EPYC or host-cpuprofile Fedora 30 works Running Fedora 30 nested : FreeBSD 12 works as well Qemuversion on that : 3.1.0-9.fc30 pgrep -fa 'kvm|qemu' 2686 /usr/bin/qemu-system-x86_64 -name guest=freebsd12.0,debug-threads=on -S -ob...

Fair enough , but 12 did work on the Fedora , i am reproducing it in a vm with Fedora now Results will we posted later on

I was running 12..

That is impossible unfortunately , the Fedora box got reinstalled with proxmox ... :(

Well , this FreeBSD worked flawless with the EPYC cputype on Fedora 30 though And i see the same weird behaviour with Debian , Ubuntu and even Arch

qm config 100 bootdisk: virtio0 cores: 1 cpu: EPYC hotplug: disk,network memory: 8192 name: BSD net0: virtio=FE:87:95:5E:29:09,bridge=vmbr0,firewall=1 numa: 0 ostype: other sata0: local:iso/FreeBSD-12.0-RELEASE-amd64-disc1.iso,media=cdrom,size=871550K scsihw: virtio-scsi-single smbios1...

After switching it from opteron G3 to EPYC (So i could make the screenshot) Jul 08 19:14:30 pve pvedaemon[1721]: <root@pam> update VM 100: -cores 1 -cpu EPYC -delete vcpus,cpulimit,cpuunits -numa 0 -sockets 1 Jul 08 19:14:30 pve pvedaemon[1721]: cannot delete 'vcpus' - not set in current...

This hangs with the EPYC/host profile (it just hangs forever on the USB, while the generic kvm64 works)

Reformatted the code , i mean with booting poorly : They either hang or crash :)

Hi guys , The following issue (It works on Fedora 30 with KVM though) : On both Proxmox 5.4 and 6 i can't get VM's to boot properly with the EPYC or host-cpuprofile With KVM64 or Opteron G3 it works My setup : # pveversion --verbose proxmox-ve: 6.0-1 (running kernel: 5.0.15-1-pve) pve-manager...

You really don't want to use Centos 5.x now ... support for this has ended 31th of March 2017