search for: devicepath

Sorry guys; I got a bit lost about Gene's request on this thread; usually a handle dump like # dh > handles.txt it's all we need to see the relationship between the NBP's device handle and the Service Binding handles. Did you get handles.txt? is it available for download somewhere? >>> Gene, after modifying some of Patrick's code I have been able to get the

Thanks Derrik; I got your efi-dh.txt I've found this: 252: SimpleNetwork PXEBaseCode LoadFile DevicePath(0000:0000:0000:0000:0000:0000)) 267: SimpleNetwork PXEBaseCode LoadFile DevicePath(065F36E00EE,0x1)/IPv4(0.0.0.0)) 27C: SimpleNetwork PXEBaseCode LoadFile DevicePath(0000:0000:0000:0000:0000:0000)) 291: SimpleNetwork PXEBaseCode LoadFile DevicePath(065F36E00EF,0x1)/IPv4(0.0.0.0)) 2A6: SimpleNetwork...

On Fri, Jul 31, 2015 at 12:37 PM, Patrick Masotta via Syslinux <syslinux at zytor.com> wrote: >>>> > > 5) upload handles.txt somewhere > > It's waiting at http://okkie.nu/tmp/handles.txt > <<< > > > OK your HP has 4 NICs > > DevicePath(0x0,0x0)/MAC(ECB1D775E524,0x0) > DevicePath(0x0,0x1)/MAC(ECB1D775E525,0x0)) > DevicePath(0x0,0x2)/MAC(ECB1D775E526,0x0)) > DevicePath(0x0,0x3)/MAC(ECB1D775E527,0x0)) > > Plus the PXEBaseCode handles are different than UDPv4ServiceBinding/TCPv4ServiceBinding handles. > Therefore yo...

> 5) upload handles.txt somewhere It's waiting at http://okkie.nu/tmp/handles.txt

...--- a/tools/python/xen/xend/XendDomainInfo.py Tue Sep 19 14:26:47 2006 +0100 +++ b/tools/python/xen/xend/XendDomainInfo.py Wed Sep 20 14:20:52 2006 -0500 @@ -1093,15 +1093,15 @@ class XendDomainInfo: ## public: def destroyDevice(self, deviceClass, devid): - if type(devid) is str: - devicePath = ''%s/device/%s'' % (self.dompath, deviceClass) - for entry in xstransact.List(devicePath): - backend = xstransact.Read(''%s/%s'' % (devicePath, entry), "backend") - devName = xstransact.Read(backend, "dev") - if devName == devid: - #...

>>> >> OK your HP has 4 NICs >> >> DevicePath(0x0,0x0)/MAC(ECB1D775E524,0x0) >> DevicePath(0x0,0x1)/MAC(ECB1D775E525,0x0)) >> DevicePath(0x0,0x2)/MAC(ECB1D775E526,0x0)) >> DevicePath(0x0,0x3)/MAC(ECB1D775E527,0x0)) According to HP it's actually one nic with four ports. I cannot disable them individually. <<...

On Fri, Aug 28, 2015 at 4:22 AM, Patrick Masotta <masottaus at yahoo.com> wrote: > Thanks Derrik; I got your efi-dh.txt > > I've found this: > > 252: SimpleNetwork PXEBaseCode LoadFile DevicePath(0000:0000:0000:0000:0000:0000)) > 267: SimpleNetwork PXEBaseCode LoadFile DevicePath(065F36E00EE,0x1)/IPv4(0.0.0.0)) > 27C: SimpleNetwork PXEBaseCode LoadFile DevicePath(0000:0000:0000:0000:0000:0000)) > 291: SimpleNetwork PXEBaseCode LoadFile DevicePath(065F36E00EF,0x1)/IPv4(0.0.0.0)) &gt...

From: Sylvain Gault <sylvain.gault at gmail.com> I don't know if I should merge those trivial warning fix into one commit. I can reformat it as requested. Those are a few warning fixes for the efi part. The code involved has mainly been introduced in recent commits. Sylvain Gault (3): efi: fix warnings about argument types efi: fix pointer-type mismatch assigment warning efi: fix

>>> > 5) upload handles.txt somewhere It's waiting at http://okkie.nu/tmp/handles.txt <<< OK your HP has 4 NICs DevicePath(0x0,0x0)/MAC(ECB1D775E524,0x0) DevicePath(0x0,0x1)/MAC(ECB1D775E525,0x0)) DevicePath(0x0,0x2)/MAC(ECB1D775E526,0x0)) DevicePath(0x0,0x3)/MAC(ECB1D775E527,0x0)) Plus the PXEBaseCode handles are different than UDPv4ServiceBinding/TCPv4ServiceBinding handles. Therefore you should follow this thread t...

>> OK your HP has 4 NICs >> >> DevicePath(0x0,0x0)/MAC(ECB1D775E524,0x0) >> DevicePath(0x0,0x1)/MAC(ECB1D775E525,0x0)) >> DevicePath(0x0,0x2)/MAC(ECB1D775E526,0x0)) >> DevicePath(0x0,0x3)/MAC(ECB1D775E527,0x0)) According to HP it's actually one nic with four ports. I cannot disable them individually. > git://gi...

