Search results

No, 255.255.255.255 is correct for venet0 in CT. Because you can imagine it as a peer-to-peer connection between host and CT.

Hello Fr0ggynator Difficult to say, depends on amount of disk-access, and I don´t know how your applications work in detail. In any case it´s safer to have the virtual disks distributed across more physical disks. I usually check what top (in host as well as in vm) says: top - 18:40:04 up...

Hello Fr0ggynator It is not a PCI card, but SATA controllers are usually controlled by the PCI bus. Have a look with lspci | grep SATA I cannot say (maybe somebody else in the forum knows it for sure) if there is another possibility than VT-d to access directly - but probably not. kind...

Hello vinc, obviously you don´t have access from CT to internet. Your CT address 10.147.42.61 is a local one, without having a NAT router to it it cannot work. Probably your proxmox host has a NIC connected to internet, assuming it´s eth0 a simple NAT works if you add iptables -t nat -A...

Hello Berthold Usually it works without any problems - I use frequently different IP address in order to access the WEB-GUI. Check it with netstat: netstat -l | grep 8006 tcp 0 0 *:8006 *:* LISTEN If you tell us more about your...

Hello engelant, I cannot see any restriction for bridge names - br0 should work. The whole configuration seems to be ok. Strange that "ifconfig -a" does not show br0. Check if ovs service is running by /etc/init.d/openvswitch-switch status the response should look like this ovsdb-server...

Hello Edgar, I understood you tried to change one or more IP addresses. Yes, it´s possible; you have to change IP addresses in /etc/network/interfaces and then /etc/init.d/networking restart It´s not necessary to add a new vmbr, but of course you can. Note: if you use the WEB-GUI for...

Hello engelant, I also had problems with VLANs bridged to VMs. Of course, not exactly the same configuration. Just as a hint: I changed to openvswitch and everything works perfectly (with VMs - in case of CTs a small trick was necessary but works no fine too). kind regards Mr.Holmes

You need the proper filesystem driver also in that case. Usually it can be done by modprobe ufs but this kernel module is not available in proxmox, moreover I think that supports only "read-only". Deeper investigation would be necessary.

For access to ntfs filesystem package ntfs-3g is needed which is not included in standard proxmox installation. After installing it it should work - but I didn´t test it in a proxmox installation yet.

Hopefully possible in your case! Recently I had a similar case and resolved it as follows: - removed the physical disk where the VMs were stored and connected to an empty (resp. to be overwritten) one; not the standard installation process possibly makes changes on all existing disks - made a...

Hello inkrmp, venet is for CTs (containers) but not for (k)VMs. In case of VMs you have to define (at least one) bridge on host and network cards in guests which are connected to that bridge. If you use containers to add an IP address is simple: select respective CT, go network-tab and make...

Yes Another possibilty seems to be "guestfish" (see new post). I didn´t know it before and don´t know what the advantage is compared with qemu-nbd which is already included in proxmox.

Hello AntoWkill I think you mean VM templates rather than CT templates. The answer is: No! Note that a template is ready to be the base for one or more linked clones and a change in it´s filesystem can destroy all these dependencies. Therefore: as soon as a VM is converted to a template...

check also LVM data pvdisplay vgdisplay lvdisplay

Hello bonsairack, Your vm´s are just the mentioned above openvz containers - right? I guess you mean to proxmox. The safer way. Possible but not recommended. It should be able to verify if restored container works before you delete the original one. Process it as follows: - make a...

Since in the meantime there was another reply the prepared answer became obsolete ...

A change to OVS without reboot of both host and VM is possible. In that case you have to - prepare /etc/network/interfaces.new (possible with GUI) - release linux-bridge from current VMs (brctl command) - stop network with /etc/init.d/networking stop - copy /etc/network/interfaces.new to...

Hello Josh, First an understanding question: It seems you have no DHCP client active except eth1 in the firewall container!? ARE YOU SURE? If so probably your cable modem scans all existing ports (resp. waits for the first occurring mac address on the line) and makes by itself an IP...

Hello gkovacs Yes - suggestion below No - but recommended to change to ovs (if you don´t use it yet) No Yes - but usually not necessary No - even it is possible to assign a NIC to an ovs and a linux-bridge at the same time - but it is a bug and dangerous! What I understood: A second LAN...