I''ve tried a couple times to PXE boot a domU by passing the "--pxe" option to virt-install but it stalls at: "Searching for server (DHCP)........" I also tried dumping an existing domU to an xml file and editing the boot device to "net", but then I''m unable to import the xml as a new domain. Is PXE possible for an HVM domU on a Solaris dom0? I installed remote installation services on a Windows server running as an HVM dom0. I noticed that the DHCP service in the Windows HVM doesn''t get the DHCP client requests when using the PV NIC driver. If I revert to the default NIC driver then the DHCP server in the domU works just fine. Any thoughts on this one? -- This message posted from opensolaris.org
On Mon, Nov 24, 2008 at 08:05:11PM -0800, Chris wrote:> I''ve tried a couple times to PXE boot a domU by passing the "--pxe" > option to virt-install but it stalls at: "Searching for server > (DHCP)........" I also tried dumping an existing domU to an xml > file and editing the boot device to "net", but then I''m unable to > import the xml as a new domain. Is PXE possible for an HVM domU on > a Solaris dom0?I''ve used PXE boot for Solaris HVM guests on Solaris dom0, including a couple of days ago. Admittedly this was a domain created with a .py file, but it doesn''t sound like that is the difference.> I installed remote installation services on a Windows server running > as an HVM dom0. I noticed that the DHCP service in the Windows HVM > doesn''t get the DHCP client requests when using the PV NIC driver. > If I revert to the default NIC driver then the DHCP server in the > domU works just fine. Any thoughts on this one?That''s odd. The packets passed to the driver should be the same in both cases (the come from the same source in dom0). When you say "doesn''t get the DHCP client requests", do you mean that it never makes an offer, or you''ve used a packet sniffer to be sure that the requests are not received?
>From a Windows server 2003 domU running a DHCP server, I used the Windows network monitor to capture incoming frames. When the default Realtek 8139 driver is used, the capture shows the DHCP requests and offers. A bare-metal client will PXE boot in this scenario, but another domU on the same physical system doesn''t seem to get the DHCP offer. I''ll have to set up another DHCP server to see if I can PXE boot a domU from an external system.When I use the PV NIC driver on the Windows DHCP server, the network monitor doesn''t list any network devices. I don''t haven''t tried using anything else to capture frames from the Windows domU, so I can''t say for sure that the server isn''t getting the DHCP requests, but after swapping the server''s NIC driver out for the PV version, even bare-metal clients fail to PXE boot. -- This message posted from opensolaris.org
On Tue, Nov 25, 2008 at 05:58:14PM -0800, Chris wrote:> From a Windows server 2003 domU running a DHCP server, I used the > Windows network monitor to capture incoming frames. When the > default Realtek 8139 driver is used, the capture shows the DHCP > requests and offers. A bare-metal client will PXE boot in this > scenario, but another domU on the same physical system doesn''t seem > to get the DHCP offer.This should work, though it''s not something that I''ve tested. At the risk of asking for the moon, have you used a non-DHCP server in a domU at any time?> When I use the PV NIC driver on the Windows DHCP server, the network > monitor doesn''t list any network devices. I don''t haven''t tried > using anything else to capture frames from the Windows domU, so I > can''t say for sure that the server isn''t getting the DHCP requests, > but after swapping the server''s NIC driver out for the PV version, > even bare-metal clients fail to PXE boot.This sounds like an issue specific to the Windows PV drivers. I''ll talk to the maintainers.
On Wed, Nov 26, 2008 at 10:28:23AM +0000, David Edmondson wrote:> On Tue, Nov 25, 2008 at 05:58:14PM -0800, Chris wrote: > > From a Windows server 2003 domU running a DHCP server, I used the > > Windows network monitor to capture incoming frames. When the > > default Realtek 8139 driver is used, the capture shows the DHCP > > requests and offers. A bare-metal client will PXE boot in this > > scenario, but another domU on the same physical system doesn''t seem > > to get the DHCP offer. > > This should work, though it''s not something that I''ve tested. At the > risk of asking for the moon, have you used a non-DHCP server in a domU > at any time?I mean, a non-Windows DHCP server.