Search results

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

It is NexentaStor 4.0.4 , the current one. I've turned off ACPI , just for testing purposes ( It was slow before anyway ). I will try your config as soon as I get home from work :) Thanks for your time for now :)

@ the moment I am @ work so I don't have access . I can give you the details that I remember : 3 sockets with 1 vcpu ( Could not get it to work with 1 socket and 3 Vcpu's) Virtio raw disk 20 gig , writeback. Virtio NIC. ACPI Off , KVM 1 , Solaris OS type. 6 Gigs ram. Cputype = host scsihw =...

This used to work in an esxi setup before though , with quite fast performance. But this remark doesn't solve my problem though :) Why is Solaris this slow on my setup? :) Even without the intention to make it a storage VM , the performance is really bad.

I want to make a Nexenta or at least Illumos-based ZFS storage which i intend to pass back to proxmox over iSCSI. The VM is really slow , especially noticeable when connecting to the webinterface of that VM. It has been configured with 3 Vcpu's and 6 Gigs ram for now , my ZFS array will be...

Has anyone managed to get this working? With or withour Virtio disks/nic's it just takes ages to get into the webinterface CPU : AMD FX8320 , 16 Gigs of ram pveversion -v proxmox-ve: 4.0-16 (running kernel: 4.2.2-1-pve) pve-manager: 4.0-50 (running version: 4.0-50/d3a6b7e5)...