On Mon, Aug 3, 2015 at 6:24 PM, Patrick Masotta <masottaus at yahoo.com> wrote: >>>> > >> OK your HP has 4 NICs > >> > >> DevicePath(0x0,0x0)/MAC(ECB1D775E524,0x0) > >> DevicePath(0x0,0x1)/MAC(ECB1D775E525,0x0)) > >> DevicePath(0x0,0x2)/MAC(ECB1D775E526,0x0)) > >> DevicePath(0x0,0x3)/MAC(ECB1D775E527,0x0)) > > According to HP it's actually one nic with four ports. I cannot disable > t...

...install-a-device-driver-in-a-windows-vm/ @@ -345,6 +347,81 @@ sub _add_service_to_registry $g->upload ($tmpdir . "/system", $system_filename); } +# We copy the VirtIO drivers to a directory on the guest and add this directory +# to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\DevicePath so that it will +# be searched automatically when automatically installing drivers. +sub _prepare_virtio_drivers +{ + my $g = shift; + my $tmpdir = shift; + my $desc = shift; + my $devices = shift; + my $config = shift; + + # Copy the target VirtIO drivers to the guest + my $dr...

...the following for(;;) structure will never have a MAC match, then the BS->OpenProtocol will never fail returning the needed "status != EFI_SUCCESS" to avoid de-referencing an undefined pointer (sbp->CreateChild) in the next code line. ... for (i = 0; i < nr_handles; i++) { DevicePath = DevicePathFromHandle(handles[i]); if (efi_get_MAC(DevicePath, &mac_2, PXE_MAC_LENGTH) && memcmp(mac_1, mac_2, PXE_MAC_LENGTH) == 0) { sb_handle = handles[i]; status = uefi_call_wrapper(BS->OpenProtocol, 6, sb_handle, bguid, (void **)&sbp, image_handle,...

...case under the handle 172 instead). The HP 2570p is not really an old PC (~2013) then I can think if we continue using the "same handle" method we will have problems PXE booting lot of UEFI PCs. I think when we receive the image_DeviceHandle we must save it but also parse the associated DevicePath saving the MAC address too. When looking for Pxebc Protocol we can use the image_DeviceHandle, next when ServiceBinding we need to detect all the available SB handles of the required type, parse their DevicePath and take the one with a matching MAC. Let me know if you see any alternative to MAC p...

...l never have a MAC match, then the > BS->OpenProtocol will never fail returning the needed "status != EFI_SUCCESS" > to avoid de-referencing an undefined pointer (sbp->CreateChild) in the next code line. > > ... > for (i = 0; i < nr_handles; i++) { > DevicePath = DevicePathFromHandle(handles[i]); > if (efi_get_MAC(DevicePath, &mac_2, PXE_MAC_LENGTH) > && memcmp(mac_1, mac_2, PXE_MAC_LENGTH) == 0) { > sb_handle = handles[i]; > status = uefi_call_wrapper(BS->OpenProt...

...dle 172 instead). > > The HP 2570p is not really an old PC (~2013) then I can think if we continue using the "same handle" method we will have > problems PXE booting lot of UEFI PCs. > I think when we receive the image_DeviceHandle we must save it but also parse the associated DevicePath saving the MAC address too. > When looking for Pxebc Protocol we can use the image_DeviceHandle, next when ServiceBinding we need to detect > all the available SB handles of the required type, parse their DevicePath and take the one with a matching MAC. > > Let me know if you see any al...

During conversion we copy the necessary drivers to the directory "%systemroot%\Drivers\Virtio", adding it to the DevicePath registry value. As documented in [1], this should be enough for Windows to find device drivers and successfully install them. However, it doesn't always happen. Commit 73e009c04 ("v2v: windows: Document use of pnputil to install drivers.") describes such issues with Win2k12R2. I...

On Fri, Jun 26, 2015 at 10:49 AM, Patrick Masotta <masottaus at yahoo.com> wrote: >>>> > Commit 23b2707 should resolve this. Please > let me know if you need > test binaries > > -- > -Gene > <<< > > > 1) About the Service Binding protocols, PXE protocol, etc having the same handle# is clear if we > see that the number is in fact

During conversion we copy the necessary drivers to the directory "%systemroot%\Drivers\Virtio", adding it to the DevicePath registry value. As documented in [1], this should be enough for Windows to find device drivers and successfully install them. However, it doesn't always happen. Commit 73e009c04 ("v2v: windows: Document use of pnputil to install drivers.") describes such issues with Win2k12R2. I...

On Wed, Jul 8, 2015 at 7:34 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > What about the observed symptoms? Have you performed an inline packet Jeff, there's specific code that creates specific responses that if you had mentioned what you saw, I'd expect we could have seen something sooner. -- -Gene