I have proceeded with the same VM installation process that I used for TW and used the Win 10 iso. When I get to the point where I have to customize the installation I have retained the Q35 chipset for now but am stuck on which Firmware I should select from the dropdown. I have tried but it takes me to a shell.
Which should I use, ie that which relates to the host or that which relates to the guest. I had assumed /ovmf-x86_64-ms-code.bin but this landed me in a shell.
I do have swtpm installed but it seems too old:-
alastair@HP-Z640-1:~> swtpm --version
TPM emulator version 0.5.3, Copyright (c) 2014 IBM Corp.
That’s the correct firmware, it’s because you need to set the boot options in the virtual machine to set the windows dvd to be first in the boot order, or when you see the TianoCore logo press the esc key to get to the virtual machine BIOS and boot from the windows iso image.
I succeeded in installing Windows 10 Pro on my VM host but it ran quite slowly with the defaults so I thought I would install it again, for practice, rather than adjust the VM that had been built.
It took me half a dozen tries before I could complete another machine. Apart from my errors of omission when I reached the point where I had to select a drive for the installation nothing was shown whereas first time round I was offered the right drive.
Also if I didn’t press a key at the beginning to start it kept reverting to shell, so rather more messing about than I had anticipated. It might be worth while turning your instructive pdf into a sticky for folk like me!
Not sure why the glitches but will now have a go at Windows 11
My Windows 11 VM is not yet running.
In all cases I have to press a key once the installation is started or I get returned to a shell not the boot screen options.
More importantly I seek some more help with the TPM. I had thought that since my machine was already running a secure boot and the TPM emulator was installed that all I would have to do in following the Win 11 thread would be to change the chipset to i440FX. Didn’t make any difference. Clearly I have to edit the XML file of the machine and I need guidance, not least because the XML editing is disabled in Preferences and I have no idea which “Preferences” are referred to.
The suggested edit I see is:-
That has nailed it and installation is proceeding.
I really do appreciate this and am sure that others will too.
The details I had to be sure to include were:-
Selecting any key at start or system reverted to shell.
Selecting the disk driver for the virtual disk
Adding this TPM.
So many options I could fiddle with now I am looking at such a big system but have started with 8192 GB and 6 cores as before.
If all goes smoothly I shall start on the servers.
Will report later.
Mine just activated, I might have pressed the troubleshooting button on WinXI. That’s why suggested to just install WinX to start with, the TPM 2.0 option will allow you to upgrade, if and when you decide to.
Just returned to this to look at activation. I have two VMs set up, one W10 and the other VMXI but named W10-2 from your link help.
I cannot activate W10 VM. It seems that I should check my activation on the native HP W10 system and use M$ account. Is that what you did or is there another way?
All this is still familiarization for when I use W10 VM for work on IBM Leap 15.3 server. It may be fun as the old machine which replaces it is a home brew from many years ago with a Win 7 Pro which has been upgraded over the years. I still have the disk and license so it is worth a try but still just learning and getting familiar with VMs.!
Maybe you will need to disconnect the current drives and put in a temp drive and install Windows 10 Pro and get the code? I’ve only ever used offline account with Windows, for Home versions when it gets to that point I just unplug the network cable go back, then forward and it lets you add an offline account.
An existing and activated Win 7 system will upgrade to WinX without any issues, now drivers are a different kettle of fish, for example my USB serial cable driver would not play nice, had to do some regedit foo to get it to stop upgrading (like a package lock) the driver.
Hi, been distracted by various work crises but am now seeking to advance with using Win10 in work environment but as VM on one of my servers.
I have inadvertently run into a problem with activation. When I was learning how to use VM I practised on the HP Z640 machines and went so far as to set up the M$ cloud because we use this in the office.
Not surprisingly this has now linked my Windows installation to these HP machines, even though I used my original Win7 disks and keys during the initial installation.
Unfortunately now I am unable to set up and activate on the IBM servers because I cannot de-activate the HP machines. I have no idea if the activation process used actually referred to the Win 7 key I used or the HP built in keys but I am stuck with unwanted activation capability.
It would be really difficult to play with disk drives on the IBM servers as they are all in cage RAID arrays and it would be cheaper just to buy another oem win7 CD but thought I would ask if there are any other options. I appreciate I have only myself to blame but thought I would ask as there are some suggestions for removing activation keys. Just don’t want to damage the HP machines.
Any thoughts would be appreciated.
I probably didn’t need to use my disk but I was rehearsing for using the IBM which doesn’t have any windoze hardware. My mistake, should have gone straight to IBM but hindsight is two pence a ton!
Will see if I can contact M$ when I have time. Thanks for the the reply.