search for: enabledhcp

...he problem we're seeing, as it is a bit more general and might even apply in some cloud scenarios. If you have a Windows guest which starts out with a static IP address (no DHCP) it might be configured like this on VMware: 00:50:56:01:02:03 192.168.128.10 vmxnet3 "Ethernet0" EnableDHCP=0 After conversion we preserve the MAC address and add virtio drivers, but the new netkvm.sys driver just adds a new network interface so it'll end up like this: (no hardware) 192.168.128.10 vmxnet3 "Ethernet0" EnableDHCP=0 00:50:56:01:02:03 (no address) netkvm...

...> > general and might even apply in some cloud scenarios. If you have a > > Windows guest which starts out with a static IP address (no DHCP) it > > might be configured like this on VMware: > > > > 00:50:56:01:02:03 192.168.128.10 vmxnet3 "Ethernet0" EnableDHCP=0 > > > > After conversion we preserve the MAC address and add virtio drivers, > > but the new netkvm.sys driver just adds a new network interface so > > it'll end up like this: > > > > (no hardware) 192.168.128.10 vmxnet3 "Ethernet0" En...

...gt; > general and might even apply in some cloud scenarios. If you have a > > Windows guest which starts out with a static IP address (no DHCP) it > > might be configured like this on VMware: > > > > 00:50:56:01:02:03 192.168.128.10 vmxnet3 "Ethernet0" EnableDHCP=0 > > > > After conversion we preserve the MAC address and add virtio drivers, > > but the new netkvm.sys driver just adds a new network interface so > > it'll end up like this: > > > > (no hardware) 192.168.128.10 vmxnet3 "Ethernet0"...

...ing, as it is a bit more > general and might even apply in some cloud scenarios. If you have a > Windows guest which starts out with a static IP address (no DHCP) it > might be configured like this on VMware: > > 00:50:56:01:02:03 192.168.128.10 vmxnet3 "Ethernet0" EnableDHCP=0 > > After conversion we preserve the MAC address and add virtio drivers, > but the new netkvm.sys driver just adds a new network interface so > it'll end up like this: > > (no hardware) 192.168.128.10 vmxnet3 "Ethernet0" EnableDHCP=0 > 00:50:56:01:...

This patch is just for discussion. There are still a couple of issues that I'm trying to fix. One is that all of the test guests I have, even ones with static IPs, have multiple interfaces, some using DHCP, so the conditions for adding the Powershell script don't kick in. This makes testing very awkward. However a bigger issue is that I think the premise is wrong. In some registries

v1 was here with much discussion: https://www.redhat.com/archives/libguestfs/2018-December/msg00048.html v2: - Fix the case where there are multiple interfaces. Note this does not preserve order correctly (see patch for comment on why that is a hard problem). - Preserve name servers. This patch is still for discussion only. I'd like to see what might be done to get this upstream