Hello all, I''m trying to PXE boot (via kickstarts) the newly opensourced xenserver 6.2 image. Previous versions of citrix xenserver and xcp 1.6 booted successfully with the following boot options: XCP 1.6: append /images/xcp16/xen.gz dom0_mem=752M com1=115200,8n1 console=com1,vga --- /images/xcp16/vmlinuz xencons=hvc console=hvc0 console=tty0 answerfile=http://@@cblr_master@@/cblr/svc/op/ks/profile/xcp16 install --- /images/xcp16/install.img Citrix XenServer 6.0.2: append /images/xen602/xen.gz dom0_mem=752M com1=115200,8n1 console=com1,vga --- /images/xen602/vmlinuz xencons=hvc console=hvc0 console=tty0 answerfile=http://@@cblr_master@@/cblr/svc/op/ks/profile/xen602 install --- /images/xen602/install.img The same options do not work for Xenserver 6.2 however. There is no change in the answerfiles from what I could read. The PXE screen hangs at: .... Console [tty] enabled Console [hvc0] enabled What could be going wrong? Thanks, -- Prasanna., ------------------------ Powered by BigRock.com
Try removing all the extra consoles. Also maybe specify a ramdisk for root. I usually have something like this for my pxe cmdline and it installs 6.2.0 without issues. append XENSERVER_6.2.0_64/xen.gz --- XENSERVER_6.2.0_64/vmlinuz root=/dev/ram0 ramdisk_size=32758 atexit=shell answerfile=http://answerfile install --- XENSERVER_6.2.0_64/install.img -----Original Message----- From: xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf Of Prasanna Santhanam Sent: Thursday, July 04, 2013 11:07 AM To: xen-users@lists.xen.org Subject: [Xen-users] PXE booting XenServer 6.2 Hello all, I''m trying to PXE boot (via kickstarts) the newly opensourced xenserver 6.2 image. Previous versions of citrix xenserver and xcp 1.6 booted successfully with the following boot options: XCP 1.6: append /images/xcp16/xen.gz dom0_mem=752M com1=115200,8n1 console=com1,vga --- /images/xcp16/vmlinuz xencons=hvc console=hvc0 console=tty0 answerfile=http://@@cblr_master@@/cblr/svc/op/ks/profile/xcp16 install --- /images/xcp16/install.img Citrix XenServer 6.0.2: append /images/xen602/xen.gz dom0_mem=752M com1=115200,8n1 console=com1,vga --- /images/xen602/vmlinuz xencons=hvc console=hvc0 console=tty0 answerfile=http://@@cblr_master@@/cblr/svc/op/ks/profile/xen602 install --- /images/xen602/install.img The same options do not work for Xenserver 6.2 however. There is no change in the answerfiles from what I could read. The PXE screen hangs at: .... Console [tty] enabled Console [hvc0] enabled What could be going wrong? Thanks, -- Prasanna., ------------------------ Powered by BigRock.com _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Mon, Jul 08, 2013 at 02:24:32PM +0000, Joseph Hom wrote:> Try removing all the extra consoles. Also maybe specify a ramdisk > for root. I usually have something like this for my pxe cmdline and > it installs 6.2.0 without issues. > > append XENSERVER_6.2.0_64/xen.gz --- XENSERVER_6.2.0_64/vmlinuz > root=/dev/ram0 ramdisk_size=32758 atexit=shell > answerfile=http://answerfile install --- > XENSERVER_6.2.0_64/install.imgThanks, I tried this and it worked for xcp 1.6 and xen 6.0.2 but didn''t for xen 6.2. Still stuck on the console line: http://prntscr.com/1eektk -- Prasanna., ------------------------ Powered by BigRock.com
Can you paste your full modified PXE entry? -----Original Message----- From: Prasanna Santhanam [mailto:tsp@apache.org] Sent: Tuesday, July 09, 2013 8:18 AM To: Joseph Hom Cc: Prasanna Santhanam; xen-users@lists.xen.org Subject: Re: [Xen-users] PXE booting XenServer 6.2 On Mon, Jul 08, 2013 at 02:24:32PM +0000, Joseph Hom wrote:> Try removing all the extra consoles. Also maybe specify a ramdisk for > root. I usually have something like this for my pxe cmdline and it > installs 6.2.0 without issues. > > append XENSERVER_6.2.0_64/xen.gz --- XENSERVER_6.2.0_64/vmlinuz > root=/dev/ram0 ramdisk_size=32758 atexit=shell > answerfile=http://answerfile install --- > XENSERVER_6.2.0_64/install.imgThanks, I tried this and it worked for xcp 1.6 and xen 6.0.2 but didn''t for xen 6.2. Still stuck on the console line: http://prntscr.com/1eektk -- Prasanna., ------------------------ Powered by BigRock.com
On Tue, Jul 09, 2013 at 03:25:33PM +0000, Joseph Hom wrote:> Can you paste your full modified PXE entry? >Sure, here it is from /var/lib/tftpboot/pxelinux.cfg/default: default linux prompt 0 timeout 1 label linux kernel /images/xen62/mboot.c32 ipappend 2 append /images/xen62/xen.gz --- /images/xen62/vmlinuz root=/dev/ram0 ramdisk_size=32758 atexit=shell answerfile=http://10.208.8.5/cblr/svc/op/ks/system/test-xen62-1 install --- /images/xen62/install.img -- Prasanna., ------------------------ Powered by BigRock.com
Hello. El 09/07/13 08:17, Prasanna Santhanam escribió:> On Mon, Jul 08, 2013 at 02:24:32PM +0000, Joseph Hom wrote: >> Try removing all the extra consoles. Also maybe specify a ramdisk >> for root. I usually have something like this for my pxe cmdline and >> it installs 6.2.0 without issues. >> >> append XENSERVER_6.2.0_64/xen.gz --- XENSERVER_6.2.0_64/vmlinuz >> root=/dev/ram0 ramdisk_size=32758 atexit=shell >> answerfile=http://answerfile install --- >> XENSERVER_6.2.0_64/install.img > > Thanks, I tried this and it worked for xcp 1.6 and xen 6.0.2 but > didn''t for xen 6.2. Still stuck on the console line: > http://prntscr.com/1eektkI''m successfully booting XS 6.2 installation via PXE. So far it boots on a VirtualBox VM, but can''t get beyond networking detection. It seems something is wrong with the dhclient in XS 6.2 initrd. I have not tested it on physical hardware yet. Maybe yours is the same problem, maybe not. This are some points worth checking: 1. Make sure the option "redirect console after boot" is disabled in your BIOS. I''m not sure what this option is intended for, but I find it messes up things when playing with serial console. It is not needed to be enabled for a serial console setup with Linux. 2. When using serial console, on previous versions of Xen, I have seen some output to be missed, it was not copied to both, the physical and serial console. My solution was to decide which I use and not to count on the other one. Since you are using a iDRAC card, which gives you a "normal" graphical console, consider dropping the serial console and omit it''s reference from the boot configuration. 3. Check your serial ports configuration in BIOS. What is mapped as com1, the internal port or the external one? If it''s external and there is something connected to it, it may confuse the console. 4.Check the debug virtual console (Alt-F2, hope your iDRAC can do it). It''s possible that something went wrong with your answers file or networking detection. 5. Try booting without answers file first. With answers file, since the process is supposed to be unattended, the feedback is poor. This is my boot configuration (mostly copied from my XCP 1.6 install setup): append deploy/XenServer-6.2.0-install-cd/boot/xen.gz dom0_mem=752M com2=115200,8n1 console=com2,vga --- deploy/XenServer-6.2.0-install-cd/boot/vmlinuz console=tty0 xencons=hvc console=hvc0 --- deploy/XenServer-6.2.0-install-cd/install.img For reference, in production I use serial console on com2, mapped to my PowerEdge''s internal serial port, which I access via IPMI SOL. Greetings. -- Alexandre Kouznetsov
On Tue, Jul 09, 2013 at 10:58:37AM -0500, Alexandre Kouznetsov wrote:> Hello.Thanks for the detailed pointers, results of my tests are inline.> > El 09/07/13 08:17, Prasanna Santhanam escribi?: > >On Mon, Jul 08, 2013 at 02:24:32PM +0000, Joseph Hom wrote: > >>Try removing all the extra consoles. Also maybe specify a ramdisk > >>for root. I usually have something like this for my pxe cmdline and > >>it installs 6.2.0 without issues. > >> > >> append XENSERVER_6.2.0_64/xen.gz --- XENSERVER_6.2.0_64/vmlinuz > >> root=/dev/ram0 ramdisk_size=32758 atexit=shell > >> answerfile=http://answerfile install --- > >> XENSERVER_6.2.0_64/install.img > > > >Thanks, I tried this and it worked for xcp 1.6 and xen 6.0.2 but > >didn''t for xen 6.2. Still stuck on the console line: > >http://prntscr.com/1eektk > > I''m successfully booting XS 6.2 installation via PXE. So far it > boots on a VirtualBox VM, but can''t get beyond networking detection. > It seems something is wrong with the dhclient in XS 6.2 initrd. I > have not tested it on physical hardware yet. >I''ve got it installed on a virtualbox but not with PXE yet. I will attempt that next.> Maybe yours is the same problem, maybe not. This are some points > worth checking: > > 1. Make sure the option "redirect console after boot" is disabled in > your BIOS. I''m not sure what this option is intended for, but I find > it messes up things when playing with serial console. It is not > needed to be enabled for a serial console setup with Linux. >This was enabled so I disabled it and attempted a PXE boot and the iDrac console was stuck at the same point. So looks like the option didn''t have any effect.> 2. When using serial console, on previous versions of Xen, I have > seen some output to be missed, it was not copied to both, the > physical and serial console. My solution was to decide which I use > and not to count on the other one. Since you are using a iDRAC card, > which gives you a "normal" graphical console, consider dropping the > serial console and omit it''s reference from the boot configuration. >I dropped all console references as Joseph had pointed and that didn''t work for Xen 6.2 but did for previous version.> 3. Check your serial ports configuration in BIOS. What is mapped as > com1, the internal port or the external one? If it''s external and > there is something connected to it, it may confuse the console. >com1 is external but not connected to anything. I set to com2 and attempted booting. No go. Then set to "Remove Access Device" and still no use.> 4.Check the debug virtual console (Alt-F2, hope your iDRAC can do > it). It''s possible that something went wrong with your answers file > or networking detection. >This option doesn''t seem to be supported on my iDrac.> 5. Try booting without answers file first. With answers file, since > the process is supposed to be unattended, the feedback is poor. >I booted from the CD image and the installation was successful. But here''s my answers file for reference. The vars ($server, $distro) are replaced by cobbler on boot. <?xml version="1.0"?> <installation mode="fresh" srtype="lvm"> <primary-disk gueststorage="yes">sda</primary-disk> <keymap>us</keymap> <root-password>password</root-password> <source type="url">http://$server/cblr/links/$distro</source> <admin-interface name="eth0" proto="dhcp" /> <timezone>UTC</timezone> <time-config-method>ntp</time-config-method> <ntp-servers>ntp</ntp-servers> <ntpservers>0.in.pool.ntp.org</ntpservers> </installation>> This is my boot configuration (mostly copied from my XCP 1.6 install setup): > append deploy/XenServer-6.2.0-install-cd/boot/xen.gz dom0_mem=752M > com2=115200,8n1 console=com2,vga --- > deploy/XenServer-6.2.0-install-cd/boot/vmlinuz console=tty0 > xencons=hvc console=hvc0 --- > deploy/XenServer-6.2.0-install-cd/install.imgyup I had the same setup working for xen 6.1. I''m still not clear why that would go wrong for 6.2. Thanks for the help so far.> > For reference, in production I use serial console on com2, mapped to > my PowerEdge''s internal serial port, which I access via IPMI SOL. > > Greetings. > > -- > Alexandre Kouznetsov > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users-- Prasanna., ------------------------ Powered by BigRock.com
Hello. El 10/07/13 04:39, Prasanna Santhanam escribió:> On Tue, Jul 09, 2013 at 10:58:37AM -0500, Alexandre Kouznetsov wrote: >> >> 1. Make sure the option "redirect console after boot" is disabled in >> your BIOS. I''m not sure what this option is intended for, but I find >> it messes up things when playing with serial console. It is not >> needed to be enabled for a serial console setup with Linux. >> > This was enabled so I disabled it and attempted a PXE boot and the > iDrac console was stuck at the same point. So looks like the option > didn''t have any effect.A least, one thing less to worry about. Shall be safe to leave it that way.>> 2. When using serial console, on previous versions of Xen, I have >> seen some output to be missed, it was not copied to both, the >> physical and serial console. My solution was to decide which I use >> and not to count on the other one. Since you are using a iDRAC card, >> which gives you a "normal" graphical console, consider dropping the >> serial console and omit it''s reference from the boot configuration. >> > I dropped all console references as Joseph had pointed and that didn''t > work for Xen 6.2 but did for previous version.Another one less.>> 3. Check your serial ports configuration in BIOS. What is mapped as >> com1, the internal port or the external one? If it''s external and >> there is something connected to it, it may confuse the console. >> > com1 is external but not connected to anything. I set to com2 and > attempted booting. No go. Then set to "Remove Access Device" and still > no use.I think with this you have eliminated the possibility of something interfering with the console. So, the issue should be within the installation process.>> 4.Check the debug virtual console (Alt-F2, hope your iDRAC can do >> it). It''s possible that something went wrong with your answers file >> or networking detection. >> > This option doesn''t seem to be supported on my iDrac.I''m afraid you will have to use the physical console to finish exploring this option then. I''m almost sure it''s the network detection fault, not the console.>> 5. Try booting without answers file first. With answers file, since >> the process is supposed to be unattended, the feedback is poor. >> > I booted from the CD image and the installation was successful.No, forget the CD for now. The proof of concept would be to boot installation from PXE and without answerfile. Just omit the "answerfile=" parameter on your pxelinux config.> But here''s my answers file for reference. > > The vars ($server, $distro) are replaced by cobbler on boot. > > <?xml version="1.0"?> > <installation mode="fresh" srtype="lvm"> > <primary-disk gueststorage="yes">sda</primary-disk> > <keymap>us</keymap> > <root-password>password</root-password> > <source type="url">http://$server/cblr/links/$distro</source> > <admin-interface name="eth0" proto="dhcp" /> > <timezone>UTC</timezone> > <time-config-method>ntp</time-config-method> > <ntp-servers>ntp</ntp-servers> > <ntpservers>0.in.pool.ntp.org</ntpservers> > </installation>Looks good to me. Greetings. -- Alexandre Kouznetsov
On Wed, Jul 10, 2013 at 09:58:02AM -0500, Alexandre Kouznetsov wrote:> >> > >I booted from the CD image and the installation was successful. > No, forget the CD for now. The proof of concept would be to boot > installation from PXE and without answerfile. Just omit the > "answerfile=" parameter on your pxelinux config.Unfortunately, it gets stuck w.o the answerfile added in the boot args too. :/ -- Prasanna., ------------------------ Powered by BigRock.com
Hello. El 11/07/13 06:55, Prasanna Santhanam escribió:> On Wed, Jul 10, 2013 at 09:58:02AM -0500, Alexandre Kouznetsov wrote: >>>> >>> I booted from the CD image and the installation was successful. >> No, forget the CD for now. The proof of concept would be to boot >> installation from PXE and without answerfile. Just omit the >> "answerfile=" parameter on your pxelinux config. > > Unfortunately, it gets stuck w.o the answerfile added in the boot > args too. :/I guess, your next available option is to check the physical server. Look for error logs on virtual consoles, accessible with Alt-F* keys. It should say what''s wrong. -- Alexandre Kouznetsov