thr3ads.net - Xen users - [Xen-users] Using pygrub [Dec 2006]

If this information is useful, please help other people find it:
Share via:

Steve Kemp

2006-Dec-28 17:00 UTC

[Xen-users] Using pygrub

Having recently become aware of pygrub I''ve started using it.

  In general it works well, adding "bootloader = /path/to/pygrub" in
 the domU configuration and adding a simple menu.lst file to the
 domain''s file system works.

  However arguments don''t appear to be passed to the kernel.  With
 a menu.lst file such as this:

--
 title Xen 3.0 rescue
 kernel /boot/vmlinuz-2.6.16.33-xen root=/dev/sda1 init=/bin/sh
 initrd /boot/initrd.img-2.6.16.33-xen
--

  The system boots and the kernel ignores the "init=/bin/sh" argument
 completely.  Looking over the code I see mention of "args" but it 
 doesn''t look like it is used as I''d expect.  The following
fails too:

 args init=/bin/sh

  Is there a simple method of appending kernel arguments using pygrub?

Steve
-- 
http://www.steve.org.uk/

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Henning Sprang

2006-Dec-29 16:55 UTC

head link

Re: [Xen-users] Using pygrub

On 12/28/06, Steve Kemp <steve@steve.org.uk>
wrote:> [...]
>   The system boots and the kernel ignores the "init=/bin/sh"
argument
>  completely.  Looking over the code I see mention of "args" but
it
>  doesn''t look like it is used as I''d expect.  The
following fails too:
>
>  args init=/bin/sh
>
>   Is there a simple method of appending kernel arguments using pygrub?
Never used that myself yet, but because I know Fedora uses them when
setting up a vm with virt-install/ virt-manager, I looked at my fedora
test system.
There, when I set init=/bin/sh I am thrown into /bin/sh as wanted.

Not tried on Debian cause there I use only partitions - the standard
tools there don''t bother me with layering multiple partioning and
volume management tools but let me use simple partitoins :)

Are you sure you edited the menu.lst *inside* the domU and point the
bootloader correctly to this? Or, maybe you did not uncomment a
kernel= and root= line in the vm config file and this one is used
instead? Do you see a grub boot menu when starting the domain?

Henning

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Steve Kemp

2006-Dec-29 17:09 UTC

head link

Re: [Xen-users] Using pygrub

On Fri, Dec 29, 2006 at 05:55:24PM +0100, Henning Sprang wrote:
> Never used that myself yet, but because I know Fedora uses them when
> setting up a vm with virt-install/ virt-manager, I looked at my fedora
> test system.
> There, when I set init=/bin/sh I am thrown into /bin/sh as wanted.
  Right that is good to know.

  If from dom0 I call the pygrub program manually I see output which
 suggests things are working:

root@mine:~# /usr/bin/pygrub /dev/mine/trial.my.flat-disk

Going to boot Xen 3.0 default
  kernel: /boot/vmlinuz-2.6.16.33-xen
  initrd: /boot/initrd.img-2.6.16.33-xen

linux (kernel /var/run/xend/boot/boot_kernel.7juE6P)
      (ramdisk /var/run/xend/boot/boot_ramdisk.3tfTUo)
      (args ''init=/bin/sh root=/dev/sda1 ro console=tty0'')

  So the arguments have been read and contain my "init" string.

  However the system boots with no mention of that, and if I run
 "cat /proc/cmdline" in domU I don''t see that string at all.
> Are you sure you edited the menu.lst *inside* the domU and point the
> bootloader correctly to this?
  Yes.  (Well I certainly edited the menu.lst file in domU, but I
didn''t
 point anything else anywhere - except to add the kernel  + initrd files
 inside the domU and add the ''bootloader'' setting to the Xen
config.)
> Or, maybe you did not uncomment a kernel= and root= line in the vm
> config file and this one is used instead? Do you see a grub boot 
> menu when starting the domain?
  My complete domU configuration file is:

