Windows 7 x64 install failed at startnet.cmd

[satoru]

Hi all,
I'm evaluating opsi 4.0.3.1 on CentOS6.5 and installing Windows 7 64bit on CentOS6.5/KVM VM with openQRM5.1.2.
I setup opsi as instructed on P.40-51 of opsi-getting-started-stable-en.pdf, then VM is rebooted from opsi successfully.

However console showed up error as below:
X:¥Windows¥System32>c:¥opsi¥startnet.cmd
The system can not find the path specified.

There is no c: drive mounted on the system.
Why it runs on X: drive and am I wrong to configure something on opsi?

Any suggestions would be greatly appreciated.
Regards,
Satoru Funai

[n.wenselowski]

Hallo satoru,

did you modify the WinPE as instructed in the getting started? (Sorry, I do only have a version without pages here atm )

The missing file is created by opsi from the bootimage.
Maybe your bootimage.log contains some hints if something went wrong.

With kind regards

Niko

[satoru]

Hi Niko
I have not made modification on wimpe. Is it needed to change boot drive to c: from current x:?
Thanks and regards,
Satoru

[satoru]

Hi again,
I would like to know that startnet.cmd runs on x: drive is wrong behavior?
If it is right behavior , the problem should be c: drive is not mounted correctly.
Regards,
Satoru

[n.wenselowski]

Hello saturo,

as far as I know X: is some sort of RAMDISK in the WinPE.
That should be correct. Windows should be installed on C:.

My guess here is that the problem you experience comes from the storage drivers in your WinPE and that they are not able to mount the harddisk. You now have the possibilty of changing how your Harddisk is emulated (I run KVM myself and emulate harddisks for Windows mostly as IDE), you can try to integrate the proper drivers into you WinPE (there was a project that tried to provide proper Windows drivers for KVM, should be found through $yourfavouritesearchengine) or you can try to use a non-virtualized client. But be aware that the use of non-virtualized hardware can lead to similar issues if the hardware itself requires special drivers.


With kind regards,

Niko

[satoru]

Thanks for your answer!
I tried again with virtio driver, but still failed as same phenomenon.
I installed virtio drivers as below;
1. downloaded the latest virtio-win from http://alt.fedoraproject.org/pub/alt/virtio-win/latest/
2. Created winpe image for win7-x64 on my test Windows7 machine by WAIK
3. Add drivers
> dism /Mount-Wim /WimFile:C:\winpe\ISO\sources\boot.wim /index:1 /MountDir:c:\winpe\mount
> dism /Image:C:\winpe\mount /Add-Driver /Driver:C:\WLH\AMD64 /Recurse
> dism /Unmount-Wim /MountDir:c:\winpe\mount /Commit
Then Copied the directory C:\winpe\ISO with the target name winpe to /opt/pcbin/install/win7-x64.
run opsi-setup --set-rights /opt/pcbin/install/win7-x64 on opsi server.

Also I tried virtio drivers both of WIN7/AMD64 and WLH(W2k8)/AMD64, but failed.

Executed command line DISKPART and LIST VOLUME on Winpe command window,
It shows only empty D:drive (CD-ROM) and no C: drive.

Any ideas?
regards,
Satoru Funai

[n.wenselowski]

Hello satoru,

please try to emulate your disks as SATA or IDE and check if the problem still exists.


Kind regards

Niko

[satoru]

Hi Niko,
Could you tell me how to emulate disks as SATA or IDE, please?
Thanks in advance,
Satoru

[n.wenselowski]

Hello satoru,

Could you tell me how to emulate disks as SATA or IDE, please?

I am running virt-manager for managing my machines. There you can just specify it in the advanced options. See http://imgur.com/82PXF1O
Another way probably is to edit the config files for your machines.


Kind regards

Niko