Search results

Exactly. Up to 12 VMs, depending on their computation and memory needs, managed via the web interface of any of the NUCs. With 1.3GHz base clock and 2.6GHz turbo and 4GiB RAM the VMs won't be terribly powerful, but sufficient for office work or several servers.

Is it possible to install drivers from the installer? If so you could install the VirtIO or updated E1000 drivers (see wiki). Then you could log in via RDP to see what's the issue with the mouse/keyboard driver.

It may very well be that the issue can't be solved by vagrant alone. The simplest way to solve the issue might be to just solve the root of the problem, the untrusted, self-signed certificate. You can either replace it by a trusted cert (let's encrypt would be a simple approach) or add the cert...

You might try the --insecure option for vagrant up in addition to box_download_insecure. I can't find any clear statement on whether or not this option exists, but it's not documented in the --help page.

Just to be clear on how I understand your setup: enp0s25 is meant to connect you to the host and only to the host enp2s0 is meant to connect the VMs to the internet Those NICs are connected to separate networks A laptop connected to network for VMs will get an IP via DHCP, but the VM will not...

The problem is the self-signed certificate used by the VM. According to this issue it's possible to add config.vm.box_download_insecure = true to the config to skip the certificate verification. Alternatively the --insecure parameter may work for vagrant up.

You could try disabling tablet mode for the mouse in the VM options.

The error tells you that apparmor denied a mount operation of the container. I suspect you inspired your setup from heider.io. However containers share the host's kernel and aren't allowed to load kernel modules. The autodev hook is run after the container was loaded and its /dev has been...

Did you make sure that the IGD is in its own IOMMU group? If it isn't you may need to override the ACS as described here. Are you sure Windows installed the drivers for the IGD? I've noticed Windows to only install the drivers that are absolutely required. During installation the IGD likely...

Do you get normal upload speed with pfsense disabled? Did you configure it to monitor outgoing traffic?

Whether or not a host responds to a ping is entirely decided by that host. Web servers mostly do. I usually test outside connectivity with one of Google's DNS servers, like 8.8.8.8. I'm not entirely sure I understand what you mean. Be aware that Qemu's NAT capability is not meant for anything...

Compared to what? Can you give specific numbers?

If only one public IP is available NAT is the only possibility. The NAT can be managed by qemu (I suppose that's your current setup) or a virtual router, which is assigned the public IP on one NIC and has the virtual network with all other VMs and the host on the other NIC. With multiple public...

That's why neither directory is deleted. They would be if they were actually empty, as they are of no relevance to the package manager.

If the network uses MAC whitelisting and you don't have administrative access to the responsible device you can either configure your virtual machines in a separate, virtual network and have a virtual router to connect it to the physical network. You can then ssh into the VMs by IP or domain...

Do any of the VMs get an IP via vmbr1? Did you apply the network config? Did you reboot the VMs after applying the network config? Is routing required and in place for the blue network?

You can try booting from the 5.0 ISO. If it boots it shouldn't be a general hardware incompatibility. In that case the course of action would be backup and clean reinstall.

Please try reinstalling the kernel and regenerating the initial RamFS with # apt-get install --reinstall pve-kernel-4.10.17-1-pve and post the output.

And I assume the initial ramdisk is given by initrd /boot/initrd.img-4.10.17-1-pve

They should work. Be aware that there should only be one parameter regarding logging on the kernel line. Otherwise the last parameter takes precedence. So if the kernel line in grub is linux /boot/vmlinuz-4.10.17-1-pve root=/dev/mapper/pve-root ro debug quiet the resulting output will be quiet.