Thank you for the info.
On 8/14/2016 8:23 PM, jd1008 wrote:
Some things you might want to know:
1. When you boot windows on the real HW, it creates a HW profile,
let's name it X.
2. When you configure the windows partition (Under Linux) to be a
drive for a VBox VM,
and you boot that machine, then windows will detect that it is
running on different HW
than original HW profile, and will ask for a different installation
key, else it will
declare your windows under VBOx VM to be an illegal copy.
That's what happened to me and other colleagues.
While I have not tried to run vbox under fedora since for me that would
be running a vm in a vm; I've copied, moved, modified, cloned, and even
upgraded vm's running w7 to w10 successfully on both vbox 4x & 5x all
w/o degrading windows activation and across substantially different
hardware and even with Windows Server os's. It's a matter of keeping
track of & managing the machine uuid which is what vbox uses to report
hw to Windows and what Windows reads to determine whether or not
substantial changes have been made to hw. So I'm hoping copying my
existing windows vm files to a fedora vbox environment will give me
similar results as long as I follow the same approach should the need
I've never had the need or inclination to virtualize a hardware
installed Windows environment since I've always had enough legitimate
Windows licenses to use or play with so I don't know how that impacts
Windows activation. However I would not need to take that approach
should my former method work well.