Date: Thu, 15 Oct 2009 10:09:41 +0800 From: Alex Jurkiewicz <alex@bluebottle.net.au> To: Tim Judd <tajudd@gmail.com>, freebsd-questions@freebsd.org Subject: Re: restore(8)ing new / -- boots on metal but not in a VM Message-ID: <98ac902a0910141909j5a359940j7006eecb15fd05cd@mail.gmail.com> In-Reply-To: <ade45ae90910131142j12a6b257i7216f007b38adfb4@mail.gmail.com> References: <98ac902a0910120214m29d299b5o6aa58fdba45c9f95@mail.gmail.com> <ade45ae90910121153u4dddaf25ofbee2a1ef984a4f3@mail.gmail.com> <98ac902a0910121745h204124ear51139091572676f3@mail.gmail.com> <ade45ae90910131142j12a6b257i7216f007b38adfb4@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2009/10/14 Tim Judd <tajudd@gmail.com>: > My suggestion is to check the VM config and see if you can emulate an > IDE ad(4) device instead of the possible SCSI da(4) device that > vmware/virtualbox may setup. =C2=A0I'm almost positive (not 100% because = I > don't have either one of those installed at the moment) that both > those products default to a SCSI device. Both are capable of emulating IDE, and both can offer something that FreeBSD uses the da driver for (SATA for Vbox, SCSI for Vmware). I've tested with both ad and da drives on both solutions. Creating a dump image fresh in a VM gives me a file I can restore from and boot successfully in VMs. I haven't tested physical machines yet -- if I can boot physical machines off this new dump file my problems are solved. If not... At this point it seems simplest to produce a few different versions of my dump image. Chances there's just something different in the first few sectors of the disk, but having a single dump image and multiple first sectors for the image seems more complex overall. Thanks for the help, AJ
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?98ac902a0910141909j5a359940j7006eecb15fd05cd>