Search results

Can the spice monitors been seen inside the VM? Run xrandr

Usually the internal network is not known in the public one. Therefore NAT is required. In your particular case it would look like iptables -t nat -A POSTROUTING -s 192.168.10.0/24 -j MASQUERADE

A general answer cannot be given. As long as there is not a high amount of I/O wait ( > 10%) for a longer period system may become slow but not really "blocked". As a rough estimation I would say as tzhe idle rate is > 50% there is no reason for any concern. Constantly 90% is unusual but will...

Possibly the function and/or bus ID had been changed after activation. Run lsusb -v Before and after starting the VM and compare the data about your device whether there is any difference.

They are seen as "rename8" and "rename9" since according to Debian network interface naming rules (see more here https://wiki.debian.org/NetworkInterfaceNames) they would get identical names to the 2 interfaces ens2f0 and ens2f1. To avoid this create your own /etc/udev/rules.d/*-persistent-net.rules

In containers you can always see the host devices but they can be accessed from inside the container only if it's allowed by a lxc.cgroup.devices.allow entry.

You have to hibernate the VM, in case of a script using the command line add "--todisk" to the suspend subcommand, e.g. qm suspend 111 --todisk

Check whether the interfaces can be seen via ip addr

In other words qcow2 file in an LVM which is located in an iscsi device? It is an usual approach, however, should be possible. That means the storage is simply type "Directory" and the respective filesystem has to be mounted accordingly. If it works with fstab depends on the iscsi device it it...

Voraussetzung ist, dass der Provider global Unicast Adressen zur Verfügung stellt. Üblicherweise gibt es da einen /64 Breich, bei dem aber das Netzwerk erwartet, dass alle Adressen direkt vom letzten Router (bei Provider, nicht die Fritz Box) aus erreicht werden können (also im selben LAN...

They should be close to each other, i.e. be connected with powerful (10Gbps for Ceph, 1Gbps for Cluster) LAN to each other. In other word have to be in the same datacenter. Even the protocol allow to connect the nodes via WAN such a setup will not work reliably.

The recommended way is to define in pve firs an iscsi storage an then of top of it an LVM one. To add somethinǵ for it (in host's) fstab is not necessary. For clarification it would be useful to have look into storage and VM configuration; when running pvereport > pvereport.log both will be...

Host's enp0s31f6 is bridged to vmbr0 and has the same IP address. This will not work (a bridged NIC should never have an IP address). AFAIU in case of "routed solution" you must not bridge the physical NIC; however for provider specific issue contact their forum. In general it helps to follow...

For further investigation it would be necessary to have lot at the containers configuration file as well as at the hosts IP configuration, e.g. ip addr in the host.

Check first whether the IP configuration is correct by ip addr or - if nettools are installed - ifconfig if you can see the correctly configured vlan305 trace the interface by tcpdump -eni vlan305 whether packets are sent/received as expected. Depending on the result a next step for...

You can use the iptables -t nat command. Firewall configuration via GUI is for filtering only.

Sound like you have IPs from OVH but these IPs sould be assigned to (virtual)machines hosted elsewhere. Possible if you route the traffic via (the VPS hosted by) OVH from and to your elsewhere hosted VM (via routing and VPN) but not an optimal solution. Try to get an IP from the provider which...

Use https://docs.openvswitch.org/en/latest/faq/configuration/

You have to increase (i.e. when using parted to delete it and create it again with a larger size) the partition /dev/sda3 first.

"multi"path means more than one logical connection to target. Yes, usually in case of having more NICs, but not necessarily. To figure out which connections currently exist run iscsiadm --mode session Yes, this is normal Follow exactly the advices is...