cant start Win7 installation

sunghost

Active Member
May 27, 2011
146
1
38
solved: cant start Win7 installation

Hello,
i installed a fresh squeeze and proxmox 2.0. After uploaded the .iso for installation and setup a new vm, i cant start it.
/var/log/syslog
Feb 8 15:38:01 pserver01 pvedaemon: start failed: command '/usr/bin/kvm -id 100 -chardev 'socket,id=monitor,path=/var/run/qemu-server/100.mon,server,nowait' -mon 'chardev=monitor,mode=readline' -vnc unix:/var/run/qemu-server/100.vnc,x509,password -pidfile /var/run/qemu-server/100.pid -daemonize -usbdevice tablet -name pserver01a -smp 'sockets=1,cores=1' -nodefaults -boot 'menu=on' -vga std -tdf -localtime -rtc-td-hack -k en-us -drive 'file=/var/lib/vz/iso/template/iso/win7_professional_x64.iso,if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=device-ide2,bootindex=200' -drive 'file=/var/lib/vz/images/100/vm-100-disk-1.raw,if=none,id=drive-ide0,aio=native,cache=none' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=device-ide0,bootindex=100' -m 2048 -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge' -device 'rtl8139,mac=C6:A9:7A:60:BB:58,netdev=net0,bus=pci.0,addr=0x12,bootindex=300' -cpuunits 1000' failed: exit code 1
Feb 8 15:38:01 pserver01 pvedaemon[2744]: <root@pam> end task UPIDserver01:0000151C:00091A5A:4F3288C9:qmstart:100:root@pam: start failed: command '/usr/bin/kvm -id 100 -chardev 'socket,id=monitor,path=/var/run/qemu-server/100.mon,server,nowait' -mon 'chardev=monitor,mode=readline' -vnc unix:/var/run/qemu-server/100.vnc,x509,password -pidfile /var/run/qemu-server/100.pid -daemonize -usbdevice tablet -name pserver01a -smp 'sockets=1,cores=1' -nodefaults -boot 'menu=on' -vga std -tdf -localtime -rtc-td-hack -k en-us -drive 'file=/var/lib/vz/iso/template/iso/win7_professional_x64.iso,if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=device-ide2,bootindex=200' -drive 'file=/var/lib/vz/images/100/vm-100-disk-1.raw,if=none,id=drive-ide0,aio=native,cache=none' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=device-ide0,bootindex=100' -m 2048 -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge' -device 'rtl8139,mac=C6:A9:7A:60:BB:58,netdev=net0,bus=pci.0,addr=0x12,bootindex=300' -cpuunits 1000' failed: exit code 1
Feb 8 15:38:07 pserver01 pvedaemon[5435]: start VM 100: UPIDserver01:0000153B:00091C9A:4F3288CF:qmstart:100:root@pam:
Feb 8 15:38:07 pserver01 pvedaemon[2744]: <root@pam> starting task UPIDserver01:0000153B:00091C9A:4F3288CF:qmstart:100:root@pam:
Feb 8 15:38:07 pserver01 pvedaemon[5435]: start failed: command '/usr/bin/kvm -id 100 -chardev 'socket,id=monitor,path=/var/run/qemu-server/100.mon,server,nowait' -mon 'chardev=monitor,mode=readline' -vnc unix:/var/run/qemu-server/100.vnc,x509,password -pidfile /var/run/qemu-server/100.pid -daemonize -usbdevice tablet -name pserver01a -smp 'sockets=1,cores=1' -nodefaults -boot 'menu=on' -vga std -tdf -localtime -rtc-td-hack -k en-us -drive 'file=/var/lib/vz/iso/template/iso/win7_professional_x64.iso,if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=device-ide2,bootindex=200' -drive 'file=/var/lib/vz/images/100/vm-100-disk-1.raw,if=none,id=drive-ide0,aio=native,cache=none' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=device-ide0,bootindex=100' -m 2048 -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge' -device 'rtl8139,mac=C6:A9:7A:60:BB:58,netdev=net0,bus=pci.0,addr=0x12,bootindex=300' -cpuunits 1000' failed: exit code 1
Feb 8 15:38:07 pserver01 pvedaemon[2744]: <root@pam> end task UPIDserver01:0000153B:00091C9A:4F3288CF:qmstart:100:root@pam: start failed: command '/usr/bin/kvm -id 100 -chardev 'socket,id=monitor,path=/var/run/qemu-server/100.mon,server,nowait' -mon 'chardev=monitor,mode=readline' -vnc unix:/var/run/qemu-server/100.vnc,x509,password -pidfile /var/run/qemu-server/100.pid -daemonize -usbdevice tablet -name pserver01a -smp 'sockets=1,cores=1' -nodefaults -boot 'menu=on' -vga std -tdf -localtime -rtc-td-hack -k en-us -drive 'file=/var/lib/vz/iso/template/iso/win7_professional_x64.iso,if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=device-ide2,bootindex=200' -drive 'file=/var/lib/vz/images/100/vm-100-disk-1.raw,if=none,id=drive-ide0,aio=native,cache=none' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=device-ide0,bootindex=100' -m 2048 -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge' -device 'rtl8139,mac=C6:A9:7A:60:BB:58,netdev=net0,bus=pci.0,addr=0x12,bootindex=300' -cpuunits 1000' failed: exit code 1
Feb 8 15:38:37 pserver01 pvedaemon[5530]: start VM 100: UPID:pserver01:0000159A:00092861:4F3288ED:qmstart:100:root@pam:
Feb 8 15:38:37 pserver01 pvedaemon[2747]: <root@pam> starting task UPIDserver01:0000159A:00092861:4F3288ED:qmstart:100:root@pam:
Feb 8 15:38:37 pserver01 pvedaemon[5530]: start failed: command '/usr/bin/kvm -id 100 -chardev 'socket,id=monitor,path=/var/run/qemu-server/100.mon,server,nowait' -mon 'chardev=monitor,mode=readline' -vnc unix:/var/run/qemu-server/100.vnc,x509,password -pidfile /var/run/qemu-server/100.pid -daemonize -usbdevice tablet -name pserver01a -smp 'sockets=1,cores=1' -nodefaults -boot 'menu=on' -vga std -tdf -localtime -rtc-td-hack -k en-us -drive 'file=/var/lib/vz/iso/template/iso/win7_professional_x64.iso,if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=device-ide2,bootindex=200' -drive 'file=/var/lib/vz/images/100/vm-100-disk-1.raw,if=none,id=drive-ide0,aio=native,cache=none' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=device-ide0,bootindex=100' -m 2048 -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge' -device 'rtl8139,mac=C6:A9:7A:60:BB:58,netdev=net0,bus=pci.0,addr=0x12,bootindex=300' -cpuunits 1000' failed: exit code 1
Feb 8 15:38:37 pserver01 pvedaemon[2747]: <root@pam> end task UPIDserver01:0000159A:00092861:4F3288ED:qmstart:100:root@pam: start failed: command '/usr/bin/kvm -id 100 -chardev 'socket,id=monitor,path=/var/run/qemu-server/100.mon,server,nowait' -mon 'chardev=monitor,mode=readline' -vnc unix:/var/run/qemu-server/100.vnc,x509,password -pidfile /var/run/qemu-server/100.pid -daemonize -usbdevice tablet -name pserver01a -smp 'sockets=1,cores=1' -nodefaults -boot 'menu=on' -vga std -tdf -localtime -rtc-td-hack -k en-us -drive 'file=/var/lib/vz/iso/template/iso/win7_professional_x64.iso,if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=device-ide2,bootindex=200' -drive 'file=/var/lib/vz/images/100/vm-100-disk-1.raw,if=none,id=drive-ide0,aio=native,cache=none' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=device-ide0,bootindex=100' -m 2048 -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge' -device 'rtl8139,mac=C6:A9:7A:60:BB:58,netdev=net0,bus=pci.0,addr=0x12,bootindex=300' -cpuunits 1000' failed: exit code 1
Setup: 2GB RAM, 1CPU, rtl8139, ide disk no cache
 
