Search results

When you create a VM with an ISO, you have to install the OS and you select the root password.

Create a vmbr# (pick any number you like), do not give it an IP and do not attach it to any devices Install a firewall/router distro in a KVM (I prefer VyOS) For the VM, assign eth0(VM setting, not host network setting) to vmbr0, and assign eth1 to your new vmbr Set up your router distro in...

Gotta love nutanix website. They explain nothing while just spouting off buzzwords and marketing speak

That screenshot is of a container. Not a KVM

Use the api's for provisioning VMs. But I don't know what you're talking about with a network tab on kvm. Kvm will always require a manual config in the VM unless you are running a dhcp server on the network.

You can tag the nic setting in the VM options with the vlan tag. You don't need subinterfaces on the eth device on Proxmox host.

There should be no struggle at all. Use your single VMBR0, and in your VM settings under the network interface setting, you just tag the interfaces you want on whatever VLAN you want them. It is really straight forward and there is no need for weird or special rules on your proxmox interfaces...

I used the special vlan interfaces prior to the addition to the tags capabilities on the vz containers. It's an unnecessary complexity now. Much easier to just tag the vlan. If I want to add a vlan to my network, I can do it now without changing any network configurations on Proxmox

Special vlan interfaces are no longer required in Proxmox. Every kvm and vz can get a vlan tag on it. This configuration appears to be overly complicated for what the op has requested. It's as simple as having one interface with the vmbr0, and tag whatever vlans need to be tagged. If a VM...

But you can just pass the VLAN tag right on your VMBR0. You do not need to create sub interfaces. When you use the VLAN tag it actually mimics that sub interface. Can you provide a network diagram? You have a router that handles the VLAN traffic, yes? You simply tag the VMBR with the VLAN...

A. Only put an IP address on the vmbr0(the one you use to connect to Proxmox) B. You do not need IP addresses on other bridges C. Make a vmbr that isn't connected to a eth device and you will have a VM only nic. From what you have described that you want, you don't need anything more than...

You should not have the IP on the eth device but on the vmbr0

Mdraid works fine. I use a raid 10. You just need to configure it from cli and then add it as a directory

You added to a cluster over a WAN link? Through VPN i hope?

You shouldn't have an IP directly on the eth device. Put it on the vmbr0

Yeah, totally not blaming them, huh? Last I checked, I was free to have an account on a forum and discuss things. Don't like what I say? Just report the post and move the fuck along. I don't really care if they ban me. These guys do more for everyone here than they should and it always...

senior member just means I have been around the forums for a long time, it means fuck all when it comes to association with proxmox. I have no association with proxmox aside from being on these forums and using the product for years....so basing your decision on getting support directly from...

The problem with this logic that you seem to want to try to put in my mouth? YOU DIDNT PAY FOR PROXMOX. If you did, contact them on your support. This is an open source project, find a problem? Fix it.

What would you like the proxmox guys to look at? If it's an issue with seabios, that's not specific to proxmox and would happen on any kvm. You specifically state "I'm not blaming them, I just wish they would look into it". That is blaming proxmox. Talk to upstream kvm or the guys that write...

My 4 proxmox nodes have been running Windows xp, 7, 2008, 2012 just fine for years... Not sure why since people seem to have issues and want to blame proxmox.