windows 8.1 ?

[fpausp]

Hi, I tried to test the demoversion of windows 8.1 64bit and 32bit. Both are in a bootloop. Has anyone running it ?

 

[gansc]

Hi, I tried to test the demoversion of windows 8.1 64bit and 32bit. Both are in a bootloop. Has anyone running it ?

Hi,

i will check it & test it in my configuration.

Feedback as soon ...

 

[tom]

I just installed win81 32 bit with success, using these settings:

args: -cpu kvm64,+sep
bootdisk: virtio0
cores: 1
ide0: iso-template:iso/virtio-win-0.1-59.iso,media=cdrom,size=60572K
ide2: iso-template:iso/WindowsBlue-ClientwithApps-32bit-English-X1899604.iso,media=cdrom,size=2723468K
memory: 1024
name: win8.1-32
net0: virtio=6A:BE:03:9D:49:F4,bridge=vmbr0
ostype: win8
sockets: 1
virtio0: local:105/vm-105-disk-1.qcow2,format=qcow2,cache=writeback,size=32G

 

[gansc]

I just installed win81 32 bit with success, using these settings:

args: -cpu kvm64,+sep
bootdisk: virtio0
cores: 1
ide0: iso-template:iso/virtio-win-0.1-59.iso,media=cdrom,size=60572K
ide2: iso-template:iso/WindowsBlue-ClientwithApps-32bit-English-X1899604.iso,media=cdrom,size=2723468K
memory: 1024
name: win8.1-32
net0: virtio=6A:BE:03:9D:49:F4,bridge=vmbr0
ostype: win8
sockets: 1
virtio0: local:105/vm-105-disk-1.qcow2,format=qcow2,cache=writeback,size=32G

yes, 32bit works for me too. I will check 64 bit now.

 

[tom]

So far I got the 8.1 64 edition only running on a AMD box, and without virtio (on my intel test server I got boot loop with the 64-bit edition)

physical cpu: AMD Athlon II Neo N36L (HP microserver)

qm config 108

boot: cdn
bootdisk: ide1
cores: 1
cpu: host
ide1: local:108/vm-108-disk-1.qcow2,format=qcow2,cache=writeback,size=32G
ide2: nfs-mits1:iso/WindowsBlue-ClientwithApps-64bit-English-X1899605.iso,media=cdrom
memory: 1024
name: win81-64
net0: e1000=B6:3E:DB:FA:AE:F2,bridge=vmbr0
ostype: win8
sockets: 1

 

[brucecran]

It seems there's a problem with the kvm64 CPU type, because I found that when I switched to Nehelem the boot loop stopped. I've posted a message on Microsoft's forum - http://answers.microsoft.com/en-us/...cpu-type/b5c33704-e1a9-4315-a60a-1c26a25bd61a .

 

[brucecran]

It seems there's a problem with the kvm64 CPU type - I got around the boot loop by switching the CPU to emulate Nehalem.
(apologies for the double post - for some reason my original reply didn't show up)

 

[brucecran]

From the TechNet forums:

Windows 8.1 requires CMPXCHG16B

This also causes failures for Virtualbox:

http://4sysops.com/forums/topic/windows-server-2012-r2-on-virtual-box-error-0x000000c4/

I guess KVM64 emulates the very earliest x64 CPU which didn't have that instruction, so for Windows 8.1/Server 2012R2 we need to use a more modern CPU type.

 

[kk_proxmox]

chang the cpu type to host and try again

 

[greenvomit8]

Changing CPU type to Nehelem worked for me. Thank you : )

 

[rengiared]

the same problem as in 2012 R2
http://forum.proxmox.com/threads/16206-Windows-Server-2012-R2-and-0x0000005D-Error

hopefully sometime it will be solved with the default cpu type

 

[spirit]

the same problem as in 2012 R2
http://forum.proxmox.com/threads/16206-Windows-Server-2012-R2-and-0x0000005D-Error

hopefully sometime it will be solved with the default cpu type

they are a missing flag in kvm64 cpu def.

you can use qemu64.

(I'm going to add a patch for next proxmox release, to add the missing flag to kvm64 cpu def)

 

[rengiared]

that would be very nice, thank you

 

[blackpaw]

(I'm going to add a patch for next proxmox release, to add the missing flag to kvm64 cpu def)

Any chance of it arriving via updates?

When is the next release scheduled for and what will be in it? the roadmap stops at 3.1

Just curious, thanks.