Attempt to load same F10 PV DomU via profile , to avoid pygrub issue :-
memory = 1024
name = "FedoraPV"
ramdisk="/home/boris/kernel/initrd-2.6.27.19-170.2.35.fc10.x86_64.img"
kernel="/home/boris/kernel/vmlinuz-2.6.27.19-170.2.35.fc10.x86_64"
root="/dev/VolGroup00/LogVol00 ro"
extra = 'console=hvc0'
# vif = [ 'mac=00:16:3e:00:00:00' ]
disk = [ 'phy:/dev/sdb7,xvda,w']
vif = [ 'bridge=eth1' ]
Failure at booting up:-
****************************************************************
XENBUS: Timeout connecting to device: /device/vbd/51712
vif(0) could not be connected . Hotplug scripts not working.
*****************************************************************
Boris.
--- On Mon, 5/11/09, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Subject: Re: [Xen-devel] Changeset 19594 for Xen 3.4 build on Ubuntu Server 9.04 causes pygrub doesn't return any data anymore
To: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Monday, May 11, 2009, 5:11 PM
Attempt to install F10 PV DomU fails at DHCP request for DomU:-
Welcome to Fedora for x86_64
+-------------------------------------------------------+
| |
| root@ServerJaunty:/home/boris/vm# Error: Device 0 (vif) could
not be connected. Hotplug scripts not working. |
+-------------------------------------------------------+
--- On Mon, 5/11/09, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Subject: [Xen-devel] Changeset 19594 for Xen 3.4 build on Ubuntu Server 9.04 causes pygrub doesn't return any data anymore
To: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>
Cc:
"xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Monday, May 11, 2009, 4:27 PM
I was able to rebuild xen& tools with only one line modified in Config.mk :-
PYTHON ?= /usr/bin/python2.5
PYTHON_PREFIX_ARG ?= --prefix="$(PREFIX)"
# make clean
# make uninstall
# make install-xen
# make install-tools
IF PYTHON_PREFIX_ARG ?=''
OR
PYTHON_PREFIX_ARG ?= --prefix=''
# make tools
fails.
Xen 3.4 Dom0 with 2.6.30-rc3-tip loads fine. Xend starts fine.
Reports bellow :-
# xm info
# brctl show
# ifconfig
Demonstrate normal Xen
Host state.
However, working in same Xen environment and same kernel , been built on top of Ubuntu Server 8.10, F10 PV DomU fails to start:-
root@ServerJaunty:/home/boris/vm# cat f10.pyrun
name="F10PV"
memory=2048
disk = ['phy:/dev/sdb7,xvda,w' ]
vif = [ 'bridge=eth1' ]
bootloader =
"/usr/bin/pygrub"
vcpus=2
root@ServerJaunty:/home/boris/vm# xm create -c f10.pyrun
Using config file "./f10.pyrun".
Traceback (most recent call last):
File "/usr/bin/pygrub", line 684, in <module>
chosencfg = run_grub(file,
entry, fs, incfg["args"])
File "/usr/bin/pygrub", line 521, in run_grub
curses.wrapper(run_main)
File "/usr/lib/python2.5/curses/wrapper.py", line 47, in wrapper
root@ServerJaunty:/home/boris/vm# Error: Boot loader didn't return any data!
root@ServerJaunty:/home/boris/vm# xm create -c f10.pyrun
Using config file "./f10.pyrun".
Error: Boot loader didn't return any
data!
root@ServerJaunty:/home/boris/vm# xm create -c rhel.pyrun
Using config file "./rhel.pyrun".
Error: Boot loader didn't return any data!
root@ServerJaunty:/home/boris/vm#
Boris
|
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
