headers
Matthew Dillon | 1 Jan 2007 22:00

Release Schedule for 1.8

    * The CVS tree will be branched in two weeks, on Sunday, January 14th

    * The 1.8 release is slated for January 28th.

    I would like people to start testing release oriented bits if possible.  
    We have about two weeks before the CVS tree is branched, and two weeks
    after it is branched for fine-tuning and package building.  So if there
    are things you want to get into the 1.8 release but haven't gotten to yet,
    now is the time.

							-Matt
Permalink | Reply | 0 comments |
headers
Joe Talbott | 5 Jan 2007 21:48
Favicon

DVD READ_BIG errors

Hello,

When I try to play a DVD with mplayer I get the following error
hundreds of times:

kernel: acd0: READ_BIG - ILLEGAL REQUEST asc=0x6f ascq=0x03 error=0x00

I am able to mount the dvd and navigate around without getting these
errors.

Here's the dmesg bit:

acd0: DVD-R <PIONEER DVD-RW DVR-K16A> at ata1-master PIO4
cd0 at ata1 bus 0 target 0 lun 0
cd0: <PIONEER DVD-RW  DVR-K16A 1.63> Removable CD-ROM SCSI-0 device 
cd0: 16.000MB/s transfers
cd0: Attempt to query device size failed: NOT READY, Medium not present

Full dmesg here:

http://www.xenno.com/dfbsd/dmesg-20061210.txt

Thanks,
Joe
Permalink | Reply | 0 comments |
headers
Matthew Dillon | 5 Jan 2007 23:23

Heads up: TLS system calls being renamed

    sys_set_tls_area() is being renamed to set_tls_area()
    sys_get_tls_area() is being renamed to get_tls_area()

    I did a google search and it didn't come up with any uses.

    A number of people have noted the confusion that adding a sys_
    prefix to a system call name creates (from the point of view of
    userland).  I agree.

    This is different from the sys_ prefix used in the kernel sources
    for system call implementation procedures, which of course were a 
    great idea and are sticking around.

    In anycase, when I make the commit, anyone building HEAD should be
    sure to completely rebuild both the kernel and the world.  Old libraries
    will remain compatible, since the syscall number and function arguments
    haven't changed.

					-Matt
					Matthew Dillon 
					<dillon <at> backplane.com>
Permalink | Reply | 0 comments |
headers
Matthew Dillon | 6 Jan 2007 21:11

Virtual kernel progress update

    There are still a ton of things that I have to get working, but the
    VKERNEL now boots through to the point where it tries to vmfork() the
    init process. 

test28# ./kernel.debug -m 64m
Copyright (c) 2003, 2004, 2005, 2006, 2007 The DragonFly Project.
Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
DragonFly 1.7.0-DEVELOPMENT #179: Sat Jan  6 11:55:07 PST 2007
    root <at> test28.backplane.com:/usr/obj/usr/src/sys/VKERNEL
real memory = 67108864 (65536K bytes)
avail memory = 62578688 (61112K bytes)
Segmentation fault (core dumped)

    I got the virtual kernel's page table (for its KVM) working.  The big
    ticket items left to do are as follows.   My goal is to be able to boot
    the virtual kernel through to a login: prompt on the console by the time
    we release in one week.

    * Adding TLS info to the vmspace context, since just about any program
      we might want to run needs TLS support.

    * Adding FP support, same reason.

    * Root filesystem support (it will be synchronous to begin with, i.e.
      not the fastest thing in the world.  It will just use read() and
      write() to a root filesystem image file for now).

    * We need a clock 'interrupt' to provide ticks to the virtual kernel.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Thomas E. Spanjaard | 6 Jan 2007 22:24

Re: Virtual kernel progress update

Matthew Dillon wrote:
>     There are still a ton of things that I have to get working, but the
>     VKERNEL now boots through to the point where it tries to vmfork() the
>     init process. 

Good stuff :).

>     * A Pseudo network interface has to be designed and built (so you can 
>       login to the virtual kernel in some way other then the console).

A backend to a tap(4) interface? E.g. Qemu uses that.

Cheers,
--

-- 
         Thomas E. Spanjaard
         tgen <at> netphreax.net
Permalink | Reply | 1 comment |
headers
Matthew Dillon | 6 Jan 2007 22:38

Re: Virtual kernel progress update


