I have some OpenBSD AMD64 (as 'other-64bit') VMs running fine for months under
ESX 4.1.0 e.g:
We've had the Seattle BSD user group site hosted on an OpenBSD VM for
something like 2 years with no problems. I can probably ask our host
what config options they[1] used when setting it up. If
On 11/01/2011 12:47 AM, Daniel Ouellet wrote:
ESXi 3.5?? Can you test with ESXi 4 U2??
I read his tests to be under 5.0
Hi, I setup four 4.9-RELEASE installs under ESXi 5.0.0:
Only the host was a 3.5 year old server.
You may want to read it again.
Best,
Daniel
Yes, yes ... was my
On 1. nov. 2011, at 00.15, carlopmart wrote:
On 10/31/2011 10:01 PM, Tyler Morgan wrote:
Hi, I setup four 4.9-RELEASE installs under ESXi 5.0.0:
amd64 as Other
amd64 as FreeBSD
i386 as Other
i386 as FreeBSD
All 4 got 512megs of RAM, unlimited use of the 8 available CPU cores,
and
Hi, I setup four 4.9-RELEASE installs under ESXi 5.0.0:
amd64 as Other
amd64 as FreeBSD
i386 as Other
i386 as FreeBSD
All 4 got 512megs of RAM, unlimited use of the 8 available CPU cores,
and totally default installs other than stress from ports.
After installing I ran stress --cpu 8 --io 4
On 10/31/2011 10:01 PM, Tyler Morgan wrote:
Hi, I setup four 4.9-RELEASE installs under ESXi 5.0.0:
amd64 as Other
amd64 as FreeBSD
i386 as Other
i386 as FreeBSD
All 4 got 512megs of RAM, unlimited use of the 8 available CPU cores,
and totally default installs other than stress from ports.
ESXi 3.5?? Can you test with ESXi 4 U2??
I read his tests to be under 5.0
Hi, I setup four 4.9-RELEASE installs under ESXi 5.0.0:
Only the host was a 3.5 year old server.
You may want to read it again.
Best,
Daniel
I was wrong, just changing the guest OS type did not fix my problem.
The morning following this email I found the CPU being pegged again.
I ended up installing the i386 version of 4.9 and used FreeBSD 32-bit
as the guest os type. These VMs have been running for four days
without a problem. If
This is just an update, I've still got to try everything that was
suggested before.
This issue is finally occurring again, and I have been able to collect
more information about it:
# uptime
11:46AM up 3 days, 22:50, 1 user, load averages: 1.33, 1.12, 1.10
# ps aux
USER PID %CPU %MEM
On 10/23/2011 09:10 PM, Gene wrote:
This is just an update, I've still got to try everything that was
suggested before.
This issue is finally occurring again, and I have been able to collect
more information about it:
# uptime
11:46AM up 3 days, 22:50, 1 user, load averages: 1.33, 1.12, 1.10
This problem appears to be resolved. By changing the guest os type
from FreeBSD (64-bit) to Other (64-bit) these vm guests perform
much better.
I found out I could easily duplicate the problem with the following command:
find / -type f -exec grep -i moo {} \;
After ten or so minutes dmesg
On 2011/10/19 16:19, Gene wrote:
- Might be worth giving -current a spin (or 5.0 when it's
available - release isn't far off - note that people who pre-order
CDs often receive them before the official release date ;-)
Does 5.0 have VM specific features in it?
No but there have
I'm trying to run OpenBSD 4.9 (amd64) under VMware vSphere 5 (ESXi 5). I
set up four virtual machines with one core, 256 MB of RAM, and 4 GB of disk
space each. I used the install49.iso as my installation medium. Aside from
the OS installation, I haven't installed anything on them yet.
They
dmesg?
On Wed, 19 Oct 2011 11:55:19 -0700, Gene gh5...@gmail.com wrote:
I'm trying to run OpenBSD 4.9 (amd64) under VMware vSphere 5 (ESXi 5).
I
set up four virtual machines with one core, 256 MB of RAM, and 4 GB of
disk
space each. I used the install49.iso as my installation medium. Aside
What hardware version did you use? Have you tried different?
// Johan
2011/10/19 Gonzalo L. R. gonz...@x61.com.ar:
dmesg?
On Wed, 19 Oct 2011 11:55:19 -0700, Gene gh5...@gmail.com wrote:
I'm trying to run OpenBSD 4.9 (amd64) under VMware vSphere 5 (ESXi 5).
I
set up four virtual machines
I'm using amd64. I'll try i386 later today to see if the issue occurs
again. Another person replied to me saying i386 works fine for him in ESXi
5.
I had the VMs powered off. I started them back up and am trying to
reproduce the problem. So far dmesg isn't giving me anything beyond the
Haven't tried esxi 5 but I have some hack VMs under 4.1 which are
working ok (i386 and amd64). Some things to try:-
- Try different guest os types in the vm config page. On 4.1
I typically set rhel 5 32-bit which seems to work fairly well,
even for amd64, and uses the vic(4) network driver.
-
On Wed, Oct 19, 2011 at 11:55 AM, Gene gh5...@gmail.com wrote:
I'm trying to run OpenBSD 4.9 (amd64) under VMware vSphere 5 (ESXi 5). I
set up four virtual machines with one core, 256 MB of RAM, and 4 GB of disk
They perform terribly. The load average hovers around 1.5 on all of these
What
On Wed, Oct 19, 2011 at 2:54 PM, Joe S js.li...@gmail.com wrote:
On Wed, Oct 19, 2011 at 11:55 AM, Gene gh5...@gmail.com wrote:
I'm trying to run OpenBSD 4.9 (amd64) under VMware vSphere 5 (ESXi 5). I
set up four virtual machines with one core, 256 MB of RAM, and 4 GB of
disk
They
On Wed, Oct 19, 2011 at 2:52 PM, Stuart Henderson s...@spacehopper.orgwrote:
Haven't tried esxi 5 but I have some hack VMs under 4.1 which are
working ok (i386 and amd64). Some things to try:-
- Try different guest os types in the vm config page. On 4.1
I typically set rhel 5 32-bit which
On Wed, Oct 19, 2011 at 8:41 PM, Gene gh5...@gmail.com wrote:
I'm using amd64. B I'll try i386 later today to see if the issue occurs
again. B Another person replied to me saying i386 works fine for him in
ESXi
5.
I'm also running 4.9 i386 in a VMware and it sure is fine:
[edho@tomoka ~]$
What could we ask you that would get you to post those messages from boot?
On Wed, Oct 19, 2011 at 3:41 PM, Gene gh5...@gmail.com wrote:
I'm using amd64. I'll try i386 later today to see if the issue occurs
again. Another person replied to me saying i386 works fine for him in ESXi
5.
I
What's it take to get an actual dmesg around here? Just post the output
for us to look at regardless of whether or not you think the messages at
boot are important. They're needed to troubleshoot any problem like
this.
On 19-Oct-11 16:19, Gene wrote:
On Wed, Oct 19, 2011 at 2:52 PM, Stuart Hendersons...@spacehopper.orgwrote:
Haven't tried esxi 5 but I have some hack VMs under 4.1 which are
working ok (i386 and amd64). Some things to try:-
- Try different guest os types in the vm config page. On 4.1
I
When the initial dmesg question was asked (dmesg?) I didn't understand
that it was a request for the entire dmesg output. I thought he was asking
if errors were showing up in dmesg.
I have attached the entirety of a dmesg output.
-Gene
On Wed, Oct 19, 2011 at 6:53 PM, James Shupe
I haven't been able to reproduce the problem since this morning.
Nothing has been changed on the vmhosts so I'm at a bit of a loss at
the moment.
When the issue reoccurs I'll try everything that has been suggested today.
Thank you very much for your help everyone.
-Gene
On Wed, Oct 19, 2011 at
25 matches
Mail list logo
