xen discuss - Aug 2007 - fyi: nv66 domU boots with F7 linux dom0 pygrub - very nice!

hi,

i just tried booting my nv66 domU using pygrub as the bootloader, *and it just
worked*. very nice. i had assumed that the image py script was the only way to
boot the kernel, but that''s not the case. now i no longer need to copy
the boot_archive back to the dom0''s domU image directory when
it''s updated!

fwiw, my guest''s py config file:

#
# solaris nv66
#
name = "solaris-11.nv66"
memory = 192
maxmem = 256
bootloader = "/usr/bin/pygrub"
root = "/dev/dsk/c0d0s0"
disk = [ ''phy:sdb5,0,w'' ]
vif = [ ''mac=00:1b:2c:3e:4d:5e, bridge=xenbr0'' ]
# boot verbosely
extra = "/platform/i86xpv/kernel/unix -v"
# boot verbosely in single user mode.
#extra = "/platform/i86xpv/kernel/unix -vs"
# boot verbosely under kmdb.
#extra = "/platform/i86xpv/kernel/unix -vdk"
on_shutdown = "destroy"
on_reboot = "destroy"
on_crash = "destroy"


Sherry
 
 
This message posted from opensolaris.org

On Fri, Aug 10, 2007 at 10:16:45AM -0700, Sherry L. Frasier wrote:
> i just tried booting my nv66 domU using pygrub as the bootloader, *and it
> just worked*. very nice. i had assumed that the image py script was the
only
> way to boot the kernel, but that''s not the case. now i no longer
need to copy
> the boot_archive back to the dom0''s domU image directory when
it''s updated!
> bootloader = "/usr/bin/pygrub"
What version of Xen are you using, and on what OS/distro?

thanks
john

> What version of Xen are you using, and on what
> OS/distro?
> 
> thanks
> john
Xen 3.1, running with a Fedora 7 dom0.
 
 
This message posted from opensolaris.org

On Thu, Aug 30, 2007 at 11:02:41AM -0700, Sherry L. Frasier wrote:
> > What version of Xen are you using, and on what
> > OS/distro?
> 
> Xen 3.1, running with a Fedora 7 dom0.
extra = "/platform/i86xpv/kernel/unix -v"

can be:

extra = "-v"

and it should still work.

regards
john

Just a quick question:-
I''ve recently installed F7 x86_64 along win Xen from distribution CD
(04/20/07) followed by "yum update" from Update CD (07/21/07)
# brctl show
reports that name of xen-bridge is "virbr0".
You are referencing vif=[''bridge=xenbr0''] in  Solaris
domU''s profile.
May be I am missing something or shouldn''t perform "yum
update" ?
 
 
This message posted from opensolaris.org

On Thu, Oct 04, 2007 at 10:07:41AM -0700, Boris Derzhavets
wrote:
> Just a quick question:-
> I''ve recently installed F7 x86_64 along win Xen from distribution
CD (04/20/07) followed by "yum update" from Update CD (07/21/07)
> # brctl show
> reports that name of xen-bridge is "virbr0".
> You are referencing vif=[''bridge=xenbr0''] in  Solaris
domU''s profile.
> May be I am missing something or shouldn''t perform "yum
update" ?
You can use "vif=[''bridge=virbr0''] (or probably just
"vif=['''']".

Actually , I''ve tried both options trying to reproduce:-
http://bderzhavets.blogspot.com/2007/09/install-solaris-domu-64-bit-under-xen-3.html
It worked fine for Xen 3.1 CentOS 5 and Debian Etch 4.0 Dom0 (64 bit)
(Xen 3.1 Binary install had been done previously)
However, in case of F7 installed along with it''s own Xen I was unable
to "scp" /a/platform/i86pc/amd64/boot_archive to F7 Dom0
I even couldn''t ping F7 dom0
 
 
This message posted from opensolaris.org

I reinstalled F7 (04/20/07) and attempted to create Solaris DomU.
After packages installation phase dropped to shell  and
tryed to ping F7 dom0 (192.168.122.7 assigned by me) and virbr0 (192.168.122.1
assigned by system). No respond.

Compared  Xen 3.1 on CentOS 5 and F7''s( built in) network reports.
On F7:-
1. ifconfig shows virbr0 as active 192.168.122.1 on F7 dom0
immediately after F7 install
2."brctl show" doesn''t show any interfaces connected to
bridge "virbr0"
On CentOS 5:-
1.ifcconfig shows xenbr0 without any assigned IP.
2."brctl show" shows two interfaces connected to bridge:- 
peth0,vif1.0
 
 
This message posted from opensolaris.org

Boris Derzhavets wrote:
> I reinstalled F7 (04/20/07) and attempted to create Solaris DomU.
> After packages installation phase dropped to shell  and
> tryed to ping F7 dom0 (192.168.122.7 assigned by me) and virbr0
(192.168.122.1 assigned by system). No respond.
> 
> Compared  Xen 3.1 on CentOS 5 and F7''s( built in) network reports.
> On F7:-
> 1. ifconfig shows virbr0 as active 192.168.122.1 on F7 dom0
> immediately after F7 install
> 2."brctl show" doesn''t show any interfaces connected to
bridge "virbr0"
> On CentOS 5:-
> 1.ifcconfig shows xenbr0 without any assigned IP.
> 2."brctl show" shows two interfaces connected to bridge:- 
peth0,vif1.0
>  
I just ran though a 32-bit bit Solaris domU on my Fedora7
dom0 (with latest bits). I used DHCP for the network..
Everything worked fine for me...