:
:>     * A Pseudo network interface has to be designed and built (so you can 
:>       login to the virtual kernel in some way other then the console).
:
:A backend to a tap(4) interface? E.g. Qemu uses that.
:
:Cheers,
:-- 
:         Thomas E. Spanjaard

    I believe that TAP can be used for this purpose.

					-Matt
Permalink | Reply | 0 comments |
headers
Matthew Dillon | 7 Jan 2007 07:05

VKernel progress update

    I'm making very good progress.  The virtual kernel is able to boot
    all the way through to where it mounts the root filesystem and then
    tries to load init.  It is able to find the init binary and start
    loading it before it crashes and burns :-)

    BTW, if anyone wants to fool around or follow my progress, here are
    the instructions for building and using a virtual kernel.  Remember
    that it is going to crash and burn... it's aint ready for prime time
    yet!

    (1) You have to be running the absolute latest HEAD and you have to
	enable virtual kernel operation with a sysctl, and create 
	/var/vkernel to hold miscellanious files.

	sysctl vm.vkernel_enable=1
	mkdir /home/var.vkernel
	ln -s /home/var.vkernel /var/vkernel

    (2) Construct a root filesystem image.  Create a disk file and use
	vnconfig to initialize it:

	dd if=/dev/zero of=/var/vkernel/rootimg.01 bs=1m count=2048
	vnconfig -c -s labels vn0 /var/vkernel/rootimg.01
	disklabel -r -w vn0 auto
	(edit the label to create a vn0a partition)
	newfs /dev/vn0a
	mount /dev/vn0a /mnt
	cpdup / /mnt
	umount /mnt
	vnconfig -u vn0
(Continue reading)

Permalink | Reply | 1 comment |
headers
Matthew Dillon | 7 Jan 2007 09:44

Re: VKernel progress update

    ... now it successfully executes /sbin/init up to the point where it
    tries to install a TLS segment (I don't have TLS handling in yet).
    But I know its running real code because not only am I getting a 
    couple of page fault traps, I am also getting system call traps!

    I'm very excited.  I can smell it.  I'll get a login: prompt on Sunday.

						-Matt

test28# ./kernel.debug -m 64m -r /var/vkernel/rootimg.01

Using memory file: /var/vkernel/memimg.000000
Copyright (c) 2003, 2004, 2005, 2006, 2007 The DragonFly Project.
Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
DragonFly 1.7.0-DEVELOPMENT #345: Sun Jan  7 00:08:47 PST 2007
    root <at> test28.backplane.com:/usr/obj/usr/src/sys/VKERNEL
real memory = 67108864 (65536K bytes)
avail memory = 62578688 (61112K bytes)
md0: Malloc disk
initclocks
cputimer_intr_config
IP packet filtering initialized, divert disabled, rule-based forwarding enabled,
 default to accept, logging disabled
DUMMYNET initialized (011031)
IPsec: Initialized Security Association Processing.
Mounting root from ufs:vd0a
CAUGHT SEGFAULT EIP 282ba570 ERR 4fe97000 TRAPNO 393228
CAUGHT SEGFAULT EIP 282ba570 ERR 4fe87000 TRAPNO 393228
(Continue reading)

Permalink | Reply | 0 comments |
headers
Kobajashi Zaghi | 7 Jan 2007 11:12
Picon

RE: VKernel progress update

Is this VKERNEL stuff similar to Linux kernel's Kernel-based Virtual
Machine ( http://kvm.sourceforge.net/ )? Where can i found more
information about VKERNEL?

Thanks.

--
kobi
Permalink | Reply | 3 comments |
headers
Gergo Szakal | 7 Jan 2007 12:33
Picon
Gravatar

Re: VKernel progress update

On Sun, 7 Jan 2007 11:12:31 +0100
"Kobajashi Zaghi" <kobajashi <at> gmail.com> wrote:

> Is this VKERNEL stuff similar to Linux kernel's Kernel-based Virtual
> Machine ( http://kvm.sourceforge.net/ )? Where can i found more
> information about VKERNEL?
> 

KVM is a hardware-accelerated virtualisation mechanism that you can run a guest OS within, while VKERNEL
is a Dragonfly kernel running like a normal program.

--

-- 
Gergo Szakal <bastyaelvtars <at> gmail.com>
University Of Szeged, HU
Faculty Of General Medicine

/* Please do not CC me with replies, thank you. */
Permalink | Reply | 0 comments |

Gmane