Re: Neat kernel development environment.
This is the same way that OS servers under Mach3 were developed and debugged! John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Neat kernel development environment.
On Sat, Apr 01, 2000 at 04:32:36AM +1000, Matthew Dillon wrote: I can just see all the coolness seeping out. Now guys, we have to have as a goal something at least as comparable as what IBM did with one of their mainframes. Oh, say, lets shoot for being able to run 4000 copies or so of linux under VMWare on FreeBSD :-) Since VMWare is our equivalent of IBM VM/CMS's CP, how about being able to run 4000 _nested_ copies of FreeBSD :-). (Run FreeBSD on real H/W, start VMWare, run FreeBSD under VMware and recurse). Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Neat kernel development environment.
Julian Elischer writes: | | I have just managed to get the following going: | | By writing a device driver that is two terminals back-to-back, | and configuring vmware to map one of the virtual ttys over the | 'null-modem' device, and then running a kernel configured with the console | on com1 and the gdb port on com2, (in the virtual machine in vmware) | I can on a single machine run a test system, allow it to run the vmware X | server, and at the same time have access to the console, AND be able to | single step it under xxdgb or DDB depending on the task. FYI, via the latest Etherboot port that was commited you can netboot a vmware machine. Could you post your null-modem device? ... it saves on serial ports. Doug A. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Neat kernel development environment.
:I have just managed to get the following going: : :By writing a device driver that is two terminals back-to-back, :and configuring vmware to map one of the virtual ttys over the :.. : :Thus no need to have that second machine for debugging.. ::-) :It's amazing to see on the same X screen, :1/ The xserver of the virtual BSD box :2/ the console in another window, (which can be sent into DDB if needed) :3/ a 3rd window running xxgdb, single stepping the kernel with source :and setting breakpoints etc. :4/ some othe rwindow on the host system, completely unaffected. : :I'll try get a screenshot. :(And yes I did buy a vmware licence) : :Julian I can just see all the coolness seeping out. Now guys, we have to have as a goal something at least as comparable as what IBM did with one of their mainframes. Oh, say, lets shoot for being able to run 4000 copies or so of linux under VMWare on FreeBSD :-) Once we fix the deadlocks, that is. -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Neat kernel development environment.
In message [EMAIL PROTECTED], Matthew Dillon writes: :I have just managed to get the following going: : :By writing a device driver that is two terminals back-to-back, :and configuring vmware to map one of the virtual ttys over the :.. : :Thus no need to have that second machine for debugging.. ::-) :It's amazing to see on the same X screen, :1/ The xserver of the virtual BSD box :2/ the console in another window, (which can be sent into DDB if needed) :3/ a 3rd window running xxgdb, single stepping the kernel with source :and setting breakpoints etc. :4/ some othe rwindow on the host system, completely unaffected. : :I'll try get a screenshot. :(And yes I did buy a vmware licence) : :Julian I can just see all the coolness seeping out. Now guys, we have to have as a goal something at least as comparable as what IBM did with one of their mainframes. Oh, say, lets shoot for being able to run 4000 copies or so of linux under VMWare on FreeBSD :-) Once we fix the deadlocks, that is. We don't need VMWare really, we can just run N jails... -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Neat kernel development environment.
I'll put the device driver on http://www.freebsd.org/~julian/ but it needs teh eyes of someone who's really at home in the tty system to look at it. I got kinda confused half way through hacking it (from the pty driver) and it shows. basically each pair of minor numbers is a pair and are connected to each other back-to-back. The support for 'select' etc is a bit confused at this stage. also originally I wanted it to shut down the other one (e.g. like loss of carrier) when one gets closed, and for one that is openning to stall waiting for its partner, but it turns out that makes it hard to use with vmware. So I backed that out (which gives a bit more confusion). the screenshot will be there too, (but it's big) also the little script I use to get it all sarteed (trivial). Julian On Fri, 31 Mar 2000, Doug Ambrisko wrote: Julian Elischer writes: | | I have just managed to get the following going: | | By writing a device driver that is two terminals back-to-back, | and configuring vmware to map one of the virtual ttys over the | 'null-modem' device, and then running a kernel configured with the console | on com1 and the gdb port on com2, (in the virtual machine in vmware) | I can on a single machine run a test system, allow it to run the vmware X | server, and at the same time have access to the console, AND be able to | single step it under xxdgb or DDB depending on the task. FYI, via the latest Etherboot port that was commited you can netboot a vmware machine. Could you post your null-modem device? ... it saves on serial ports. Doug A. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Neat kernel development environment.
In message [EMAIL PROTECTED], Julian El ischer writes: Oh? can you run a kernel in a jail for debugging? No, not quite yet, but what IBM bragged about the 41k linuxes for was for what jails do for you. Poul-Henning That's what I'm using it for.. (debugging kernel code.. I only have one machine here.) On Fri, 31 Mar 2000, Poul-Henning Kamp wrote: run 4000 copies or so of linux under VMWare on FreeBSD :-) Unfortunatly you can only run one vmware at a time under BSD. Once we fix the deadlocks, that is. We don't need VMWare really, we can just run N jails... -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Neat kernel development environment.
Poul-Henning Kamp writes: | In message [EMAIL PROTECTED], Julian |El | ischer writes: | | Oh? can you run a kernel in a jail for debugging? | | No, not quite yet, but what IBM bragged about the 41k linuxes for | was for what jails do for you. Nope not quite. Since you could actually crash the kernel in the VM/Linux session and the others are still going. Crash the kernel in a jail and all sessions are toast. Note I do like jail on FreeBSD one thing that would be nice with jail is if the IP address for the jail disappeared from the non-jail machine. For example sendmail doesn't like to send mail to the jail session if it sees the jail's IP is one of its own IPs. Sort of like, I'm already there why bother and it could cause mail looping under mis-configuration. This isn't a problem for the IBM type solution or vmware. Then with IBM the machine can disable a bad CPU and call home for a fix. None of the session are bothered (except performance) assuming you have more then one CPU working. Maybe we heard different bragging. Doug A. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
