IBCS2 regression in FreeBSD 5??
Rich Naill
We have been using FREEBSD 4.x now 4.11 for several years.
Running old Altos binaries with ibcs2 emulation.
Starting with BSD 5.x thur 8.x the binarys will not run anymore using ibcs2.
See problem report 156353
Also references to ibcs2 regression in FreeBSD 5
We would very much like to get this corrected $$$
Any help would be great
Rich Naill
Enterprise Systems Inc
616-243-9883
ri...@enterprisesystems.net
_______________________________________________
freebsd-...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulat...@freebsd.org"
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-...@muc.de
Kostik Belousov
> Hello,
>
> We have been using FREEBSD 4.x now 4.11 for several years.
>
> Running old Altos binaries with ibcs2 emulation.
>
> Starting with BSD 5.x thur 8.x the binarys will not run anymore using ibcs2.
>
> See problem report 156353
>
> Also references to ibcs2 regression in FreeBSD 5
>
> We would very much like to get this corrected $$$
>
> Any help would be great
FreeBSD 5.x is too old to be interested.
Can you test on HEAD or at least stable/8 ?
Can you provide a self-contained test binary and clear description
what does not work ?
Ted Mittelstaedt
> On Wed, Jul 20, 2011 at 09:53:21AM -0400, Rich Naill wrote:
>>
>> We have been using FREEBSD 4.x now 4.11 for several years.
>>
>> Running old Altos binaries with ibcs2 emulation.
>>
>> Starting with BSD 5.x thur 8.x the binarys will not run anymore using ibcs2.
>>
According to the following:
http://www.freebsd.org/cgi/query-pr.cgi?pr=73978
ibcs2 was running under FreeBSD 5.3-release. I think you need to
review all of the PR reports, the closed ones too.
Ted
>> See problem report 156353
>>
>> Also references to ibcs2 regression in FreeBSD 5
>>
>> We would very much like to get this corrected $$$
>>
>> Any help would be great
>
> FreeBSD 5.x is too old to be interested.
>
> Can you test on HEAD or at least stable/8 ?
> Can you provide a self-contained test binary and clear description
> what does not work ?
_______________________________________________
Julian H. Stacey
cc freebsd-...@freebsd.org
,
Reference:
> From: "Rich Naill" <ri...@enterprisesystems.net>
> Date: Wed, 20 Jul 2011 09:53:21 -0400
> Message-id: <62358EEA788F4379AD461DBC5D721039@COMPAQGR>
"Rich Naill" wrote:
> Hello,
>
> We have been using FREEBSD 4.x now 4.11 for several years.
>
> Running old Altos binaries with ibcs2 emulation.
>
> Starting with BSD 5.x thur 8.x the binarys will not run anymore using ibcs2.
>
> See problem report 156353
>
> Also references to ibcs2 regression in FreeBSD 5
>
> We would very much like to get this corrected $$$
............................................... ^^^
If '$$$' is an indication your company wants to pay a FreeBSD person
at commercial rates to solve its's problem,
here's a world wide geographic indexed list of FreeBSD consultants:
http://berklix.com/consultants/
& please cc freebsd-...@freebsd.org as some on list would probably
be interested.
> Any help would be great
>
> Rich Naill
>
> Enterprise Systems Inc
> 616-243-9883
> ri...@enterprisesystems.net
Cheers,
Julian
--
Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com
Reply below, not above; Indent with "> "; Cumulative like a play script.
Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable.
Ted Mittelstaedt
While I will be among the first to say that FreeBSD is often used
in this capacity (serving as a base for a commercial product), it
would be - in my opinion - a far better use of money to pay a
developer to write a FreeBSD application that would run on FreeBSD
8 and duplicate whatever functionality that this antique
SCO program is doing.
FreeNSD 4.X runs great under VirtualBox and that is probably what
the OP should be doing. I also happen to have a FreeBSD 8 system
that has a VirtualBox session running FreeBSD 4 that an older program
is running in.
Ted
_______________________________________________
Joe Sciulli
I'm trying to do the same thing on FreeBSD, and found the undocumented and deprecated command still works:
VBoxManage internalcommands dumphdinfo freebsd_home.vdi
I got the following for the virtual disk image holding the /home (no root hence no MBR) disk for a FreeBSD guest:
Header: offBlocks=4096 offData=28672
But since the mount command in FreeBSD doesn't support "offset", I have to dd the image into another file. I believe the default "block" size in dd is 512 bytes, so the offset 28672 (bytes?) is 56 blocks. So I used the command:
dd skip=56 if=freebsd_home.vdi of=freebsd_home_56.vdi
Then attempt to mount it:
mdconfig -a -t vnode -f /tmp/freebsd_home_56.vdi -u 0
mount /dev/md0 /tmp/aaa/
mount -t cd9660 /dev/md0 /tmp/aaa/
unfortunately both the above two mount commands failed with "Invalid argument". I tried skip=28672 to no avail as well. Anything did I do wrong?
Or is there any other solution in FreeBSD host to mount virtualbox vdi file? There appears to be a "vdfuse" but is not ported yet, and the attempt to port appears to be not for VirtualBox 4.
Andrey V. Elsukov
> Is it possible to mount virtualbox vdi file on the FreeBSD host? This appears to be doable on
> windows and linux hosts, which basically is done in two steps: 1. find offset in the image. 2.
> mount the image with that offset.
>
> I'm trying to do the same thing on FreeBSD, and found the undocumented and deprecated command
> still works:
>
> VBoxManage internalcommands dumphdinfo freebsd_home.vdi
>
> I got the following for the virtual disk image holding the /home (no root hence no MBR) disk for
> a FreeBSD guest:
>
> Header: offBlocks=4096 offData=28672
>
>
> mdconfig -a -t vnode -f /tmp/freebsd_home_56.vdi -u 0 mount /dev/md0 /tmp/aaa/ mount -t cd9660
> /dev/md0 /tmp/aaa/
>
> unfortunately both the above two mount commands failed with "Invalid argument". I tried
> skip=28672 to no avail as well. Anything did I do wrong?
I have not any Vbox images with fixed size, but i tried this:
# mdconfig -f 10G_GPT_UFS.vdi
# gnop create -v -o 41472 /dev/md0
where 41472 is offData value. After that md0.nop was tasted and reports about invalid GPT.
So, i think if your image is fixed size disk yout can try this method and mount UFS (not cd9660).
--
WBR, Andrey V. Elsukov
Brandon Gooch
> On 25.07.2011 10:18, Joe Sciulli wrote:
>> Is it possible to mount virtualbox vdi file on the FreeBSD host? This appears to be doable on
>> windows and linux hosts, which basically is done in two steps: 1. find offset in the image. 2.
>> mount the image with that offset.
>>
>> I'm trying to do the same thing on FreeBSD, and found the undocumented and deprecated command
>> still works:
>>
>> VBoxManage internalcommands dumphdinfo freebsd_home.vdi
>>
>> I got the following for the virtual disk image holding the /home (no root hence no MBR) disk for
>> a FreeBSD guest:
>>
>> Header: offBlocks=4096 offData=28672
>>
>> Then attempt to mount it:
>>
>> mdconfig -a -t vnode -f /tmp/freebsd_home_56.vdi -u 0 mount /dev/md0 /tmp/aaa/ mount -t cd9660
>> /dev/md0 /tmp/aaa/
>>
>> unfortunately both the above two mount commands failed with "Invalid argument". I tried
>> skip=28672 to no avail as well. Anything did I do wrong?
>
> I have not any Vbox images with fixed size, but i tried this:
> # mdconfig -f 10G_GPT_UFS.vdi
> # gnop create -v -o 41472 /dev/md0
>
> where 41472 is offData value. After that md0.nop was tasted and reports about invalid GPT.
> So, i think if your image is fixed size disk yout can try this method and mount UFS (not cd9660).
>
> --
> WBR, Andrey V. Elsukov
There was a CFT sent out a while back about a fuse module for mounting
vdi images:
http://lists.freebsd.org/pipermail/freebsd-emulation/2010-September/007964.html
Not sure about the state of this now though...
-Brandon
Joe Sciulli
--- On Mon, 7/25/11, Brandon Gooch <jamesbra...@gmail.com> wrote:
http://lists.freebsd.org/pipermail/freebsd-emulation/2010-September/007964.html
-Brandon
Thanks for your replies.
I tried
mdconfig -f freebsd_home.vdi
gnop create -v -o 28672 /dev/md0
Indeed /dev/md0.nop etc were created. But mounting with the following commands still yielded the dreaded "Invalid argument" error:
mount /dev/md0.nop /tmp/aaa/
mount -t ufs /dev/md0.nop /tmp/aaa/
One thing interesting is, in the gnop command, if I change 28672 to anything else such as 28671 or 28673 or whatever, that gnop command would fail with:
gnop: Invalid offset for provider md0.
so that suggests the offset is correct. It's just that how to mount it.
The vdi is a variable size disk in virtualbox. But I had shutdown virtualbox and copied it to another file before mdconfig on it.
I looked closer at virtualbox-ose-fuse.shar Brandon linked, it appears to be hardcoded to work with VirtualBox-3.2.8-OSE, while I only have VBoxGuestAdditions_4.0.12 as in the ports tree.
Any more idea, thanks.
Juergen Lock
> 2011/7/25 Andrey V. Elsukov <bu7...@yandex.ru>:
> >> windows and linux hosts, which basically is done in two steps: 1. find offset in the image. 2.
> >> mount the image with that offset.
> >>
> >> I'm trying to do the same thing on FreeBSD, and found the undocumented and deprecated command
> >> still works:
> >>
> >> VBoxManage internalcommands dumphdinfo freebsd_home.vdi
> >>
> >> I got the following for the virtual disk image holding the /home (no root hence no MBR) disk for
> >> a FreeBSD guest:
> >>
> >> Header: offBlocks=4096 offData=28672
> >>
> >>
> >> mdconfig -a -t vnode -f /tmp/freebsd_home_56.vdi -u 0 mount /dev/md0 /tmp/aaa/ mount -t cd9660
> >> /dev/md0 /tmp/aaa/
> >>
> >> unfortunately both the above two mount commands failed with "Invalid argument". I tried
> >> skip=28672 to no avail as well. Anything did I do wrong?
> >
> > # mdconfig -f 10G_GPT_UFS.vdi
> > # gnop create -v -o 41472 /dev/md0
> >
> > where 41472 is offData value. After that md0.nop was tasted and reports about invalid GPT.
> > So, i think if your image is fixed size disk yout can try this method and mount UFS (not cd9660).
> >
> > --
> > WBR, Andrey V. Elsukov
>
> vdi images:
>
> http://lists.freebsd.org/pipermail/freebsd-emulation/2010-September/007964.html
>
> Not sure about the state of this now though...
Yeah sorry I never got back to this after getting reports that
writes are stuck in wdrain... [1] I guess what happens is the
vdfuse process wants to write many(?) more blocks than the number
that got queued by the original fuse request and/or too many writes
get queued up at once before the vdfuse process gets to handle them
(trying to increase runningbufspace even more), and thus there is
deadlock. :( So my question for -hackers is, does anyone have a
clever idea how to fix this? Should the fuse requests for this be
exempted from the wdrain bookkeeping so that only the actual writes
by the vdfuse process get counted, and if yes, how would I best
accomplish this?
Thanx! :)
Juergen
[1] http://fxr.watson.org/fxr/source/kern/vfs_bio.c?im=excerpts#L417
Andrey V. Elsukov
>> There was a CFT sent out a while back about a fuse module for mounting
>> vdi images:
>>
>> http://lists.freebsd.org/pipermail/freebsd-emulation/2010-September/007964.html
>>
>> Not sure about the state of this now though...
>
I made a basic GEOM class for read-only access to VDI images.
It seems works, but i have not many images to test it.
http://people.freebsd.org/~ae/geom_vdi/
Just make && make load, then use mdconfig -f DiskFileName.vdi.
Kostik Belousov
> On Mon, Jul 25, 2011 at 06:31:36PM -0500, Brandon Gooch wrote:
> > >> windows and linux hosts, which basically is done in two steps: 1. find offset in the image. 2.
> > >> mount the image with that offset.
> > >>
> > >> I'm trying to do the same thing on FreeBSD, and found the undocumented and deprecated command
> > >> still works:
> > >>
> > >> VBoxManage internalcommands dumphdinfo freebsd_home.vdi
> > >>
> > >> I got the following for the virtual disk image holding the /home (no root hence no MBR) disk for
> > >> a FreeBSD guest:
> > >>
> > >> Header: offBlocks=4096 offData=28672
> > >>
> > >>
> > >> mdconfig -a -t vnode -f /tmp/freebsd_home_56.vdi -u 0 mount /dev/md0 /tmp/aaa/ mount -t cd9660
> > >> /dev/md0 /tmp/aaa/
> > >>
> > >> unfortunately both the above two mount commands failed with "Invalid argument". I tried
> > >> skip=28672 to no avail as well. Anything did I do wrong?
> > >
> > > # mdconfig -f 10G_GPT_UFS.vdi
> > > # gnop create -v -o 41472 /dev/md0
> > >
> > > where 41472 is offData value. After that md0.nop was tasted and reports about invalid GPT.
> > > So, i think if your image is fixed size disk yout can try this method and mount UFS (not cd9660).
> > >
> > > --
> > > WBR, Andrey V. Elsukov
> >
> > vdi images:
> >
> > http://lists.freebsd.org/pipermail/freebsd-emulation/2010-September/007964.html
> >
> > Not sure about the state of this now though...
>
> writes are stuck in wdrain... [1] I guess what happens is the
> vdfuse process wants to write many(?) more blocks than the number
> that got queued by the original fuse request and/or too many writes
> get queued up at once before the vdfuse process gets to handle them
> (trying to increase runningbufspace even more), and thus there is
> deadlock. :( So my question for -hackers is, does anyone have a
> clever idea how to fix this? Should the fuse requests for this be
> exempted from the wdrain bookkeeping so that only the actual writes
> by the vdfuse process get counted, and if yes, how would I best
> accomplish this?
>
> Thanx! :)
> Juergen
Excluding any buffers from runningbufspace is absolutely wrong.
You will get another deadlock due to excessive pressure on the buffer
space.
Juergen Lock
> On Tue, Jul 26, 2011 at 08:03:35PM +0200, Juergen Lock wrote:
> > > >> windows and linux hosts, which basically is done in two steps: 1. find offset in the image. 2.
> > > >> mount the image with that offset.
> > > >>
> > > >> I'm trying to do the same thing on FreeBSD, and found the undocumented and deprecated command
> > > >> still works:
> > > >>
> > > >> VBoxManage internalcommands dumphdinfo freebsd_home.vdi
> > > >>
> > > >> I got the following for the virtual disk image holding the /home (no root hence no MBR) disk for
> > > >> a FreeBSD guest:
> > > >>
> > > >> Header: offBlocks=4096 offData=28672
> > > >>
> > > >>
> > > >> mdconfig -a -t vnode -f /tmp/freebsd_home_56.vdi -u 0 mount /dev/md0 /tmp/aaa/ mount -t cd9660
> > > >> /dev/md0 /tmp/aaa/
> > > >>
> > > >> unfortunately both the above two mount commands failed with "Invalid argument". I tried
> > > >> skip=28672 to no avail as well. Anything did I do wrong?
> > > >
> > > > # mdconfig -f 10G_GPT_UFS.vdi
> > > > # gnop create -v -o 41472 /dev/md0
> > > >
> > > > where 41472 is offData value. After that md0.nop was tasted and reports about invalid GPT.
> > > > So, i think if your image is fixed size disk yout can try this method and mount UFS (not cd9660).
> > > >
> > > > --
> > > > WBR, Andrey V. Elsukov
> > >
> > > vdi images:
> > >
> > > http://lists.freebsd.org/pipermail/freebsd-emulation/2010-September/007964.html
> > >
> > > Not sure about the state of this now though...
> >
> > writes are stuck in wdrain... [1] I guess what happens is the
> > vdfuse process wants to write many(?) more blocks than the number
> > that got queued by the original fuse request and/or too many writes
> > get queued up at once before the vdfuse process gets to handle them
> > (trying to increase runningbufspace even more), and thus there is
> > deadlock. :( So my question for -hackers is, does anyone have a
> > clever idea how to fix this? Should the fuse requests for this be
> > exempted from the wdrain bookkeeping so that only the actual writes
> > by the vdfuse process get counted, and if yes, how would I best
> > accomplish this?
> >
> > Thanx! :)
> > Juergen
>
> You will get another deadlock due to excessive pressure on the buffer
> space.
Alright, so how to fix the deadlocks then? :)
Wondering...
Juergen