Problem by changing Hosthardware -> Windows will have an Reboot after first start

[boospy]

Good day,

when i have an windows vm and i change the hosthardware, at first boot of the windows guest the vm will have an reboot. So it is possible to set options with vboxmange to set an generic hardware, so on bios, one cpu. Always the same.

Problem that us VMs are set to immutable. So the rebootquestions is on every new start of the guest.

We are using Virtualbox 5.0.24.

Thanks for help

[socratis]

i change the host hardware

From what to what? You must realize that "hardware" covers a lot of parameters. Be specific. Very specific.

the windows guest the vm will have an reboot

Reboot as in Windows-guest reboot, or VirtualBox abort and you have to reboot? I believe it's Windows, but please explain.

So it is possible to set options with vboxmange to set an generic hardware, so on bios, one cpu. Always the same.

Up to a point. Unless 1) you tell us what the problem is and 2) more importantly, what are you trying to do. Exactly.

Problem that us VMs are set to immutable.

Immutable means that it is fixed-in-time. The next time you shutdown and reboot the VM (not from within Windows, but from VirtualBox) the machine reverts to the fixed-in-time state. That means that if you change the hardware on an immutable system, in the next round you'll have to re-apply the hardware changes.

[boospy]

i change the host hardware

From what to what? You must realize that "hardware" covers a lot of parameters. Be specific. Very specific.

I changed for example from an AMD Dualcore to an Penium i5. So i copied the VM to another host. Dualcore have 4GB RAM, I5 have 8GB RAM, Dualcore was from Lenovo and i5 from HP. I found this in Docu, maybe this helps me: https://www.virtualbox.org/manual/ch08.html

Code: Select all

[--cpu-profile "host|Intel 80[86|286|386]"]
[--cpuid-portability-level <0..3>
[--cpuidset <leaf> <eax> <ebx> <ecx> <edx>]
[--cpuidremove <leaf>]
[--cpuidremoveall]
[--hardwareuuid <uuid>]

the windows guest the vm will have an reboot

Reboot as in Windows-guest reboot, or VirtualBox abort and you have to reboot? I believe it's Windows, but please explain.

At first start on an other machine an window pop up and ask, that windows have detected some changes and must reboot that the changes take effect.

So it is possible to set options with vboxmange to set an generic hardware, so on bios, one cpu. Always the same.

Up to a point. Unless 1) you tell us what the problem is and 2) more importantly, what are you trying to do. Exactly.

I would like to set the hardware like in qemu-kvm. I would like to set an generic Bios like SMBIOS in qemu, and a generic CPU like kvm64. Sorry, i know only this things with KVM.

Problem that us VMs are set to immutable.

Immutable means that it is fixed-in-time. The next time you shutdown and reboot the VM (not from within Windows, but from VirtualBox) the machine reverts to the fixed-in-time state. That means that if you change the hardware on an immutable system, in the next round you'll have to re-apply the hardware changes.

Yes.

[socratis]

I believe that you can do the move to the new host, change the VM's HD to normal, apply the changes, reboot, change the HD back to immutable. Problem solved.

Some other comments:

• It took me 15' to figure out that "Docu" is not a program that you download, it stands for Documentation. Tsk...
• I don't do Qemu or KVM. I wouldn't know what you're talking about.
• "cpu-profile": That's a relatively new one, but something doesn't sit right. I wouldn't want to set my VM to present a 80386 (at best) to the guest OS. Unless my guest is Windows Me.
• "cpuid-portability-level": I have no clue what it does or doesn't do. I believe it is used in teleporting, but I could be wrong.
• "cpuidset": It could lead to problems if set inaccurately, i.e. you could present capabilities that do not exist, or hide capabilities that are available.
• The "hardwareuuid" is not needed in your case. I wouldn't mess with it.

[socratis]

I found some more information about the different options, in the SDK reference:

• cpu-profile
• cpuid-portability-level
• cpuidset
• hardwareuuid

As you'll notice most of them are either experimental or subject to change. And they only appear on the Developer's documentation. That should be a hint of sorts

[michaln]

As people sometimes say, if you define a problem no one else has, you also have to figure out the solution no one else cares for.

[boospy]

Ok, thanks all. I need time to test all potential option. I give here a report when i have some answers. That what i can say now is that i'am searching for the old onvailable option "--synthcpu on". Here is an old example: http://peer.st/dw/doku.php?id=v_lizedla ... _maschinen