Hi!
Got a fresh install of b129.
Did an install of Fedora12, worked great. Fedora goes through the
entire install,
finishes, and wants to reboot.
Can''t reboot, I get the following error:
# virsh start fedora
error: Failed to start domain fedora
error: POST operation failed: xend_post: error from xen daemon:
(xend.err "Boot loader didn''t return any data!")
I can look at the zvol (/dev/zvol/dsk/rpool/guests/fedora) and see that
grub did get installed.
# dd if=/dev/zvol/rdsk/rpool/guests/fedora of=/tmp/junk bs=1024k count=2
# od -c /tmp/junk > /tmp/junk.od-c
# more /tmp/junk.od-c
....
0000560 \0 276 223 } 350 * \0 353 376 G R U B \0 G
0000600 e o m \0 H a r d D i s k \0 R e
....
Here was my install script:
MEDIA=nfs:192.168.5.1:/storage/misc/Downloads/ISOs/Linux/Fedora12/Fedora-12-x86_64-DVD
NAME=fedora
POOL=rpool/guests
#zfs create -V 50G ${POOL}/${NAME}
virt-install \
--paravirt \
--nographics \
--noautoconsole \
--debug \
--os-type linux \
--os-variant fedora11 \
-n ${NAME} \
-f /dev/zvol/dsk/${POOL}/${NAME} \
-l ${MEDIA} \
--vcpus=1 \
-r 1024
(I tried with and without ''nographics'' and
''autoconsole'')
Any suggestions?
emike
Hi eMike, I haven''t any idea if it will help, but usually when I refer to a zvol, I use a different syntax. --disk path=/tank/guests/dom1/disk0,size=10,driver=phy,subdriver=zvol http://hub.opensolaris.org/bin/view/Community+Group+xen/virtinstall Perhaps that will help? On Dec 14, 2009, at 7:17 PM, E. Mike Durbin wrote:> Hi! > > Got a fresh install of b129. > > Did an install of Fedora12, worked great. Fedora goes through the entire install, > finishes, and wants to reboot. > > Can''t reboot, I get the following error: > > # virsh start fedora > error: Failed to start domain fedora > error: POST operation failed: xend_post: error from xen daemon: (xend.err "Boot loader didn''t return any data!") > > I can look at the zvol (/dev/zvol/dsk/rpool/guests/fedora) and see that > grub did get installed. > > # dd if=/dev/zvol/rdsk/rpool/guests/fedora of=/tmp/junk bs=1024k count=2 > # od -c /tmp/junk > /tmp/junk.od-c > # more /tmp/junk.od-c > .... > 0000560 \0 276 223 } 350 * \0 353 376 G R U B \0 G > 0000600 e o m \0 H a r d D i s k \0 R e > .... > > Here was my install script: > > MEDIA=nfs:192.168.5.1:/storage/misc/Downloads/ISOs/Linux/Fedora12/Fedora-12-x86_64-DVD > > NAME=fedora > POOL=rpool/guests > > #zfs create -V 50G ${POOL}/${NAME} > > virt-install \ > --paravirt \ > --nographics \ > --noautoconsole \ > --debug \ > --os-type linux \ > --os-variant fedora11 \ > -n ${NAME} \ > -f /dev/zvol/dsk/${POOL}/${NAME} \ > -l ${MEDIA} \ > --vcpus=1 \ > -r 1024 > > (I tried with and without ''nographics'' and ''autoconsole'') > > Any suggestions? > > emike > > > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org
CS 19740 from xen-3.4-testing.hg appears to be applied to current xVM’s tree :-
xen_changeset : Fri Dec 11 08:54:46 2009 +0300 19667:efeb205e29b8
Build on 11/30/09 was still affected. Date for 129 is 11/24/09 , hence CS 19740
was not applied yet.
View :
http://xenbits.xensource.com/xen-3.4-testing.hg?rev/7a57911ff09e
________________________________
From: E. Mike Durbin <emike@sun.com>
To: xen-discuss@opensolaris.org
Sent: Tue, December 15, 2009 5:17:56 AM
Subject: [xen-discuss] Boot loader didn''t return any data!
Hi!
Got a fresh install of b129.
Did an install of Fedora12, worked great. Fedora goes through the entire
install,
finishes, and wants to reboot.
Can''t reboot, I get the following error:
# virsh start fedora
error: Failed to start domain fedora
error: POST operation failed: xend_post: error from xen daemon: (xend.err
"Boot loader didn''t return any data!")
I can look at the zvol (/dev/zvol/dsk/rpool/guests/fedora) and see that
grub did get installed.
# dd if=/dev/zvol/rdsk/rpool/guests/fedora of=/tmp/junk bs=1024k count=2
# od -c /tmp/junk > /tmp/junk.od-c
# more /tmp/junk.od-c
....
0000560 \0 276 223 } 350 * \0 353 376 G R U B \0 G
0000600 e o m \0 H a r d D i s k \0 R e
....
Here was my install script:
MEDIA=nfs:192.168.5.1:/storage/misc/Downloads/ISOs/Linux/Fedora12/Fedora-12-x86_64-DVD
NAME=fedora
POOL=rpool/guests
#zfs create -V 50G ${POOL}/${NAME}
virt-install \
--paravirt \
--nographics \
--noautoconsole \
--debug \
--os-type linux \
--os-variant fedora11 \
-n ${NAME} \
-f /dev/zvol/dsk/${POOL}/${NAME} \
-l ${MEDIA} \
--vcpus=1 \
-r 1024
(I tried with and without ''nographics'' and
''autoconsole'')
Any suggestions?
emike
_______________________________________________
xen-discuss mailing list
xen-discuss@opensolaris.org
I also presume , that you''ve changed a type of boot partition to
ext3fs.
Otherwise, CS 19740 won''t help either.
If i am wrong about ext4fs support for boot partitions PV DomUs by xVM 3.4.2,
please, advise.
________________________________
From: Boris Derzhavets <bderzhavets@yahoo.com>
To: E. Mike Durbin <emike@sun.com>; xen-discuss@opensolaris.org
Sent: Tue, December 15, 2009 9:10:32 AM
Subject: Re: [xen-discuss] Boot loader didn''t return any data!
CS 19740 from xen-3.4-testing.hg appears to be applied to current xVM’s tree :-
xen_changeset : Fri Dec 11 08:54:46 2009 +0300 19667:efeb205e29b8
Build on 11/30/09 was still affected. Date for 129 is 11/24/09 , hence CS 19740
was not applied yet..
View :
http://xenbits.xensource.com/xen-3.4-testing.hg?rev/7a57911ff09e
________________________________
From: E. Mike Durbin <emike@sun.com>
To: xen-discuss@opensolaris.org
Sent: Tue, December 15, 2009 5:17:56 AM
Subject: [xen-discuss] Boot loader didn''t return any data!
Hi!
Got a fresh install of b129.
Did an install of Fedora12, worked great. Fedora goes through the entire
install,
finishes, and wants to reboot.
Can''t reboot, I get the following error:
# virsh start fedora
error: Failed to start domain fedora
error: POST operation failed: xend_post: error from xen daemon: (xend.err
"Boot loader didn''t return any data!")
I can look at the zvol (/dev/zvol/dsk/rpool/guests/fedora) and see that
grub did get installed.
# dd if=/dev/zvol/rdsk/rpool/guests/fedora of=/tmp/junk bs=1024k count=2
# od -c /tmp/junk > /tmp/junk.od-c
# more /tmp/junk.od-c
....
0000560 \0 276 223 } 350 * \0 353 376 G R U B \0 G
0000600 e o m \0 H a r d D i s k \0 R e
....
Here was my install script:
MEDIA=nfs:192.168.5.1:/storage/misc/Downloads/ISOs/Linux/Fedora12/Fedora-12-x86_64-DVD
NAME=fedora
POOL=rpool/guests
#zfs create -V 50G ${POOL}/${NAME}
virt-install \
--paravirt \
--nographics \
--noautoconsole \
--debug \
--os-type linux \
--os-variant fedora11 \
-n ${NAME} \
-f /dev/zvol/dsk/${POOL}/${NAME} \
-l ${MEDIA} \
--vcpus=1 \
-r 1024
(I tried with and without ''nographics'' and
''autoconsole'')
Any suggestions?
emike
_______________________________________________
xen-discuss mailing list
xen-discuss@opensolaris.org
Boris Derzhavets wrote:> CS 19740 > <http://xenbits.xensource.com/xen-3.4-testing.hg?rev/7a57911ff09e> from > xen-3.4-testing.hg appears to be applied to current xVM’s tree :- > xen_changeset : Fri Dec 11 08:54:46 2009 +0300 19667:efeb205e29b8 > Build on 11/30/09 was still affected. Date for 129 is 11/24/09 , > hence CS 19740 > was not applied yet.. > View : > http://xenbits.xensource.com/xen-3..4-testing.hg?rev/7a57911ff09e > <http://xenbits.xensource.com/xen-3.4-testing.hg?rev/7a57911ff09e>We won't be integrating 19740... This grub timeout=0 bug is fixed in b130. 6895002 curses-timeout-workaround breaks Linux pygrub boot MRJ _______________________________________________ xen-discuss mailing list xen-discuss@opensolaris.org
Boris Derzhavets wrote:> I also presume , that you''ve changed a type of boot partition to ext3fs. > Otherwise, CS 19740 won''t help either. > If i am wrong about ext4fs support for boot partitions PV DomUs by xVM > 3.4.2, > please, advise.Correct pygrub does not have support for ext4. You need to install F12 with ext3. MRJ
Doh! That did the trick. Everything is working now. emike Mark Johnson wrote:> > > Boris Derzhavets wrote: >> I also presume , that you''ve changed a type of boot partition to ext3fs. >> Otherwise, CS 19740 won''t help either. >> If i am wrong about ext4fs support for boot partitions PV DomUs by >> xVM 3.4.2, >> please, advise. > > Correct pygrub does not have support for ext4. You need > to install F12 with ext3. > > > MRJ >
As far as to my knowledge only xen-3.4.1-5.fc12.src.rpm & xen-3.4.2-2.fc13.src.rpm allows to install Xen on top F12 , mostly with pvops kernel supporting Dom0, which provide ext4 support for pygrub in meantime. RH''s package e2fsprogs-devel (41) is required to build corresponding packages via source rpm. Some time ago same question was posted by one of core xVM developers to xen-devel mailing list, so Sun is aware of the issue. ________________________________ From: E. Mike Durbin <emike@sun.com> To: Mark Johnson <Mark.Johnson@sun.com> Cc: Boris Derzhavets <bderzhavets@yahoo.com>; xen-discuss@opensolaris.org Sent: Tue, December 15, 2009 4:56:40 PM Subject: Re: [xen-discuss] Boot loader didn''t return any data! Doh! That did the trick. Everything is working now. emike Mark Johnson wrote:> > > Boris Derzhavets wrote: >> I also presume , that you''ve changed a type of boot partition to ext3fs. >> Otherwise, CS 19740 won''t help either. >> If i am wrong about ext4fs support for boot partitions PV DomUs by >> xVM 3.4.2, >> please, advise. > > Correct pygrub does not have support for ext4. You need > to install F12 with ext3. > > > MRJ >
Boris Derzhavets wrote:> As far as to my knowledge only xen-3.4.1-5.fc12.src.rpm & > xen-3.4.2-2.fc13.src.rpm > allows to install Xen on top F12 , mostly with pvops kernel supporting > Dom0, which > provide ext4 support for pygrub in meantime. RH''s package > e2fsprogs-devel (41) is required to build corresponding packages via > source rpm. Some time ago same question was posted by one > of core xVM developers to xen-devel mailing list, so Sun is aware of the > issue.I have a patch for ext4 support for pygrub which I''m testing now.. MRJ> ------------------------------------------------------------------------ > *From:* E. Mike Durbin <emike@sun.com> > *To:* Mark Johnson <Mark.Johnson@sun.com> > *Cc:* Boris Derzhavets <bderzhavets@yahoo.com>; xen-discuss@opensolaris.org > *Sent:* Tue, December 15, 2009 4:56:40 PM > *Subject:* Re: [xen-discuss] Boot loader didn''t return any data! > > Doh! > That did the trick. Everything is working now. > > emike > > Mark Johnson wrote: > > > > > > Boris Derzhavets wrote: > >> I also presume , that you''ve changed a type of boot partition to ext3fs. > >> Otherwise, CS 19740 won''t help either. > >> If i am wrong about ext4fs support for boot partitions PV DomUs by > >> xVM 3.4.2, > >> please, advise. > > > > Correct pygrub does not have support for ext4. You need > > to install F12 with ext3. > > > > > > MRJ > > > >
Mark Johnson wrote:> > > Boris Derzhavets wrote: >> As far as to my knowledge only xen-3.4.1-5.fc12.src.rpm & >> xen-3.4.2-2.fc13.src.rpm >> allows to install Xen on top F12 , mostly with pvops kernel supporting >> Dom0, which >> provide ext4 support for pygrub in meantime. RH''s package >> e2fsprogs-devel (41) is required to build corresponding packages via >> source rpm. Some time ago same question was posted by one >> of core xVM developers to xen-devel mailing list, so Sun is aware of >> the issue. > > I have a patch for ext4 support for pygrub which I''m > testing now..pygrub ext4 support is integrated into b131. MRJ
I''ve processed mercurial queues not only for xen.hg , but for every *.hg where m-queue was not empty. I believe, that otherwise data might be inconsistent. Made a build and installed packages on another OSOL129 freshly installed instance. Virsh appears to be completely broken ( virsh list,.. as well) regardless build has been done on OSOL129. # xm console VF12 brought up vnc-console for f12 virt-install . Patch works fine. F12''s PV DomU installed and loaded with ext4 boot partition # xm start VF12 # vncviewer localhost:0 Thanks. Boris. ________________________________ Boris Derzhavets wrote:> Just committed via patch submitted to xen-devel:- > > wget http://dlc.sun.com/osol/on/downloads/b129/xvm-src.tar.bz2 > bzcat xvm-src.tar.bz2 | tar xf - > cd xen.hghg qpush -a hg qimport pygrub-ext4-support.patch hg qpush ../sunos.hg/bin/build-all MRJ> ------------------------------------------------------------------------ > *From:* Mark Johnson <Mark.Johnson@Sun.COM> > *To:* Boris Derzhavets <bderzhavets@yahoo.com> > *Cc:* E. Mike Durbin <emike@Sun.COM>; xen-discuss@opensolaris.org > *Sent:* Wed, December 16, 2009 9:22:48 PM > *Subject:* Re: [xen-discuss] Boot loader didn''t return any data! > > > > Mark Johnson wrote: > > > > > > Boris Derzhavets wrote: > >> As far as to my knowledge only xen-3.4.1-5.fc12.src.rpm & xen-3.4.2-2.fc13.src.rpm > >> allows to install Xen on top F12 , mostly with pvops kernel supporting Dom0, which > >> provide ext4 support for pygrub in meantime. RH''s package e2fsprogs-devel (41) is required to build corresponding packages via source rpm. Some time ago same question was posted by one > >> of core xVM developers to xen-devel mailing list, so Sun is aware of the issue. > > > > I have a patch for ext4 support for pygrub which I''m > > testing now.. > > pygrub ext4 support is integrated into b131. > > > > MRJ >
Fresh instance 129 bfu''ed to 130 with one issue :- root@opensolaris:~# svcs -x svc:/system/metainit:default (SVM initialization) State: disabled since December 18, 2009 4:18:50 PM MSK Reason: Disabled by an administrator. See: http://sun.com/msg/SMF-8000-05 See: metainit(1M) Impact: 1 dependent service is not running. (Use -v for list.) svc:/network/iscsi/initiator:default (iSCSI initiator daemon) State: maintenance since December 18, 2009 4:19:03 PM MSK Reason: Start method failed repeatedly, last exited with status 255. See: http://sun.com/msg/SMF-8000-KS See: iscsi(7D) See: /var/svc/log/network-iscsi-initiator:default.log Impact: This service is not running. Installed SunStudio12U1 via package manager and # pkg install SUNWgcc # pkg install SUNWmercurial # pkg install SUNWgmake # pkg install SUNWbcc # pkg install SUNWlibtool # pkg install SUNWgnome-common-devel # pkg install SUNWgnu-automake-110 # pkg install SUNWaconf # pkg install SUNWxwinc # pkg install SUNWgit # pkg install SUNWgnu-readline wget http://dlc.sun.com/osol/on/downloads/b130/xvm-src.tar.bz2 bzcat xvm-src.tar.bz2 | tar xf - Apply m-queue and ext4 patch ./sunos.hg/bin/build-all Build committed clean Virsh seems to be completely functional, however virt-install hangs attempting to connect 5900 Virsh console <DomainName> issued in different terminal session brings up vnc console, more over restarts DomU , allows to finish F12 PV DomU creation and create F12 PV DomU properly manageable via virsh and vncviewer. -- This message posted from opensolaris.org
Performed
# pkg install SUNWima SUNWimac SUNWiscsi SUNWiscsidm \
SUNWiscsit SUNWiscsitgt
#reboot -p
root@opensolaris:~# svcs -xv
svc:/system/metainit:default (SVM initialization)
State: disabled since December 18, 2009 6:58:17 PM MSK
Reason: Disabled by an administrator.
See: http://sun.com/msg/SMF-8000-05
See: man -M /usr/share/man -s 1M metainit
Impact: 1 dependent service is not running:
svc:/system/metasync:default
Unrelated to issue.
--
This message posted from opensolaris.org
************** First session :- ************** root@opensolaris:~# virt-install -n VF12S -r 1024 -p --vnc --os-type=linux --os-variant=fedora11 \> -f /dev/zvol/dsk/tank02/guest -l http://192.168.1.34/f12 --debugFri, 18 Dec 2009 19:03:35 DEBUG Using libvirt URI ''xen'' Fri, 18 Dec 2009 19:03:35 DEBUG Requesting virt method ''xen'' Fri, 18 Dec 2009 19:03:35 DEBUG Received virt method ''xen'' Fri, 18 Dec 2009 19:03:35 DEBUG Hypervisor name is ''xen'' Fri, 18 Dec 2009 19:03:35 DEBUG Setting size for existing storage to ''21.0'' Fri, 18 Dec 2009 19:03:35 DEBUG Detected storage as type ''block'' Fri, 18 Dec 2009 19:03:36 DEBUG Could not open "/etc/sysconfig/keyboard" [Errno 2] No such file or directory: ''/etc/sysconfig/keyboard'' Fri, 18 Dec 2009 19:03:36 DEBUG Could not open "/etc/X11/xorg.conf": [Errno 2] No such file or directory: ''/etc/X11/xorg.conf'' Fri, 18 Dec 2009 19:03:36 DEBUG Did not parse any usable keymapping. Fri, 18 Dec 2009 19:03:36 DEBUG DistroInstaller location is a network source. Starting install... Fri, 18 Dec 2009 19:03:36 DEBUG Attempting to detect distro: Fri, 18 Dec 2009 19:03:36 DEBUG Fetching URI: http://192.168.1.34/f12/.treeinfo Fri, 18 Dec 2009 19:03:36 DEBUG Saved file to /var/tmp/virtinst-.treeinfo.ZsYpGu Retrieving file .treeinfo 100% |=========================| 1.2 kB 00:00 Fri, 18 Dec 2009 19:03:36 DEBUG Fetching URI: http://192.168.1.34/f12/images/pxeboot/vmlinuz Fri, 18 Dec 2009 19:03:36 DEBUG Saved file to /var/tmp/virtinst-vmlinuz.gJVAkE Retrieving file vmlinuz.. 100% |=========================| 3.3 MB 00:00 Fri, 18 Dec 2009 19:03:36 DEBUG Fetching URI: http://192.168.1.34/f12/images/pxeboot/initrd.img Retrieving file initrd.im 87% |===================== | 20 MB 00:00 ETA Fri, 18 Dec 2009 19:03:37 DEBUG Saved file to /var/tmp/virtinst-initrd.img.K6J5gU Retrieving file initrd.im 100% |=========================| 22 MB 00:00 Fri, 18 Dec 2009 19:03:37 DEBUG Creating guest from: <domain type=''xen''> <name>VF12S</name> <currentMemory>1048576</currentMemory> <memory>1048576</memory> <uuid>31d31310-7f07-3e9d-a7cc-785d6a72b99f</uuid> <os> <type arch=''i686''>linux</type> <kernel>/var/tmp/virtinst-vmlinuz.gJVAkE</kernel> <initrd>/var/tmp/virtinst-initrd.img.K6J5gU</initrd> <cmdline>method=http://192.168.1.34/f12</cmdline> </os> <clock offset="utc"/> <on_poweroff>destroy</on_poweroff> <on_reboot>destroy</on_reboot> <on_crash>destroy</on_crash> <distro> <type>linux</type> <variant>fedora11</variant> </distro> <vcpu>1</vcpu> <devices> <disk type=''block'' device=''disk''> <source dev=''/dev/zvol/dsk/tank02/guest''/> <target dev=''xvda'' bus=''xen''/> </disk> <interface type=''bridge''> <source bridge=''''/> <mac address=''00:16:36:24:8a:0b''/> </interface> <input type=''mouse'' bus=''xen''/> <graphics type=''vnc'' port=''-1'' keymap=''en-us''/> </devices> </domain> Creating domain... 0 B 00:03 Fri, 18 Dec 2009 19:03:40 DEBUG Created guest, looking to see if it is running Fri, 18 Dec 2009 19:03:40 DEBUG Launching console callback Fri, 18 Dec 2009 19:03:40 DEBUG VNC Port: 5900; VNC host: localhost Fri, 18 Dec 2009 19:03:40 DEBUG Saving XML boot config: <domain type=''xen''> <name>VF12S</name> <currentMemory>1048576</currentMemory> <memory>1048576</memory> <uuid>31d31310-7f07-3e9d-a7cc-785d6a72b99f</uuid> <bootloader>/usr/lib/xen/bin/pygrub</bootloader> <clock offset="utc"/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <distro> <type>linux</type> <variant>fedora11</variant> </distro> <vcpu>1</vcpu> <devices> <disk type=''block'' device=''disk''> <source dev=''/dev/zvol/dsk/tank02/guest''/> <target dev=''xvda'' bus=''xen''/> </disk> <interface type=''bridge''> <source bridge=''''/> <mac address=''00:16:36:24:8a:0b''/> </interface> <input type=''mouse'' bus=''xen''/> <graphics type=''vnc'' port=''-1'' keymap=''en-us''/> </devices> </domain> TigerVNC Viewer for X version 1.0.0 Copyright (C) 2002-2005 RealVNC Ltd. Copyright (C) 2000-2006 TightVNC Group Copyright (C) 2004-2009 Peter Astrand for Cendio AB See http://www.tigervnc.org for information on TigerVNC. Fri Dec 18 19:03:41 2009 CConn: connected to host localhost port 5900 Fri Dec 18 19:08:06 2009 CConnection: Server supports RFB protocol version 3.8 CConnection: Using RFB protocol version 3.8 TXImage: Using default colormap and visual, TrueColor, depth 24. CConn: Using pixel format depth 24 (32bpp) little-endian rgb888 CConn: Using Tight encoding ****************** Second session :- ****************** root@opensolaris:~# virsh console VF12S Initializing cgroup subsys cpuset Initializing cgroup subsys cpu Linux version 2.6.31.5-127.fc12.x86_64 (mockbuild@x86-4.fedora.phx.redhat.com) (gcc version 4.4.2 20091027 (Red Hat 4.4.2-7) (GCC) ) #1 SMP Sat Nov 7 21:11:14 EST 2009 Command line: method=http://192.168.1.34/f12 KERNEL supported cpus: Intel GenuineIntel AMD AuthenticAMD Centaur CentaurHauls ACPI in unprivileged domain disabled BIOS-provided physical RAM map: Xen: 0000000000000000 - 00000000000a0000 (usable) Xen: 00000000000a0000 - 0000000000100000 (reserved) Xen: 0000000000100000 - 0000000040000000 (usable) DMI not present or invalid. last_pfn = 0x40000 max_arch_pfn = 0x400000000 init_memory_mapping: 0000000000000000-0000000040000000 RAMDISK: 019ce000 - 04498000 No NUMA configuration found Faking a node at 0000000000000000-0000000040000000 Bootmem setup node 0 0000000000000000-0000000040000000 NODE_DATA [0000000000008000 - 000000000001dfff] bootmap [000000000001e000 - 0000000000025fff] pages 8 (7 early reserv69b000] #6 [0000100000 - 00002d8000] PGTABLE ==> [0000100000 - 00002d8000] Zone PFN ranges: DMA 0x00000000 -> 0x00001000 DMA32 0x00001000 -> 0x00100000 Normal 0x00100000 -> 0x00100000 Movable zone start PFN for each node early_node_map[2] active PFN ranges 0: 0x00000000 -> 0x000000a0 0: 0x00000100 -> 0x00040000 SMP: Allowing 1 CPUs, 0 hotplug CPUs No local APIC present APIC: disable apic facility PM: Registered nosave memory: 00000000000a0000 - 000000000010000Freeing SMP alternatives: 33k freed ftrace: converting mcount calls to 0f 1f 44 00 00 ftrace: allocating 20852 entries in 82 pages Brought up 1 CPUs Booting paravirtualized kernel on Xen Xen version: 3.4.2-xvm-debug (preserve-AD) Grant table initialized regulator: core version 0.5 Time: 165:165:165 Date: 165/165/65 NET: Registered protocol family 16 PCI: Fatal: No config space access function found bio: create slab <bio-0> at 0 ACPI: Interpreter disabled. xen_balloon: Initialising balloon driver. vgaarb: loaded SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default pnp: PnP ACPI: disabled NET: Registered protocol family 2 IP route cache hash table entries: 32768 (order: 6, 262144 bytes) TCP established hash table entries: 131072 (order: 9, 2097152 bytes) TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP reno registered NET: Registered protocol family 1 Trying to unpack rootfs image as initramfs... Freeing initrd memory: 43816k freed platform rtc_cmos: registered platform RTC device (no PNP device found) audit: initializing netlink socket (disabled) type=2000 audit(1261152220.702:1): initialized HugeTLB registered 2 MB page size, pre-allocated 0 pages VFS: Disk quotas dquot_6.5.2 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) msgmni has been set to 2133 alg: No test for stdrng (krng) Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 pciehp: PCI Express Hot Plug Controller Driver version: 0.4 acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 Console: switching to colour frame buffer device 100x37 console [tty0] enabled Non-volatile memory driver v1.3 Linux agpgart interface v0.103 Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled brd: module loaded loop: module loaded input: Macintosh mouse button emulation as /devices/virtual/input/input0 Fixed MDIO Bus: probed ehci_hcd: USB 2.0 ''Enhanced'' Host Controller (EHCI) Driver ohci_hcd: USB 1.1 ''Open'' Host Controller (OHCI) VNC Console is up -- This message posted from opensolaris.org
Actually, "virsh console <DomName>" unlocks virt-install session. Terminal running the last command may be closed right after VNC-console comes up. -- This message posted from opensolaris.org
Virt-install behaves same on way fresh OSOL 130 installed as advised $ pfexec pkg install xvm-gui $ pfexec svcadm enable milestone/xvm $ pfexec reboot Virt-install works absolutely usual in environment :- Libvirt 0.7.1.-15 & Xen 3.4.2 on top of Fedora 12 with Dom0 supported by the recent pvops 2.6.31.6 or xenified kernel 2.6.31.8 kernel. So, OSOL is not the unique modern implementation Libvirt 0.7.0 -> Xen 3.4.2 Hypervisor Seems as virtinst&libvirt bug on OSOL 130 -- This message posted from opensolaris.org
I am not sure it does matter, but on F12 :- [root@fedora12sda]# virsh version Compiled against library: libvir 0.7.1 Using library: libvir 0.7.1 Using API: Xen 3.0.1 Running hypervisor: Xen 3.4.0 Version of libvirt for Xen 3.4 is different from OSOL''s one - 0.7.0 -- This message posted from opensolaris.org
> wget http://dlc.sun.com/osol/on/downloads/b130/xvm-src.tar.bz2 > bzcat xvm-src.tar.bz2 | tar xf - >Applied m-queue and ext4 patch only for xen.hgI''ve verified with "hg log" libvirt.hg,virtinst.hg,.... Mercurial queues have to be applied everywhere, where they are not empty. I''ve also cloned one more time via "hg" xvm-3.4 gate , processed all m-queues, made a build on OSOL130 and copied packages on USB pen. Created separate BE for xvm on fresh OSOL128a and installed packages into new BE , activating xVM without milestone/xvm. Several times i was able to pass via virt-install with VNC-console. Regarding xwin-issues with b130 i am not sure what kind of problem came up. It might be unrelated with libvirt.hg or virtinst.hg because Xen 3.4.2 VFB is affected as well. It''s easy to verify via "xm create new.cfg" with vfb = [ ''type=vnc,vncunused=1'']. -- This message posted from opensolaris.org
Same issue with b131. Virt-install hangs attempting "vncviewer localhost:0" during F12 and CentOS 5.4 PV installs. Same workaround:- virt-install ... --noautoconsole virsh console <DomName> & > log & sleep 3 vncviewer localhost:0 -- This message posted from opensolaris.org