On 13/04/17 9:39 AM, Mark Saad wrote:
Hello All
Anyone out there running E5-2699v4 Haswells .
Are you seeing problems with them? We are currently using E5-2698v3
processors without any issues, new boxes will probably use E5-2699v4.
Cheers,
Ian.
Hello All
Anyone out there running E5-2699v4 Haswells .
--
Mark Saad
ms...@lucera.com
---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify
My testing seems to imply that inotify is not available for use on lofs
mounts inside an LX zone. Too bad.
--jason
On Mon, Apr 3, 2017, at 06:09 PM, Robert Mustacchi wrote:
> On 4/3/17 14:40 , Jason Lawrence wrote:
> > Are there any filesystem limitations? For example, should it work fine
> >
>
>
> The reason why I haven't got the concerning entry is lines from #36 to
> #38 of the source (https://github.com/joyent/smartos-live/blob/
> 64998c0b5a7c33287eb7dd118fef4aea42e5a6f3/src/vm/sbin/rotate-
> kvm-logs.sh#L36) --
>
> "
> if [[ ! -s ${logfile} ]]; then
> # file doesn't
Hi Stefan,
Is the hostname not being set? Can you raise an issue here please?
https://github.com/joyent/fedora-kvm-image-builder/issues
Thanks!
On Wed, Apr 12, 2017 at 4:57 AM Stefan wrote:
> Dear List,
>
> we have the effect, that the hostname is finally set to the VM
>From: Josh Wilsdon [mailto:jwils...@joyent.com]
>Sent: 星期三, 四月 12, 2017 0:25
>To: smartos-discuss@lists.smartos.org
>Subject: Re: [smartos-discuss] rotate-kvm-log
>Yes. But "/usr/vm/sbin/rotate-kvm-logs.sh script" won't add entries in
>"/var/logadm/timestamps" like following:
Dear List,
we have the effect, that the hostname is finally set to the VM uuid:
Apr 11 08:50:53 localhost.localdomain systemd[1]: Set hostname to
.
Apr 11 08:50:58 localhost.localdomain NetworkManager[437]:
[1491900658.0727] settings: hostname changed from (none) to ""
Apr 11 08:50:58