similar to: How to configure pxe options in the xen config file

Hi everyone, I want to know whether domain-U can boot PXE. I read relative article from here mailing list or many web sites already, but I don''t understand clearly. I concluded it is impossible, but Virtual Iron support VM''s(domU) pxe boot. I am confused. If it is possible, in my opinion, it needs a boot-loader support PXE ( for example, pygrub support pxe boot - of course I

Hi everyone, I want to know whether domain-U can boot PXE. I read relative article from here mailing list or many web sites already, but I don''t understand clearly. I concluded it is impossible, but Virtual Iron support VM''s(domU) pxe boot. I am confused. If it is possible, in my opinion, it needs a boot-loader support PXE ( for example, pygrub support pxe boot - of course I

Ok, that makes sense. PXELINUX had become a de facto standard and has in fact been extended with ipv6 support by agreement between me and Peter Jones, used in at least some versions of Grub. Here is the problem I see: arch discovery is orthogonal with address-based discovery. It creates a complex problem because we don't want to try all possible combinations. One option is to have an

On Mon, Feb 24, 2014 at 11:56 PM, Don Cupp <doncuppjr at yahoo.com> wrote: > https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/s1-netboot-pxe-config-efi.html Don, thanks for the reference. If Jeremy is doing this, then the dhcpd DOES INFACT know EXACTLY what it's booting and can easily use different directories. Without something

That is what I thought, but just to clarify: I am using static dhcp hosts in the dhcpd.conf and our network config. is similar to this: 3 subnets 192.168.15.0/24 192.168.16.0/24 192.168.17.0/24 dhcpd.conf ### Global Settings for DHCP Services ### option domain-name="dom.com"; default-lease-time 900; max-lease-time 1800; ddns-update-style none; authoritative; allow bootp; allow

Implements tool interfaces for scheduling domains. libxenctrl, xm, and xend. signed-off-by: Mike D. Day <ncmike@us.ibm.com> -- libxc/xc_domain.c | 85 +++++++++++++++++++++++++++++++++--- libxc/xenctrl.h | 43 ++++++++++++++++-- python/xen/xend/XendDomain.py | 78 +++++++++++++++++++++++++++++++++ python/xen/xend/server/SrvDomain.py |

On Mon, Feb 24, 2014 at 8:41 PM, Jeremy Kerr <jk at ozlabs.org> wrote: > As Gene has mentioned, we could indeed do this in pxelinux through > serving different binary images, but this means we need a different > method for different pxe loader implementations, and this won't work > when the loader binary is already present on the machine. > > What I'm looking to do

On Mon, Feb 24, 2014 at 10:09 PM, Jeremy Kerr <jk at ozlabs.org> wrote: > Hi Gene, > >>> What I'm looking to do here is establish a bit of a convention for >>> allowing machines of multiple architectures to be perform PXE >>> configuration in a uniform way (in this case, without requiring the DHCP >>> server to send out different lease parameters

https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/s1-netboot-pxe-config-efi.html On Monday, February 24, 2014 8:50 PM, Gene Cumm <gene.cumm at gmail.com> wrote: On Mon, Feb 24, 2014 at 10:09 PM, Jeremy Kerr <jk at ozlabs.org> wrote: > Hi Gene, > >>> What I'm looking to do here is establish a bit of a

# HG changeset patch # User john.levon@sun.com # Date 1181229858 25200 # Node ID e46be7b5f9bf2b17f66c82950b4fc3962e1266d0 # Parent 2a188f88483d726cb5b880f948a1baeeb2bd42a1 Remove unimplemented xm migrate --resource option. Signed-off-by: Gary Pennington <gary.pennington@sun.com> diff --git a/tools/python/xen/xend/XendDomain.py b/tools/python/xen/xend/XendDomain.py ---

Currently, the TFTP configuration file discovery process will request a set of files based on the UUID, MAC address, lease IP address and eventually fall back to "default": /mybootdir/pxelinux.cfg/b8945908-d6a6-41a9-611d-74a6ab80b83d /mybootdir/pxelinux.cfg/01-88-99-aa-bb-cc-dd /mybootdir/pxelinux.cfg/C000025B [...] /mybootdir/pxelinux.cfg/C /mybootdir/pxelinux.cfg/default

Hi Gene, >> What I'm looking to do here is establish a bit of a convention for >> allowing machines of multiple architectures to be perform PXE >> configuration in a uniform way (in this case, without requiring the DHCP >> server to send out different lease parameters in response to the >> client's DHCP architecture ID). > > How do you have multiple

Gene, All good questions. Thanks for taking time to respond. You've given me great leads to follow up w/ DHCP appliance consultant. >filename being file. I presume it looks like "/path/to/syslinux.efi" >or "/path/to/bootx64.efi" and not a TFTP URL? Correct. >> TFTP Server Name (66) -- a string. I have tried: >> - TFTP Server's IP

Hi I ve installed xen-3.2.3-0xs in Red Hat Enterprise Linux Server release 5.. & I ve successfully created guest domain with Fedora 4 image file While booting the guest domain first it shows the b---- state in xm list command and when the dom U gets booted up it turns to blank state.. Is there anything else to be configured to solve this issue?? [root@xencluster ~]# xm list Name

Hi all, >> https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/s1-netboot-pxe-config-efi.html > > Don, thanks for the reference. If Jeremy is doing this, then the > dhcpd DOES INFACT know EXACTLY what it's booting and can easily use > different directories. This approach is what I'd prefer to do (modifying DHCP lease

On Mon, Feb 24, 2014 at 3:14 AM, Jeremy Kerr <jk at ozlabs.org> wrote: > When serving PXE config files to machines of different architectures > (requiring separate boot images and config files), this means we > cannot use the autodisovery mechanism without having prior knowledge of > a MAC/IP/uuid-to-architecture mapping. Actually, you can. COM32 modules are not usable across

Hello, I''m trying to get a Xen v4 Guest running. When I start it I get a "ImportError: No module named ext" error and a note to report the problem to this list. xm create -x guest.cfg Using config file "./guest.cfg". Unexpected error: <type ''exceptions.ImportError''> Please report to xen-devel@lists.xensource.com Traceback (most recent call

I''ve attached the preliminary patch to add vncviewer options to the ''xl create''. It applies cleanly against c/s 4e1d091d10d8. All feedback is welcome. Goncalo # HG changeset patch # User Goncalo Gomes <goncalo.gomes@eu.citrix.com> # Date 1332257809 0 # Node ID 46f8afe643dee8de2c592c65204567fbad657616 # Parent 4e1d091d10d83130842170cd61f1194e5459f2aa Add

Hi all, >> In other words, the dhcp server has to start the client on the >> correct binary for it's arch and by virtue of running different bins, >> we can determine the most appropriate config file for the client? > > That is definitely one way to deal with it. > > There is no way around the fact that you have to have different binaries > for different

In other words, the dhcp server has to start the client on the correct binary for it's arch and by virtue of running different bins, we can determine the most appropriate config file for the client? On Monday, February 24, 2014 9:13 AM, Gene Cumm <gene.cumm at gmail.com> wrote: On Mon, Feb 24, 2014 at 3:14 AM, Jeremy Kerr <jk at ozlabs.org> wrote: > When serving PXE config