Actually, this question is whether I should use a virtual machine to remaster a distro. I want to remaster a certain DVD-sized distro into a CD-sized version of itself. But to do that, normally I would have to go to the store and buy a pack of DVD-Rs, and before doing that, I will try to "cheat" that by running the liveCD ISO in a virtual machine, installing it on the virtual hard drive, and then remastering it.

I'm just wondering if remastering inside a virtual machine would create any complications that would interfere with remastering.

A virtual machine is just fine for this.
Which complications would you expect?

A virtual machine for the most part is just as if you had a standalone computer available. This is a great way to test and hobby and diag some idea you have without danger to the host OS. I use VM's all the time to do tasks that I'm afraid would bork my install.

However the issue is more of the ability to do what you want over the ability of a VM to do it I'd think.

Possibly relating to a lack of memory in the virtual machine; and I vaguely thought the use of virtual machine hardware and software drivers might make a difference. That if I installed the liveCD ISO to the virtual hard drive, the virtual video hardware might cause the liveCD to use a different video driver than it would if it were my physical computer. If it did that, would my remastered copy expect to use the same driver on my real computer?

You might have done that by mistake, but more likely, you're commenting on my duplicate post. Did you consider that my duplicate post might have been inadvertent?

The double post was accidental, we had some problems with double posts for a short while.
Back to topic, no, the drivers that are used in the VM will not affect the live-CD after you are done with remastering, unless you explicitly configured the live-CD to do so, for example with a custom xorg.conf. Almost any Linux system (actually, I don't know of one that doesn't) will scan the hardware on boot and load the appropriate drivers, unless you explicitly tell it to not do so.

1 members found this post helpful.

For anyone who looks up this post: I was just doing this (and looked up my old post on the subject first), and figured out that the 256 MB of virtual RAM assigned by default is inadequate for remastering inside the virtual machine. It kept freezing on me, or displaying a blank black screen I couldn't get out of, until I quit and tried increasing the memory to 512 MB. The problem immediately disappeared.

Probably the best argument for using a virtual machine – with an adequate amount of RAM, of course – would simply be that "now you can test the result!"

Having made the new disks, you're obviously going to need to be able to test them to see if it works. Well, you can now very-easily create a brand new virtual machine for testing purposes, alongside the one that you used to make it. (And just wipe the sucker out and make a new one, as many times as necessary, until you finally do get it right.)