similar to: FreeBSD Errata Notice FreeBSD-EN-13:02.vtnet

I'm running FreeBSD 9-STABLE as a guest under RHEL 6.4 KVM virtualisation. I have networking and storage in the FreeBSD guest using the Virtio drivers (with the virtual disk set to "Virtio" in the definition on the host). Everything is working nicely: I have a vtnet network adapter and see vtbd devices for my virtual disks in FreeBSD. Performance is much better compared with an

On Tue, Mar 12, 2019 at 11:10:40PM +0100, Lars Lindstrom wrote: >Hi everyone! > >I have the following requirement: I need to connect a set of Docker >containers to a KVM. The containers shall be isolated in a way that they >cannot communicate to each other without going through the KVM, which >will act as router/firewall. For this, I thought about the following >simple setup

Hi everyone! I have the following requirement: I need to connect a set of Docker containers to a KVM. The containers shall be isolated in a way that they cannot communicate to each other without going through the KVM, which will act as router/firewall. For this, I thought about the following simple setup (as opposed to a more complex one involving a bridge with vlan_filtering and a seperate VLAN

Hi, Just update my 8.x kernel sources last weekend, and newly built kernel did not boot for me: link_elf: symbol mem_range_softc undefined KLD file acpi.ko - could not finalize loading kernel trap 12 with interrupts disabled This is stripped down kernel with everything possible loaded from modules. Any ideas? Did not see any warnings in UPDATING... ./danfe

Hello! I'm trying to compile libvirt using GCC 5.1 but one of the test are failing and I have no idea why :( Hopefully someone of you could help me, here part of my log: ========================================== libvirt 1.2.14: tests/test-suite.log ========================================== # TOTAL: 109 # PASS: 107 # SKIP: 1 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents::

Hi Sorry for the cross-posting, I''d sent this to zfs-code originally. Wrong forum. I''m looking into forensic aspects of ZFS, in particular ways to use ZFS tools to investigate ZFS file systems without writing to the pools. I''m working on a test suite of file system images within VTOC partitions. At the moment, these only have 1 file system per pool per VTOC

Hi I''m looking into forensic aspects of ZFS, in particular ways to use ZFS tools to investigate ZFS file systems without writing to the pools. I''m working on a test suite of file system images within VTOC partitions. At the moment, these only have 1 file system per pool per VTOC partition for simplicity''s sake, and I''m using Solaris 10 6/06, which may not

Hi guys, I can't see virtio in releng/9.1, is there any particular reason why it isn't going to be included given that it works reasonable well (and is optional anyway, so not likely to be detrimental)? Thanks, Joe

Good afternoon. I'm new to the list, so apologies in advance if the noob in me comes through too loudly. >From things I've read in the distant past, I have the impression that the OpenSSH project tries to keep new features to a minimum, and there are good security reasons to do this. That said, one feature that I feel would be a good addition to OpenSSH is the ability to send logs via

This is of course an incorrect usage, which I've trapped at R level, so as to give an informative warning. On Tue, 28 May 2002 NEFTH@pacbell.net wrote: > The following sequence of commands: > graphics.off() > dev.control("inhibit") > > causes R to memory-fault and core dump. This is reported > for a new port of R, but is also reproducible on Windows > and

B.t.w. I've created a PR for it that resolves it (see https://github.com/NLnetLabs/nsd/pull/346 ), but we may need to discuss if and how to resolve it first. First I'd like to know if your configuration is similar in that the CNAME or DNAME target does contain an allow-query list. Op 03-07-2024 om 10:52 schreef Willem Toorop via nsd-users: > Hi Jamie, > > I can reproduce,

Hi Rowland, Just a quick summary, we had to roll back the AD migration due to some users having issues accessing the shares post the migration. They were getting server couldn't not be found , using both hostname and IP. It won't even show the shares available in the server. Some users had no issues, which is the puzzling bit Re the OS and file system: I had a look at the following