Search results

I would love to hear anything factual from the OP as to why he believes dnsmasq is not robust.

Shutdown the KVM. Delete the e1000 NIC. Add a virtio NIC. Reboot :)

It's hard to parse what you are saying. By 'direct access', you bridge that NIC to the VM, and have proxmox not use the NIC itself. That works fine. If the performance is bad, that is possibly the debian driver proxmox uses, but there is no way to avoid that, since the guest has to go through...

Possibly that host is blacklisted though.

Aha, I wonder if they have that block blacklisted?

For what it's worth, there is at least once (fairly) recent thread on these forums about similar situations. Here is one: http://forum.proxmox.com/archive/index.php/t-4727.html?

Wait, is the above /etc/network/interfaces from the host or the guest?

I assume the 'xxx' is sanitized? I hope the gateway address is not also xxx. If you wanted this private, you would have been better to sanitize the other part of the address. e.g. instead of 1.2.3.xxx, something like a.b.c.1 and a.b.c.2 etc... At this point, I can't help you unless I know...

Post the contents of /etc/network/interfaces to start with.

To look at what? You haven't posted your network setup. If you mean spend some unknown amount of time trying to help you personally, sorry, I don't have the time...

I'd need to see the see the setup on the guest. e.g. how is the subnet defined there?

No guarantees, but looks okay to me...

Is there any kind of iptables that might be blocking the comcast traffic? What do you see (if anything) is you do a tcpdump on the ethernet interface on the guest while trying to reach it from the comcast address?

What kind of guest? How is the guest configured to use the subnet(s)? If it is an openvz guest, are you bridging the ethernet or using the container networking?

Offhand, this looks like it should work.

Being sarcastic will not get you help. You have provided several bits of information in your second post that were not in the first one.

Not a lot of detail here :( Are you saying the guest has those IPs assigned to it? An understanding of the network layout would help.

What is the problematic guest?

Safest way - boot the VM with clonezilla, save the disk to some storage (usb HD?), create a VM under esx, boot that VM with clonezilla, and restore it.

I wonder what he means by 'KVM VZ'?