After adding "args: -xsave" to vmid.conf, I got error below
Code:
kvm: -xsave: invalid option
Just wanted to confirm using qemu64 CPU worked for me without any issue. I am using Proxmox 3.1 and FreeNAS 9.1
Unfortunately I am having the same issue.
If I disable the option "KVM hardware virtualization" it works. When this option is enabled the virtual system freezes right after boot with one cpu core going up to 100%.
Used CPU:
Used vmid.conf:
pveversion -v
If I disable the option "KVM hardware virtualization" it works. When this option is enabled the virtual system freezes right after boot with one cpu core going up to 100%.
Used CPU:
Code:
model name : Intel(R) Xeon(R) CPU E3-1230 V2 @ 3.30GHzUsed vmid.conf:
Code:
args: -cpu kvm64,-xsave
bootdisk: sata0
cores: 4
cpu: kvm64
ide2: local:iso/FreeNAS-9.1.1-RELEASE-x64.iso,media=cdrom,size=357074K
memory: 8096
name: freenas
net0: e1000=8A:94:D2:5A:41:CC,bridge=vmbr0
ostype: solaris
sata0: local:101/vm-101-disk-1.qcow2,format=qcow2,size=8G
sockets: 1pveversion -v
Code:
proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-26-pve)
pve-manager: 3.1-24 (running version: 3.1-24/060bd5a6)
pve-kernel-2.6.32-26-pve: 2.6.32-114
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-2
pve-cluster: 3.0-8
qemu-server: 3.1-8
pve-firmware: 1.0-23
libpve-common-perl: 3.0-9
libpve-access-control: 3.0-8
libpve-storage-perl: 3.0-18
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-6
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.1-1Hi, qemu-kvm 1.7 should come very soon in proxmox, it could be possible that this bug is fixed.
Maybe can you wait some more days ?
Maybe can you wait some more days ?
I just installed freenas 9.1.1 release-x64, granted, it failed with default kvm config. But changed cpu to qemu64 and it ran right out of the gate. YMMV with other disk/net configs as I have not tried those. I only made the one change.
But if your indications are the host CPU, it might be, mine is;
Code:
bootdisk: ide0
cores: 2
cpu: qemu64
ide0: proxmoxnfs:155/vm-155-disk-1.qcow2,format=qcow2,size=32G
ide2: none,media=cdrom
memory: 2048
name: freenas
net0: e1000=BE:AA:2C:17:A2:33,bridge=vmbr0
ostype: other
sockets: 2But if your indications are the host CPU, it might be, mine is;
Code:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 24
On-line CPU(s) list: 0-23
Thread(s) per core: 2
Core(s) per socket: 6
Socket(s): 2
NUMA node(s): 4
Vendor ID: AuthenticAMD
CPU family: 21
Model: 1
Stepping: 2
CPU MHz: 2393.956
BogoMIPS: 4787.40
Virtualization: AMD-V
L1d cache: 16K
L1i cache: 64K
L2 cache: 2048K
L3 cache: 6144K
NUMA node0 CPU(s): 0,2,4,6,8,10
NUMA node1 CPU(s): 12,14,16,18,20,22
NUMA node2 CPU(s): 1,3,5,7,9,11
NUMA node3 CPU(s): 13,15,17,19,21,23I can reproduce it 100% with amd opteron host, and any vm cpumodel which is amd model.(host,opteron_g4,kvm64)
kvm64 is emulate an amd , qemu64 emulated an intel.
I think It's a freebsd bug with amd cpu detection, or a seabios bug in qemu 1.4.
qemu 1.7 is coming very soon in proxmox, maybe it'll be fixed.
freezing after menu selection, upgrade to latest version too
tested several parametter and no solution yet
The same problem, pfSense 2.1 64-bit freeze at menu on boot, I've tried every possible way, waiting a patch for this issue!
My system: Dell PowerEdge R210 II with E3-1240.V2 and Proxmox VE 3.1.
Thank you very much for Proxmox team for the excellent work, We hope your help.
Asem
My system: Dell PowerEdge R210 II with E3-1240.V2 and Proxmox VE 3.1.
Thank you very much for Proxmox team for the excellent work, We hope your help.
Asem
The same problem, pfSense 2.1 64-bit freeze at menu on boot, I've tried every possible way, waiting a patch for this issue!
My system: Dell PowerEdge R210 II with E3-1240.V2 and Proxmox VE 3.1.
Thank you very much for Proxmox team for the excellent work, We hope your help.
Asem
My system: Dell PowerEdge R210 II with E3-1240.V2 and Proxmox VE 3.1.
Thank you very much for Proxmox team for the excellent work, We hope your help.
Asem
With my setup on an Intel-Core-i5-4570 CPU (Haswell) this was no good - the vm would freeze with 100% cpu not matter what. I strongly believe that this is an issue with all Haswell based cpus.
I have now installed pve kernel 3.10 and can report success. The FreeNAS 9.2.1.1 booting just fine.