Search results

I see very slightly increase ... node not under full load, can try to pick another one with more load for comparison. (update and kexec soft-reboot just before the startup peak) System specs: Supermicro X10DRi 2 x Intel(R) Xeon(R) CPU E5-2667 v4 @ 3.20GHz 256 GB

Updated 2 serves (my old lab HP MicroServer G8 plus one recent Skylake) wihtou any boot problems. Will keep an eye on the monitoring ;) Jip...the whole it world is having a "funny" new year 2018 i guess...

Awesome, thank you, we highly appreciate the overtime you presumably had in last days ;)

For me, arc cache is behaving weird (stuck at 2G regardless of the setting)...disabling huge pages fixed this.

Once upon a time ;) i've been using daemonlogger for this (sending all incoming traffic to a Snort VM) which worked quite good.

You could also try apt-cacher-ng, which just mirrors all the packages being downloaded during update/installation

Looks like you're using PXE (no ISO attached)...Thomas is right, this misleading message is due to pxe-booted kernel and initrd does not match the anaconda installer.

Can do this tomorrow. For me, it does not matter as the vm user is accessing it via RDP anyway...i'm just used to install all virtio drivers ;)

I've migrated a physical windows to vm last week and tracked my bsod down to the qxl driver.

Latest (141) QXL drivers are failing for me. Rest is alright.

I'm wondering if this might be possible with the latest Ubuntu Stack in Windows ... Not sure if the subsystem is able to access the watchdog device.

Latest flavour of my stuff: https://gitlab.com/morph027/pve-infra-poc

Something i'm using: https://gitlab.com/morph027/pve-infra-poc (based on https://morph027.gitlab.io/post/pve-kickseed/)

Ok, well that was awesome ;) Just setup a local mirror of the current image and a simple ignition config file and my Docker VM is ready in a minute (ok, minus the API creation time ;)): # time ./coreos-install -d /dev/zvol/ssd/test/vm-100-disk-1 -i ignition.json -C stable -b...

Right now i'm playing around with CoreOS and it's simple installation. Basically it just needs a block device and a config file. Will see how easy and far i can get with this.

Hm, not fixing my issue :/ Was worth a try. Anyway, good to have this patch, no other issues appeared.

Thanks, installed and testing ... can deploy the kernel also on another machine which is more error prone to this (in use during office hours ;) )

Looking at this, this might be the cause for my weirdo hanging lxc's ... if you need testers, always waiting for tasks ;)

Here's another container: arch: amd64 cpulimit: 4 cpuunits: 1024 hostname: fileserver memory: 1024 net0: bridge=vmbr0,gw=XXX,hwaddr=XXX,ip=XXX,name=eth0,type=veth onboot: 1 ostype: debian rootfs: rpool-vm:subvol-132-disk-1,size=8G searchdomain: XXX swap: 512 lxc.mount.entry: /data/files/1...

Sure. Kind of Heisenbug...not present when looking at it :D