Re: OpenBSD 3.7 on VM Workstation 5
On 7/28/05, Jason Opperisano <[EMAIL PROTECTED]> wrote: > On Wed, Jul 27, 2005 at 11:22:56PM +0200, Johan P. Lindstrvm wrote: > > Just finished installing OpenBSD 3.7 from CD onto VM Ware Workstation > > 5 build 13124 with Windows XP sp2 as host OS. > > > > As Client OS I chose FreeBSD, VM Ware tools not installed, virtual > > terminals CTRL+ALT+Fn does not work since CTRL+ALT releases control > > from the VM Ware application. > > i think it's great that this thread went on so long an no one answered > the question. the answer is: you add to the key sequence and > it prevents the from releasing. so--hold down and > hit to get to the console. Funny, I didn't see a question mark in the original message. Greg
Re: OpenBSD 3.7 on VM Workstation 5
On Wed, Jul 27, 2005 at 11:22:56PM +0200, Johan P. Lindstrvm wrote: > Just finished installing OpenBSD 3.7 from CD onto VM Ware Workstation > 5 build 13124 with Windows XP sp2 as host OS. > > As Client OS I chose FreeBSD, VM Ware tools not installed, virtual > terminals CTRL+ALT+Fn does not work since CTRL+ALT releases control > from the VM Ware application. i think it's great that this thread went on so long an no one answered the question. the answer is: you add to the key sequence and it prevents the from releasing. so--hold down and hit to get to the console. -j -- "Stewie: Careful! You're washing a baby's scalp, not scrubbing the vomit out of a Christmas dress, you stupid holiday drunk." --Family Guy
Re: OpenBSD 3.7 on VM Workstation 5
The best way to get the answer is to state a contrary fact, rather than to ask for advice here. :D I would have said "OpenBSD console switching in VMWARE kicks butt!" and waited for those with real information to counter you, then show their cards :D "I am not your puppet. Since when? Now get your spongy ping ass out there and dance for the cameras" -Nora in (Death to Smoochy) On Thu, 28 Jul 2005, [ISO-8859-1] Johan P. Lindstrvm wrote: > Date: Thu, 28 Jul 2005 14:16:35 +0200 > From: "[ISO-8859-1] Johan P. Lindstrvm" <[EMAIL PROTECTED]> > To: OpenBSD MISC > Subject: Re: OpenBSD 3.7 on VM Workstation 5 > > On 7/27/05, Johan P. Lindstrvm <[EMAIL PROTECTED]> wrote: >> Just finished installing OpenBSD 3.7 from CD onto VM Ware Workstation >> 5 build 13124 with Windows XP sp2 as host OS. > > --- cut --- > > Look how interesting this got, now in this thread we have a way to > dodge the virtual terminal issue and better knowledge of what to [not] > do when posting to the list. > > btw, does anyone run vm ware 5 on obsd under linux emulation? experiences? > > I found this googling, I can't tell how accurate it is for 3.7 and 5 > though, or is there a smarter solution? > > http://www.monkey.org/~marius/pages/?page=VMWare_for_OpenBSD > > Everyone is a beginner at some point in time... I apologize if I have > offended someone. > > -- JPL
Re: OpenBSD 3.7 on VM Workstation 5
On 7/27/05, Johan P. Lindstrvm <[EMAIL PROTECTED]> wrote: > Just finished installing OpenBSD 3.7 from CD onto VM Ware Workstation > 5 build 13124 with Windows XP sp2 as host OS. --- cut --- Look how interesting this got, now in this thread we have a way to dodge the virtual terminal issue and better knowledge of what to [not] do when posting to the list. btw, does anyone run vm ware 5 on obsd under linux emulation? experiences? I found this googling, I can't tell how accurate it is for 3.7 and 5 though, or is there a smarter solution? http://www.monkey.org/~marius/pages/?page=VMWare_for_OpenBSD Everyone is a beginner at some point in time... I apologize if I have offended someone. -- JPL
Re: OpenBSD 3.7 on VM Workstation 5
And you could always use that silly patch that makes it so that alt-fn switches console modes :D "I am not your puppet. Since when? Now get your spongy ping ass out there and dance for the cameras" -Nora in (Death to Smoochy) On Thu, 28 Jul 2005, Andre Naehring wrote: Date: Thu, 28 Jul 2005 07:36:07 +0200 From: Andre Naehring <[EMAIL PROTECTED]> To: OpenBSD MISC Subject: Re: OpenBSD 3.7 on VM Workstation 5 Johan P. Lindstrvm schrieb: Just finished installing OpenBSD 3.7 from CD onto VM Ware Workstation 5 build 13124 with Windows XP sp2 as host OS. As Client OS I chose FreeBSD, VM Ware tools not installed, virtual terminals CTRL+ALT+Fn does not work since CTRL+ALT releases control from the VM Ware application. You can reconfigure VMWare to use another hotkey for releasing control. Then you can use the terminals. -- Sauerland Spielgerdte GmbH Andri Ndhring
Re: OpenBSD 3.7 on VM Workstation 5
Johan P. Lindstrvm schrieb: > Just finished installing OpenBSD 3.7 from CD onto VM Ware Workstation > 5 build 13124 with Windows XP sp2 as host OS. > > As Client OS I chose FreeBSD, VM Ware tools not installed, virtual > terminals CTRL+ALT+Fn does not work since CTRL+ALT releases control > from the VM Ware application. > You can reconfigure VMWare to use another hotkey for releasing control. Then you can use the terminals. -- Sauerland Spielgerdte GmbH Andri Ndhring
Re: OpenBSD 3.7 on VM Workstation 5
Brad wrote: > I'm just curious what the point of sending the dmesg was? All things considered, I'd rather have five things I don't need than have one thing I wanted that was missing. If for nothing else, it's a refreshing Something Different from the "Send me some useful info!" exchanges). Heck, how many times have I spotted something in a "unneeded" dmesg that actually did or may have pertained to the user's question? (A: lots!) If nothing else, dmesg tells us if someone is running a Theo-built kernel, a home-built GENERIC (which we have to take with a big grain of salt until we commit those changes that prevent even root from editing /usr/src/sys/arch/*/conf/GENERIC), or a definite Ricer, which are details that aren't always communicated accurately through other means. Granted, in this case, OpenBSD was working perfectly, VMware was blocking certain keystrokes, but obviously the OP didn't recognize that, or they wouldn't have posted here. Hey, not sure reassigning the "release" sequence would have occurred to me if one of my coworkers hadn't said, "You'll want to change that so CTR-ALT-F works". I've also discovered there are ways to configure VMware so it doesn't work with OpenBSD. Besides, I haven't seen a VMware 5 dmesg yet, and we all know how excited I get over dmesgs. :) (what's the point of YOUR sending the dmesg again, rather than trimming down the reply? :) If in doubt, send the dmesg. If you think it isn't necessary, send the dmesg. If you are absolutely sure the question has nothing to do with hardware (or virtual hardware), and you have confirmed the situation on five different platforms, dmesg is optional. In my opinion, of course. :) However, my time lately is much less, there are lots of messages I've been completely ignoring (or laughing at to myself as others try to "help" the clueless, but still never ask for the obvious first-step in debugging) because I don't have time to beg for every bit and piece of info to verify (or disprove) a suspicion. Nick. (dmesg, dammit!)
Re: OpenBSD 3.7 on VM Workstation 5
Fine then you should have read my email to misc@ about vmware 5. Also fixed the mpt support so this information *is* out there. Brad is right. On Wed, Jul 27, 2005 at 05:55:54PM -0700, Spruell, Darren-Perot wrote: > From: Brad [mailto:[EMAIL PROTECTED] > > > From: Brad [mailto:[EMAIL PROTECTED] > > > > I'm just curious what the point of sending the dmesg was? > > > > > > > > It's not like people haven't been running OpenBSD under VMware for > > > > years now. This isn't stating anything new. > > > > > > Because its the Proper thing to do. Don't discourage thoroughness. > > > > > > DS > > > > I can look in the mailing list archives and find plenty of dmesgs from > > VMware. Posting another one doesn't do anything useful. I'm not > > discouraging thoroughness but I am discouraging pointless > > posts to [EMAIL PROTECTED] > > And suppose VMWare decides to emulate different hardware/architectures in > their VMs? Suddenly, the dmesg becomes very pertinent. > > Point is, better to be swamped with too much information than too little. > You'll find that statement in the archives as well. > > DS
Re: OpenBSD 3.7 on VM Workstation 5
In Vmware Workstation, you can adjust the hot keys for releasing the session
under the Edit menu, Preferences and the Hot Keys tab. I set mine to
CTRL+ALT+Shift, then you can use the virtual terminals.
BTW, I use Other as the client OS choice. Seems to work better, but I don't
have any statistics on that.
Jim O'Donald
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Johan P.
Lindstrvm
Sent: Wednesday, July 27, 2005 4:23 PM
To: OpenBSD MISC
Subject: OpenBSD 3.7 on VM Workstation 5
Just finished installing OpenBSD 3.7 from CD onto VM Ware Workstation
5 build 13124 with Windows XP sp2 as host OS.
As Client OS I chose FreeBSD, VM Ware tools not installed, virtual
terminals CTRL+ALT+Fn does not work since CTRL+ALT releases control
from the VM Ware application.
Here is the dmesg.boot
OpenBSD 3.7 (GENERIC) #50: Sun Mar 20 00:01:57 MST 2005
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Pentium(R) 4 CPU 3.00GHz ("GenuineIntel" 686-class) 3 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,PNI
real mem = 267952128 (261672K)
avail mem = 237731840 (232160K)
using 3296 buffers containing 13500416 bytes (13184K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(a5) BIOS, date 02/11/05, BIOS32 rev. 0 @ 0xfd880
apm0 at bios0: Power Management spec V1.2
apm0: AC on, battery charge unknown
pcibios0 at bios0: rev 2.1 @ 0xfd880/0x780
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdf30/176 (9 entries)
pcibios0: PCI Interrupt Router at 000:07:0 ("Intel 82371FB ISA" rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc/0x8000 0xc8000/0x1000 0xdc000/0x4000! 0xe/0x4000!
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x01
ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x01
pci1 at ppb0 bus 1
pcib0 at pci0 dev 7 function 0 "Intel 82371AB PIIX4 ISA" rev 0x08
pciide0 at pci0 dev 7 function 1 "Intel 82371AB IDE" rev 0x01: DMA,
channel 0 configured to compatibility, channel 1 configured to
compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 64-sector PIO, LBA, 4096MB, 8388608 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
atapiscsi0 at pciide0 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: <_NEC, DVD_RW ND-3520A, 1.04> SCSI0
5/cdrom removable
cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
uhci0 at pci0 dev 7 function 2 "Intel 82371AB USB" rev 0x00: irq 9
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
"Intel 82371AB Power Mgmt" rev 0x08 at pci0 dev 7 function 3 not configured
vga1 at pci0 dev 15 function 0 "VMware Virtual SVGA II" rev 0x00
wsdisplay0 at vga1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
mpt0 at pci0 dev 16 function 0 "Symbios Logic 53c1030" rev 0x01: irq 11
mpt0: running in vmware, skipping pageretrieval
mpt0: IM support: 0
scsibus1 at mpt0: 16 targets
le1 at pci0 dev 17 function 0 "AMD 79c970 PCnet-PCI" rev 0x10: irq 10
le1: address 00:0c:29:91:ef:ac
le1: 8 receive buffers, 2 transmit buffers
eap0 at pci0 dev 18 function 0 "Ensoniq AudioPCI97" rev 0x02: irq 9
ac97: codec id 0x43525913 (Cirrus Logic CS4297A rev 3)
audio0 at eap0
midi0 at eap0:
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0 (mux 1 ignored for console): console keyboard, using wsdisplay0
pmsi0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pmsi0 mux 0
pcppi0 at isa0 port 0x61
midi1 at pcppi0:
sysbeep0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
npx0 at isa0 port 0xf0/16: using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
biomask eb65 netmask ef65 ttymask ffe7
pctr: user-level cycle counter enabled
dkcsum: wd0 matched BIOS disk 80
root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302
Re: OpenBSD 3.7 on VM Workstation 5
From: Brad [mailto:[EMAIL PROTECTED] > > From: Brad [mailto:[EMAIL PROTECTED] > > > I'm just curious what the point of sending the dmesg was? > > > > > > It's not like people haven't been running OpenBSD under VMware for > > > years now. This isn't stating anything new. > > > > Because its the Proper thing to do. Don't discourage thoroughness. > > > > DS > > I can look in the mailing list archives and find plenty of dmesgs from > VMware. Posting another one doesn't do anything useful. I'm not > discouraging thoroughness but I am discouraging pointless > posts to [EMAIL PROTECTED] And suppose VMWare decides to emulate different hardware/architectures in their VMs? Suddenly, the dmesg becomes very pertinent. Point is, better to be swamped with too much information than too little. You'll find that statement in the archives as well. DS
Re: OpenBSD 3.7 on VM Workstation 5
Spruell, Darren-Perot wrote: > Because its the Proper thing to do. Don't discourage thoroughness. http://www.openbsd.org/faq/faq4.html#SendDmesg says it's [EMAIL PROTECTED], not [EMAIL PROTECTED]
Re: OpenBSD 3.7 on VM Workstation 5
On Wed, Jul 27, 2005 at 04:56:23PM -0700, Spruell, Darren-Perot wrote: > From: Brad [mailto:[EMAIL PROTECTED] > > I'm just curious what the point of sending the dmesg was? > > > > It's not like people haven't been running OpenBSD under VMware for > > years now. This isn't stating anything new. > > Because its the Proper thing to do. Don't discourage thoroughness. > > DS I can look in the mailing list archives and find plenty of dmesgs from VMware. Posting another one doesn't do anything useful. I'm not discouraging thoroughness but I am discouraging pointless posts to [EMAIL PROTECTED]
Re: OpenBSD 3.7 on VM Workstation 5
From: Brad [mailto:[EMAIL PROTECTED] > I'm just curious what the point of sending the dmesg was? > > It's not like people haven't been running OpenBSD under VMware for > years now. This isn't stating anything new. Because its the Proper thing to do. Don't discourage thoroughness. DS
Re: OpenBSD 3.7 on VM Workstation 5
I'm just curious what the point of sending the dmesg was?
It's not like people haven't been running OpenBSD under VMware for
years now. This isn't stating anything new.
On Wed, Jul 27, 2005 at 11:22:56PM +0200, Johan P. Lindstrvm wrote:
> Just finished installing OpenBSD 3.7 from CD onto VM Ware Workstation
> 5 build 13124 with Windows XP sp2 as host OS.
>
> As Client OS I chose FreeBSD, VM Ware tools not installed, virtual
> terminals CTRL+ALT+Fn does not work since CTRL+ALT releases control
> from the VM Ware application.
>
> Here is the dmesg.boot
>
> OpenBSD 3.7 (GENERIC) #50: Sun Mar 20 00:01:57 MST 2005
> [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: Intel(R) Pentium(R) 4 CPU 3.00GHz ("GenuineIntel" 686-class) 3 GHz
> cpu0:
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,PNI
> real mem = 267952128 (261672K)
> avail mem = 237731840 (232160K)
> using 3296 buffers containing 13500416 bytes (13184K) of memory
> mainbus0 (root)
> bios0 at mainbus0: AT/286+(a5) BIOS, date 02/11/05, BIOS32 rev. 0 @ 0xfd880
> apm0 at bios0: Power Management spec V1.2
> apm0: AC on, battery charge unknown
> pcibios0 at bios0: rev 2.1 @ 0xfd880/0x780
> pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdf30/176 (9 entries)
> pcibios0: PCI Interrupt Router at 000:07:0 ("Intel 82371FB ISA" rev 0x00)
> pcibios0: PCI bus #1 is the last bus
> bios0: ROM list: 0xc/0x8000 0xc8000/0x1000 0xdc000/0x4000! 0xe/0x4000!
> cpu0 at mainbus0
> pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
> pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x01
> ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x01
> pci1 at ppb0 bus 1
> pcib0 at pci0 dev 7 function 0 "Intel 82371AB PIIX4 ISA" rev 0x08
> pciide0 at pci0 dev 7 function 1 "Intel 82371AB IDE" rev 0x01: DMA,
> channel 0 configured to compatibility, channel 1 configured to
> compatibility
> wd0 at pciide0 channel 0 drive 0:
> wd0: 64-sector PIO, LBA, 4096MB, 8388608 sectors
> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
> atapiscsi0 at pciide0 channel 1 drive 0
> scsibus0 at atapiscsi0: 2 targets
> cd0 at scsibus0 targ 0 lun 0: <_NEC, DVD_RW ND-3520A, 1.04> SCSI0
> 5/cdrom removable
> cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
> uhci0 at pci0 dev 7 function 2 "Intel 82371AB USB" rev 0x00: irq 9
> usb0 at uhci0: USB revision 1.0
> uhub0 at usb0
> uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> uhub0: 2 ports with 2 removable, self powered
> "Intel 82371AB Power Mgmt" rev 0x08 at pci0 dev 7 function 3 not configured
> vga1 at pci0 dev 15 function 0 "VMware Virtual SVGA II" rev 0x00
> wsdisplay0 at vga1: console (80x25, vt100 emulation)
> wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
> mpt0 at pci0 dev 16 function 0 "Symbios Logic 53c1030" rev 0x01: irq 11
> mpt0: running in vmware, skipping pageretrieval
> mpt0: IM support: 0
> scsibus1 at mpt0: 16 targets
> le1 at pci0 dev 17 function 0 "AMD 79c970 PCnet-PCI" rev 0x10: irq 10
> le1: address 00:0c:29:91:ef:ac
> le1: 8 receive buffers, 2 transmit buffers
> eap0 at pci0 dev 18 function 0 "Ensoniq AudioPCI97" rev 0x02: irq 9
> ac97: codec id 0x43525913 (Cirrus Logic CS4297A rev 3)
> audio0 at eap0
> midi0 at eap0:
> isa0 at pcib0
> isadma0 at isa0
> pckbc0 at isa0 port 0x60/5
> pckbd0 at pckbc0 (kbd slot)
> pckbc0: using irq 1 for kbd slot
> wskbd0 at pckbd0 (mux 1 ignored for console): console keyboard, using
> wsdisplay0
> pmsi0 at pckbc0 (aux slot)
> pckbc0: using irq 12 for aux slot
> wsmouse0 at pmsi0 mux 0
> pcppi0 at isa0 port 0x61
> midi1 at pcppi0:
> sysbeep0 at pcppi0
> lpt0 at isa0 port 0x378/4 irq 7
> npx0 at isa0 port 0xf0/16: using exception 16
> pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
> pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
> fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
> fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
> biomask eb65 netmask ef65 ttymask ffe7
> pctr: user-level cycle counter enabled
> dkcsum: wd0 matched BIOS disk 80
> root on wd0a
> rootdev=0x0 rrootdev=0x300 rawdev=0x302
Re: OpenBSD 3.7 on VM Workstation 5
And you dont know how to reassign the release key?
On Wed, Jul 27, 2005 at 11:22:56PM +0200, Johan P. Lindstrvm wrote:
> Just finished installing OpenBSD 3.7 from CD onto VM Ware Workstation
> 5 build 13124 with Windows XP sp2 as host OS.
>
> As Client OS I chose FreeBSD, VM Ware tools not installed, virtual
> terminals CTRL+ALT+Fn does not work since CTRL+ALT releases control
> from the VM Ware application.
>
> Here is the dmesg.boot
>
> OpenBSD 3.7 (GENERIC) #50: Sun Mar 20 00:01:57 MST 2005
> [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: Intel(R) Pentium(R) 4 CPU 3.00GHz ("GenuineIntel" 686-class) 3 GHz
> cpu0:
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,PNI
> real mem = 267952128 (261672K)
> avail mem = 237731840 (232160K)
> using 3296 buffers containing 13500416 bytes (13184K) of memory
> mainbus0 (root)
> bios0 at mainbus0: AT/286+(a5) BIOS, date 02/11/05, BIOS32 rev. 0 @ 0xfd880
> apm0 at bios0: Power Management spec V1.2
> apm0: AC on, battery charge unknown
> pcibios0 at bios0: rev 2.1 @ 0xfd880/0x780
> pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdf30/176 (9 entries)
> pcibios0: PCI Interrupt Router at 000:07:0 ("Intel 82371FB ISA" rev 0x00)
> pcibios0: PCI bus #1 is the last bus
> bios0: ROM list: 0xc/0x8000 0xc8000/0x1000 0xdc000/0x4000! 0xe/0x4000!
> cpu0 at mainbus0
> pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
> pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x01
> ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x01
> pci1 at ppb0 bus 1
> pcib0 at pci0 dev 7 function 0 "Intel 82371AB PIIX4 ISA" rev 0x08
> pciide0 at pci0 dev 7 function 1 "Intel 82371AB IDE" rev 0x01: DMA,
> channel 0 configured to compatibility, channel 1 configured to
> compatibility
> wd0 at pciide0 channel 0 drive 0:
> wd0: 64-sector PIO, LBA, 4096MB, 8388608 sectors
> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
> atapiscsi0 at pciide0 channel 1 drive 0
> scsibus0 at atapiscsi0: 2 targets
> cd0 at scsibus0 targ 0 lun 0: <_NEC, DVD_RW ND-3520A, 1.04> SCSI0
> 5/cdrom removable
> cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
> uhci0 at pci0 dev 7 function 2 "Intel 82371AB USB" rev 0x00: irq 9
> usb0 at uhci0: USB revision 1.0
> uhub0 at usb0
> uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> uhub0: 2 ports with 2 removable, self powered
> "Intel 82371AB Power Mgmt" rev 0x08 at pci0 dev 7 function 3 not configured
> vga1 at pci0 dev 15 function 0 "VMware Virtual SVGA II" rev 0x00
> wsdisplay0 at vga1: console (80x25, vt100 emulation)
> wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
> mpt0 at pci0 dev 16 function 0 "Symbios Logic 53c1030" rev 0x01: irq 11
> mpt0: running in vmware, skipping pageretrieval
> mpt0: IM support: 0
> scsibus1 at mpt0: 16 targets
> le1 at pci0 dev 17 function 0 "AMD 79c970 PCnet-PCI" rev 0x10: irq 10
> le1: address 00:0c:29:91:ef:ac
> le1: 8 receive buffers, 2 transmit buffers
> eap0 at pci0 dev 18 function 0 "Ensoniq AudioPCI97" rev 0x02: irq 9
> ac97: codec id 0x43525913 (Cirrus Logic CS4297A rev 3)
> audio0 at eap0
> midi0 at eap0:
> isa0 at pcib0
> isadma0 at isa0
> pckbc0 at isa0 port 0x60/5
> pckbd0 at pckbc0 (kbd slot)
> pckbc0: using irq 1 for kbd slot
> wskbd0 at pckbd0 (mux 1 ignored for console): console keyboard, using
> wsdisplay0
> pmsi0 at pckbc0 (aux slot)
> pckbc0: using irq 12 for aux slot
> wsmouse0 at pmsi0 mux 0
> pcppi0 at isa0 port 0x61
> midi1 at pcppi0:
> sysbeep0 at pcppi0
> lpt0 at isa0 port 0x378/4 irq 7
> npx0 at isa0 port 0xf0/16: using exception 16
> pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
> pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
> fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
> fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
> biomask eb65 netmask ef65 ttymask ffe7
> pctr: user-level cycle counter enabled
> dkcsum: wd0 matched BIOS disk 80
> root on wd0a
> rootdev=0x0 rrootdev=0x300 rawdev=0x302
OpenBSD 3.7 on VM Workstation 5
Just finished installing OpenBSD 3.7 from CD onto VM Ware Workstation
5 build 13124 with Windows XP sp2 as host OS.
As Client OS I chose FreeBSD, VM Ware tools not installed, virtual
terminals CTRL+ALT+Fn does not work since CTRL+ALT releases control
from the VM Ware application.
Here is the dmesg.boot
OpenBSD 3.7 (GENERIC) #50: Sun Mar 20 00:01:57 MST 2005
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Pentium(R) 4 CPU 3.00GHz ("GenuineIntel" 686-class) 3 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,PNI
real mem = 267952128 (261672K)
avail mem = 237731840 (232160K)
using 3296 buffers containing 13500416 bytes (13184K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(a5) BIOS, date 02/11/05, BIOS32 rev. 0 @ 0xfd880
apm0 at bios0: Power Management spec V1.2
apm0: AC on, battery charge unknown
pcibios0 at bios0: rev 2.1 @ 0xfd880/0x780
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdf30/176 (9 entries)
pcibios0: PCI Interrupt Router at 000:07:0 ("Intel 82371FB ISA" rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc/0x8000 0xc8000/0x1000 0xdc000/0x4000! 0xe/0x4000!
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x01
ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x01
pci1 at ppb0 bus 1
pcib0 at pci0 dev 7 function 0 "Intel 82371AB PIIX4 ISA" rev 0x08
pciide0 at pci0 dev 7 function 1 "Intel 82371AB IDE" rev 0x01: DMA,
channel 0 configured to compatibility, channel 1 configured to
compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 64-sector PIO, LBA, 4096MB, 8388608 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
atapiscsi0 at pciide0 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: <_NEC, DVD_RW ND-3520A, 1.04> SCSI0
5/cdrom removable
cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
uhci0 at pci0 dev 7 function 2 "Intel 82371AB USB" rev 0x00: irq 9
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
"Intel 82371AB Power Mgmt" rev 0x08 at pci0 dev 7 function 3 not configured
vga1 at pci0 dev 15 function 0 "VMware Virtual SVGA II" rev 0x00
wsdisplay0 at vga1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
mpt0 at pci0 dev 16 function 0 "Symbios Logic 53c1030" rev 0x01: irq 11
mpt0: running in vmware, skipping pageretrieval
mpt0: IM support: 0
scsibus1 at mpt0: 16 targets
le1 at pci0 dev 17 function 0 "AMD 79c970 PCnet-PCI" rev 0x10: irq 10
le1: address 00:0c:29:91:ef:ac
le1: 8 receive buffers, 2 transmit buffers
eap0 at pci0 dev 18 function 0 "Ensoniq AudioPCI97" rev 0x02: irq 9
ac97: codec id 0x43525913 (Cirrus Logic CS4297A rev 3)
audio0 at eap0
midi0 at eap0:
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0 (mux 1 ignored for console): console keyboard, using wsdisplay0
pmsi0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pmsi0 mux 0
pcppi0 at isa0 port 0x61
midi1 at pcppi0:
sysbeep0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
npx0 at isa0 port 0xf0/16: using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
biomask eb65 netmask ef65 ttymask ffe7
pctr: user-level cycle counter enabled
dkcsum: wd0 matched BIOS disk 80
root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302
