Re: OpenBSD on VMware ESXi
We have been running succesfully for a very long time, earlier editions (5.5) didn’t recover so well after storage hiccups, but these days running very well, no customizations needed. Sorry I can’t download the vmx right now. OpenBSD 6.3 GENERIC.MP#107 amd64 Running openbgpd, pf and relayd. Esxi 6.5 on Intel "Sandy Bridge” Generation EVC VMFS5 datastore on FC - Thick provision lazy zeroed VMXNET3 VM version 10 hardware compatibility Guest OS emulation - Freebsd 64bit 8vcpu 8gig mem > On 22 May 2019, at 12:46, Roderick wrote: > > > Hallo! > > As far as I read in WWW, OpenBSD do run on VMware ESXi out of the box. > > What does run better on amd64 virtual machine? i386 or amd64? > Are there reasons to preffer one to the other? > > Any recommendations in general? Current or stable? > > I have a virtual server, just for testing, at the moment with debian > and I find it awfull. Is there any reasong to keep it with linux? > > A detail: the console is in WWW, almost unreadable small fonts, > unstable, high latency (result of low price :). The best would > be a short installation path to get a listening sshd and end the > installation with shell login. > > Thanks for any hint > Rodrigo >
Re: OpenBSD on VMware ESXi
On Thu, 23 May 2019, Ian Darwin wrote: ..., but if you just wanted hosting in a hurry and cheap, vultr.com offers an entry-level vhost with OpenBSD 6.5 (or half a dozen others including BSDs and Linuxes) already installed (or you can use any ISO to install from) for US$2.50/month, with console access. I'm hosting my secondary DNS there and have had zero issues so far, though I didn't do a full reinstall. Well, I was just testing for being prepared when I need "hosting in a hurry and cheap". Waiting till one is in need makes the need and the price bigger. It was an offer of ionos.de, 500MB Ram, 10 GB SSD, 1vCore, Linux OS. For me OK, I like to test under spare resources. What runs under spare resources, runs much better under better conditions: it is a way to select what to run. The price of ionos.de: 1 EUR/Month, bound to 1 year, but one can end the contract in the first 30 days. Probably an offer to catch customers. The answer to my question to change to "LSI Logic SAS" was: they cannot do individual adaptions, but I can take a root server from them. This answer is perfectly acceptable, as also the ugly Web Console, if one can rely in their offer of 1 Eur/month, if it is not a trap to catch customers. They are not saying me, I must take a root server from them. It is possible to boot a CD and install an own OS. It would have been wonderfull to run OpenBSD, unfortunately almost worked. Rodrigo
Re: OpenBSD on VMware ESXi
On 2019-05-22 11:04, Stuart Henderson wrote: No idea, I don't run those. I have some experience: For over three years I have been running a qemu/KVM on Linux hypervisor for a lab that's had at least four running OpenBSD vms with virtio and e1000 nics. The obsd vms have never had a kernel panic, where they usually do basic routing/nating for a dev network, but occasionally do a lot of iperf traffic while I work on their pf.conf files. -- Sent from a phone, apologies for poor formatting. On 22 May 2019 17:20:16 Igor Podlesny wrote: On Wed, 22 May 2019 at 23:06, Stuart Henderson wrote: [...] vmxnet3 suffers kernel panics under some conditions, e1000 is rock solid for me. Any known similarities in regards of vio -- VirtIO network device (bhyve, KVM, QEMU, and VirtualBox)? -- End of message. Next message?
Re: Installer buggy (Re: OpenBSD on VMware ESXi)
Thanks, Jan, thanks Otto for the personal mail. Yes, the problem is sure that. I will se with the provider. When I changed the fdisk partition (first writes), they were not written, but the disklabel. When I did not, but changed the disklabel, then the disklabel was not changed. I hope enough dmesg is written before KARL!!! Rodrigo
Re: Installer buggy (Re: OpenBSD on VMware ESXi)
> On Thu, 23 May 2019, Jan Vlach wrote: > > > IIRC, pvscsi used to eat up first write to the paravirtual storage > > device with VMware. Not sure what's the current situation as I tend to > > use LSI Logic SAS. > > I do not understand very much, but yes, something is being eaten up. > > The fsck I mentioned before was not effective, I landed with a system > with ro mounted root system. It was impossible to do anything reasonable > with it. > > pci3 at ppb2 bus 3 > vmwpvs0 at pci3 dev 0 function 0 "VMware PVSCSI" rev 0x02: apic 1 int 18 ^^ https://marc.info/?l=openbsd-misc=144899602327183=2 I think you're seeing this. Change the Storage adapter in VMware to LSI Logic SAS or ask your VM provider to do this for you. JV
Re: Installer sucks ! (Re: OpenBSD on VMware ESXi)
On 5/23/19 7:51 AM, Roderick wrote: I wonder that no one noted this bugs before: are there no new people installing OpenBSD? Or it is a problem only with VMWare? Yes, the fact that nobody else has run into your problem suggest that it might in fact be your problem. Or your provider may be doing something strange. It's great that you are exploring this, and may yet find an actual issue, but if you just wanted hosting in a hurry and cheap, vultr.com offers an entry-level vhost with OpenBSD 6.5 (or half a dozen others including BSDs and Linuxes) already installed (or you can use any ISO to install from) for US$2.50/month, with console access. I'm hosting my secondary DNS there and have had zero issues so far, though I didn't do a full reinstall.
Re: Installer buggy (Re: OpenBSD on VMware ESXi)
On Thu, 23 May 2019, Jan Vlach wrote: IIRC, pvscsi used to eat up first write to the paravirtual storage device with VMware. Not sure what's the current situation as I tend to use LSI Logic SAS. I do not understand very much, but yes, something is being eaten up. The fsck I mentioned before was not effective, I landed with a system with ro mounted root system. It was impossible to do anything reasonable with it. I booted bsd.rd and did fsck /dev/rsd0a: tice!!! The first one did not mark it as clean. And now, I boot, but do not get a compleete /var/run/dmesg.boot for Tom Smyth. Below is all what I get. It seems, it was not the installer. :) Any idea how to continue? How to get the ESXi version? Thanks Rodrigo v 0x00 vga1: aperture needed wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) ppb1 at pci0 dev 17 function 0 "VMware PCI" rev 0x02 pci2 at ppb1 bus 2 ahci0 at pci2 dev 0 function 0 "VMware AHCI" rev 0x00: apic 1 int 18, AHCI 1.3 ahci0: port 0: 6.0Gb/s scsibus0 at ahci0: 32 targets cd0 at scsibus0 targ 0 lun 0: ATAPI 5/cdrom removable ppb2 at pci0 dev 21 function 0 "VMware PCIE" rev 0x01 pci3 at ppb2 bus 3 vmwpvs0 at pci3 dev 0 function 0 "VMware PVSCSI" rev 0x02: apic 1 int 18 scsibus1 at vmwpvs0: 16 targets sd0 at scsibus1 targ 0 lun 0: SCSI4 0/direct fixed naa.6000c290fd42ddbb45acd19e285b95bf sd0: 20480MB, 512 bytes/sector, 41943040 sectors ppb3 at pci0 dev 21 function 1 "VMware PCIE" rev 0x01 pci4 at ppb3 bus 4 ppb4 at pci0 dev 21 function 2 "VMware PCIE" rev 0x01 pci5 at ppb4 bus 5 ppb5 at pci0 dev 21 function 3 "VMware PCIE" rev 0x01 pci6 at ppb5 bus 6 ppb6 at pci0 dev 21 function 4 "VMware PCIE" rev 0x01 pci7 at ppb6 bus 7 ppb7 at pci0 dev 21 function 5 "VMware PCIE" rev 0x01 pci8 at ppb7 bus 8 ppb8 at pci0 dev 21 function 6 "VMware PCIE" rev 0x01 pci9 at ppb8 bus 9 ppb9 at pci0 dev 21 function 7 "VMware PCIE" rev 0x01 pci10 at ppb9 bus 10 ppb10 at pci0 dev 22 function 0 "VMware PCIE" rev 0x01 pci11 at ppb10 bus 11 vmx0 at pci11 dev 0 function 0 "VMware VMXNET3" rev 0x01: apic 1 int 19, address 00:50:56:0a:ad:be ppb11 at pci0 dev 22 function 1 "VMware PCIE" rev 0x01 pci12 at ppb11 bus 12 ppb12 at pci0 dev 22 function 2 "VMware PCIE" rev 0x01 pci13 at ppb12 bus 13 ppb13 at pci0 dev 22 function 3 "VMware PCIE" rev 0x01 pci14 at ppb13 bus 14 ppb14 at pci0 dev 22 function 4 "VMware PCIE" rev 0x01 pci15 at ppb14 bus 15 ppb15 at pci0 dev 22 function 5 "VMware PCIE" rev 0x01 pci16 at ppb15 bus 16 ppb16 at pci0 dev 22 function 6 "VMware PCIE" rev 0x01 pci17 at ppb16 bus 17 ppb17 at pci0 dev 22 function 7 "VMware PCIE" rev 0x01 pci18 at ppb17 bus 18 ppb18 at pci0 dev 23 function 0 "VMware PCIE" rev 0x01 pci19 at ppb18 bus 19 ppb19 at pci0 dev 23 function 1 "VMware PCIE" rev 0x01 pci20 at ppb19 bus 20 ppb20 at pci0 dev 23 function 2 "VMware PCIE" rev 0x01 pci21 at ppb20 bus 21 ppb21 at pci0 dev 23 function 3 "VMware PCIE" rev 0x01 pci22 at ppb21 bus 22 ppb22 at pci0 dev 23 function 4 "VMware PCIE" rev 0x01 pci23 at ppb22 bus 23 ppb23 at pci0 dev 23 function 5 "VMware PCIE" rev 0x01 pci24 at ppb23 bus 24 ppb24 at pci0 dev 23 function 6 "VMware PCIE" rev 0x01 pci25 at ppb24 bus 25 ppb25 at pci0 dev 23 function 7 "VMware PCIE" rev 0x01 pci26 at ppb25 bus 26 ppb26 at pci0 dev 24 function 0 "VMware PCIE" rev 0x01 pci27 at ppb26 bus 27 ppb27 at pci0 dev 24 function 1 "VMware PCIE" rev 0x01 pci28 at ppb27 bus 28 ppb28 at pci0 dev 24 function 2 "VMware PCIE" rev 0x01 pci29 at ppb28 bus 29 ppb29 at pci0 dev 24 function 3 "VMware PCIE" rev 0x01 pci30 at ppb29 bus 30 ppb30 at pci0 dev 24 function 4 "VMware PCIE" rev 0x01 pci31 at ppb30 bus 31 ppb31 at pci0 dev 24 function 5 "VMware PCIE" rev 0x01 pci32 at ppb31 bus 32 ppb32 at pci0 dev 24 function 6 "VMware PCIE" rev 0x01 pci33 at ppb32 bus 33 ppb33 at pci0 dev 24 function 7 "VMware PCIE" rev 0x01 pci34 at ppb33 bus 34 isa0 at pcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 irq 1 irq 12 pckbd0 at pckbc0 (kbd slot) wskbd0 at pckbd0: console keyboard, using wsdisplay0 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 softraid0 at root scsibus2 at softraid0: 256 targets root on rd0a swap on rd0b dump on rd0b syncing disks... done rebooting... OpenBSD 6.4 (GENERIC) #926: Thu Oct 11 13:43:06 MDT 2018 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC real mem = 536227840 (511MB) avail mem = 511414272 (487MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: date 09/19/18, BIOS32 rev. 0 @ 0xfd780, SMBIOS rev. 2.7 @ 0xe0010 (620 entries) bios0: vendor Phoenix Technologies LTD version "6.00" date 09/19/2018 bios0: VMware, Inc. VMware Virtual Platform acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT FACP BOOT APIC MCFG SRAT HPET WAET acpi0: wakeup devices PCI0(S3) USB_(S1) P2P0(S3) S1F0(S3) S2F0(S3) S8F0(S3) S16F(S3) S18F(S3) S22F(S3) S23F(S3) S24F(S3) S25F(S3) PE40(S3) S1F0(S3) PE50(S3) S1F0(S3) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits
Re: Installer sucks ! (Re: OpenBSD on VMware ESXi)
The web console copy/paste functionnality is a VMWare limitation. I don't think it ever worked. It think would require the console to emulate/simulate key presses depending on what is pasted and somehow assuming what the VM keymap is. I didn't try to install 6.5 on ESXI yet, but I definitely installed 6.4. On a lot of ESXi versions from 5.5 to 6.7. So you could try to install 6.4 to see if you have the same problems ? Never experienced your problems, although I experienced some strange behaviors with disklabeling (if I remember well sometimes it couldn't install the bootloader or wouldn't boot after install). They were resolved by : - dropping to the shell at the start of the install - fdisk -i - return to the install and proceed normally Never tried to install a custom label on ESXi, but did it sucessfully on virtualbox with 6.5 without any issue (not even needed to fdisk -i). What ESXi version are you running ? What disk controller are you showing to OpenBSD ? AB Le 2019-05-23 12:17, Roderick a écrit : On Thu, 23 May 2019, Otto Moerbeek wrote: You must be doing something wrong. Since it installer surely leats you use a custom label. But since you are not showgin waht you did and you start insulting remarks, you won't get much help. Excuse me, although my words was not flowers, they were no insult. And there was no intention to insult, but it is realy nerving to deal with this web console. I cannot even do "copy and paste" in it for showing what I did. That is why I described it. It is sure a bug there. As said: it is not my previous experience with OpenBSD. There is sure a bug there: (1) if you installed a label before, the installer does not offer it to you. (2) it changes the "custom label" you write in the process. Really changes it. That can never be something else than a bug. (3) "disklabel -E /dev/sd0" puts alway cpg=1. The installer in the autoinstall puts numbers like 10277, 16384. Rodrigo
Re: Installer sucks ! (Re: OpenBSD on VMware ESXi)
include a copy of dmesg and you might get info about the virtual hardware / hypervisor you are running on On Thu, 23 May 2019 at 12:58, Roderick wrote: > > On Thu, 23 May 2019, Arnaud BRAND wrote: > > > So you could try to install 6.4 to see if you have the same problems ? > > Just copied bsd.rd from 6.4 in the root of the running system and > booted it. It was a litle better. > > My settings to fdisk, namely change of offset from 64 to 2048, were > ignored, and so the automatic disklabel offered an offset of 64. > > My settings to disklabel were this time not ignored. > > I will proceed to do "fdisk -i", perhaps reinstall, perhaps not. > > The changing of the offset from 64 to 2048 did help: after a "hardware > shutdown" I got again a bootable system, although a fsck is necessary. > > I wonder that no one noted this bugs before: are there no new people > installing OpenBSD? Or it is a problem only with VMWare? > > > What ESXi version are you running ? > > No idea. I must ask the hoster. > > > What disk controller are you showing to OpenBSD ? > > sd0 > > Thanks > Rodrigo > > -- Kindest regards, Tom Smyth.
Re: Installer sucks ! (Re: OpenBSD on VMware ESXi)
On Thu, 23 May 2019, Arnaud BRAND wrote: So you could try to install 6.4 to see if you have the same problems ? Just copied bsd.rd from 6.4 in the root of the running system and booted it. It was a litle better. My settings to fdisk, namely change of offset from 64 to 2048, were ignored, and so the automatic disklabel offered an offset of 64. My settings to disklabel were this time not ignored. I will proceed to do "fdisk -i", perhaps reinstall, perhaps not. The changing of the offset from 64 to 2048 did help: after a "hardware shutdown" I got again a bootable system, although a fsck is necessary. I wonder that no one noted this bugs before: are there no new people installing OpenBSD? Or it is a problem only with VMWare? What ESXi version are you running ? No idea. I must ask the hoster. What disk controller are you showing to OpenBSD ? sd0 Thanks Rodrigo
Re: Installer buggy (Re: OpenBSD on VMware ESXi)
Hi Rodrigo, IIRC, pvscsi used to eat up first write to the paravirtual storage device with VMware. Not sure what's the current situation as I tend to use LSI Logic SAS. Also, the first eaten-up write would explain why you're still seeing Linux partitions instead of OpenBSD. # fdisk sd0 Disk: sd0 geometry: 14593/255/63 [234441648 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: id C H S - C H S [ start:size ] --- 0: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused *3: A6 0 1 2 - 14592 254 63 [ 64: 234436481 ] OpenBSD jvl P.S. Description or even screenshots would help to know where you got stuck.
Re: Installer buggy (Re: OpenBSD on VMware ESXi)
Some more details about my experience. Excuseme that I dont take fotos of the screen and just describe, with the data y wrote down. As I wrote, yesterday my instalation did not work. Today morning I began to inspect with the shell of cd65.iso the partitions. fdisk gave me 41943040 sectors divided as follows: startsize 0* 2048 997376 Linux files 1 999424 40943616 Linux LVM disklabel gave me the sizes I typed: a 409600 0 4.2BSD b 1048576 409600 swap c 41943040 0 e 40484864 1458176 4.2BSD you see there the offset zero, no MBR. That is why the system did not boot. I went to the shell and did "fdisk -iy sd0". Now I have a partition 3 with the whole, 64 till 41942976. I started the installer and got an installation, as described, only with the automatic set values. The server hoster offers two kinds of shutting down the system by clicking on their web plattform: software and hardware. If I restart with "hardware", the system does not go up anymore, unless I reinstall the whole system. I though the hoster spoiled my disk because it writes in the first 2048 sectors. I went to install again, but with an offset of 2048 in the OpenBSD fdisk partition: no way, the installer ignores my settings. Rodrigo
Re: Installer sucks ! (Re: OpenBSD on VMware ESXi)
On Thu, 23 May 2019, Otto Moerbeek wrote: You must be doing something wrong. Since it installer surely leats you use a custom label. But since you are not showgin waht you did and you start insulting remarks, you won't get much help. Excuse me, although my words was not flowers, they were no insult. And there was no intention to insult, but it is realy nerving to deal with this web console. I cannot even do "copy and paste" in it for showing what I did. That is why I described it. It is sure a bug there. As said: it is not my previous experience with OpenBSD. There is sure a bug there: (1) if you installed a label before, the installer does not offer it to you. (2) it changes the "custom label" you write in the process. Really changes it. That can never be something else than a bug. (3) "disklabel -E /dev/sd0" puts alway cpg=1. The installer in the autoinstall puts numbers like 10277, 16384. Rodrigo
Re: Installer sucks ! (Re: OpenBSD on VMware ESXi)
On Thu, May 23, 2019 at 08:42:05AM +, Roderick wrote: > > Please, delete the cc to b...@openbsd.org in any answer. > > I am now, after hours typing in the damned web console and dealing > with the buggy installer, a little bit furious. This is definitively > not the OpenBSD I know! > > I did manage to install OpenBSD in VMWare, with the "autopartition", but I > want a custom partition due to my spare resources. I will now do a pause to > calm myself and then continue trying. I appreciate any hint > and thank for it very much. You must be doing something wrong. Since it installer surely leats you use a custom label. But since you are not showgin waht you did and you start insulting remarks, you won't get much help. > My remarks: > > (1) There no way to write a custom disklabel. After doing it, after giving the > command w and leaving with x, or after leaving with q, the installer > overwrites it with something arbitrary that may be unusable (then > one will note it no later than when loading the sets due to error > "cannot determine prefetch ...").OA see above > > (2) "disklabel -E" in cd65.iso puts a cpg=1 for all partitions: is that > correct? yes. The cpg field is used for some redundant fs metadata these days and will be filled in by newfs. > > (4) No way to leave the disklabel as it is. I wrote one with the shell > of cd65.iso (and cpg=1), also did nefwfs on the partitions, but > the installer do not show the partition it anywhere. One is compelled > to type again, and again comes the unusable arbitrary modification. see above > > (5) Auto allocaton puts partitions for X11 even if one selects > that one will run no X11. You can easily edit the auto label and delete partitions you do not want. > > (6) No vi in cd65.iso (but at least ed). > > Rodrigo >
Installer sucks ! (Re: OpenBSD on VMware ESXi)
Please, delete the cc to b...@openbsd.org in any answer. I am now, after hours typing in the damned web console and dealing with the buggy installer, a little bit furious. This is definitively not the OpenBSD I know! I did manage to install OpenBSD in VMWare, with the "autopartition", but I want a custom partition due to my spare resources. I will now do a pause to calm myself and then continue trying. I appreciate any hint and thank for it very much. My remarks: (1) There no way to write a custom disklabel. After doing it, after giving the command w and leaving with x, or after leaving with q, the installer overwrites it with something arbitrary that may be unusable (then one will note it no later than when loading the sets due to error "cannot determine prefetch ..."). (2) "disklabel -E" in cd65.iso puts a cpg=1 for all partitions: is that correct? (4) No way to leave the disklabel as it is. I wrote one with the shell of cd65.iso (and cpg=1), also did nefwfs on the partitions, but the installer do not show the partition it anywhere. One is compelled to type again, and again comes the unusable arbitrary modification. (5) Auto allocaton puts partitions for X11 even if one selects that one will run no X11. (6) No vi in cd65.iso (but at least ed). Rodrigo
Re: OpenBSD on VMware ESXi
On 5/22/2019 6:46 AM, Roderick wrote: > Any recommendations in general? Current or stable? I've had bad luck with softupdates and OpenBSD on ESXi when the ESXi datastore is on nfs. (Encountered on ESX 5.0, 5.1, and 5.5; I must not learn from my mistakes.) From what I can tell, if the nfs datastore takes too long to respond OpenBSD thinks the disk has gone away and panics. It's not OpenBSD's fault; if a real disk stopped responding a panic is probably the best result. Probably some tuning could be done to make the ESXi nfs timeout match the OpenBSD timeout, but it's easier to just not use softupdates and match the backing disk to my performance requirements. Note that softupdates are not enabled by default.
Re: OpenBSD on VMware ESXi
There's a bug in ESXI 6.5 specifically with vmxnet 3. We we're using Linux when it was noticed but anytime one of our floating ips (haproxy, keepalived) would switch to the node with vmxnet 3, instant kernel panic. I wonder if the problem is happening to you. https://kb.vmware.com/s/article/2151480 Like others have mentioned, E1000 doesn't have the problem and the issue also goes away after upgrading to 6.7. On Wed, May 22, 2019, 4:24 PM Roderick, wrote: > > Of course never booted: /var/log/messages is empty. :) > > I was too sleepy and optimistic. > > >
Re: OpenBSD on VMware ESXi
Of course never booted: /var/log/messages is empty. :) I was too sleepy and optimistic.
Re: OpenBSD on VMware ESXi
On Wed, 22 May 2019, Roderick wrote: The installed system seems to boot. Or perhaps not. I put in /etc/hostname.vmx0 with the help of cd65.iso: dhcp. But got no connection. Dificult to know without console. In the rescue disk was "dhclient vmx0" enough for getting connection. I did MBR, no gpt. I suppose that is not the problem. Rodrigo
Re: OpenBSD on VMware ESXi
No idea, I don't run those. -- Sent from a phone, apologies for poor formatting. On 22 May 2019 17:20:16 Igor Podlesny wrote: On Wed, 22 May 2019 at 23:06, Stuart Henderson wrote: [...] vmxnet3 suffers kernel panics under some conditions, e1000 is rock solid for me. Any known similarities in regards of vio -- VirtIO network device (bhyve, KVM, QEMU, and VirtualBox)? -- End of message. Next message?
Re: OpenBSD on VMware ESXi
I thanks a lot! I need a litle more help, I do not want to give up. :) I use now the terms of the provider, I do not like virtual machines and have no experience with them. I loaded cd65.iso in the providers platform as "other 64-bit OS image". Then I loaded it in the (virtual) DVD rom and started the server. bsd.rd booted, vmx0 appeared and did work, I installed the system with internet connection. The installed system seems to boot. I can start and stop it clicking in the web, with the offered "software method" that supposedly does not work without the "VMWare tools". But it complains that without "VMWare tools" there is no console, and I do not get the damned WWW console, called "KVM console" by the provider. And the installed and booted system do not react to ping and ssh, probably a net configuration is necessary. This means: I must use c65.iso as rescue system. c65.iso as (virtual) DVD do boot and I get the console, although I also get the same messages that without the "VMWare tools" that is not possible. Whay the difference? During installation there was something strange, but I think that it is not the origin of the problem. The automatic partition offered me: a 2048 on / c 41943040 i 997376 extfs (?!) to be mounted nowhere j 40943616 unknown to be mounted nowhere Although this was very suspicious, I answered yes for not dealing long with the console. It seems, it did no do partition and fs. It did not load the sets, it complained "cannot determine prefetch area ...". Perhaps a bug? I did the partition manually (what I always use to do). 200 times more than that a on /, 512 times more that that a as b (swap), and the rest as e on /usr. There was then no problem with the installation. But was that ext2fs that appeared in the automatic partition necessary for something?! Thanks again for any hint Rodrigo
Re: OpenBSD on VMware ESXi
On Wed, 22 May 2019 at 23:06, Stuart Henderson wrote: [...] > vmxnet3 suffers kernel panics under some conditions, e1000 is rock solid > for me. Any known similarities in regards of vio -- VirtIO network device (bhyve, KVM, QEMU, and VirtualBox)? -- End of message. Next message?
Re: OpenBSD on VMware ESXi
On 2019-05-22, Reyk Floeter wrote: > > But unfortunately, there is no openbsd template. So use "Other 64bit" > and enable vmxnet3 manually, as mentioned in vmx(4): > > The following entry must be added to the VMware configuration file to > provide the vmx device: > >ethernet0.virtualDev = "vmxnet3" > > This is much better than the e1000 emulation. vmxnet3 suffers kernel panics under some conditions, e1000 is rock solid for me.
Re: OpenBSD on VMware ESXi
On 2019-05-22 09:25, mxb wrote: I think FreeBSD or any Linux template will work just fine and add vmxnet3. However, last I checked (1year ago) vmxnet3 been less stable than e1000 under pressure. Don't use the Linux templates. I would recommend against using the FreeBSD templates, and go with "Other (64-bit)" instead. YMMV on using FreeBSD vs Other, I haven't seen consistent results here yet... just don't pick Linux, or DOS, or Windows - in some situations, that allows VMware to take certain shortcuts that are based on assumptions about the Linux/Win/etc. kernel & device drivers that (probably) aren't valid under OpenBSD. Various people have reported different problems with vmxnet3; I'm aware of at least 4 or 5 different environment-specific issues (i.e. can't be reproduced on any other vSphere/ESXi system). I have some of those problems, and I cannot reproduce them outside my production environment, but they don't prevent me from running OpenBSD. Workarounds: * use vmxnet2 * use e1000 If vmxnet3 and pvscsi work for you (you'll know pretty darn fast!), use them. When they work, which is usually (in my experience), they're generally very stable and high-performing compared to the emulated h/w (e1000, lsisas, lsiscsi, buslogic). I also experience timer issues, and I've had to specify kern.timecounter.hardware=i8254 in sysctl.conf. This is likely a VMware problem, not an OpenBSD problem, but it's non-trivial to diagnose. (Even i8254 doesn't work perfectly: e.g. usleep() isn't very accurate in my VMs!) I'm also running these VMs on very heavily-loaded hosts, which is probably a factor. My disk write throughput is horrible, but that's an interaction between how OpenBSD does writes, how VMware handles writes into thin-provisioned disks, and how my NFS storage handles writes on thin-provisioned volumes; it's not an OpenBSD problem, strictly speaking, although that's the only place it's normally visible. Overall, OpenBSD works well under ESXi, but there are semi-random problems that do have workarounds. Several years ago, Theo noted (approximately, I'm going from memory here AND paraphrasing) that it was hard enough for OpenBSD to handle broken hardware implementations, it's exponentially harder to handle an incorrect software emulation of hardware that was incorrect in the first place. This has proven accurate, and VMware doesn't really care much about OpenBSD, since I doubt it even registers on their radar so they're not terribly interested in fixing VMware bugs that are only visible under OpenBSD. (If you have a support contract, please submit bug reports to VMware. If enough of us do so, they might start fixing some of the problems.) -Adam
Re: OpenBSD on VMware ESXi
Vmware ESXI detects as FreeBSD 32bit. Set network interface to vmxnet3. Also you can use pvscsi driver ( I had some issues with filesystem corruption, there is a weird bug, but there is a workaround.) In general buslogic is more resilient. Regards, Em qua, 22 de mai de 2019 às 14:26, mxb escreveu: > I think FreeBSD or any Linux template will work just fine and add vmxnet3. > However, last I checked (1year ago) vmxnet3 been less stable than e1000 > under pressure. > > Sent from my iDevice > > > 22 мая 2019 г., в 13:47, Reyk Floeter написал(а): > > > >> On Wed, May 22, 2019 at 01:43:35PM +0200, Janne Johansson wrote: > >> Den ons 22 maj 2019 kl 12:52 skrev Roderick : > >> > >>> Hallo! > >>> As far as I read in WWW, OpenBSD do run on VMware ESXi out of the box. > >>> What does run better on amd64 virtual machine? i386 or amd64? > >>> Are there reasons to preffer one to the other? > >>> > >> > >> The ESX template for 64-bit comes with more recent "hardware" in the > >> environment IIRC, so it will be less tweaking the supplied virtualized > >> hardware if you select 64bit guest instead of 32bit. > >> Apart from that, 64bit is better on both virtual and real hw. > >> > > > > But unfortunately, there is no openbsd template. So use "Other 64bit" > > and enable vmxnet3 manually, as mentioned in vmx(4): > > > > The following entry must be added to the VMware configuration file to > > provide the vmx device: > > > > ethernet0.virtualDev = "vmxnet3" > > > > This is much better than the e1000 emulation. > > > > Reyk > > > >
Re: OpenBSD on VMware ESXi
I think FreeBSD or any Linux template will work just fine and add vmxnet3. However, last I checked (1year ago) vmxnet3 been less stable than e1000 under pressure. Sent from my iDevice > 22 мая 2019 г., в 13:47, Reyk Floeter написал(а): > >> On Wed, May 22, 2019 at 01:43:35PM +0200, Janne Johansson wrote: >> Den ons 22 maj 2019 kl 12:52 skrev Roderick : >> >>> Hallo! >>> As far as I read in WWW, OpenBSD do run on VMware ESXi out of the box. >>> What does run better on amd64 virtual machine? i386 or amd64? >>> Are there reasons to preffer one to the other? >>> >> >> The ESX template for 64-bit comes with more recent "hardware" in the >> environment IIRC, so it will be less tweaking the supplied virtualized >> hardware if you select 64bit guest instead of 32bit. >> Apart from that, 64bit is better on both virtual and real hw. >> > > But unfortunately, there is no openbsd template. So use "Other 64bit" > and enable vmxnet3 manually, as mentioned in vmx(4): > > The following entry must be added to the VMware configuration file to > provide the vmx device: > > ethernet0.virtualDev = "vmxnet3" > > This is much better than the e1000 emulation. > > Reyk >
Re: OpenBSD on VMware ESXi
On Wed, May 22, 2019 at 01:43:35PM +0200, Janne Johansson wrote: > Den ons 22 maj 2019 kl 12:52 skrev Roderick : > > > Hallo! > > As far as I read in WWW, OpenBSD do run on VMware ESXi out of the box. > > What does run better on amd64 virtual machine? i386 or amd64? > > Are there reasons to preffer one to the other? > > > > The ESX template for 64-bit comes with more recent "hardware" in the > environment IIRC, so it will be less tweaking the supplied virtualized > hardware if you select 64bit guest instead of 32bit. > Apart from that, 64bit is better on both virtual and real hw. > But unfortunately, there is no openbsd template. So use "Other 64bit" and enable vmxnet3 manually, as mentioned in vmx(4): The following entry must be added to the VMware configuration file to provide the vmx device: ethernet0.virtualDev = "vmxnet3" This is much better than the e1000 emulation. Reyk
Re: OpenBSD on VMware ESXi
Den ons 22 maj 2019 kl 12:52 skrev Roderick : > Hallo! > As far as I read in WWW, OpenBSD do run on VMware ESXi out of the box. > What does run better on amd64 virtual machine? i386 or amd64? > Are there reasons to preffer one to the other? > The ESX template for 64-bit comes with more recent "hardware" in the environment IIRC, so it will be less tweaking the supplied virtualized hardware if you select 64bit guest instead of 32bit. Apart from that, 64bit is better on both virtual and real hw. -- May the most significant bit of your life be positive.
Re: OpenBSD on VMware ESXi
Hi Roderick, use amd64 ... as it offers better mitigation's and has better support overall also if your hypervisor / machine offers nested virtualisation you would be able to run vmm inside your machine... i386 does not have support for vmm anymore use stable if you want to run in production, and want to avoid rebooting use current if you want to run and test latest features, ( and you dont mind rebooting to upgrade regularly) sysupgrade in current makes running current much easier, Vmxnet worked fine for me in the past. I have had issues with vmware 6.0 ... But these were solved with vmware6.0 Update 2 Thanks On Wed, 22 May 2019 at 12:09, Roderick wrote: > > Hallo! > > As far as I read in WWW, OpenBSD do run on VMware ESXi out of the box. > > What does run better on amd64 virtual machine? i386 or amd64? > Are there reasons to preffer one to the other? > > Any recommendations in general? Current or stable? > > I have a virtual server, just for testing, at the moment with debian > and I find it awfull. Is there any reasong to keep it with linux? > > A detail: the console is in WWW, almost unreadable small fonts, > unstable, high latency (result of low price :). The best would > be a short installation path to get a listening sshd and end the > installation with shell login. > > Thanks for any hint > Rodrigo > > -- Kindest regards, Tom Smyth.
Re: openbsd and vmware
On Thu Feb 7 2013 17:50, Jan Lambertz wrote: I also tried the socket trick in different setups but couldn't make it work. You *do* boot bsd.mp, right? Because bsd.rd never recognised a such configured VM as being SMP-capable in my case, and installed bsd.sp by default, instead. I tried a smp 4,threads 1 cores 1 sockets 4. Sysctl tells cpus are found but not used. Did you pass any special cpu information to qemu ? Sorry, I can't tell. I used RHEV 3.1 and by increasing the number of sockets, it linearly increased the number of cores, too. So, did you try 4 cores and 4 sockets, then?
Re: openbsd and vmware
I also tried the socket trick in different setups but couldn't make it work. I tried a smp 4,threads 1 cores 1 sockets 4. Sysctl tells cpus are found but not used. Did you pass any special cpu information to qemu ? Virtio: i'm not following current right now, but this are great news. Thank you.
Re: openbsd and vmware
On Thu Feb 7 2013 05:33, Jan Lambertz wrote: problems i found using kvm and openbsd: SMP not working as it should. I usually increase the number of virtual sockets to get those extra cores recognised by OpenBSD. This seems to make the hypervisor produce better ACPI routing information ... No virto drivers for openbsd(disk i miss the most) Hm? On -current: virtio2 at pci0 dev 5 function 0 Qumranet Virtio Storage rev 0x00: Virtio Block Device vioblk0 at virtio2 scsibus1 at vioblk0: 2 targets sd0 at scsibus1 targ 0 lun 0: VirtIO, Block Device, SCSI3 0/direct fixed sd0: 8192MB, 512 bytes/sector, 16777216 sectors virtio2: apic 1 int 10 ... and these ... virtio0 at pci0 dev 3 function 0 Qumranet Virtio Network rev 0x00: Virtio Network Device vio0 at virtio0: address 00:1a:4a:15:00:1f virtio0: apic 1 int 11 virtio6 at pci0 dev 9 function 0 Qumranet Virtio Memory rev 0x00: Virtio Memory Balloon Device viomb0 at virtio6 virtio6: apic 1 int 10
Re: openbsd and vmware
I'm Using KVM to virtualize OpenBSD 5.2 right now. I'm not that impressed about Vmware. I used a esxi server for 2 years extensivly. Things i didnt like : cli,closed software,bloated,technical documentation,gui. Not that KVM is much better at this point,but at least, i have the sources. problems i found using kvm and openbsd: SMP not working as it should. spice and qxl is not that good right now. No virto drivers for openbsd(disk i miss the most) Virt-viewer (remote spice viewer app) has some annoying keyboardlayout obfuscation. And with a look in the future i dont think the problems are going to to be solved. A recent article on phoronix.com had information about qxl getting KMS support. Correct me if im wrong, but this seems quite linux only to me. Non the less, i use KVM right now for a few OpenBSD,Linux and Win8 Maschines and overall it performs quite well. One of myinterests are VDI solutions, for that i will check citrix (xen) as an alternative in the future. --send from mobile
Re: openbsd and vmware
On 02/05/13 06:03, Bogdan Andu wrote: Hello, A few questions related to openbsd and vmware. What are the best practices to run OpenBSD in vmware? Just Do It? I haven't found any problems running OpenBSD in VMware ESXi or whatever they call it this week. I usually just tell the management tool the VM is a FreeBSD system. However, I'll admit my uses are fairly simple and more development/testing/low-need type stuff...i.e., VM appropriate. Are there any known problems one should take into consideration before virtualization? Lots. The exact same as any other OS, though. All eggs in one basket, security farce, complexity leading to increasing downtime, etc. In short, take almost everything VMware calls a benefit, invert, and you are close to reality. But again, nothing to do with OpenBSD. In terms of OpenBSD on VMware benefits...forget vmware tools. Much of the functionality is built into OpenBSD, unlike most other OSs pushed for virtualizing. I already have a functional machine runnig OpenBSD 5.2 /amd64 on bare metal. It is possible to create a virtual machine from one already running apart from installing the os in vm and then migrating and installing all applications? In almost all cases, you will find OpenBSD much easier than most other OS for this kind of stuff. Take a physical machine, disk image it, drop it on vmware, boot single user, mount root partition, rename hostname.whatever0 to hostname.em0, if you are not using DUIDs (and you switched from wd(4) to sd(4) disks), fix fstab (not necessary if you are using DUIDs), and it will just work (I may be forgetting something, but it's all totally simple). Try that with Windows or Linux -- not gonna happen. Note: P2V by raw disk image is not my recommended way of doing it, but I find the ability to do it shows how darned nifty OpenBSD is about things like this. Nick.
Re: openbsd and vmware
On Tue, Feb 05, 2013 at 03:03:34AM -0800, Bogdan Andu wrote: Hello, A few questions related to openbsd and vmware. What are the best practices to run OpenBSD in vmware? Are there any known problems one should take into consideration before virtualization? I already have a functional machine runnig OpenBSD 5.2 /amd64 on bare metal. It is possible to create a virtual machine from one already running apart from installing the os in vm and then migrating and installing all applications? Thank you in advanced, Bogdan Try to consider oVirt[1], it is open-source, based on top of KVM, aims to be vSphere competitor. Issues till now: * upstream do not provide all-in-one binary tarball, building from source would need to download additional java deps. * spice-xpi firefox plugin is buggy on OpenBSD, you can get spice console via little hacks in ovirt-cli thought. Any help would be appreciated. oVirt is upstream for RHEV-M, so there's big support behind. jirib
Re: openbsd and vmware
Try to consider oVirt[1], it is open-source, based on top of KVM, aims to be vSphere competitor. ...forgotten url - http://www.ovirt.org jirib
Re: openbsd and vmware
On Tue, Feb 05, 2013 at 07:19:02AM -0500, Nick Holland wrote: Take a physical machine, disk image it, drop it on vmware, boot single user, mount root partition, rename hostname.whatever0 to hostname.em0, You can also change the ethernet0.virtualDev setting from e1000 to vmxnet in your .vmx configuration file to use vic0 instead of em0. See the vic(4) manual page for more information... reyk
Re: openbsd and vmware
vmnet2 works fine too. On 5 feb 2013, at 16:14, Reyk Floeter r...@openbsd.org wrote: On Tue, Feb 05, 2013 at 07:19:02AM -0500, Nick Holland wrote: Take a physical machine, disk image it, drop it on vmware, boot single user, mount root partition, rename hostname.whatever0 to hostname.em0, You can also change the ethernet0.virtualDev setting from e1000 to vmxnet in your .vmx configuration file to use vic0 instead of em0. See the vic(4) manual page for more information... reyk
Re: openbsd and vmware
Am 05.02.2013 16:44, schrieb Dan Shechter: My product, which is a networking virtual appliance, is running on ESXi without any problems. I ran it as 32 bit since I also run the product on an HW appliance which do not run 64bit. Best regards, Dan On Tue, Feb 5, 2013 at 1:03 PM, Bogdan Andu bo...@yahoo.com wrote: Hello, A few questions related to openbsd and vmware. What are the best practices to run OpenBSD in vmware? Are there any known problems one should take into consideration before virtualization? I already have a functional machine runnig OpenBSD 5.2 /amd64 on bare metal. It is possible to create a virtual machine from one already running apart from installing the os in vm and then migrating and installing all applications? Thank you in advanced, Bogdan I am running a bridged firewall since OpenBSD 4.something on VMware Server/ESXi without problems. The only thing you will have to consider that snapshots while running the OS might leave you with an inconsisten filesystem because there are no vmware tools which quiesce your vm. In general, I try to take snapshots only when the vm is down, so I dont have to deal with filesystem repairs in any kind. But so far no problems with the only downtimes when the OS has to be updated. Regards, Matthias
Re: openbsd and vmware
I've personally never has issues and performance is good. I've been running a php-fpm/nginx stack with OpenBSD and VMware and performance has been great. Only issue is the tools install. I've had issues with that but it runs fine without it. I've also run it on KVM and found VMWare to be better. I have iSCSI storage with ZFS as a backend and can't complain Sent from my Android phone using TouchDown (www.nitrodesk.com) -Original Message- From: Bogdan Andu [bo...@yahoo.com] Received: Tuesday, 05 Feb 2013, 6:04am To: misc@openbsd.org [misc@openbsd.org] Subject: openbsd and vmware Hello, A few questions related to openbsd and vmware. What are the best practices to run OpenBSD in vmware? Are there any known problems one should take into consideration before virtualization? I already have a functional machine runnig OpenBSD 5.2 /amd64 on bare metal. It is possible to create a virtual machine from one already running apart from installing the os in vm and then migrating and installing all applications? Thank you in advanced, Bogdan
Re: openbsd and vmware
The only problem I ever had with running OpenBSD with ESX/i was doing snapshots for backups with BackupExec. With the vmt(4), vCenter and BackupExec *think* that VMware Tools is running and try to quiesce the VM before backing it up. That fails, so the backup fails. Disabling the vmt(4) driver in the kernel allowed vCenter/BackupExec to see OpenBSD as a non-compatible snapshot capable system (even though I could take snapshots in general) and would back it up. On Tue, Feb 5, 2013 at 9:53 AM, Bentley, Dain dbent...@nas.edu wrote: I've personally never has issues and performance is good. I've been running a php-fpm/nginx stack with OpenBSD and VMware and performance has been great. Only issue is the tools install. I've had issues with that but it runs fine without it. I've also run it on KVM and found VMWare to be better. I have iSCSI storage with ZFS as a backend and can't complain Sent from my Android phone using TouchDown (www.nitrodesk.com) -Original Message- From: Bogdan Andu [bo...@yahoo.com] Received: Tuesday, 05 Feb 2013, 6:04am To: misc@openbsd.org [misc@openbsd.org] Subject: openbsd and vmware Hello, A few questions related to openbsd and vmware. What are the best practices to run OpenBSD in vmware? Are there any known problems one should take into consideration before virtualization? I already have a functional machine runnig OpenBSD 5.2 /amd64 on bare metal. It is possible to create a virtual machine from one already running apart from installing the os in vm and then migrating and installing all applications? Thank you in advanced, Bogdan
Re: OpenBSD ESXi VMware image on Soekris Net5501
* Michal mic...@sharescope.co.uk [2009-05-21 11:01]: Oh I didnt realise it was that under-poweredoh now I just feel stupid :( Well, we are all laughing at you. but only because too many of us get hit with this bullshit at work. http://a2.vox.com/6a00d09e512cfdbe2b00f30f5b193a0001-pi I mean everyone knows Vmware makes everything run faster, use less power, more securely, gives blowjobs under the table, etc.. And the great part about your only tool being a hammer is you sure spend less time deciding what to use so it's more efficient :)
Re: OpenBSD ESXi VMware image on Soekris Net5501
I know that VMware does all that, I even hear the next release makes you coffee while you use it and not just instant, as in proper Columbian brewed coffee...fantastic. But still yes, every once in a while a smart arse pops his head up and claims he has heard of this VMWARE blah blah blah. It's nice to know I can bring a little with of laughter to people's lives though, it sure beats everyone moaning at me as they cannot read e-mails clearly marked IMPORTANT, DO THIS OR YOUR E-MAIL WONT WORK, then moaning when their email doesn't work -Original Message- From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of Bob Beck Sent: 26 May 2009 17:35 To: Michal Cc: misc@openbsd.org Subject: Re: OpenBSD ESXi VMware image on Soekris Net5501 * Michal mic...@sharescope.co.uk [2009-05-21 11:01]: Oh I didnt realise it was that under-poweredoh now I just feel stupid :( Well, we are all laughing at you. but only because too many of us get hit with this bullshit at work. http://a2.vox.com/6a00d09e512cfdbe2b00f30f5b193a0001-pi I mean everyone knows Vmware makes everything run faster, use less power, more securely, gives blowjobs under the table, etc.. And the great part about your only tool being a hammer is you sure spend less time deciding what to use so it's more efficient :)
Re: OpenBSD ESXi VMware image on Soekris Net5501
When you've got something to start with job it up on Sourceforge and pop us a message on this list. Maybe some of us have a use for the same application and will want to help. On Fri, May 22, 2009 at 8:05 PM, Obiozor Okeke obiozorok...@yahoo.comwrote: Thanks Ross/Ed, yes we're going to dump the custom Windows app and use an open source solution using Samba's file share capability (with Samba running on OBSD of course :). --- On Fri, 5/22/09, Ross Cameron abal...@gmail.com wrote: From: Ross Cameron abal...@gmail.com Subject: Re: OpenBSD ESXi VMware image on Soekris Net5501 To: Ed Ahlsen-Girard eagir...@cox.net Cc: misc@openbsd.org Date: Friday, May 22, 2009, 9:05 AM On Fri, May 22, 2009 at 5:56 PM, Ed Ahlsen-Girard eagir...@cox.net wrote: On 2009-05-22 Ross Cameron wrote: Certainly the hardware chosen isnt anywhere NEAR potent enough,... and u're leaving ure whole configuration open for attack via the ESXi sub layer. Why not just port the custom app to OpenBSD and run the configuration natively on the hardware? There are apps on Windows for which porting to OpenBSD would be roughly equivalent to porting to NetWare Virtual Loadable Module. Maybe he doesn't mind doing it all over from scratch, but that's about what it might turn out to be. True but then again I generally find that rewriting and targeting the code for portability and re-use is worth the efforts in the long run. Painting you're self into a corner with regards to coding standards/languages/host OS are generally just a headache waiting to happen in the years to come. -- Opportunity is most often missed by people because it is dressed in overalls and looks like work. Thomas Alva Edison Inventor of 1093 patents, including: The light bulb, phonogram and motion pictures.
Re: OpenBSD ESXi VMware image on Soekris Net5501
On Thu, May 21, 2009 at 6:53 PM, obiozorok...@yahoo.com wrote: Well I'm certainly no expert in all this and I'm happy to be corrected before I make any more mistakes with my configuration. Man am I glad I put this post out because I'm getting such great feedback! I'll have to re-think this but I honestly thought (I guess I'm wrong) that if I my first OpenBSD VM image running on ESXi as my strong firewall I would be ok. Basically its just a virtualization of my physical environment but all on one box with 3 VM images. So my idea was to have second OpenBSD image (not the firewall OpenBSD image) running with Samba as my Domain Controller and File server, and Email server and then the third Windows VM running just the custom app. I figured that as long as all the 'Net traffic hit my first OpenBSD VM and was properly filtered and controlled by pf, spam greylisting, brute force checked, etc I would be ok? No? Certainly the hardware chosen isnt anywhere NEAR potent enough,... and u're leaving ure whole configuration open for attack via the ESXi sub layer. Why not just port the custom app to OpenBSD and run the configuration natively on the hardware?
Re: OpenBSD ESXi VMware image on Soekris Net5501
On 2009-05-22 Ross Cameron wrote: Certainly the hardware chosen isnt anywhere NEAR potent enough,... and u're leaving ure whole configuration open for attack via the ESXi sub layer. Why not just port the custom app to OpenBSD and run the configuration natively on the hardware? There are apps on Windows for which porting to OpenBSD would be roughly equivalent to porting to NetWare Virtual Loadable Module. Maybe he doesn't mind doing it all over from scratch, but that's about what it might turn out to be. -- Ed Ahlsen-Girard [demime 1.01d removed an attachment of type APPLICATION/DEFANGED which had a name of eagirard.8621DEFANGED-vcf]
Re: OpenBSD ESXi VMware image on Soekris Net5501
On Fri, May 22, 2009 at 5:56 PM, Ed Ahlsen-Girard eagir...@cox.net wrote: On 2009-05-22 Ross Cameron wrote: Certainly the hardware chosen isnt anywhere NEAR potent enough,... and u're leaving ure whole configuration open for attack via the ESXi sub layer. Why not just port the custom app to OpenBSD and run the configuration natively on the hardware? There are apps on Windows for which porting to OpenBSD would be roughly equivalent to porting to NetWare Virtual Loadable Module. Maybe he doesn't mind doing it all over from scratch, but that's about what it might turn out to be. True but then again I generally find that rewriting and targeting the code for portability and re-use is worth the efforts in the long run. Painting you're self into a corner with regards to coding standards/languages/host OS are generally just a headache waiting to happen in the years to come.
Re: OpenBSD ESXi VMware image on Soekris Net5501
Ross Cameron wrote: On Fri, May 22, 2009 at 5:56 PM, Ed Ahlsen-Girard eagir...@cox.net mailto:eagir...@cox.net wrote: -(snip)- There are apps on Windows for which porting to OpenBSD would be roughly equivalent to porting to NetWare Virtual Loadable Module. Maybe he doesn't mind doing it all over from scratch, but that's about what it might turn out to be. True but then again I generally find that rewriting and targeting the code for portability and re-use is worth the efforts in the long run. Painting you're self into a corner with regards to coding standards/languages/host OS are generally just a headache waiting to happen in the years to come. I am sympathetic with that POV. It's part of why I decided to learn Perl instead of VB when I wanted to automate accounts on a Windows web server. When I had to clean up and migrate a Linux web server years later (without having meaningful Linux experience), I was very happy about my choice. [demime 1.01d removed an attachment of type APPLICATION/DEFANGED which had a name of eagirard.26699DEFANGED-vcf]
Re: OpenBSD ESXi VMware image on Soekris Net5501
Thanks Ross/Ed, yes we're going to dump the custom Windows app and use an open source solution using Samba's file share capability (with Samba running on OBSD of course :). --- On Fri, 5/22/09, Ross Cameron abal...@gmail.com wrote: From: Ross Cameron abal...@gmail.com Subject: Re: OpenBSD ESXi VMware image on Soekris Net5501 To: Ed Ahlsen-Girard eagir...@cox.net Cc: misc@openbsd.org Date: Friday, May 22, 2009, 9:05 AM On Fri, May 22, 2009 at 5:56 PM, Ed Ahlsen-Girard eagir...@cox.net wrote: On 2009-05-22 Ross Cameron wrote: Certainly the hardware chosen isnt anywhere NEAR potent enough,... and u're leaving ure whole configuration open for attack via the ESXi sub layer. Why not just port the custom app to OpenBSD and run the configuration natively on the hardware? There are apps on Windows for which porting to OpenBSD would be roughly equivalent to porting to NetWare Virtual Loadable Module. Maybe he doesn't mind doing it all over from scratch, but that's about what it might turn out to be. True but then again I generally find that rewriting and targeting the code for portability and re-use is worth the efforts in the long run. Painting you're self into a corner with regards to coding standards/languages/host OS are generally just a headache waiting to happen in the years to come.
Re: OpenBSD ESXi VMware image on Soekris Net5501
Hi, 2009/5/21 Obiozor Okeke obiozorok...@yahoo.com: Hi Diana (and Stuart) thanks for all your advice. The problem or nut we're trying to crack is that we're trying to deploy OpenBSD to remote clients and we wanted an inexpensive but very high reliability system with the flexibility to change configurations (switch in/out different VMs) and add/modify services remotely on-the-fly. For example we could upgrade a client from 4.4 to 4.5 along with all the custom apps and client data packaged in a VM. We would grab the old 4.4 VM bring it back to our lab, then upgrade and re-configure it the way we wanted to and drop it back on the ESXi. Then just change the network configs and switch the old for the new all remotely without ever visiting the client Thanks again all. Even if this were feasible (given the hardware limitations of the 5501), you would still have to maintain ESX in a manner which requires console access. Wrapping OpenBSD up in ESX defeats the typical purpose of using OpenBSD. ESX and other x86 virtualization software introduces a whole new vulnerable layer of software which requires patching and rebooting. Take it from the horses mouth... A critical vulnerability in the virtual machine display function might allow a guest operating system to run code on the host. The Common Vulnerabilities and Exposures Project (cve.mitre.org) has assigned the name CVE-2009-1244 to this issue. http://kb.vmware.com/selfservice/microsites/search.do?language=en_UScmd=disp layKCexternalId=1009853 A memory corruption condition might occur in the virtual machine hardware. A malicious request sent from the guest operating system to the virtual hardware might cause the virtual hardware to write to uncontrolled physical memory. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2008-4917 to this issue. http://kb.vmware.com/selfservice/microsites/search.do?language=en_UScmd=disp layKCexternalId=1007507 VMware addresses an in-guest privilege escalation on 64-bit guest operating systems. VMware products emulate hardware functions including CPU, memory, and I/O. A flaw in VMware's CPU hardware emulation could allow the virtual CPU to jump to an incorrect memory address. Exploitation of this issue on the guest operating system does not lead to a compromise of the host system, but could lead to a privilege escalation on guest operating systems. An attacker would need to have a user account on the guest operating system. Affected guest operating systems include 64-bit Windows, 64-bit FreeBSD, and possibly other 64-bit operating systems. http://kb.vmware.com/selfservice/microsites/search.do?language=en_UScmd=disp layKCexternalId=1007090 This is just a small sample. All this will get you extra complexity and the doubt that a problem with the guest software is really with it or the host. Shane
Re: OpenBSD ESXi VMware image on Soekris Net5501
I ran OpenBSD on ESXi on a Dell 905 at my old job and it worked quite well. It wasn't really fast, but it didn't need to be. All it did was mail web forms. The security auditors didn't even mention it in their report. Ed Ahlsen-Girard
OFF TOPIC: Re: OpenBSD ESXi VMware image on Soekris Net5501
David - it looks like my mobile device did a horrendous job of displaying your email so I apologise for coming off a bit half-cocked in the last email (and despite it being so much more OT conversation on the list, I still wanted to do it publicly). 2009/5/20 David Talkington dt...@flyingjoke.org: Kevin Wilcox wrote: that practically necessitates IBM, Sun, HP or Dell hardware. No it doesn't. That was based on my last review of the .pdf we received from our VMWare rep that was, admittedly, some time ago. I just checked the ESXi HCL and I'm glad to see that support has grown *substantially*, particularly with them offering ESXi. So, my apologies for outdated information. Skip the virtualisation cruft and install natively. That isn't a helpful or enlightened answer (not that one should expect help with this topic here). Agreed. A better reply (though perhaps less relevant) would be, O.P. - I do not have experience with OBSD on VMWare ESXi on a Soekris. I do have quite a bit of experience with OpenBSD on VMWare ESX on officially supported hardware and the results vary depending on load and how much tweaking you may or may not have to do with your configuration. For certain storage backends we have to do some minor voodoo to the disk configuration before the VM is made aware of the disk - this has caused several of our OpenBSD VMs to panic, an issue that in no way, shape, form or fashion am I blaming on OpenBSD - that problem lies with VMWare. On the other hand, I have virtualised OpenBSD firewalls on plain configurations sitting in front of virtualised servers (yes, it works for our needs) that never hiccup. The latest I am using is 4.4 as I've been unable to take any of those machines down for upgrade since receiving the 4.5 cds. Because of the quirks that are introduced with running on top of VMWare, if you have the hardware and this is a single use machine, I can't stress highly enough that, if at all possible, you should skip the virtualisation cruft and install natively. Performance *will* be better, as will reliability and the chance of finding some form of community assistance. O.P., you should start here for detailed ESXi hardware support info: http://www.vm-help.com/ And the official VMWare HCL here should you ever decide to move to supported hardware: http://www.vmware.com/resources/compatibility/search.php?action=basedeviceCa tegory=server kmw -- To take from one, because it is thought that his own industry and that of his fathers has acquired too much, in order to spare to others, who, or whose fathers have not exercised equal industry and skill, is to violate arbitrarily the first principle of association, bthe guarantee to every one of a free exercise of his industry, the fruits acquired by it.'
Re: OpenBSD ESXi VMware image on Soekris Net5501
Hi Diana (and Stuart) thanks for all your advice. The problem or nut we're trying to crack is that we're trying to deploy OpenBSD to remote clients and we wanted an inexpensive but very high reliability system with the flexibility to change configurations (switch in/out different VMs) and add/modify services remotely on-the-fly. For example we could upgrade a client from 4.4 to 4.5 along with all the custom apps and client data packaged in a VM. We would grab the old 4.4 VM bring it back to our lab, then upgrade and re-configure it the way we wanted to and drop it back on the ESXi. Then just change the network configs and switch the old for the new all remotely without ever visiting the client Thanks again all. --- On Wed, 5/20/09, Diana Eichert deich...@wrench.com wrote: From: Diana Eichert deich...@wrench.com Subject: Re: OpenBSD ESXi VMware image on Soekris Net5501 To: misc@openbsd.org Date: Wednesday, May 20, 2009, 7:16 PM On Wed, 20 May 2009, Obiozor Okeke wrote: Hi I am hoping to run an ESXi OpenBSD 4.5 image on a Soekris Net5501 appliance and I was wondering if anyone has already tried successfully running ESXi on the Soekris Net5501 before I order the hardware? Any advice or comments is appreciated. Thanks in advance The better question is, What nut are you trying to crack? Why would you even consider running a virtualization system on what is effectively a 486? Okay, a 500MHz 586, but still, it's slow to start with. diana Past hissy-fits are not a predictor of future hissy-fits. Nick Holland(06 Dec 2005)
Re: OpenBSD ESXi VMware image on Soekris Net5501
On Thu, May 21, 2009 at 06:47:08AM -0700, Obiozor Okeke wrote: Hi Diana (and Stuart) thanks for all your advice. The problem or nut we're trying to crack is that we're trying to deploy OpenBSD to remote clients and we wanted an inexpensive but very high reliability system with the flexibility to change configurations (switch in/out different VMs) and add/modify services remotely on-the-fly. For example we could upgrade a client from 4.4 to 4.5 along with all the custom apps and client data packaged in a VM. We would grab the old 4.4 VM bring it back to our lab, then upgrade and re-configure it the way we wanted to and drop it back on the ESXi. Then just change the network configs and switch the old for the new all remotely without ever visiting the client No offense, but that's a terrible design. Get yourself two inexpensive systems (5501's are ok) and run them in a failover configuration. You have redundancy and the flexiblity to alternate between releases. Without the headache of middleware patches, an unsupported configuration, etc. -- Jason Dixon DixonGroup Consulting http://www.dixongroup.net/
Re: OpenBSD ESXi VMware image on Soekris Net5501
Wow!! Thanks guys for all your advice and the vm-help.com site! The OpenBSD community is fantastic!!! --- On Wed, 5/20/09, Kevin Wilcox ke...@tux.appstate.edu wrote: From: Kevin Wilcox ke...@tux.appstate.edu Subject: Re: OpenBSD ESXi VMware image on Soekris Net5501 To: David Talkington dt...@flyingjoke.org, misc@openbsd.org Date: Wednesday, May 20, 2009, 7:44 PM David, I'm currently mobile and unable to track down the HCL for ESX/i myself - thus my mentioning them to the original poster with what I could remember off the top of my head about supported machines. If that was an insufficient response then the OP is more than welcome to ignore it. On the other hand, the OP could always say, oh, ESXi HCL, I wonder... and google 'vmware esxi hardware compatibility'. kmw On 20/05/2009, David Talkington dt...@flyingjoke.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is way OT for this list, but: Kevin Wilcox wrote: My understanding is that it has a strict HCL, Yes it does. that practically necessitates IBM, Sun, HP or Dell hardware. No it doesn't. Skip the virtualisation cruft and install natively. That isn't a helpful or enlightened answer (not that one should expect help with this topic here). O.P., you should start here for detailed ESXi hardware support info: http://www.vm-help.com/ Cheers -d - -- David Talkington dt...@flyingjoke.org - -- PGP key: http://www.flyingjoke.org/keys/801E3976.asc (What's this? http://en.wikipedia.org/wiki/Digital_signature) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (GNU/Linux) iQEcBAEBAgAGBQJKFKpkAAoJEO7jL1CAHjl2+YgH/jwqmzLTgAGD1wDkxBPbJGZC qOQkT2lYoyy0obJ66777wfh/BRcZt88jIpnBVxPfprfnE3h4HUVw/0pP4xtriWcK nOQp+dWQeuhGYmV9QycWXAWvhRIrSwgmB3LagKPPYUQ4eR0aVz8NJ/LzkJpzwRb1 4kdxc4KXYxDG+HdaQ/mhQ4yGeY2AiTs41zs0oEjBQraeBb/FUwdXzKfFmK9brFxd kOEuKYUW9QAFnpzAmkKcFHM7QOQ8zIhLNIs7K/jTmLPVYycU14eutUUR+Q+SoI9W YriQmxcZ2PTxHIXA2hjvORM9FZiy0NwyDU8H9NHl2gA34rq1vheuVUnsHRJVH4U= =eE8z -END PGP SIGNATURE- -- Sent from my mobile device To take from one, because it is thought that his own industry and that of his fathers has acquired too much, in order to spare to others, who, or whose fathers have not exercised equal industry and skill, is to violate arbitrarily the first principle of association, bthe guarantee to every one of a free exercise of his industry, the fruits acquired by it.'
Re: OpenBSD ESXi VMware image on Soekris Net5501
On Thu, 21 May 2009, Obiozor Okeke wrote: Wow!! Thanks guys for all your advice and the vm-help.com site! The OpenBSD community is fantastic!!! FWIW, I've run ESXi on run of the mill desktops, you just have to know the various boot options to get the ESXi kernel to boot. But to sound like a broken record, I hate running higly customized configurations for production systems. Just because you can do something doesn't mean you should do something. However it's ultimately up to you, try it out and let us know how it worked. g.day
Re: OpenBSD ESXi VMware image on Soekris Net5501
On Thu, 21 May 2009, Obiozor Okeke wrote: Hi Diana (and Stuart) thanks for all your advice. The problem or nut we're trying to crack is that we're trying to deploy OpenBSD to remote clients and we wanted an inexpensive but very high reliability system with the flexibility to change configurations (switch in/out different VMs) and add/modify services remotely on-the-fly. For example we could upgrade a client from 4.A4 to 4.5 along with all the custom apps and client data packaged in a VM. We would grab the old 4.4 VM bring it back to our lab, then upgrade and re-configure it the way we wanted to and drop it back on the ESXi. Then just change the network configs and switch the old for the new all remotely without ever visiting the client Thanks again all. If you want to stick with the Soekris you might want to consider basing your solution on flashboot, http://lists.mindrot.org/pipermail/flashboot/2009-May/000223.html . Using a CF with multiple partitions would allow you to upgrade remotely the flashboot kernel. Of course this would take some work to fine tune the upgrade procedure to minimize failure mechanisms. diana
Re: OpenBSD ESXi VMware image on Soekris Net5501
Well I should have mentioned that the ESXi is also running a Windows server VM for a custom app that requires it. So the idea was to have one box running ESXi and reduce hardware costs. --- On Thu, 5/21/09, Jason Dixon ja...@dixongroup.net wrote: From: Jason Dixon ja...@dixongroup.net Subject: Re: OpenBSD ESXi VMware image on Soekris Net5501 To: Obiozor Okeke obiozorok...@yahoo.com Cc: misc@openbsd.org, Diana Eichert deich...@wrench.com Date: Thursday, May 21, 2009, 7:19 AM On Thu, May 21, 2009 at 06:47:08AM -0700, Obiozor Okeke wrote: Hi Diana (and Stuart) thanks for all your advice. The problem or nut we're trying to crack is that we're trying to deploy OpenBSD to remote clients and we wanted an inexpensive but very high reliability system with the flexibility to change configurations (switch in/out different VMs) and add/modify services remotely on-the-fly. For example we could upgrade a client from 4.4 to 4.5 along with all the custom apps and client data packaged in a VM. We would grab the old 4.4 VM bring it back to our lab, then upgrade and re-configure it the way we wanted to and drop it back on the ESXi. Then just change the network configs and switch the old for the new all remotely without ever visiting the client No offense, but that's a terrible design. Get yourself two inexpensive systems (5501's are ok) and run them in a failover configuration. You have redundancy and the flexiblity to alternate between releases. Without the headache of middleware patches, an unsupported configuration, etc. -- Jason Dixon DixonGroup Consulting http://www.dixongroup.net/
Re: OpenBSD ESXi VMware image on Soekris Net5501
On Thu, May 21, 2009 at 08:05:52AM -0700, Obiozor Okeke wrote: Well I should have mentioned that the ESXi is also running a Windows server VM for a custom app that requires it. So the idea was to have one box running ESXi and reduce hardware costs. BWAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHA *whew* Thanks, I needed that. -- Jason Dixon DixonGroup Consulting http://www.dixongroup.net/
Re: OpenBSD ESXi VMware image on Soekris Net5501
Jason Dixon wrote: On Thu, May 21, 2009 at 08:05:52AM -0700, Obiozor Okeke wrote: Well I should have mentioned that the ESXi is also running a Windows server VM for a custom app that requires it. So the idea was to have one box running ESXi and reduce hardware costs. BWAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHA *whew* Thanks, I needed that. Er yes, you will not be able to get there from here. Re-think. Don't run vmware on your firewall. If you virtualize your entire DC in to a single box, still don't run your firewall as a vm.
Re: OpenBSD ESXi VMware image on Soekris Net5501
-Original Message- From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of Jason Dixon Sent: 21 May 2009 17:08 To: Obiozor Okeke Cc: misc@openbsd.org; Diana Eichert Subject: Re: OpenBSD ESXi VMware image on Soekris Net5501 On Thu, May 21, 2009 at 08:05:52AM -0700, Obiozor Okeke wrote: Well I should have mentioned that the ESXi is also running a Windows server VM for a custom app that requires it. So the idea was to have one box running ESXi and reduce hardware costs. BWAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHA *whew* Thanks, I needed that. -- Jason Dixon DixonGroup Consulting http://www.dixongroup.net/ What a helpful e-mail that was. Thanks for helping the community with that one
Re: OpenBSD ESXi VMware image on Soekris Net5501
On Thu, May 21, 2009 at 11:35 PM, Michal mic...@sharescope.co.uk wrote: -Original Message- From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of Jason Dixon Sent: 21 May 2009 17:08 To: Obiozor Okeke Cc: misc@openbsd.org; Diana Eichert Subject: Re: OpenBSD ESXi VMware image on Soekris Net5501 On Thu, May 21, 2009 at 08:05:52AM -0700, Obiozor Okeke wrote: Well I should have mentioned that the ESXi is also running a Windows server VM for a custom app that requires it. B So the idea was to have one box running ESXi and reduce hardware costs. BWAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHA *whew* Thanks, I needed that. -- Jason Dixon DixonGroup Consulting http://www.dixongroup.net/ What a helpful e-mail that was. Thanks for helping the community with that one just think, a system with 500mhz and 512MB ram running two VMs. One of them is Windows (nt4? 98? 3.1?) , no less -- O ascii ribbon campaign - stop html mail - www.asciiribbon.org
Re: OpenBSD ESXi VMware image on Soekris Net5501
Oh I didnt realise it was that under-poweredoh now I just feel stupid :( -Original Message- From: Edho P Arief [mailto:edhopr...@gmail.com] Sent: 21 May 2009 17:54 To: Michal Cc: misc@openbsd.org Subject: Re: OpenBSD ESXi VMware image on Soekris Net5501 On Thu, May 21, 2009 at 11:35 PM, Michal mic...@sharescope.co.uk wrote: -Original Message- From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of Jason Dixon Sent: 21 May 2009 17:08 To: Obiozor Okeke Cc: misc@openbsd.org; Diana Eichert Subject: Re: OpenBSD ESXi VMware image on Soekris Net5501 On Thu, May 21, 2009 at 08:05:52AM -0700, Obiozor Okeke wrote: Well I should have mentioned that the ESXi is also running a Windows server VM for a custom app that requires it. So the idea was to have one box running ESXi and reduce hardware costs. BWAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHA *whew* Thanks, I needed that. -- Jason Dixon DixonGroup Consulting http://www.dixongroup.net/ What a helpful e-mail that was. Thanks for helping the community with that one just think, a system with 500mhz and 512MB ram running two VMs. One of them is Windows (nt4? 98? 3.1?) , no less -- O ascii ribbon campaign - stop html mail - www.asciiribbon.org
Re: OpenBSD ESXi VMware image on Soekris Net5501
On Thu, 21 May 2009, Michal wrote: Oh I didnt realise it was that under-poweredoh now I just feel stupid :( No needed to feel stupid, you added to the entertainment value of this thread. ;-) diana
Re: OpenBSD ESXi VMware image on Soekris Net5501
Well I'm certainly no expert in all this and I'm happy to be corrected before I make any more mistakes with my configuration. Man am I glad I put this post out because I'm getting such great feedback! I'll have to re-think this but I honestly thought (I guess I'm wrong) that if I my first OpenBSD VM image running on ESXi as my strong firewall I would be ok. Basically its just a virtualization of my physical environment but all on one box with 3 VM images. So my idea was to have second OpenBSD image (not the firewall OpenBSD image) running with Samba as my Domain Controller and File server, and Email server and then the third Windows VM running just the custom app. I figured that as long as all the 'Net traffic hit my first OpenBSD VM and was properly filtered and controlled by pf, spam greylisting, brute force checked, etc I would be ok? No? --- On Thu, 5/21/09, Dag Richards dagricha...@speakeasy.net wrote: From: Dag Richards dagricha...@speakeasy.net Subject: Re: OpenBSD ESXi VMware image on Soekris Net5501 To: misc@openbsd.org Date: Thursday, May 21, 2009, 9:24 AM Jason Dixon wrote: On Thu, May 21, 2009 at 08:05:52AM -0700, Obiozor Okeke wrote: Well I should have mentioned that the ESXi is also running a Windows server VM for a custom app that requires it. So the idea was to have one box running ESXi and reduce hardware costs. BWAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHA *whew* Thanks, I needed that. Er yes, you will not be able to get there from here. Re-think. Don't run vmware on your firewall. If you virtualize your entire DC in to a single box, still don't run your firewall as a vm.
Re: OpenBSD ESXi VMware image on Soekris Net5501
On Thu, 21 May 2009, obiozorok...@yahoo.com wrote: SNIP I'll have to re-think this but I honestly thought (I guess I'm wrong) that if I my first OpenBSD VM image running on ESXi as my strong firewall I would be ok. Basically its just a virtualization of my physical environment but all on one box with 3 VM images. So my idea was to have second OpenBSD image (not the firewall OpenBSD image) running with Samba as my Domain Controller and File server, and Email server and then the third Windows VM running just the custom app. I figured that as long as all the 'Net traffic hit my first OpenBSD VM and was properly filtered and controlled by pf, spam greylisting, brute force checked, etc I would be ok? No? Yes, you could do this (please NOT on a Soekris) but your system won't be any more secure than the weakest link. We haven't really seen the exploits for ESX, yet. Virtualization is really cool, you could own the virtual hardware and the O/S would never know. It takes the issue related to binary blobs to a whole new level. diana
Re: OpenBSD ESXi VMware image on Soekris Net5501
On Thu, May 21, 2009 at 11:06 AM, Diana Eichert deich...@wrench.com wrote: SNIP . Virtualization is really cool, you could own the virtual hardware and the O/S would never know. It takes the issue related to binary blobs to a whole new level. Entire machine as binary blob - never thought of it that way, but its sort of true.
Re: OpenBSD ESXi VMware image on Soekris Net5501
On Thu, May 21, 2009 at 09:53:16AM -0700, obiozorok...@yahoo.com wrote: Well I'm certainly no expert in all this and I'm happy to be corrected before I make any more mistakes with my configuration. Man am I glad I put this post out because I'm getting such great feedback! I'll have to re-think this but I honestly thought (I guess I'm wrong) that if I my first OpenBSD VM image running on ESXi as my strong firewall I would be ok. Basically its just a virtualization of my physical environment but all on one box with 3 VM images. So my idea was to have second OpenBSD image (not the firewall OpenBSD image) running with Samba as my Domain Controller and File server, and Email server and then the third Windows VM running just the custom app. I figured that as long as all the 'Net traffic hit my first OpenBSD VM and was properly filtered and controlled by pf, spam greylisting, brute force checked, etc I would be ok? No? No. The traffic doesn't hit your vm first; it hits the host os first. Any and all network stack issues there are still in play. --- On Thu, 5/21/09, Dag Richards dagricha...@speakeasy.net wrote: From: Dag Richards dagricha...@speakeasy.net Subject: Re: OpenBSD ESXi VMware image on Soekris Net5501 To: misc@openbsd.org Date: Thursday, May 21, 2009, 9:24 AM Jason Dixon wrote: On Thu, May 21, 2009 at 08:05:52AM -0700, Obiozor Okeke wrote: Well I should have mentioned that the ESXi is also running a Windows server VM for a custom app that requires it. So the idea was to have one box running ESXi and reduce hardware costs. BWAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHA *whew* Thanks, I needed that. Er yes, you will not be able to get there from here. Re-think. Don't run vmware on your firewall. If you virtualize your entire DC in to a single box, still don't run your firewall as a vm.
Re: OpenBSD ESXi VMware image on Soekris Net5501
2009/5/21 obiozorok...@yahoo.com: I'll have to re-think this but I honestly thought (I guess I'm wrong) that if I my first OpenBSD VM image running on ESXi as my strong firewall I would be ok. B Basically its just a virtualization of my physical environment but all on one box with 3 VM images. So my idea was to have second OpenBSD image (not the firewall OpenBSD image) running with Samba as my Domain Controller and File server, and Email server and then the third Windows VM running just the custom app. B I figured that as long as all the 'Net traffic hit my first OpenBSD VM and was properly filtered and controlled by pf, spam greylisting, brute force checked, etc I would be ok? B No? There are some strategic issues with virtualising a firewall. What should be the simplest, most rock solid member of your network is now on the same hardware as foo virtual machines. If one of the application servers is compromised then it's *possible* that the VMWare server itself could be compromised, rendering the firewall VM under the control of The Bad Guys. If one of the VMs screws the pooch and takes down the server then you've not only lost the ability to communicate with those servers, you've lost the ability to communicate with your firewall. If one of the application VMs isn't configured with proper resource limits then performance on the firewall will drop under periods of heavy traffic. For that matter, you've already introduced overhead on throughput of the firewall by forcing traffic to be received by the VM OS before it's received by OpenBSD. If the VM server is compromised then the things that can be done to traffic without ever actually disrupting the firewall are almost certainly fun fun fun (in all fairness, I haven't tried mucking with traffic on ESX/i, this is based entirely in speculation). I'm sure there are obvious things that I'm missing but these are the ones that blast the loudest through my brain when I think about virtualising a firewall. As I stated before, I have done it and there are a few that I maintain - and they do their job well - but that doesn't mean I condone the practice in general and it surely doesn't suggest that I think it's something that should be done on a whim or with a light attitude. It is dangerous and unsupported and you need to understand there is significant risk in doing so. kmw -- To take from one, because it is thought that his own industry and that of his fathers has acquired too much, in order to spare to others, who, or whose fathers have not exercised equal industry and skill, is to violate arbitrarily the first principle of association, bthe guarantee to every one of a free exercise of his industry, the fruits acquired by it.'
Re: OpenBSD ESXi VMware image on Soekris Net5501
Dag Richards wrote: Jason Dixon wrote: On Thu, May 21, 2009 at 08:05:52AM -0700, Obiozor Okeke wrote: Well I should have mentioned that the ESXi is also running a Windows server VM \ for a custom app that requires it. So the idea was to have one box running ESXi \ and reduce hardware costs. BWAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHA *whew* Thanks, I needed that. Er yes, you will not be able to get there from here. Re-think. Don't run vmware on your firewall. If you virtualize your entire DC in to a single box, still don't run your firewall as a vm. Run a firewall on *hardware* that is not doing anything else. The firewall is practically by definition the thing that is NOT protected by something else; have no additional holes in it or in what it relies on. Like VMWare, or a Windows application server. -- Ed Ahlsen-Girard Ft. Walton Beach FL
Re: OpenBSD ESXi VMware image on Soekris Net5501
Many, many thanks to all who responded! I now plan to run my OpenBSD firewall *stand-alone* on directly on a Soekris box for sure (no VM) and isolate all else on a separate box running the ESXi that fully supports the ESXi HCL. Many thanks to all the developers and especially Theo for creating IMHO the world's greatest OS!! --- On Thu, 5/21/09, Kevin Wilcox ke...@tux.appstate.edu wrote: From: Kevin Wilcox ke...@tux.appstate.edu Subject: Re: OpenBSD ESXi VMware image on Soekris Net5501 To: obiozorok...@yahoo.com Cc: misc@openbsd.org Date: Thursday, May 21, 2009, 11:39 AM 2009/5/21 obiozorok...@yahoo.com: I'll have to re-think this but I honestly thought (I guess I'm wrong) that if I my first OpenBSD VM image running on ESXi as my strong firewall I would be ok. B Basically its just a virtualization of my physical environment but all on one box with 3 VM images. So my idea was to have second OpenBSD image (not the firewall OpenBSD image) running with Samba as my Domain Controller and File server, and Email server and then the third Windows VM running just the custom app. B I figured that as long as all the 'Net traffic hit my first OpenBSD VM and was properly filtered and controlled by pf, spam greylisting, brute force checked, etc I would be ok? B No? There are some strategic issues with virtualising a firewall. What should be the simplest, most rock solid member of your network is now on the same hardware as foo virtual machines. If one of the application servers is compromised then it's *possible* that the VMWare server itself could be compromised, rendering the firewall VM under the control of The Bad Guys. If one of the VMs screws the pooch and takes down the server then you've not only lost the ability to communicate with those servers, you've lost the ability to communicate with your firewall. If one of the application VMs isn't configured with proper resource limits then performance on the firewall will drop under periods of heavy traffic. For that matter, you've already introduced overhead on throughput of the firewall by forcing traffic to be received by the VM OS before it's received by OpenBSD. If the VM server is compromised then the things that can be done to traffic without ever actually disrupting the firewall are almost certainly fun fun fun (in all fairness, I haven't tried mucking with traffic on ESX/i, this is based entirely in speculation). I'm sure there are obvious things that I'm missing but these are the ones that blast the loudest through my brain when I think about virtualising a firewall. As I stated before, I have done it and there are a few that I maintain - and they do their job well - but that doesn't mean I condone the practice in general and it surely doesn't suggest that I think it's something that should be done on a whim or with a light attitude. It is dangerous and unsupported and you need to understand there is significant risk in doing so. kmw -- To take from one, because it is thought that his own industry and that of his fathers has acquired too much, in order to spare to others, who, or whose fathers have not exercised equal industry and skill, is to violate arbitrarily the first principle of association, bthe guarantee to every one of a free exercise of his industry, the fruits acquired by it.'
Re: OpenBSD ESXi VMware image on Soekris Net5501
On 2009-05-21, Diana Eichert deich...@wrench.com wrote: On Thu, 21 May 2009, Obiozor Okeke wrote: Hi Diana (and Stuart) thanks for all your advice. The problem or nut we're trying to crack is that we're trying to deploy OpenBSD to remote clients and we wanted an inexpensive but very high reliability system with the flexibility to change configurations (switch in/out different VMs) and add/modify services remotely on-the-fly. For example we could upgrade a client from 4.A4 to 4.5 along with all the custom apps and client data packaged in a VM. We would grab the old 4.4 VM bring it back to our lab, then upgrade and re-configure it the way we wanted to and drop it back on the ESXi. Then just change the network configs and switch the old for the new all remotely without ever visiting the client Thanks again all. If you want to stick with the Soekris you might want to consider basing your solution on flashboot, http://lists.mindrot.org/pipermail/flashboot/2009-May/000223.html . Using a CF with multiple partitions would allow you to upgrade remotely the flashboot kernel. Of course this would take some work to fine tune the upgrade procedure to minimize failure mechanisms. with flashboot, it's reasonably ok on a single partition too, just point boot.conf at the right one after downloading. failure recovery would usually involve a serial port, resetting, and typing at the boot prompt, but if it's not too disastrous a failure you might get away with setting the bios to turn the reset button over to software control and having some daemon check the gpio pin and, when the button's detected, revert to a previous boot.conf.
Re: OpenBSD ESXi VMware image on Soekris Net5501
* Obiozor Okeke obiozorok...@yahoo.com [090520 19:40]: Hi I am hoping to run an ESXi OpenBSD 4.5 image on a Soekris Net5501 appliance and I was wondering if anyone has already tried successfully running ESXi on the Soekris Net5501 before I order the hardware? Any advice or comments is appreciated. Thanks in advance So in other words, you plan to run OpenBSD on top of ESXi. Moreover, you plan to run ESXi on a Soekris. This doesn't smell like a recipe for success. It may be possible, but the light weight nature of a Soekris would preclude ESXi and anything as a VM in my opinion. I don't know if you can even boot/run ESXi on a Soekris. Better to just to install OpenBSD natively on the Soekris and skip VMWare altogether. HTH, Jim
Re: OpenBSD ESXi VMware image on Soekris Net5501
This is doomed to failure, mostly because I am *almost* certain that you'll never get ESXi to install on a Soekris. My understanding is that it has a strict HCL, very similar if not identical to the HCL for ESX, that practically necessitates IBM, Sun, HP or Dell hardware. Skip the virtualisation cruft and install natively. kmw On 20/05/2009, Obiozor Okeke obiozorok...@yahoo.com wrote: Hi I am hoping to run an ESXi OpenBSD 4.5 image on a Soekris Net5501 appliance and I was wondering if anyone has already tried successfully running ESXi on the Soekris Net5501 before I order the hardware? Any advice or comments is appreciated. Thanks in advance -- Sent from my mobile device To take from one, because it is thought that his own industry and that of his fathers has acquired too much, in order to spare to others, who, or whose fathers have not exercised equal industry and skill, is to violate arbitrarily the first principle of association, bthe guarantee to every one of a free exercise of his industry, the fruits acquired by it.'
Re: OpenBSD ESXi VMware image on Soekris Net5501
On 2009-05-20, Obiozor Okeke obiozorok...@yahoo.com wrote: Hi I am hoping to run an ESXi OpenBSD 4.5 image on a Soekris Net5501 appliance and I was wondering if anyone has already tried successfully running ESXi on the Soekris Net5501 before I order the hardware? Any advice or comments is appreciated. It's slow enough on a dual core xeon with VT enabled and sufficient ram. Even if this did work on a Geode (highly unlikely since the latest version doesn't even work on some HP ML servers properly) it would be so horribly painful you wouldn't want to do it anyway. What problem are you trying to solve?
Re: OpenBSD ESXi VMware image on Soekris Net5501
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is way OT for this list, but: Kevin Wilcox wrote: My understanding is that it has a strict HCL, Yes it does. that practically necessitates IBM, Sun, HP or Dell hardware. No it doesn't. Skip the virtualisation cruft and install natively. That isn't a helpful or enlightened answer (not that one should expect help with this topic here). O.P., you should start here for detailed ESXi hardware support info: http://www.vm-help.com/ Cheers -d - -- David Talkington dt...@flyingjoke.org - -- PGP key: http://www.flyingjoke.org/keys/801E3976.asc (What's this? http://en.wikipedia.org/wiki/Digital_signature) iQEcBAEBAgAGBQJKFKpkAAoJEO7jL1CAHjl2+YgH/jwqmzLTgAGD1wDkxBPbJGZC qOQkT2lYoyy0obJ66777wfh/BRcZt88jIpnBVxPfprfnE3h4HUVw/0pP4xtriWcK nOQp+dWQeuhGYmV9QycWXAWvhRIrSwgmB3LagKPPYUQ4eR0aVz8NJ/LzkJpzwRb1 4kdxc4KXYxDG+HdaQ/mhQ4yGeY2AiTs41zs0oEjBQraeBb/FUwdXzKfFmK9brFxd kOEuKYUW9QAFnpzAmkKcFHM7QOQ8zIhLNIs7K/jTmLPVYycU14eutUUR+Q+SoI9W YriQmxcZ2PTxHIXA2hjvORM9FZiy0NwyDU8H9NHl2gA34rq1vheuVUnsHRJVH4U= =eE8z -END PGP SIGNATURE-
Re: OpenBSD ESXi VMware image on Soekris Net5501
On Wed, 20 May 2009, Obiozor Okeke wrote: Hi I am hoping to run an ESXi OpenBSD 4.5 image on a Soekris Net5501 appliance and I was wondering if anyone has already tried successfully running ESXi on the Soekris Net5501 before I order the hardware? Any advice or comments is appreciated. Thanks in advance The better question is, What nut are you trying to crack? Why would you even consider running a virtualization system on what is effectively a 486? Okay, a 500MHz 586, but still, it's slow to start with. diana Past hissy-fits are not a predictor of future hissy-fits. Nick Holland(06 Dec 2005)
Re: OpenBSD ESXi VMware image on Soekris Net5501
David, I'm currently mobile and unable to track down the HCL for ESX/i myself - thus my mentioning them to the original poster with what I could remember off the top of my head about supported machines. If that was an insufficient response then the OP is more than welcome to ignore it. On the other hand, the OP could always say, oh, ESXi HCL, I wonder... and google 'vmware esxi hardware compatibility'. kmw On 20/05/2009, David Talkington dt...@flyingjoke.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is way OT for this list, but: Kevin Wilcox wrote: My understanding is that it has a strict HCL, Yes it does. that practically necessitates IBM, Sun, HP or Dell hardware. No it doesn't. Skip the virtualisation cruft and install natively. That isn't a helpful or enlightened answer (not that one should expect help with this topic here). O.P., you should start here for detailed ESXi hardware support info: http://www.vm-help.com/ Cheers -d - -- David Talkington dt...@flyingjoke.org - -- PGP key: http://www.flyingjoke.org/keys/801E3976.asc (What's this? http://en.wikipedia.org/wiki/Digital_signature) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (GNU/Linux) iQEcBAEBAgAGBQJKFKpkAAoJEO7jL1CAHjl2+YgH/jwqmzLTgAGD1wDkxBPbJGZC qOQkT2lYoyy0obJ66777wfh/BRcZt88jIpnBVxPfprfnE3h4HUVw/0pP4xtriWcK nOQp+dWQeuhGYmV9QycWXAWvhRIrSwgmB3LagKPPYUQ4eR0aVz8NJ/LzkJpzwRb1 4kdxc4KXYxDG+HdaQ/mhQ4yGeY2AiTs41zs0oEjBQraeBb/FUwdXzKfFmK9brFxd kOEuKYUW9QAFnpzAmkKcFHM7QOQ8zIhLNIs7K/jTmLPVYycU14eutUUR+Q+SoI9W YriQmxcZ2PTxHIXA2hjvORM9FZiy0NwyDU8H9NHl2gA34rq1vheuVUnsHRJVH4U= =eE8z -END PGP SIGNATURE- -- Sent from my mobile device To take from one, because it is thought that his own industry and that of his fathers has acquired too much, in order to spare to others, who, or whose fathers have not exercised equal industry and skill, is to violate arbitrarily the first principle of association, bthe guarantee to every one of a free exercise of his industry, the fruits acquired by it.'
Re: OpenBSD on VMware
Lurk Off: On Nov 26, 2007 2:41 AM, Xavier Mertens [EMAIL PROTECTED] wrote: Ok, the only fix that explains my issue is this one: This release fixes a problem that resulted from a conflict between Linux guest operating systems with kernel version 2.6.21 and RTC-related processes on the host. This problem caused the virtual machine to quit unexpectedly. Not really...you did say you are running an OBSD virtual machine right? Not sure how the leap to a fix for linux applies. Suggest that you establish a communications channel with the VMWare server admin to discuss the dynamics of your problem. You state you know only that VMWare Server version 1.0.3 on some MS OS is used to host the virtual machines. You need to know a little more than that in order to properly diagnose your problem; i.e.: - Specifically what MS OS, MS Server (version), XP Pro, VISTA...etc. is running on the host; and patch level. - What hardware is utilized, and are all relevant driver updates applied? - Virtual Machine configuration -- how is the VM configured to use the host resources? Memory, hardware, networking, etc. - Logs -- host and guest (Logging is enabled on the OBSD guest right?) Biggest thing, again, is communication with the VMWare server admin, and the consideration of all factors -- software and hardware in the pursuit of a possible solution. Lurk On: Could you give me more details? As the VMware server is not under my control, I need to have good arguments to ask them to upgrade! :( /x -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of PowerBSD Sent: lundi 26 novembre 2007 8:33 To: misc@openbsd.org Subject: Re: OpenBSD on VMware On Mon, Nov 26, 2007 at 08:15:03AM +0100, Xavier Mertens wrote: It's a VMware server 1.0.3. I've no more info about the config. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of PowerBSD Sent: lundi 26 novembre 2007 8:17 To: misc@openbsd.org Subject: Re: OpenBSD on VMware On Mon, Nov 26, 2007 at 07:56:16AM +0100, Xavier Mertens wrote: Hi *, I'm running a 4.1-GENERIC on a VMware server (the VMare host runs a Microsoft Windows OS). I've no access to the VMware server. At random time, the server is just powered off (that's the feedback I always received from the VMware server administrator). There is nothing in logs and as the server is off, the console is not available anymore. :( Does somebody already experienced such issue? Any tips to run OBSD as VMware guest? Regards, Xavier PS: I'm using pcn as network driver. Maybe vmnet could increase performance and/or stability? I always runs openbsd on vmware , but the vware version is workstation 6.0.2.59824 . you may post your vmware server version. read this link : http://www.vmware.com/support/server/doc/releasenotes_server.html#resolved
Re: OpenBSD on VMware
Delurk If the guest computer (your OpenBSD machine) is running in the context of the user who starts it on the host, then when that user logs off the vmware host the guest computer will shutoff. In order for it to be available at all times, it should be running in the local system context OR a specially created user. Then it runs regardless of the login status of the person who clicks the start button on the vmware console. Lurk Henry On Nov 25, 2007 10:56 PM, Xavier Mertens [EMAIL PROTECTED] wrote: Hi *, I'm running a 4.1-GENERIC on a VMware server (the VMare host runs a Microsoft Windows OS). I've no access to the VMware server. At random time, the server is just powered off (that's the feedback I always received from the VMware server administrator). There is nothing in logs and as the server is off, the console is not available anymore. :( Does somebody already experienced such issue? Any tips to run OBSD as VMware guest? Regards, Xavier PS: I'm using pcn as network driver. Maybe vmnet could increase performance and/or stability?
Re: OpenBSD on VMware
On 11/26/07, Henry Sieff [EMAIL PROTECTED] wrote: On Nov 25, 2007 10:56 PM, Xavier Mertens [EMAIL PROTECTED] wrote: Hi *, I'm running a 4.1-GENERIC on a VMware server (the VMare host runs a Microsoft Windows OS). I've no access to the VMware server. At random time, the server is just powered off (that's the feedback I always received from the VMware server administrator). There is nothing in logs and as the server is off, the console is not available anymore. :( Does somebody already experienced such issue? Any tips to run OBSD as VMware guest? If the guest computer (your OpenBSD machine) is running in the context of the user who starts it on the host, then when that user logs off the vmware host the guest computer will shutoff. In order for it to be available at all times, it should be running in the local system context OR a specially created user. Then it runs regardless of the login status of the person who clicks the start button on the vmware console. And if the admin is being uncooperative, take your business elsewhere. -Nick
Re: OpenBSD on VMware
Xavier Mertens wrote: At random time, the server is just powered off (that's the feedback I always received from the VMware server administrator). There is nothing in logs and as the server is off, the console is not available anymore. :( It sounds like the vmware guest process is crashing and exiting. The admin should be able to turn on debug logging for you, maybe that would tell you where it's crashing. I have a vmware server on a DL360 G5 on W2003 amd64, and by default it creates a file named vmware.log in the same directory as the vmdk and vmx file. That file should have all the information you need. If nothing else try downloading vmware server yourself and try to make it crash.
Re: OpenBSD on VMware
It's a VMware server 1.0.3. I've no more info about the config. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of PowerBSD Sent: lundi 26 novembre 2007 8:17 To: misc@openbsd.org Subject: Re: OpenBSD on VMware On Mon, Nov 26, 2007 at 07:56:16AM +0100, Xavier Mertens wrote: Hi *, I'm running a 4.1-GENERIC on a VMware server (the VMare host runs a Microsoft Windows OS). I've no access to the VMware server. At random time, the server is just powered off (that's the feedback I always received from the VMware server administrator). There is nothing in logs and as the server is off, the console is not available anymore. :( Does somebody already experienced such issue? Any tips to run OBSD as VMware guest? Regards, Xavier PS: I'm using pcn as network driver. Maybe vmnet could increase performance and/or stability? I always runs openbsd on vmware , but the vware version is workstation 6.0.2.59824 . you may post your vmware server version.
Re: OpenBSD on VMware
On Mon, Nov 26, 2007 at 08:15:03AM +0100, Xavier Mertens wrote: It's a VMware server 1.0.3. I've no more info about the config. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of PowerBSD Sent: lundi 26 novembre 2007 8:17 To: misc@openbsd.org Subject: Re: OpenBSD on VMware On Mon, Nov 26, 2007 at 07:56:16AM +0100, Xavier Mertens wrote: Hi *, I'm running a 4.1-GENERIC on a VMware server (the VMare host runs a Microsoft Windows OS). I've no access to the VMware server. At random time, the server is just powered off (that's the feedback I always received from the VMware server administrator). There is nothing in logs and as the server is off, the console is not available anymore. :( Does somebody already experienced such issue? Any tips to run OBSD as VMware guest? Regards, Xavier PS: I'm using pcn as network driver. Maybe vmnet could increase performance and/or stability? I always runs openbsd on vmware , but the vware version is workstation 6.0.2.59824 . you may post your vmware server version. you need upgrade vmware server to VMware Server 1.0.4
Re: OpenBSD on VMware
Ok, the only fix that explains my issue is this one: This release fixes a problem that resulted from a conflict between Linux guest operating systems with kernel version 2.6.21 and RTC-related processes on the host. This problem caused the virtual machine to quit unexpectedly. Could you give me more details? As the VMware server is not under my control, I need to have good arguments to ask them to upgrade! :( /x -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of PowerBSD Sent: lundi 26 novembre 2007 8:33 To: misc@openbsd.org Subject: Re: OpenBSD on VMware On Mon, Nov 26, 2007 at 08:15:03AM +0100, Xavier Mertens wrote: It's a VMware server 1.0.3. I've no more info about the config. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of PowerBSD Sent: lundi 26 novembre 2007 8:17 To: misc@openbsd.org Subject: Re: OpenBSD on VMware On Mon, Nov 26, 2007 at 07:56:16AM +0100, Xavier Mertens wrote: Hi *, I'm running a 4.1-GENERIC on a VMware server (the VMare host runs a Microsoft Windows OS). I've no access to the VMware server. At random time, the server is just powered off (that's the feedback I always received from the VMware server administrator). There is nothing in logs and as the server is off, the console is not available anymore. :( Does somebody already experienced such issue? Any tips to run OBSD as VMware guest? Regards, Xavier PS: I'm using pcn as network driver. Maybe vmnet could increase performance and/or stability? I always runs openbsd on vmware , but the vware version is workstation 6.0.2.59824 . you may post your vmware server version. read this link : http://www.vmware.com/support/server/doc/releasenotes_server.html#resolved
Re: OpenBSD on VMware fusion (dmesg) -- yes it works
On Fri, Dec 22, 2006 at 02:35:00AM -0800, Brian Keefer wrote: Not sure if anyone else has noticed, but VMware finally released Fusion for public beta. It's the port to Macintel. Only caveat so far is that Fusion wouldn't mount the OpenBSD CDs. I think it might have a problem mounting volumes that have spaces in the path. I downloaded cd40.iso and did an FTP install and that worked fine (NAT for networking, choose dhcp during the install since it doesn't have any way that I could find to configure vmnet). Here're the dmesg's from RAMDISK_CD and GENERIC.MP on a MBP 15 CoreDuo 2.16GHz: can you try 4.0-current (or a recent snapshot)? it should use the new vic(4) driver instead of pcn(4). OpenBSD 4.0 (RAMDISK_CD) #39: Sat Sep 16 19:34:26 MDT 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/RAMDISK_CD cpu0: Genuine Intel(R) CPU T2600 @ 2.16GHz (GenuineIntel 686-class) 2.19 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH ,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,SSE3 real mem = 267939840 (261660K) avail mem = 238141440 (232560K) using 3296 buffers containing 13500416 bytes (13184K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(2b) BIOS, date 12/06/06, BIOS32 rev. 0 @ 0xfd880, SMBIOS rev. 2.31 @ 0xe0010 (45 entries) bios0: VMware, Inc. VMware Virtual Platform apm0 at bios0: Power Management spec V1.2 apm0: flags 30102 dobusy 0 doidle 1 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 #2 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: VMware Virtual IDE Hard Drive wd0: 64-sector PIO, LBA, 8192MB, 16777216 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: NECVMWar, VMware IDE CDR10, 1.00 SCSI0 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 Intel 82371AB Power 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 mux 1: console (80x25, vt100 emulation) bha3 at pci0 dev 16 function 0 BusLogic MultiMaster rev 0x01: irq 11, BusLogic 9xxC SCSI bha3: model BT-958, firmware 5.07B bha3: sync, parity scsibus1 at bha3: 8 targets ppb1 at pci0 dev 17 function 0 vendor VMware, unknown product 0x0790 rev 0x01 pci2 at ppb1 bus 2 pcn0 at pci2 dev 0 function 0 AMD 79c970 PCnet-PCI rev 0x10, Am79c970A, rev 0: irq 9, address 00:0c:29:c9:d7:96 Ensoniq AudioPCI97 rev 0x02 at pci2 dev 1 function 0 not configured 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: console keyboard, using wsdisplay0 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 biomask fde5 netmask ffe5 ttymask ffe7 rd0: fixed, 3800 blocks wd0: no disk label dkcsum: wd0 matches BIOS drive 0x80 root on rd0a rootdev=0x1100 rrootdev=0x2f00 rawdev=0x2f02 wd0: no disk label syncing disks... done rebooting... OpenBSD 4.0 (GENERIC.MP) #936: Sat Sep 16 19:27:28 MDT 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Genuine Intel(R) CPU T2600 @ 2.16GHz (GenuineIntel 686-class) 2.17 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH ,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,SSE3 real mem = 267939840 (261660K) avail mem = 236609536 (231064K) using 3296 buffers containing 13500416 bytes (13184K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(4a) BIOS, date 12/06/06, BIOS32 rev. 0 @ 0xfd880, SMBIOS rev. 2.31 @ 0xe0010 (45 entries) bios0: VMware, Inc. VMware Virtual Platform apm0 at bios0: Power Management spec V1.2 apm0: AC on, battery charge unknown apm0: flags 30102 dobusy 0 doidle 1 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 #2 is the last bus bios0: ROM list: 0xc/0x8000 0xc8000/0x1000 0xdc000/0x4000! 0xe/0x4000! mainbus0: Intel MP Specification (Version 1.4) (INTEL440BX ) cpu0 at
Re: OpenBSD on VMware fusion (dmesg) -- yes it works
On Dec 22, 2006, at 3:09 AM, Reyk Floeter wrote: On Fri, Dec 22, 2006 at 02:35:00AM -0800, Brian Keefer wrote: Not sure if anyone else has noticed, but VMware finally released Fusion for public beta. It's the port to Macintel. Only caveat so far is that Fusion wouldn't mount the OpenBSD CDs. I think it might have a problem mounting volumes that have spaces in the path. I downloaded cd40.iso and did an FTP install and that worked fine (NAT for networking, choose dhcp during the install since it doesn't have any way that I could find to configure vmnet). Here're the dmesg's from RAMDISK_CD and GENERIC.MP on a MBP 15 CoreDuo 2.16GHz: can you try 4.0-current (or a recent snapshot)? it should use the new vic(4) driver instead of pcn(4). I added Ethernet0.virtualDev to vmxnet (wasn't present by default) and this is what I got with the latest i386 snap: vic0 at pci2 dev 0 function 0 VMware Virtual NIC rev 0x10: apic 2 int 18 (irq 9) vic0: VMXnet 864F, address 00:0c:29:c9:d7:96 Boots fine, but when it searches for DHCP lease I get: vic0: no link . giving up I tried to ifconfig vic0 down ; ifconfig vic0 up, but it still didn't get a link. I tried e1000 instead of vmxnet and em0 was able to get a link just fine. Any other options I should try? Here's the .vmx: config.version = 8 virtualHW.version = 6 numvcpus = 2 scsi0.present = TRUE memsize = 256 MemAllowAutoScaleDown = FALSE ide0:0.present = TRUE ide0:0.fileName = OpenBSD.vmdk ide1:0.present = TRUE ide1:0.fileName = /Users/chort/scratch/cd40.iso ide1:0.deviceType = cdrom-image floppy0.present = FALSE ethernet0.present = TRUE ethernet0.connectionType = nat ethernet0.wakeOnPcktRcv = FALSE sound.present = TRUE sound.fileName = -1 sound.autodetect = TRUE pciBridge0.present = TRUE isolation.tools.hgfs.disable = TRUE displayName = OpenBSD guestOS = other nvram = OpenBSD.nvram deploymentPlatform = windows virtualHW.productCompatibility = hosted RemoteDisplay.vnc.port = 0 tools.upgrade.policy = useGlobal powerType.powerOff = soft powerType.powerOn = soft powerType.suspend = soft powerType.reset = soft ethernet0.addressType = generated uuid.location = 56 4d b4 c8 87 f5 fa 58-c7 59 8e d7 8b c9 d7 96 uuid.bios = 56 4d b4 c8 87 f5 fa 58-c7 59 8e d7 8b c9 d7 96 ide0:0.redo = pciBridge0.pciSlotNumber = 17 scsi0.pciSlotNumber = 16 ethernet0.pciSlotNumber = 32 sound.pciSlotNumber = 33 vmi.pciSlotNumber = 34 ethernet0.generatedAddress = 00:0c:29:c9:d7:96 ethernet0.generatedAddressOffset = 0 tools.remindInstall = TRUE Ethernet0.virtualDev = vmxnet checkpoint.vmState = Brian Keefer www.Tumbleweed.com The Experts in Secure Internet Communication
Re: OpenBSD on VMware fusion (dmesg) -- yes it works
On Fri, Dec 22, 2006 at 03:59:10AM -0800, Brian Keefer wrote: Here're the dmesg's from RAMDISK_CD and GENERIC.MP on a MBP 15 CoreDuo 2.16GHz: can you try 4.0-current (or a recent snapshot)? it should use the new vic(4) driver instead of pcn(4). I added Ethernet0.virtualDev to vmxnet (wasn't present by default) and this is what I got with the latest i386 snap: vic0 at pci2 dev 0 function 0 VMware Virtual NIC rev 0x10: apic 2 int 18 (irq 9) vic0: VMXnet 864F, address 00:0c:29:c9:d7:96 Boots fine, but when it searches for DHCP lease I get: vic0: no link . giving up hmmm, can you try it with GENERIC (without MP)? I tried to ifconfig vic0 down ; ifconfig vic0 up, but it still didn't get a link. I tried e1000 instead of vmxnet and em0 was able to get a link just fine. Any other options I should try? Here's the .vmx: config.version = 8 virtualHW.version = 6 numvcpus = 2 scsi0.present = TRUE memsize = 256 MemAllowAutoScaleDown = FALSE ide0:0.present = TRUE ide0:0.fileName = OpenBSD.vmdk ide1:0.present = TRUE ide1:0.fileName = /Users/chort/scratch/cd40.iso ide1:0.deviceType = cdrom-image floppy0.present = FALSE ethernet0.present = TRUE ethernet0.connectionType = nat ethernet0.wakeOnPcktRcv = FALSE sound.present = TRUE sound.fileName = -1 sound.autodetect = TRUE pciBridge0.present = TRUE isolation.tools.hgfs.disable = TRUE displayName = OpenBSD guestOS = other nvram = OpenBSD.nvram deploymentPlatform = windows virtualHW.productCompatibility = hosted RemoteDisplay.vnc.port = 0 tools.upgrade.policy = useGlobal powerType.powerOff = soft powerType.powerOn = soft powerType.suspend = soft powerType.reset = soft ethernet0.addressType = generated uuid.location = 56 4d b4 c8 87 f5 fa 58-c7 59 8e d7 8b c9 d7 96 uuid.bios = 56 4d b4 c8 87 f5 fa 58-c7 59 8e d7 8b c9 d7 96 ide0:0.redo = pciBridge0.pciSlotNumber = 17 scsi0.pciSlotNumber = 16 ethernet0.pciSlotNumber = 32 sound.pciSlotNumber = 33 vmi.pciSlotNumber = 34 ethernet0.generatedAddress = 00:0c:29:c9:d7:96 ethernet0.generatedAddressOffset = 0 tools.remindInstall = TRUE Ethernet0.virtualDev = vmxnet checkpoint.vmState = Brian Keefer www.Tumbleweed.com The Experts in Secure Internet Communication
Re: OpenBSD on VMware fusion (dmesg) -- yes it works
On Dec 22, 2006, at 6:59 AM, Brian Keefer wrote: On Dec 22, 2006, at 3:09 AM, Reyk Floeter wrote: can you try 4.0-current (or a recent snapshot)? it should use the new vic(4) driver instead of pcn(4). I added Ethernet0.virtualDev to vmxnet (wasn't present by default) and this is what I got with the latest i386 snap: vic0 at pci2 dev 0 function 0 VMware Virtual NIC rev 0x10: apic 2 int 18 (irq 9) vic0: VMXnet 864F, address 00:0c:29:c9:d7:96 Boots fine, but when it searches for DHCP lease I get: vic0: no link . giving up I tried to ifconfig vic0 down ; ifconfig vic0 up, but it still didn't get a link. Both stable and current work fine on my new MBP (Core 2 Duo 2.33GHz). vic grabs a NAT fine in stable, pcn in current. # sysctl hw hw.machine=i386 hw.model=Intel(R) Core(TM)2 CPU T7600 @ 2.33GHz (GenuineIntel 686- class) hw.ncpu=2 hw.byteorder=1234 hw.physmem=267939840 hw.usermem=267927552 hw.pagesize=4096 hw.disknames=wd0,cd0 hw.diskcount=2 hw.cpuspeed=2328 hw.vendor=VMware, Inc. hw.product=VMware Virtual Platform hw.version=None hw.serialno=VMware-56 4d 0b 8d 44 53 f8 c2-8e 13 fa e0 1b 15 bd b8 hw.uuid=564d0b8d-4453-f8c2-8e13-fae01b15bdb8 # dmesg OpenBSD 4.0-current (GENERIC.MP) #1106: Wed Dec 20 14:22:11 MST 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Intel(R) Core(TM)2 CPU T7600 @ 2.33GHz (GenuineIntel 686- class) 2.33 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36, CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,SSE3,DS-CPL,CX16 real mem = 267939840 (261660K) avail mem = 236470272 (230928K) using 3302 buffers containing 13524992 bytes (13208K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(4a) BIOS, date 12/06/06, BIOS32 rev. 0 @ 0xfd880, SMBIOS rev. 2.31 @ 0xe0010 (45 entries) bios0: VMware, Inc. VMware Virtual Platform apm0 at bios0: Power Management spec V1.2 apm0: AC on, battery charge unknown apm0: flags 30102 dobusy 0 doidle 1 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 #2 is the last bus bios0: ROM list: 0xc/0x8000 0xc8000/0x1000 0xdc000/0x4000! 0xe/0x4000! acpi at mainbus0 not configured mainbus0: Intel MP Specification (Version 1.4) cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 65 MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 CPU T7600 @ 2.33GHz (GenuineIntel 686- class) 2.33 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36, CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,SSE3,DS-CPL,CX16 mainbus0: bus 0 is type PCI mainbus0: bus 1 is type PCI mainbus0: bus 2 is type PCI mainbus0: bus 3 is type ISA ioapic0 at mainbus0: apid 2 pa 0xfec0, version 11, 24 pins 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: VMware Virtual IDE Hard Drive 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: NECVMWar, VMware IDE CDR10, 1.00 SCSI0 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 piixpm0 at pci0 dev 7 function 3 Intel 82371AB Power rev 0x08: SMBus disabled vga1 at pci0 dev 15 function 0 VMware Virtual SVGA II rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) bha3 at pci0 dev 16 function 0 BusLogic MultiMaster rev 0x01: apic 2 int 17 (irq 11), BusLogic 9xxC SCSI bha3: model BT-958, firmware 5.07B bha3: sync, parity scsibus1 at bha3: 8 targets ppb1 at pci0 dev 17 function 0 vendor VMware, unknown product 0x0790 rev 0x01 pci2 at ppb1 bus 2 pcn0 at pci2 dev 0 function 0 AMD 79c970 PCnet-PCI rev 0x10, Am79c970A, rev 0: apic 2 int 18 (irq 9), address 00:0c:29:15:bd:b8 eap0 at pci2 dev 1 function 0 Ensoniq AudioPCI97 rev 0x02: apic 2 int 19 (irq 10) ac97: codec id 0x43525913 (Cirrus Logic CS4297A rev 3) audio0 at eap0 midi0 at eap0: AudioPCI MIDI UART 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: 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: PC speaker spkr0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte
Re: OpenBSD on VMware fusion (dmesg) -- yes it works
On Dec 22, 2006, at 5:15 AM, Reyk Floeter wrote: On Fri, Dec 22, 2006 at 03:59:10AM -0800, Brian Keefer wrote: Here're the dmesg's from RAMDISK_CD and GENERIC.MP on a MBP 15 CoreDuo 2.16GHz: can you try 4.0-current (or a recent snapshot)? it should use the new vic(4) driver instead of pcn(4). I added Ethernet0.virtualDev to vmxnet (wasn't present by default) and this is what I got with the latest i386 snap: vic0 at pci2 dev 0 function 0 VMware Virtual NIC rev 0x10: apic 2 int 18 (irq 9) vic0: VMXnet 864F, address 00:0c:29:c9:d7:96 Boots fine, but when it searches for DHCP lease I get: vic0: no link . giving up hmmm, can you try it with GENERIC (without MP)? It didn't make a difference. I tried commenting out the virtualDev setting to see which one it would detect if no device type was specified in the .vmx, and it went back to pcn. Jason, what does your .vmx look like? Oddly, I also found a statement: deploymentPlatform = windows, which I found rather odd since I choose other/other for the OS and type. I comment that out, but it didn't change anything. Brian Keefer www.Tumbleweed.com The Experts in Secure Internet Communication
Re: OpenBSD on VMware fusion (dmesg) -- yes it works
On Dec 22, 2006, at 12:31 PM, Brian Keefer wrote: Jason, what does your .vmx look like? Oddly, I also found a statement: deploymentPlatform = windows, which I found rather odd since I choose other/other for the OS and type. I comment that out, but it didn't change anything. config.version = 8 virtualHW.version = 6 numvcpus = 2 scsi0.present = TRUE memsize = 256 MemAllowAutoScaleDown = FALSE ide0:0.present = TRUE ide0:0.fileName = OpenBSD 4.0.vmdk ide1:0.present = TRUE ide1:0.fileName = /Users/jasondixon/cd40.iso ide1:0.deviceType = cdrom-image floppy0.present = FALSE ethernet0.present = TRUE ethernet0.connectionType = nat ethernet0.wakeOnPcktRcv = FALSE sound.present = TRUE sound.fileName = -1 sound.autodetect = TRUE pciBridge0.present = TRUE isolation.tools.hgfs.disable = TRUE displayName = OpenBSD 4.0 guestOS = other nvram = OpenBSD 4.0.nvram deploymentPlatform = windows virtualHW.productCompatibility = hosted RemoteDisplay.vnc.port = 0 tools.upgrade.policy = useGlobal powerType.powerOff = soft powerType.powerOn = soft powerType.suspend = soft powerType.reset = soft ethernet0.addressType = generated uuid.location = 56 4d 0b 8d 44 53 f8 c2-8e 13 fa e0 1b 15 bd b8 uuid.bios = 56 4d 0b 8d 44 53 f8 c2-8e 13 fa e0 1b 15 bd b8 ide0:0.redo = pciBridge0.pciSlotNumber = 17 scsi0.pciSlotNumber = 16 ethernet0.pciSlotNumber = 32 sound.pciSlotNumber = 33 vmi.pciSlotNumber = 34 ethernet0.generatedAddress = 00:0c:29:15:bd:b8 ethernet0.generatedAddressOffset = 0 tools.remindInstall = TRUE -- Jason Dixon DixonGroup Consulting http://www.dixongroup.net
Re: OpenBSD on VMware fusion (dmesg) -- yes it works
On Dec 22, 2006, at 10:26 AM, Jason Dixon wrote: On Dec 22, 2006, at 12:31 PM, Brian Keefer wrote: Jason, what does your .vmx look like? Oddly, I also found a statement: deploymentPlatform = windows, which I found rather odd since I choose other/other for the OS and type. I comment that out, but it didn't change anything. config.version = 8 ... tools.remindInstall = TRUE -- Jason Dixon DixonGroup Consulting http://www.dixongroup.net It's the same, other than the MAC addresses of course. I'm running e.x.p. 36932, but I don't figure they did another in the 3 hours between when I downloaded it and when you posted. So the only difference we know of is that you have a Core Duo2-based system? Which version of OS X? I'm on 10.4.8 with all the patches (including EFI firmware update), except for the most recent Quartz QuickTime security patch. It's strange that when you boot -current it loads vic w/o having to specify vmxnet as your dev, but when I boot the snapshot from 21st it loads pcn unless I specifically change the dev to vmxnet, then it's vic, but it has no link. Maybe I should cvsup and build from source? Brian Keefer www.Tumbleweed.com The Experts in Secure Internet Communication
Re: OpenBSD on VMware fusion (dmesg) -- yes it works
On Dec 22, 2006, at 1:41 PM, Brian Keefer wrote: So the only difference we know of is that you have a Core Duo2- based system? Which version of OS X? I'm on 10.4.8 with all the patches (including EFI firmware update), except for the most recent Quartz QuickTime security patch. Yes, this is a Core 2 Duo system running 10.4.8 with all patches. We're comparing apples to oranges (excuse the half-pun); it would be more appropriate to boot up another Core Duo and compare results. It's strange that when you boot -current it loads vic w/o having to specify vmxnet as your dev, but when I boot the snapshot from 21st it loads pcn unless I specifically change the dev to vmxnet, then it's vic, but it has no link. Maybe I should cvsup and build from source? My snapshot is from 12/20 (ftp2.usa.openbsd.org). -- Jason Dixon DixonGroup Consulting http://www.dixongroup.net