--
bootloader = ''/usr/bin/pygrub''
disk       = [ ''phy:mine/trial.my.flat-disk,sda1,w'', 
               ''phy:mine/trial.my.flat-swap,sda2,w'' ]
memory     = ''64''
name       = ''trial.my.flat''
vif        = [ ''ip=192.168.1.112'' ]
--

  Which looks valid to me ..

Steve
-- 

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Henning Sprang

2006-Dec-29 17:31 UTC

head link

Re: [Xen-users] Using pygrub

On 12/29/06, Steve Kemp <steve@steve.org.uk>
wrote:> On Fri, Dec 29, 2006 at 05:55:24PM +0100, Henning Sprang wrote:
>
> > Never used that myself yet, but because I know Fedora uses them when
> > setting up a vm with virt-install/ virt-manager, I looked at my fedora
> > test system.
> > There, when I set init=/bin/sh I am thrown into /bin/sh as wanted.
>
>   Right that is good to know.
>
>   If from dom0 I call the pygrub program manually I see output which
>  suggests things are working:
>
> root@mine:~# /usr/bin/pygrub /dev/mine/trial.my.flat-disk
>
> Going to boot Xen 3.0 default
>   kernel: /boot/vmlinuz-2.6.16.33-xen
>   initrd: /boot/initrd.img-2.6.16.33-xen
>
> linux (kernel /var/run/xend/boot/boot_kernel.7juE6P)
>       (ramdisk /var/run/xend/boot/boot_ramdisk.3tfTUo)
>       (args ''init=/bin/sh root=/dev/sda1 ro
console=tty0'')
>
>   So the arguments have been read and contain my "init" string.
>
>   However the system boots with no mention of that, and if I run
>  "cat /proc/cmdline" in domU I don''t see that string at
all.
>
> > Are you sure you edited the menu.lst *inside* the domU and point the
> > bootloader correctly to this?
>
>   Yes.  (Well I certainly edited the menu.lst file in domU, but I
didn''t
>  point anything else anywhere - except to add the kernel  + initrd files
>  inside the domU and add the ''bootloader'' setting to the
Xen config.)
>
> > Or, maybe you did not uncomment a kernel= and root= line in the vm
> > config file and this one is used instead? Do you see a grub boot
> > menu when starting the domain?
>
>   My complete domU configuration file is:
>
> --
> bootloader = ''/usr/bin/pygrub''
> disk       = [ ''phy:mine/trial.my.flat-disk,sda1,w'',
>                ''phy:mine/trial.my.flat-swap,sda2,w'' ]
> memory     = ''64''
> name       = ''trial.my.flat''
> vif        = [ ''ip=192.168.1.112'' ]
> --
>
>   Which looks valid to me ..
I see one difference: on Fedora, I see them only using this when
configuring disks as full  block devices inside the domu and not
exporting single partitions into the domu.
So, they''d have something like this instead of your disk config line:

disk       = [ ''phy:mine/trial.my.flat-disk,sda,w'' ]

and they create a partition table inside mine/trial.my.flat-disk.
(that''s what I thought of when saying I don''t like the
layering).

Don'' know if this difference can make your config not working, it
still seems to e good enough to boot, but it''s worth a try.

Henning

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

lists@higgers.me.uk

2006-Dec-29 21:46 UTC

head link

[Xen-users] Unable to Create HVM Guests

Hi All,

I recently upgraded my Xen box from OpenSUSE 10.1 to OpenSUSE 10.2.  
The kernel
is the one supplied in OpenSUSE (I haven''t compiled my own) version
2.6.18.2-34-xen and the xen version is 3.03.  I''m now unable to create
any HVM
guests, after issuing the xm create command the SDL BIOS window (if
that''s the
correct way to describe it) briefly appears for less than a second and then
dissapears.  The window isn''t visible on the screen long enough for me
to see
if there are any useful error messages.  I''ve included the output of xm
log and
the config file at the end of this message.

