There's no guarantee that upgarding a VM or rebooting it won't change
the config of said VM. Don't forget to diff the vm config file..
Adrian
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsub
> Subsequent inspection suggested that it was happening during the
> periodic daily, though we never managed to get it to happen by manually
> forcing periodic daily, so that's only a theory.
Perhaps due to a bunch of VMs all running periodic daily at the same time?
> We had a perfectly functiona
>> mlock(2) says:
>>
>> > A single process can mlock() the minimum of a system-wide
>> > ``wired pages'' limit and the per-process RLIMIT_MEMLOCK
>> > resource limit.
>>
>> Shouldn't this say maximum rather than minimum?
>
> I don't think so. The minimum of the two would be the limit that you
> wi
Mark Felder wrote:
On Thu, 29 Mar 2012 12:24:30 -0500, wrote:
I just started reading this tread, but I am wondering if I missed
something here. What does this have to do with "Windows 7"?
I emailed him off-list but I'm guessing he thought this was on VMWare
Workstation or another product t
On Fri, 30 Mar 2012 11:53:10 -0500, Joe Greco wrote:
On the same vmdk files? "Deleting the VM" makes it sound like not.
Fresh new VMDK files every time, and always thick provisioned.
None of the other VM's, even the VM's that had been abused in this
horribly insensitive manner of being pla
> On Fri, 30 Mar 2012 09:44:47 -0500, Joe Greco wrote:
> > Have you migrated these hosts, or were they installed in-place and
> > never moved?
> > fwiw the apparent integrity of things on the VM is consistent with
> > our experience too.
>
> VMMotion and StorageVMMotion does not seem to affect th
On Fri, 30 Mar 2012 09:44:47 -0500, Joe Greco wrote:
Have you migrated these hosts, or were they installed in-place and
never moved?
fwiw the apparent integrity of things on the VM is consistent with
our experience too.
VMMotion and StorageVMMotion does not seem to affect the stability. Even
> On Thu, 29 Mar 2012 19:27:31 -0500, Joe Greco wrote:
>
> > It also doesn't explain the experience here, where one VM basically
> > crapped out but only after a migration - and then stayed crapped out.
> > It would be interesting to hear about your datastore, how busy it is,
> > what technology,
> On 3/29/2012 7:01 AM, Joe Greco wrote:
> >> On 3/28/2012 1:59 PM, Mark Felder wrote:
> >>> FreeBSD 8-STABLE, 8.3, and 9.0 are untested
> >>
> >> As much as I'm sensitive to your production requirements, realistically
> >> it's not likely that you'll get a helpful result without testing a newer
>
On 03/30/12 15:36, Giovanni Trematerra wrote:
On Thu, Mar 29, 2012 at 7:18 PM, Mahesh Babu wrote:
Which part of the source code in FreeBSD 9 is responsible for making context
switching i.e. storing and restoring the process state.
Context switch is split up in machine indipendent code (MI C
On Thu, Mar 29, 2012 at 7:18 PM, Mahesh Babu wrote:
> Which part of the source code in FreeBSD 9 is responsible for making context
> switching i.e. storing and restoring the process state.
>
Context switch is split up in machine indipendent code (MI Code) and
machine dependent code (MD Code)
Fo
On Fri, Mar 30, 2012 at 12:49:31AM -0400, Jason Hellenthal wrote:
>
>
> On Thu, Mar 29, 2012 at 09:20:27AM +0100, Anton Shterenlikht wrote:
> > On Wed, Mar 28, 2012 at 04:33:17PM -0400, Brandon Falk wrote:
> > > Reverse engineering a whole driver could take a very long time, even with
> > > the
12 matches
Mail list logo