My steps are below....



[root@fedora solaris]# mount -o loop
/export/guests/install/solaris/solarisdvd.iso /mnt
[root@fedora solaris]# cp /mnt/boot/x86.miniroot /export/guests/install/solaris/
[root@fedora solaris]# cp /mnt/boot/platform/i86xpv/kernel/unix
/export/guests/install/solaris/
[root@fedora solaris]# umount /mnt
[root@fedora solaris]# dd if=/dev/zero
of=/export/guests/install/solaris/disk.img bs=1024k seek=8k count=1


[root@fedora solaris]# cat install.py


name = "solaris-install"
vcpus = 1
memory = "750"

kernel = "/export/guests/install/solaris/unix"
ramdisk = "/export/guests/install/solaris/x86.miniroot"
extra = "/platform/i86xpv/kernel/unix -B
install_media=cdrom,console=ttya"

disk =
[''file:/export/guests/install/solaris/solarisdvd.iso,6:cdrom,r'',
         ''file:/export/guests/install/solaris/disk.img,0,w'']

vif = ['''']

on_shutdown = "destroy"
on_reboot = "destroy"
on_crash = "destroy"



[root@fedora solaris]# xm create -c install.py
...
Run through the install...



Then I used the following to run the domain after the install
was completed.

[root@fedora solaris]# cat run.py
name = "solaris-install"
vcpus = 1
memory = "512"

bootloader = "/usr/bin/pygrub"
kernel = "/platform/i86xpv/kernel/unix"
ramdisk = "/platform/i86pc/boot_archive"

disk = [''file:/export/guests/install/solaris/disk.img,0,w'']

vif = ['''']

on_shutdown = "destroy"
on_reboot = "restart"
on_crash = "destroy"


[root@fedora solaris]# xm create -c run.py



-- 
Mark Johnson <mark.johnson@sun.com>
Sun Microsystems, Inc.
(781) 442-0869

It requires F7 (32 bit). Crashes immediately on either F7 (x86_64) or
CentOS 5 (x86_64). Box is built up with Core 2 Duo E6600 & ASUS P5B Deluxe.
I gonna try install original Xen 3.1 (64 bit) distribution  based on 2.6.18
linux kernel on F7 without virtualization at all.
 
 
This message posted from opensolaris.org

Bad luck. As far as to my knowledge F7 has a special Xen 3.1 implementation
involving DHCP server on Dom0 by default and expects any guest to be DHCP
client. That''s fine with me. However, 64 bit version of SNV66 for Xen
just hangs
when I ask "dhcp" configuration for PVM. F7''s  Xen default
configuration might be changed with xend-config.sxp...
 
 
This message posted from opensolaris.org

On Tue, Oct 09, 2007 at 04:56:31AM -0700, Boris Derzhavets
wrote:
> Bad luck. As far as to my knowledge F7 has a special Xen 3.1
> implementation involving DHCP server on Dom0 by default and expects
> any guest to be DHCP client. That''s fine with me. However, 64 bit
> version of SNV66 for Xen just hangs when I ask "dhcp"
configuration
> for PVM. F7''s Xen default configuration might be changed with
> xend-config.sxp...
This should work.

Can you describ how you "ask for dhcp configuration"? What is the
configuration of the guest domain?

During SNV66Xen text setup there is a screen, where you can mark one 
of two options. Configure or not DHCP for "xnf0".
It comes up at the start and looks pretty much like the forth one in:-
http://bderzhavets.blogspot.com/2007/09/install-solaris-domu-64-bit-under-xen-3.html
Then appears "Just a minute" message and installer hangs.
I''ve checked DHCP service to be up running on F7. Sounds like
"dhcbd" or
something like that. Maybe I made mistake at F7 dom0 side.
 
 
This message posted from opensolaris.org

Usually , when I selected negative option immeadiately after "dhcp"
selection screen I was asked:-
Next screen - Enter static IP address [            ]
..............
Wnen I selected to mark positive answer for DHCP option,
message like "Just a moment" came up.
 
 
This message posted from opensolaris.org

Just a screenshots:-
--------------------------Screen 1 ----------------------------------------

  Specify whether or not this network interface should use DHCP to configure
  itself.  Choose Yes if DHCP is to be used, or No if the network interface is
  to be configured manually.

  NOTE: DHCP support will not be enabled, if selected, until after the system
  reboots.

      Use DHCP for xnf0
      [X] Yes
      [ ] No

    F2_Continue    F6_Help

--------------------------Screen 2-------------------------------------------

 Confirm Information for xnf0 

  > Confirm the following information.  If it is correct, press F2;
    to change any information, press F4.


      Networked: Yes
       Use DHCP: Yes
    Enable IPv6: No


  Just a moment...
    F2_Continue    F4_Change    F6_Help
---------------------------------------------------------------------------------

Sevices running:-

dhcdbd
netplugd
Not sure this are right ones or some additional configuration is not required.
 
 
This message posted from opensolaris.org

The pause is due to the dhcp client trying to acquire an IP address.

Are you able to examine the traffic from the guest domain in dom0?
(ethereal on the link to the guest)

No , I need to be instructed how to do that. I am a DBA.
 
 
This message posted from opensolaris.org

I''ve downloaded Ethereal src.rpm along with user''s guide.
I also hardly believe , that DHCP request between Server and Client on the same
physical box may take 5 minutes. I just didn''t wait longer.
 
 
This message posted from opensolaris.org