Any suggestions on how to fix this would be gratefully received! :-)

Thanks in advance,

Steve.

xm log:

[2006-12-29 21:35:49 xend.XendDomainInfo 3910] DEBUG (XendDomainInfo:190)
XendDomainInfo.create([\047vm\047, [\047name\047, \047Win2k3\047],
[\047memory\047, 2048], [\047on_poweroff\047, \047destroy\047],
[\047on_reboot\047, \047destroy\047], [\047on_crash\047, \047destroy\047],
[\047vcpus\047, \0471\047], [\047image\047, [\047hvm\047, [\047kernel\047,
\047/usr/lib/xen/boot/hvmloader\047], [\047device_model\047,
\047/usr/lib64/xen/bin/qemu-dm\047], [\047vcpus\047, \0471\047], 
[\047boot\047,
\047d\047], [\047vncunused\047, 1], [\047sdl\047, 1], [\047display\047,
\047:99.0\047], [\047xauthority\047, \047/root/.Xauthority\047]]],
[\047device\047, [\047vbd\047, [\047uname\047,
\047phy:/dev/system/win2k3_1\047], [\047dev\047, \047ioemu:hda\047],
[\047mode\047, \047w\047]]], [\047device\047, [\047vif\047, [\047bridge\047,
\047xenbr0\047], [\047type\047, \047ioemu\047]]]])
[2006-12-29 21:35:49 xend.XendDomainInfo 3910] DEBUG (XendDomainInfo:296)
parseConfig: config is [\047vm\047, [\047name\047, \047Win2k3\047],
[\047memory\047, 2048], [\047on_poweroff\047, \047destroy\047],
[\047on_reboot\047, \047destroy\047], [\047on_crash\047, \047destroy\047],
[\047vcpus\047, \0471\047], [\047image\047, [\047hvm\047, [\047kernel\047,
\047/usr/lib/xen/boot/hvmloader\047], [\047device_model\047,
\047/usr/lib64/xen/bin/qemu-dm\047], [\047vcpus\047, \0471\047], 
[\047boot\047,
\047d\047], [\047vncunused\047, 1], [\047sdl\047, 1], [\047display\047,
\047:99.0\047], [\047xauthority\047, \047/root/.Xauthority\047]]],
[\047device\047, [\047vbd\047, [\047uname\047,
\047phy:/dev/system/win2k3_1\047], [\047dev\047, \047ioemu:hda\047],
[\047mode\047, \047w\047]]], [\047device\047, [\047vif\047, [\047bridge\047,
\047xenbr0\047], [\047type\047, \047ioemu\047]]]]
[2006-12-29 21:35:49 xend.XendDomainInfo 3910] DEBUG (XendDomainInfo:395)
parseConfig: result is {\047shadow_memory\047: None, \047uuid\047: None,
\047on_crash\047: \047destroy\047, \047on_reboot\047: \047destroy\047,
\047localtime\047: None, \047image\047: [\047hvm\047, [\047kernel\047,
\047/usr/lib/xen/boot/hvmloader\047], [\047device_model\047,
\047/usr/lib64/xen/bin/qemu-dm\047], [\047vcpus\047, \0471\047], 
[\047boot\047,
\047d\047], [\047vncunused\047, 1], [\047sdl\047, 1], [\047display\047,
\047:99.0\047], [\047xauthority\047, \047/root/.Xauthority\047]],
\047on_poweroff\047: \047destroy\047, \047bootloader_args\047: None,
\047cpus\047: None, \047name\047: \047Win2k3\047, \047backend\047: [],
\047vcpus\047: 1, \047cpu_weight\047: None, \047features\047: None,
\047vcpu_avail\047: None, \047memory\047: 2048, \047device\047: [(\047vbd\047,
[\047vbd\047, [\047uname\047, \047phy:/dev/system/win2k3_1\047], [\047dev\047,
\047ioemu:hda\047], [\047mode\047, \047w\047]]), (\047vif\047, [\047vif\047,
[\047bridge\047, \047xenbr0\047], [\047type\047, \047ioemu\047]])],
\047bootloader\047: None, \047cpu\047: None, \047maxmem\047: None}
[2006-12-29 21:35:49 xend.XendDomainInfo 3910] DEBUG (XendDomainInfo:1274)
XendDomainInfo.construct: None
[2006-12-29 21:35:49 xend.XendDomainInfo 3910] DEBUG (XendDomainInfo:1306)
XendDomainInfo.initDomain: 30 1.0
[2006-12-29 21:35:49 xend 3910] DEBUG (image:320) args: boot, val: d
[2006-12-29 21:35:49 xend 3910] DEBUG (image:320) args: fda, val: None
[2006-12-29 21:35:49 xend 3910] DEBUG (image:320) args: fdb, val: None
[2006-12-29 21:35:49 xend 3910] DEBUG (image:320) args: soundhw, val: None
[2006-12-29 21:35:49 xend 3910] DEBUG (image:320) args: localtime, val: None
[2006-12-29 21:35:49 xend 3910] DEBUG (image:320) args: serial, val: None
[2006-12-29 21:35:49 xend 3910] DEBUG (image:320) args: std-vga, val: None
[2006-12-29 21:35:49 xend 3910] DEBUG (image:320) args: isa, val: None
[2006-12-29 21:35:49 xend 3910] DEBUG (image:320) args: vcpus, val: 1
[2006-12-29 21:35:49 xend 3910] DEBUG (image:320) args: acpi, val: None
[2006-12-29 21:35:49 xend 3910] DEBUG (image:320) args: usb, val: None
[2006-12-29 21:35:49 xend 3910] DEBUG (image:320) args: usbdevice, val: None
[2006-12-29 21:35:49 xend 3910] DEBUG (balloon:146) Balloon: 2125596 KiB free;
need 2124596; done.
[2006-12-29 21:35:49 xend 3910] INFO (image:136) buildDomain os=hvm dom=30
vcpus=1
[2006-12-29 21:35:49 xend 3910] DEBUG (image:274) dom            = 30
[2006-12-29 21:35:49 xend 3910] DEBUG (image:275) image         
/usr/lib/xen/boot/hvmloader
[2006-12-29 21:35:49 xend 3910] DEBUG (image:276) store_evtchn   = 1
[2006-12-29 21:35:49 xend 3910] DEBUG (image:277) memsize        = 2048
[2006-12-29 21:35:49 xend 3910] DEBUG (image:278) vcpus          = 1
[2006-12-29 21:35:49 xend 3910] DEBUG (image:279) pae            = 1
[2006-12-29 21:35:49 xend 3910] DEBUG (image:280) acpi           = 0
[2006-12-29 21:35:49 xend 3910] DEBUG (image:281) apic           = 0
[2006-12-29 21:35:49 xend 3910] DEBUG (image:415) hvm shutdown watch 
registered
[2006-12-29 21:35:50 xend 3910] DEBUG (DevController:110) 
DevController: writing
{\047backend-id\047: \0470\047, \047virtual-device\047: \047768\047,
\047device-type\047: \047disk\047, \047state\047: \0471\047, \047backend\047:
\047/local/domain/0/backend/vbd/30/768\047} to 
/local/domain/30/device/vbd/768.
[2006-12-29 21:35:50 xend 3910] DEBUG (DevController:112) 
DevController: writing
{\047domain\047: \047Win2k3\047, \047frontend\047:
\047/local/domain/30/device/vbd/768\047, \047dev\047: \047hda\047,
\047state\047: \0471\047, \047params\047: \047/dev/system/win2k3_1\047,
\047mode\047: \047w\047, \047online\047: \0471\047, \047frontend-id\047:
\04730\047, \047type\047: \047phy\047} to /local/domain/0/backend/vbd/30/768.
[2006-12-29 21:35:50 xend 3910] DEBUG (DevController:110) 
DevController: writing
{\047state\047: \0471\047, \047backend-id\047: \0470\047, \047backend\047:
\047/local/domain/0/backend/vif/30/0\047} to /local/domain/30/device/vif/0.
[2006-12-29 21:35:50 xend 3910] DEBUG (DevController:112) 
DevController: writing
{\047bridge\047: \047xenbr0\047, \047domain\047: \047Win2k3\047, 
\047handle\047:
\0470\047, \047script\047: \047/etc/xen/scripts/vif-bridge\047, \047state\047:
\0471\047, \047frontend\047: \047/local/domain/30/device/vif/0\047,
\047mac\047: \04700:16:3e:0a:a1:ee\047, \047online\047: \0471\047,
\047frontend-id\047: \04730\047, \047type\047: \047ioemu\047} to
/local/domain/0/backend/vif/30/0.
[2006-12-29 21:35:50 xend 3910] INFO (image:398) spawning device models:
/usr/lib64/xen/bin/qemu-dm [\047/usr/lib64/xen/bin/qemu-dm\047, \047-d\047,
\04730\047, \047-m\047, \0472048\047, \047-boot\047, \047d\047, 
\047-vcpus\047,
\0471\047, \047-domain-name\047, \047Win2k3\047, \047-net\047,
\047nic,vlan=1,macaddr=00:16:3e:7c:37:fb,model=rtl8139\047, \047-net\047,
\047tap,vlan=1,bridge=xenbr0\047, \047-k\047, \047en-us\047]
[2006-12-29 21:35:50 xend 3910] INFO (image:400) device model pid: 19529
[2006-12-29 21:35:50 xend.XendDomainInfo 3910] DEBUG (XendDomainInfo:712)
Storing VM details: {\047shadow_memory\047: \04710\047, \047uuid\047:
\0478184d103-523d-ea1c-77c8-130ed8daf88d\047, \047on_reboot\047:
\047destroy\047, \047start_time\047: \0471167428150.35\047,
\047on_poweroff\047: \047destroy\047, \047name\047: \047Win2k3\047,
\047xend/restart_count\047: \0470\047, \047vcpus\047: \0471\047,
\047vcpu_avail\047: \0471\047, \047memory\047: \0472048\047, \047on_crash\047:
\047destroy\047, \047image\047: \047(hvm (kernel /usr/lib/xen/boot/hvmloader)
(device_model /usr/lib64/xen/bin/qemu-dm) (vcpus 1) (boot d) (vncunused 
1) (sdl
1) (display :99.0) (xauthority /root/.Xauthority))\047, \047maxmem\047:
\0472048\047}
[2006-12-29 21:35:50 xend.XendDomainInfo 3910] DEBUG (XendDomainInfo:747)
Storing domain details: {\047console/port\047: \0472\047, \047name\047:
\047Win2k3\047, \047console/limit\047: \0471048576\047, \047vm\047:
\047/vm/8184d103-523d-ea1c-77c8-130ed8daf88d\047, \047domid\047: \04730\047,
\047cpu/0/availability\047: \047online\047, \047memory/target\047:
\0472097152\047, \047store/ring-ref\047: \047342472\047, \047store/port\047:
\0471\047}
[2006-12-29 21:35:50 xend 3910] DEBUG (image:438) hvm_shutdown fired, shutdown
reason=None
[2006-12-29 21:35:50 xend.XendDomainInfo 3910] DEBUG (XendDomainInfo:933)
XendDomainInfo.handleShutdownWatch
[2006-12-29 21:35:50 xend 3910] DEBUG (DevController:143) Waiting for devices
vif.
[2006-12-29 21:35:50 xend 3910] DEBUG (DevController:149) Waiting for 0.
[2006-12-29 21:35:50 xend 3910] DEBUG (DevController:464) 
hotplugStatusCallback
/local/domain/0/backend/vif/30/0/hotplug-status.
[2006-12-29 21:35:51 xend 3910] DEBUG (DevController:464) 
hotplugStatusCallback
/local/domain/0/backend/vif/30/0/hotplug-status.
[2006-12-29 21:35:51 xend 3910] DEBUG (DevController:478) 
hotplugStatusCallback
1.
[2006-12-29 21:35:51 xend 3910] DEBUG (DevController:143) Waiting for devices
usb.
[2006-12-29 21:35:51 xend 3910] DEBUG (DevController:143) Waiting for devices
vbd.
[2006-12-29 21:35:51 xend 3910] DEBUG (DevController:149) Waiting for 768.
[2006-12-29 21:35:51 xend 3910] DEBUG (DevController:464) 
hotplugStatusCallback
/local/domain/0/backend/vbd/30/768/hotplug-status.
[2006-12-29 21:35:52 xend 3910] DEBUG (DevController:464) 
hotplugStatusCallback
/local/domain/0/backend/vbd/30/768/hotplug-status.
[2006-12-29 21:35:52 xend 3910] DEBUG (DevController:478) 
hotplugStatusCallback
1.
[2006-12-29 21:35:52 xend 3910] DEBUG (DevController:143) Waiting for devices
irq.
[2006-12-29 21:35:52 xend 3910] DEBUG (DevController:143) Waiting for devices
pci.
[2006-12-29 21:35:52 xend 3910] DEBUG (DevController:143) Waiting for devices
ioports.
[2006-12-29 21:35:52 xend 3910] DEBUG (DevController:143) Waiting for devices
tap.
[2006-12-29 21:35:52 xend 3910] DEBUG (DevController:143) Waiting for devices
vtpm.
[2006-12-29 21:35:52 xend 3910] INFO (XendDomain:370) Domain Win2k3 (30)
unpaused.
[2006-12-29 21:35:53 xend.XendDomainInfo 3910] INFO 
(XendDomainInfo:892) Domain
has shutdown: name=Win2k3 id=30 reason=poweroff.
[2006-12-29 21:35:53 xend.XendDomainInfo 3910] DEBUG (XendDomainInfo:1470)
XendDomainInfo.destroy: domid=30
[2006-12-29 21:35:53 xend.XendDomainInfo 3910] DEBUG (XendDomainInfo:1478)
XendDomainInfo.destroyDomain(30)
[2006-12-29 21:35:53 xend 3910] DEBUG (image:427) hvm shutdown watch
unregistered

config file:

# Initial memory allocation (in megabytes) for the new domain.
memory = 2048
# kernel image file
kernel = "/usr/lib/xen/boot/hvmloader"
builder="hvm"
device_model=''/usr/lib64/xen/bin/qemu-dm''
name="Win2k3"
disk = [ ''phy:/dev/system/win2k3_1,ioemu:hda,w'' ]
on_poweroff = ''destroy''
on_reboot   = ''destroy''
on_crash    = ''destroy''
vcpus = "1"
vif = [ ''type=ioemu, bridge=xenbr0'' ]
# Disk image for
cdrom=''/data/w2003.iso''
# boot on floppy (a), hard disk (c) or CD-ROM (d)
boot=''d''
# enable SDL library for graphics, default = 0
sdl=1
# enable VNC library for graphics, default = 1
vnc=0
# enable spawning vncviewer(only valid when vnc=1), default = 1
vncviewer=0
#serial=''pty''
#stdvga=0
#audio=0
#nographic=0
#ne2000=1





_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Xen users - Dec 2006 - Using pygrub

[Xen-users] Using pygrub

Re: [Xen-users] Using pygrub

Re: [Xen-users] Using pygrub

Re: [Xen-users] Using pygrub

[Xen-users] Unable to Create HVM Guests