Last edited:

tom

Proxmox Staff Member
Staff member
Aug 29, 2006
14,054
490
103
you got the latest packages installed? post the output of 'pveversion -v'
 

sunghost

Active Member
May 27, 2011
146
1
38
i think so.
pveversion -v
pve-manager: not correctly installed (pve-manager/2.0/16283a5a)
running kernel: 2.6.32-6-pve
pve-kernel-2.6.32-6-pve: 2.6.32-55
lvm2: 2.02.88-2pve1
clvm: not correctly installed
corosync-pve: 1.4.1-1
openais-pve: 1.1.4-1
libqb: 0.6.0-1
redhat-cluster-pve: not correctly installed
pve-cluster: not correctly installed
qemu-server: not correctly installed
pve-firmware: 1.0-14
libpve-common-perl: 1.0-11
libpve-access-control: not correctly installed
libpve-storage-perl: not correctly installed
vncterm: 1.0-2
vzctl: not correctly installed
vzprocps: 2.0.11-2
vzquota: 3.0.12-3[
 

tom

Proxmox Staff Member
Staff member
Aug 29, 2006
14,054
490
103
no, this looks not ok.
 

sunghost

Active Member
May 27, 2011
146
1
38
here are the correct output
pveversion -v
pve-manager: 2.0-18 (pve-manager/2.0/16283a5a)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 2.0-55
pve-kernel-2.6.32-6-pve: 2.6.32-55
lvm2: 2.02.88-2pve1
clvm: 2.02.88-2pve1
corosync-pve: 1.4.1-1
openais-pve: 1.1.4-1
libqb: 0.6.0-1
redhat-cluster-pve: 3.1.8-3
pve-cluster: 1.0-17
qemu-server: 2.0-13
pve-firmware: 1.0-14
libpve-common-perl: 1.0-11
libpve-access-control: 1.0-5
libpve-storage-perl: 2.0-9
vncterm: 1.0-2
vzctl: 3.0.29-3pve8
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-1
ksm-control-daemon: 1.1-1
 

sunghost

Active Member
May 27, 2011
146
1
38
Now i tried again and looked at the youtube howto for 2008 server. i used the same settings, but instead auf nfs i used the default image store. now i see the vm in the images folder, but cant start it nor delete it. damn not self explain system, the 1.9 was easy for starting.
 

tom

Proxmox Staff Member
Staff member
Aug 29, 2006
14,054
490
103
works here. if you cannot start a VM you will get an error message.
 

sunghost

Active Member
May 27, 2011
146
1
38
which settings for win7 64bit? my last try, with configuratino from the 2008 youtube clip, ends au with an entry in the iso or local storage with no possibility to start or remove. the first try creates an vm entry an the same level as the iso and local store. i hate the id thing to, why not automatic..?
 

tom

Proxmox Staff Member
Staff member
Aug 29, 2006
14,054
490
103
if you do not want to learn a new system do not try a beta system - win7 works great so you are doing obviously something wrong - see again the existing docs and the demo tutorials on YouTube.

please respect the forum rules, be always friendly and deeply grateful for all help is given to you from other people.
 

sunghost

Active Member
May 27, 2011
146
1
38
You are right. Sorry iam a bit frustrated. I search in the web and here but i cant create the win7 vm. why will the new vm shown in the storage? what are the settings to get it run?
 

tom

Proxmox Staff Member
Staff member
Aug 29, 2006
14,054
490
103
I do not get you issue, pls make a screenshot to show it here.
 

sunghost

Active Member
May 27, 2011
146
1
38
For sure:
win7_error.JPG

This is what i see, after creating an vm with settings from the 2008 vid.
 

tom

Proxmox Staff Member
Staff member
Aug 29, 2006
14,054
490
103
no error here. this is the view of the storage, showing the new disk.
 

sunghost

Active Member
May 27, 2011
146
1
38
why new disk? i clickt on the button for new vm, top right, ??? if i choose ide and realtek i get a real vm pc on the left. it was in 1.9 easier to create a vm.
 

tom

Proxmox Staff Member
Staff member
Aug 29, 2006
14,054
490
103
if you create a new VM, also new disk virtual disk is created as you specified it on the create wizard - how should it work without it?
 

sunghost

Active Member
May 27, 2011
146
1
38
Thats right and ok, but where is the real vm after creation? when i understand you correct, i see the new virtual disk of my vm, but where is the machine to start up?
 

sunghost

Active Member
May 27, 2011
146
1
38
Thx, embarressing. I thougt i checked that. damn.
Ok, now i get the same as on top of my post:
Could not access KVM kernel module: No such file or directory
failed to initialize KVM: No such file or directory
No accelerator found!
TASK ERROR: start failed: command '/usr/bin/kvm -id 100 -chardev 'socket,id=monitor,path=/var/run/qemu-server/100.mon,server,nowait' -mon 'chardev=monitor,mode=readline' -vnc unix:/var/run/qemu-server/100.vnc,x509,password -pidfile /var/run/qemu-server/100.pid -daemonize -usbdevice tablet -name win7_prof64_01 -smp 'sockets=2,cores=1' -nodefaults -boot 'menu=on' -vga std -tdf -localtime -rtc-td-hack -k en-us -drive 'file=/var/lib/vz/iso/template/iso/win7_professional_x64.iso,if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=device-ide2,bootindex=200' -drive 'file=/var/lib/vz/iso/images/100/vm-100-disk-1.raw,if=none,id=drive-virtio0,aio=native,cache=none' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100' -m 2048 -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,vhost=on' -device 'virtio-net-pci,mac=36:9B:CF:98:FD:26,netdev=net0,bus=pci.0,addr=0x12,bootindex=300'' failed: exit code 1
and
kvm hardwarevirtualisation is enabled and vt in the hostbios too
and
lsmod | grep kvm
kvm 304681 0
modprobe kvm-intel
FATAL: Error inserting kvm_intel (/lib/modules/2.6.32-6-pve/kernel/arch/x86/kvm/kvm-intel.ko): Operation not supported
Damn again, i thought it was enabled in the bios, but it wasn. Now the vm starts, but i cant connect via the console:
no connection : Connection timed out
TASK ERROR: command '/bin/nc -l -p 5900 -w 10 -c '/usr/sbin/qm vncproxy 100 2>/dev/null'' failed: exit code 1
now i found out, that the image was corrupt, take the cd and it boots, but no win7 install didnt find a valid disk?!
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!