Recent content by Docop2

You throw code at ai, hire any with 'coding' into their cv, push the crap over the user. Then do a patch if any complain too much. The mania of updating every 2min is quite a joke. Just like ms win11 as basic function are not even tested and then people got no audio, no printer, black screen...

So it's a script to auto deploy-config a new lxc in prox. Then we set the api acces. Tell where Cyberpower network card is and it's up and running ? is there a Test mode, like a quick confirmation : if you unplug the usb cable the webgui give an indication in the status or so ?

It is very very great. Full direct access, no web stuff, as it's great use and fast acess. Just like esxi6 with the fast soft acess. Maybe a great add : You are in a vm with a gpu on it. Maybe have a boutton to switch to another vm with the shutdown of the current one and power up the second...

Can this be also used to get back the console ? If we did set passthrough, at boot, it do not give back the prompt to login...

Just to follow up on your project. I check Glance and it told about an api and so.. But reading directly the device, in the location .. like '/usr/bin/awk '/Core [0-9]+ .. ' for temp of cpu package : wasn't it more simple ? And then pass via an api of prox, instead of another layer .. of Glance...

Like if we unplug an lvm or ext disk, that is in fact a network disk.. the system will be flooded by alarm if that disk is not available. Can it be possible to have that log process stop after like 30sec-1min ? Or we need to stop the log of harddisk directly from the start ?.. Mostly, if...

As with the flooding of the log.. Is there a way to make the system pause the error pumping ? Like if we get back after a week.. it will be uber clog for no reason.. Or maybe a service stop after x min of detection of an error ..?

There is no need to install in zfs and if you read what is zfs : it is exactly not made for 1 drive. ext4 all good and adjust for ceph stuff. Best is to kill most of the log that are flodding if any error appear. how to edit prox file to set a timer.. not sure.

i wonder, can it be possible to add a stop or timeout around that line : ( warn $err if $err; ) In order to stop the error spamming ? Like a 2-3min of multiple page of error can be sufficient.

For precision, with the method : echo options usb-storage quirks=152... that will put the drive in the storage tree at left. But if not plug at boot up : can we put a timer to de-activate the drive after like 4-5min ? If not the log will be flooded with error message. Or maybe a way to kill...

Boot 2 pc with live iso or a win10 and link local the 2x 25g card together. normal iperf3 will give a full 25gbps. Even an old hp microserver8 do give a full speed without parallel load. getting unknow is many time the sfp or cable. confirm that , then a fresh install of prox without vlan crap...

It is simply: Rebar off, Disconnect internet. Install prox iso 8.2 , set the blacklist file as read properly the guide and just the official one. no vbios stuff there either. And default install and run a xubuntu live iso and paf: video out. then read about error43. If you spend less than 2 days...

Is there a way to set the webhook directly by writing a file, instead of pasting into different txt field in the webgui ? If any have an example .. that can be very usefull to figure it out properly.

There is no info, no doc, about what is change.. what happen when a trigger happen. What command are run? Nut are more clear as we have control on what command are run and usb support too.

Currious to know : if you pass the ctrl.. how is proxmox running ? Is it running on an M.2 drive with a direct single iommu ?