Re: [gPXE-devel] COW Overlay in WinVBlock -- willing to implement

2011-05-22 Thread Kenton Varda
[bcc gpxe-devel] Sorry, I was under the impression that WinVBlock was considered part of the broader Etherboot project, for which gpxe-devel seemed to be the mailing list of record. Sometimes people get annoyed when I fail to CC their project's mailing list. :/ I was not aware of VHD. I spent

Re: [gPXE-devel] COW Overlay in WinVBlock -- willing to implement

2011-05-22 Thread Kenton Varda
I'm aware that I can set up COW on the server side, but I'd really rather that writes didn't cross the network at all. It's not uncommon for guests to want to install additional games which can be as much as 10GB each, and my machines have 60GB local SSDs which I'd like to utilize. In fact, longe

[gPXE-devel] COW Overlay in WinVBlock -- willing to implement

2011-05-22 Thread Kenton Varda
Hi Shao and gpxe-devel, In a post on this page you mentioned that you are planning to add COW overlay support to WinVBlock: http://reboot.pro/8168/page__st__300 I have a need for this (in order to netboot multiple machines off a common base image), and have not been able to find any existing no

Re: [gPXE-devel] COW Overlay in WinVBlock -- willing to implement

2011-05-04 Thread Miller, Shao
Pre-kernel: Perhaps you could do gPXE -> read-only iSCSI SAN -> MBR -> NTFS Partition -> NTLDR -> specially-crafted NTBOOTDD.SYS (for VHDs) -> "Master" VHD Post-kernel: MS iSCSI Initiator and Michael Brown's 'sanbootconf' driver re-establish the SAN. WinVBlock creates a new "child" VHD on a pa

Re: [gPXE-devel] COW Overlay in WinVBlock -- willing to implement

2011-05-04 Thread Miller, Shao
Good day, Kenton. I'm currently working on some serialization/deserialization code in order to simplify developing support for Microsoft's [acquired] VHD disk image format. Once implemented, the "differencing" feature of VHD image files will provide copy-on-write functionality. For example