Search results

No joy. When I try to use the DH_IPC-HX1X2X-Themis_EngSpn_N_V2.620.0000002.0.R.170830.bin file it says it is "unmatched" and reboots. Any suggestions?

Update: I found the release notes for V2.620.0000002.0.R.170830 and eventually did find the referenced firmware .bin file as well. Now to try and flash the cameras and hope they don't get bricked...

Earlier this year I replaced a few IPC-HDBW2300R-Z cameras with newer Dahua models. I'd like to give the HDBW2300R-Z's to a family member, but before I do, I wanted to try and upgrade the firmware. They are currently running 2.420.0008.0.R, build : 2015-07-10 which seems a bit crusty...

I just received my first order from @EMPIRETECANDY with one of these cameras (I'm replacing an older outdoor camera in a corner location that could benefit from additional coverage, so this seemed like a nice replace-and-go solution). The problem appears to be that the ONVIF auto-configuration...

Heh. We have a ton of Proxmox (KVM/qemu with a nice web-based UI) deployed at $DAYJOB as well. But as I mentioned before, I'm consolidating all of my services currently running on multiple servers into one main server with Docker, and didn't think I'd have a need for a Type 1 hypervisor, and...

I decided against running ESXi since I'm a Linux guy. I didn't intend to ever need anything but Docker and LXC. In retrospect, it may have been a good idea to install ESXi and then install Ubuntu 18.04 as a guest, and then run Docker and LXC there, giving me ultimate flexibility for situations...

Fair enough. Unfortunately upgrading the OS isn't an option. I don't want to risk the stability of all the other Docker and LXC containers that are running just fine (plus, only Long-Term Stable releases have hardware-related packages that are supported by vendors, and the next Ubuntu LTS...

Thanks again for taking the time to reply. I understand about needing to meet all the hardware requirements — and my system does. But VF devices are definitely supported (see the Windows docs here for example), and Intel provides drivers for VF instances of their devices for many versions of...

Just to make sure the VF NIC wasn't an issue, I created a test VM via virt-install with the same configuration parameters except for using --network=none and it boot-loops the same way with the kvm64 CPU type.

Hmmm... unless I'm missing something, the VF (Virtual Function) of the NIC should give excellent performance? It takes a physical NIC and makes it appear as (up to) 64 distinct NICs (each with their own MAC address, PCI ID, etc.) all natively in hardware courtesy of SR-IOV (single-root...

I was sure to install all the drivers ("Device Manager" was "clean", with no exclamation points) and then applied all the pending Windows updates before I shut down the guest and switched the CPU to kvm64... that's when it started boot-looping. During the install of Win10, I do have to manually...

Just curious if anybody has made progress on this. I recently consolidated multiple old, crusty servers into one "real" server (with a Xeon CPU) that will serve as a VM host for everything. The server is running Ubuntu 18.04, and is mostly Docker containers, but I just configured KVM in order...