I hope it's not inappropriate to ask about VM's in this forum. If anyone cares to offer some advice, here's what I'm having trouble with:
I've created a virtual computer on Windows Hyper-V Server 2008 R2. I'm trying to install -current via FTP or HTTP. I can boot from either floppy48.fs or cd48.iso. The virtual NIC is detected as de0. Basic network functionality seems to be working. I can ping hosts by name, for example. I can proceed through the installation, partition the virtual disk and so on, until I get about this far: Location of sets? (cd disk ftp http or 'done') [cd] ftp HTTP/FTP proxy URL? (e.g. 'http://proxy:8800', or 'none') [none] Server? (hostname, list#, 'done' or '?') [ftp.OpenBSD.org] ftp5.usa.openbsd.org Server directory? [pub/OpenBSD/snapshots/i386] Login? [anonymous] Select sets by entering a set name, a file name pattern or 'all'. De-select sets by prepending a '-' to the set name, file name pattern or 'all'. Selected sets are labelled '[X]'. [X] bsd [X] etc48.tgz [X] game48.tgz [X] xfont48.tgz [X] bsd.rd [X] misc48.tgz [X] xbase48.tgz [X] xserv48.tgz [ ] bsd.mp [X] comp48.tgz [X] xect48.tgz [X] xbase48.tgz [X] man48.tgz [X] xshare48.tgz Set names(s)? (or 'abort' or 'done') [done] bsd 7% |** | 677 KB - stalled - I've tried this with a few different mirrors. Sometimes it got a bit farther before stalling. Sometimes it times out completely. I'm guessing that the 'legacy' virtual NIC (de0) is at fault, but I don't know what (if anything) I might do about it. I can see from searching online that other people have succeeded with OpenBSD on virtual machines. Has anyone here tried on a Hyper-V server? Any advice would be appreciated. Thanks, Richard Koett.
