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.
Esx
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
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 pa
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
> 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 fs
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 doin
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
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 inst
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.r
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, an
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: sd
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 div
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
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 di
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 w
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 datasto
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/215148
Of course never booted: /var/log/messages is empty. :)
I was too sleepy and optimistic.
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 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
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 sta
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?
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:
>
>ethernet
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
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 esc
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 Joha
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 preffe
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 "ha
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, a
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 mome
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 an
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 tim
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 sp
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
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 Win
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).
> >
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).
> >
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:
st?
>
> 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.
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
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, thi
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 th
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.ver
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 pc
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 g
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.virtual
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.
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 mounti
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 d
49 matches
Mail list logo
