Re: Trouble with FTP install on virtual machine
On 09/15/2010 07:33 PM, li...@telus.net wrote: 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. Have you tried install48.iso (which includes the sets)? You should be able to get OpenBSD installed correctly, one that's done, you can test the network properly.
Re: Trouble with FTP install on virtual machine
On Sep 15, 2010, Mark (obsd) openbsd-l...@nerdish.us wrote: bsd 7% |**| 677 KB - stalled - At first glance, that symptom (stalled data transfers) looks really similar to something we battled earlier this year with our mail servers, wound up being a firewall (theirs) between us and another large company that was breaking TCP window scaling. It's been a while since I've fired up the bsd installer, I don't know if that ramdisk environment has the sysctl command or not? You can disable window scaling if it does, see if that helps things along. I'm running a rather old install right now which I'll be replacing when 4.8 releases, but on this old box it looks like the sysctl to turn off window scaling is net.inet.tcp.rfc1323=0 Hope that helps, or at least provides clues,Mark Thanks Mark. The sysctl command is present, but seems to support an abbreviated list of parameters. I do not get any error message if I try to set net.inet.tcp.rfc1323=0, but neither can I list the value of that parameter before or after. It appears that the set command is simply ignored. Your comments about firewalls were interesting, however, so I tried running the install from a different network (also behind NAT). The problem persisted, as it did when I tried connecting directly to my ISP with no intervening router or firewall. Hyper-V-Server also has its own firewall, but turning it off also did not help. I got to 100% downloading bsd, but then it just hung there at 'getting bsd.rd...'. I would welcome further suggestions anyone cares to offer. Thanks, Richard Koett.
Re: Trouble with FTP install on virtual machine
On Thu, Sep 16, 2010 at 1:03 PM, li...@telus.net wrote: I would welcome further suggestions anyone cares to offer. Is something stopping you from using install48.iso to install? http://ftp5.usa.openbsd.org/pub/OpenBSD/snapshots/i386/install48.iso I know that doesn't solve the problem, but at least that will get you to a fully functional OpenBSD install that you can try Mark's sysctl fix...
Re: Trouble with FTP install on virtual machine
On Sep 16, 2010, J Sisson sisso...@gmail.com wrote: Is something stopping you from using install48.iso to install? Installing via FTP is simply a habit I developed a long time ago (before an install ISO was made available). I just downloaded install48.iso and was able to get things running OK. I know that doesn't solve the problem, ... That's what I was thinking. If I install from CD, but there is still some underlying network issue, I may not end up with a server that performs as expected. I guess I'll just have to run it and see what happens. At this point I'm downloading src via anoncvs and it appears to be working normally. ... but at least that will get you to a fully functional OpenBSD install that you can try Mark's sysctl fix... Out of curiosity I gave that a try. It seems that sysctl is still limited as it was using cd48.iso. Thanks to all who offered advice with this and, as always, to the developers who make it all possible. :)
Re: Trouble with FTP install on virtual machine
On Thu, 16 Sep 2010 13:59:07 -0600 (MDT) li...@telus.net wrote: On Sep 16, 2010, J Sisson sisso...@gmail.com wrote: Is something stopping you from using install48.iso to install? Installing via FTP is simply a habit I developed a long time ago (before an install ISO was made available). I just downloaded install48.iso and was able to get things running OK. I know that doesn't solve the problem, ... That's what I was thinking. If I install from CD, but there is still some underlying network issue, I may not end up with a server that performs as expected. I guess I'll just have to run it and see what happens. At this point I'm downloading src via anoncvs and it appears to be working normally. ... but at least that will get you to a fully functional OpenBSD install that you can try Mark's sysctl fix... Out of curiosity I gave that a try. It seems that sysctl is still limited as it was using cd48.iso. Thanks to all who offered advice with this and, as always, to the developers who make it all possible. :) You could try downloading the image or sets (smaller) in their entirety to a small partition and then install using local. Can't imagine that your disk would pause the connection at 644kb of the kernel which it's not decompressing, but if you got to 100%, then it's certainly worth a go. You may also get a useful message or more ftp options to try. Use /mnt3 or something cos the installer uses /mnt
Trouble with FTP install on virtual machine
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.
