Hi Karen, * Karen Tung (Karen.Tung at Sun.COM) wrote: > Glenn Lagasse wrote: >> No, you've summed it up quite nicely. If the user provides a >> pre-configured VM (barring any misconfiguration like not enough RAM, >> DISK or incorrect network settings which ought to be fun to try and >> figure out a solution to detect if it's even possible) then all we need >> to do is captured in your list. >> >> Cheers, >> >> > Hi Glenn, > > Now that you mentioned some of the potential issues with a self incorrectly > configured VM, and how it would be hard for us to detect that, > I wonder whether it would have any value to even provide that as > an option for the user. > > If we were the one to create the VM, at least, we know the settings we > want to set are valid, and if the CLI command to create such a VM with > our options are failing, at least, we can immediately fail and not > continue trying to boot the ISO with a "bad" VM.
Self configuring the VM is a tricky proposition. What do we use as defaults? Default settings that work for say something like installing the liveCD equivalent might not work so well if you've added a lot more packages to the default list let's say. Also, I can very easily imagine appliance creators wanting to have some say over what the size of the virtual disk and ram in the virtual machine are set to. I think we need to have a 'default' vm configuration, likely something tuned to the liveCD. But I think we also need to allow people to plug in their own VM that they've configured for the times when our defaults don't match what they need/want. Cheers, -- Glenn
