Glenn Lagasse wrote: > Hey Ethan, > > * Ethan Quach (Ethan.Quach at Sun.COM) wrote: > >>> No. Setting up the VM is very much specific to VB. >>> >> Yes, but with #3, we're rolling that off to the user right? >> >> I might be over simplifying here, but if the user is providing >> a fully configured VM, what are the remaining interactions >> VMConstruction has with the VM? >> >> 1. Telling it to boot, with some ISO file we provide. >> 2. Catching when its done/halted. >> 3. Locating its disk file. >> .... >> .. >> >> These are pretty primative; but what else is there? I'm just >> exploring here... >> > > 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. >
Then (with #3) isn't VMConstruction closer to being virt software agnostic than we think? -ethan
