...
Hi hector, try it With cpu Type qemu Not kvm64. We had an issue 2 years ago were this worked.
I tried that and nothing. With Proxmox VE 3.4 works fine, but with Proxmox VE 4.0 not. :-(
I tried with kvm64, qemu64 and SandyBridge but nothing. I gave this error: Your PC needs to restart. Please hold down the power button. Error Code: 0x0000005D Parameters: 0x00000000178BFBF9 0x0000000028100800 0x0000000000000000 0x0000000000000000 :-( Configuration of VM: balloon: 1024 bootdisk: virtio0 cores: 2 ide2: local:iso/es_windows_server_2012.iso,media=cdrom kvm: 0 memory: 1536 name: vm05.lab.codesa.co.cu net0: virtio=32:39:31:33:33:32,bridge=vmbr0 numa: 0 ostype: win8 smbios1: uuid=c2110f35-76f7-4549-937a-f789b25b6582 sockets: 1 virtio0: local:104/vm-104-disk-1.qcow2,cache=writeback,size=60G Version of Proxmox VE 4.0: proxmox-ve: 4.0-22 (running kernel: 4.2.3-2-pve) pve-manager: 4.0-57 (running version: 4.0-57/cc7c2b53) pve-kernel-4.2.2-1-pve: 4.2.2-16 pve-kernel-4.2.3-2-pve: 4.2.3-22 lvm2: 2.02.116-pve1 corosync-pve: 2.3.5-1 libqb0: 0.17.2-1 pve-cluster: 4.0-24 qemu-server: 4.0-35 pve-firmware: 1.1-7 libpve-common-perl: 4.0-36 libpve-access-control: 4.0-9 libpve-storage-perl: 4.0-29 pve-libspice-server1: 0.12.5-2 vncterm: 1.2-1 pve-qemu-kvm: 2.4-12 pve-container: 1.0-21 pve-firewall: 2.0-13 pve-ha-manager: 1.0-13 ksm-control-daemon: 1.2-1 glusterfs-client: 3.5.2-2+deb8u1 lxc-pve: 1.1.4-3 lxcfs: 0.10-pve2 cgmanager: 0.39-pve1 criu: 1.6.0-1 zfsutils: 0.6.5-pve6~jessie :-( -- ===================================== Lic. Hector Suarez Planas Administrador Nodo CODESA Santiago de Cuba ------------------------------------- Blog: http://nihilanthlnxc.cubava.cu/ ICQ ID: 681729738 Conferendo ID: hspcuba ===================================== _______________________________________________ pve-user mailing list [email protected] http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
