[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel



Dear Boris,
 
Based on your given information, I have managed to configure static IP address inside OpenSolaris UNIX PV guest.
 
These are the two crucial lines:
 
echo 192.168.1.45 netmask 255.255.255.0 mtu 1492 > /etc/hostname.xnf0
echo 192.168.1.102 > /etc/defaultrouter
 
Please see screenshot here:
 
http://3.bp.blogspot.com/_zzjv8MCM2sk/Sm21uPKvVXI/AAAAAAAAAKU/NDQqKSld5v4/s1600-h/03.jpeg
 
May I know whether there are any PV device drivers for me to install to improve PV guests' performance? What are the recommended benchmark tools to measure I/O performance of PV guests?
 
Thank you!!!

 
Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering) BEng(Hons)(Mechanical Engineering)
Technical Support Engineer
Information Technology Department
Asiasoft Online Pte Ltd
Tampines Central 1 #04-01 Tampines Plaza
Singapore 529541
Republic of Singapore
Mobile Phone: +65-9648-9798
MSN: teoenming@xxxxxxxxxxx


-----Original Message-----
From: "Teo En Ming" <enming.teo@xxxxxxxxxxxxxxx>
To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Cc:
Date: Mon, 27 Jul 2009 21:46:37 +0800
Subject: Re: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel

Dear Boris,
 
I have to use static IP instead of dhcp because we are going to run servers.
 
I have managed to enable GNOME GUI and solved the DNS resolver issue based on the following guides:
 
http://blogs.sun.com/timthomas/entry/a_simple_vnc_server_and
 
http://defect.opensolaris.org/bz/show_bug.cgi?id=125
 
Please see my screenshots here:
 
http://teo-en-ming-aka-zhang-enming.blogspot.com/2009/07/creating-opensolaris-unix-200906-32-bit.html
 
I shall now work on hard coding static IP.
 
Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering) BEng(Hons)(Mechanical Engineering)
Technical Support Engineer
Information Technology Department
Asiasoft Online Pte Ltd
Tampines Central 1 #04-01 Tampines Plaza
Singapore 529541
Republic of Singapore
Mobile Phone: +65-9648-9798
MSN: teoenming@xxxxxxxxxxx


-----Original Message-----
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
To: enming.teo@xxxxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
Cc:
Date: Mon, 27 Jul 2009 06:15:29 -0700 (PDT)
Subject: Re: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel

1) I need to edit ~/.vnc/xstartup so that it will launch a GUI interface instead of a text console. During installation, I was able to copy .Xclients to xstartup but after installation, .Xclients do not exist anymore under my personal account. I have configured vncserver before in Linux and I was able to port the GNOME desktop to my remote vnc client.

****************************************************************************
1) It's easy to to grab content of .Xclients just simulating new install and
 save content of .Xclients via any editor. Done just now :-

20. Spanish                      
21. Swedish                      
To select desktop language, enter a number [default is 6]:
User selected: English
Configuring devices.
Mounting cdroms
Reading ZFS config: done.

opensolaris console login: jack
Password:
Sun Microsystems Inc.   SunOS 5.11      snv_111b        November 2008
jack@opensolaris:~$ cat .Xclients
#!/bin/ksh
#
# CDDL HEADER START
#
# For automatic login, we just invoke the default Gnome desktop
exec /usr/bin/dtstart jds

jack@opensolaris:~$ Jul 27 06:03:51 opensolaris in.routed[759]: route 0.0.0.0/8 --> 0.0.0.0 nexthop is not directly connected

jack@opensolaris:~$ pfexec ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000
xnf0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 index 2
        inet 192.168.1.39 netmask ffffff00 broadcast 192.168.1.255
        ether 0:16:3e:60:19:a
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1
        inet6 ::1/128
xnf0: flags=2004841<UP,RUNNING,MULTICAST,DHCP,IPv6> mtu 1500 index 2
        inet6 fe80::216:3eff:fe60:190a/10
        ether 0:16:3e:60:19:a

NO PROBLEMS WITH OBTAIN IP VIA DHCPDISCOVER,DHCPACK, ....,DHCPOFFER

****************************************************************************
2) VNC Setup at OSOL DomU as suggested by SUN

cat /etc/X11/gdm/custom.conf
# GDM Custom Configuration file.
# overrides: /usr/share/gdm/defaults.conf
[daemon]
RemoteGreeter=/usr/lib/gdmgreeter
[security]
DisallowTCP=false
# AllowRoot=true
# AllowRemoteRoot=true
[xdmcp]
Enable=true
[gui]
[greeter]
[chooser]
[debug]
[servers]

Services restart:-

svcadm disable xvnc-inetd gdm
svcadm enable xvnc-inetd gdm

***************************************************************

 
2) I could not hard code IP address (static definition, not dhcp) and network settings inside OpenSolaris like what I usually do in Linux. It seems that configuring /etc/hostname.xnf0 did not help. My VM's actual hostname is "opensolaris", so do I change that to /etc/opensolaris.xnf0? After OpenSolaris PV guest boots up, I had to manually configure the IP address, netmask and default route.

***************************************************************************
Switching OSOL DomU to static IP via SMF ( per Jurgen Keil same as per Sun :) )  :-

View http://www.opensolaris.org/jive/thread.jspa?threadID=104509&tstart=75

To switch OSOL DomU run with static IP at runtime:-

pfexec svcadm disable network/physical:nwam && \
pfexec svcadm enable  network/physical:default
pfexec ifconfig xnf0 down
pfexec ifconfig xnf0 192.168.1.45 netmask 255.255.255.0 mtu 1492
pfexec ifconfig xnf0 up
pfexec route add default 192.168.1.45

To make the settings permanent you also need:

echo 192.168.1.45 netmask 255.255.255.0 mtu 1492 > /etc/hostname.xnf0
rm /etc/dhcp.xnf0

echo 192.168.1.102 > /etc/defaultrouter
******************************************************************************

Boris.


--- On Mon, 7/27/09, Teo En Ming <enming.teo@xxxxxxxxxxxxxxx> wrote:

From: Teo En Ming <enming.teo@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel
To: "Teo En Ming" <enming.teo@xxxxxxxxxxxxxxx>, "Boris Derzhavets" <bderzhavets@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Date: Monday, July 27, 2009, 7:25 AM

Dear All,
 
I am now able to run OpenSolaris 2009.06 32-bit paravirtualized on Xen 3.4.1-rc8 Dom 0 Kernel 2.6.30-rc6 on OpenSUSE 11.1 32-bit.
 
However, there are still some outstanding configuration issues as I am not very familiar with Solaris UNIX. I am more of a Linux guy.
 
1) I need to edit ~/.vnc/xstartup so that it will launch a GUI interface instead of a text console. During installation, I was able to copy .Xclients to xstartup but after installation, .Xclients do not exist anymore under my personal account. I have configured vncserver before in Linux and I was able to port the GNOME desktop to my remote vnc client.
 
2) I could not hard code IP address (static definition, not dhcp) and network settings inside OpenSolaris like what I usually do in Linux. It seems that configuring /etc/hostname.xnf0 did not help. My VM's actual hostname is "opensolaris", so do I change that to /etc/opensolaris.xnf0? After OpenSolaris PV guest boots up, I had to manually configure the IP address, netmask and default route.
 
3) Configuring name servers in /etc/resolv.conf inside Solaris did not work. But I could still go out to the internet by pinging the IP addresses of Singapore's Starhub and Singnet ISP DNS servers. Just that name resolution didn't work on Solaris.
 
Please see the screenshots here:
 
http://teo-en-ming-aka-zhang-enming.blogspot.com/2009/07/creating-opensolaris-unix-200906-32-bit.html
 
More questions:
 
4) Are there any paravirtualized device drivers/tools I can install inside PV guests to enhance VM's performance? Like VMware tools?
 
5) Are there any benchmarking tools to measure I/O throughput of my PV guests?
 
Thank you very much.

Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering) BEng(Hons)(Mechanical Engineering)
Technical Support Engineer
Information Technology Department
Asiasoft Online Pte Ltd
Tampines Central 1 #04-01 Tampines Plaza
Singapore 529541
Republic of Singapore
Mobile Phone: +65-9648-9798
MSN: teoenming@xxxxxxxxxxx


-----Original Message-----
From: "Teo En Ming" <enming.teo@xxxxxxxxxxxxxxx>
To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Cc:
Date: Mon, 27 Jul 2009 18:22:17 +0800
Subject: Re: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel

Dear Boris,
 
I used the same ethernet network bridge in both installation and actually running of the pv guest. During installation, dhcpdiscover was sent out by the opensolaris pv guest. Dom 0 also sent out DHCPOFFER. However, opensolaris pv guest could not configure the virtual network interface using dhcp. So I had to manually configure the virtual network interface.
 
Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering) BEng(Hons)(Mechanical Engineering)
Technical Support Engineer
Information Technology Department
Asiasoft Online Pte Ltd
Tampines Central 1 #04-01 Tampines Plaza
Singapore 529541
Republic of Singapore
Mobile Phone: +65-9648-9798
MSN: teoenming@xxxxxxxxxxx


-----Original Message-----
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
To: xen-devel@xxxxxxxxxxxxxxxxxxx, enming.teo@xxxxxxxxxxxxxxx
Cc:
Date: Mon, 27 Jul 2009 03:15:24 -0700 (PDT)
Subject: Re: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel

OK. What happens if you put the same vif=['bridge=...'] in OSOL installation
profile. Are you unable to get IP for install in this case ?

Boris.

--- On Mon, 7/27/09, Teo En Ming <enming.teo@xxxxxxxxxxxxxxx> wrote:

From: Teo En Ming <enming.teo@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel
To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Date: Monday, July 27, 2009, 5:57 AM

 
 
Dear Boris,

My CentOS 4.7 32-bit PV guest is getting the dynamic IP address assignment from the dnsmasq dhcp server I have setup and configured on Xen Dom 0 OpenSUSE 11.1 32-bit host correctly.
 
So I think the issue is OpenSolaris specific.
 
Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering) BEng(Hons)(Mechanical Engineering)
Technical Support Engineer
Information Technology Department
Asiasoft Online Pte Ltd
Tampines Central 1 #04-01 Tampines Plaza
Singapore 529541
Republic of Singapore
Mobile Phone: +65-9648-9798
MSN: teoenming@xxxxxxxxxxx


-----Original Message-----
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
To: xen-devel@xxxxxxxxxxxxxxxxxxx, enming.teo@xxxxxxxxxxxxxxx
Date: Mon, 27 Jul 2009 01:57:43 -0700 (PDT)
Subject: Re: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel

Please, submit "brctl show"

Boris.

--- On Mon, 7/27/09, Teo En Ming <enming.teo@xxxxxxxxxxxxxxx> wrote:

From: Teo En Ming <enming.teo@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel
To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Date: Monday, July 27, 2009, 12:58 AM

Dear Boris,
 
I have changed my opensolaris vm configuration. Please see http://1.bp.blogspot.com/_zzjv8MCM2sk/Sm0yIVtghCI/AAAAAAAAAGE/ZGkYbBhhx5w/s1600-h/01.jpeg
 
http://1.bp.blogspot.com/_zzjv8MCM2sk/Sm0yIDWV0RI/AAAAAAAAAF8/aP9riPOEZyk/s1600-h/02.jpeg
 
http://2.bp.blogspot.com/_zzjv8MCM2sk/Sm0yHzY3WCI/AAAAAAAAAF0/gFxy7zJZXi8/s1600-h/03.jpeg
 
http://3.bp.blogspot.com/_zzjv8MCM2sk/Sm0yHm0RO8I/AAAAAAAAAFs/hIgei-yTbx4/s1600-h/04.jpeg
 
http://1.bp.blogspot.com/_zzjv8MCM2sk/Sm0yHcUoQ_I/AAAAAAAAAFk/9AiZKPqmG80/s1600-h/05.jpeg
 
http://4.bp.blogspot.com/_zzjv8MCM2sk/Sm0zdXRfyuI/AAAAAAAAAGM/ZqOaIbmTzB8/s1600-h/06.jpeg
 
I see my OpenSolaris guest sending DHCPDISCOVER and my OpenSUSE 11.1 32-bit Dom 0 Xen host sending DHCPOFFER but the OpenSolaris virtual machine is not setting the offered dynamic IP address to it's virtual NIC.
 

 
Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering) BEng(Hons)(Mechanical Engineering)
Technical Support Engineer
Information Technology Department
Asiasoft Online Pte Ltd
Tampines Central 1 #04-01 Tampines Plaza
Singapore 529541
Republic of Singapore
Mobile Phone: +65-9648-9798
MSN: teoenming@xxxxxxxxxxx


-----Original Message-----
From: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
To: <xen-devel@xxxxxxxxxxxxxxxxxxx>, <enming.teo@xxxxxxxxxxxxxxx>
Date: Mon, 27 Jul 2009 13:01:54 +0800
Subject: Re: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel


View:-

 http://www.opensolaris.org/jive/thread.jspa?threadID=104509&tstart=75

To switch OSOL DomU run with static IP:-

pfexec svcadm disable network/physical:nwam && \
pfexec svcadm enable  network/physical:default
pfexec ifconfig xnf0 down
pfexec ifconfig xnf0 192.168.1.102 netmask 255.255.255.0 mtu 1492
pfexec ifconfig xnf0 up
pfexec route add default 192.168.1.102

which i can/do @ installer time to use static IP assignements.  i just
can't seem to get them to 'stick' or 'be happy' after reboot and xen,
run-time launch.

Use the same commands with the installed system.

To make the settings permanent you also need (Jurgen Keil) :

echo 192.168.1.102 netmask 255.255.255.0 mtu 1492 > /etc/hostname.xnf0

rm /etc/dhcp.xnf0

echo 192.168.1.102 > /etc/defaultrouter


Boris.

--- On Sun, 7/26/09, Mr. Teo En Ming (Zhang Enming) < enming.teo@xxxxxxxxxxxxxxx > wrote:

From: Mr. Teo En Ming (Zhang Enming) < enming.teo@xxxxxxxxxxxxxxx >
Subject: Re: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel
To: bderzhavets@xxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
Date: Sunday, July 26, 2009, 5:08 AM
I am using static IP address.
--

Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering)
BEng(Hons)(Mechanical Engineering)

Technical Support Engineer

Information Technology Department

Asiasoft Online Pte Ltd

Tampines Central 1 #04-01
Tampines Plaza


 Singapore
 529541

 Republic of
 Singapore

Mobile Phone: +65-9648-9798

MSN: teoenming@xxxxxxxxxxx


Boris Derzhavets wrote:
Does your OpenSuse 11.1 32-bit has static IP address or it obtain it via DHCP ?
If second option is in place please submit
# brctl show

Boris.

--- On Sat, 7/25/09, Mr. Teo En Ming (Zhang Enming) <enming.teo@xxxxxxxxxxxxxxx> wrote:

From: Mr. Teo En Ming (Zhang Enming) <enming.teo@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel
To: enming.teo@xxxxxxxxxxxxxxx
Cc: "Sander Eikelenboom" <linux@xxxxxxxxxxxxxx>, bderzhavets@xxxxxxxxx , xen-devel@xxxxxxxxxxxxxxxxxxx, Pasi Kr@xxxxxxxxx
Date: Saturday, July 25, 2009, 10:50 PM
At the moment there is only one network card installed on my lab PC in my company running OpenSUSE 11.1 32-bit with Xen 3.4.1-rc8 Dom 0 kernel 2.6.30-rc6 (jeremy). So when there are more network cards installed, there will be eth0, eth1, eth2 ethernet bridges, etc.

Then I can assign the virtual network card in each virtual machine to a specific ethernet network bridge (out of many bridges) in Domain 0 using the vif command in guest domain configuration.


--

Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering)
BEng(Hons)(Mechanical Engineering)

Technical Support Engineer

Information Technology Department

Asiasoft Online Pte Ltd

Tampines Central 1 #04-01
Tampines Plaza


 Singapore
 529541

 Republic of
 Singapore

Mobile Phone: +65-9648-9798

MSN: teoenming@xxxxxxxxxxx 

Mr. Teo En Ming (Zhang Enming) wrote:
Dear Boris,

The ethernet network bridge on OpenSUSE 11.1 is eth0.


--

Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering)
BEng(Hons)(Mechanical Engineering)

Technical Support Engineer

Information Technology Department

Asiasoft Online Pte Ltd

Tampines Central 1 #04-01
Tampines Plaza


 Singapore
 529541

 Republic of
 Singapore

Mobile Phone: +65-9648-9798

MSN: teoenming@xxxxxxxxxxx 

Boris Derzhavets wrote:
This means that OSOL installer (by default ) will issue DHCPDISCOVER via your Xen bridge, looking for DHCP server on your LAN. Only on RHEL 5.3
(F10 with Xen 3.3.1 src.rpm been installed along with generated packages) with libvirtd & dnsmasq up and running you can specify
 vif=['bridge=virbr0' ] to detect DHCP Server at your Dom0.

View for instance :-
http://bderzhavets.wordpress.com/2009/05/07/backport-zfs-support-to-xen-331-f10-dom0-kernel-2630-rc3-tip/

I don't have any experience with OpenSuse 11.1 . I hardly remind they tried to reproduce RH's technology. Most probably they did it in SLES 11 (not sure). Check for libvirtd&dnsmasq daemons up and running.
But if your OpenSuse 11.1 Dom0 is on "dhcp" bridge itself , then no problems. Just vif=['bridge=eth0'].

Boris.

--- On Sat, 7/25/09, Mr. Teo En Ming (Zhang Enming) < enming.teo@xxxxxxxxxxxxxxx > wrote:

From: Mr. Teo En Ming (Zhang Enming) < enming.teo@xxxxxxxxxxxxxxx >
Subject: Re: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel
To: bderzhavets@xxxxxxxxx
Cc: "Sander Eikelenboom" <linux@xxxxxxxxxxxxxx>, Pasi Kr@xxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
Date: Saturday, July 25, 2009, 12:32 PM
Dear Boris,

This means I have to install a DHCP server or dnsmasq in my Dom 0, listening on my Dom 0's IP address, so that it can assign dynamic IP addresses to the DomU.

By the way, are there any paravirtualized device drivers that I can install in DomU to improve the performance of the virtual machine?

Thank you.
--

Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering)
BEng(Hons)(Mechanical Engineering)

Technical Support Engineer

Information Technology Department

Asiasoft Online Pte Ltd

Tampines Central 1 #04-01
Tampines Plaza


 Singapore
 529541

 Republic of
 Singapore

Mobile Phone: +65-9648-9798

MSN: teoenming@xxxxxxxxxxx 

Boris Derzhavets wrote:
>I noticed under the guest domain configuration there is a parameter called >'extra' kernel parameter. Does the 'nowin' argument stand for no >graphical windows?

Login as jack/jack to text console.

Wait until :-

$ pfexec ifconfig -a

will show up your IPv4 address

$ mkdir .vnc
$ cp .Xclients .vnc/xstartup
$ vncserver

Connect via vncviewer IP-DomU:1 from another terminal session to OSOL DomU. In case OSOL installer will fail to obtain IP via DHCPDISCOVER,
let me know. It might happen and requires Solaris Kernel Model Debugger
to disable checksum offloading at boot up. Seems to be hardware dependent issue for OSOL 2009.06

**********************************
Copy ramdisk and kernel to Dom0
**********************************

[root@ServerXen isos]# cat copy.sh
mount -o loop,ro osol-0906-x86.iso /mnt
cp /mnt/boot/amd64/x86.microroot /home/boris/solaris
cp /mnt/platform/i86xpv/kernel/amd64/unix /home/boris/solaris



***********************
Installation profile:-
***********************

[root@ServerXen solaris]# cat osol200906.install
name = "sol0906"
vcpus = 1
memory = "1024"
kernel = "/home/boris/solaris/unix"
ramdisk = "/home/boris/solaris/x86.microroot"
extra = "/platform/i86xpv/kernel/amd64/unix - nowin -B install_media=cdrom"
disk = ['phy:/dev/loop0,xvdc:cdrom,r','phy:/dev/sdb5,xvda,w']
# Would work as well
# disk = ['phy:/dev/loop0,6:cdrom,r','phy:/dev/sdb5,0,w']

vif = ['bridge=eth1']




Boris

--- On Sat, 7/25/09, Mr. Teo En Ming (Zhang Enming) < enming.teo@xxxxxxxxxxxxxxx > wrote:

From: Mr. Teo En Ming (Zhang Enming) < enming.teo@xxxxxxxxxxxxxxx >
Subject: Re: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel
To: enming.teo@xxxxxxxxxxxxxxx
Cc: "Sander Eikelenboom" <linux@xxxxxxxxxxxxxx>, "Boris Derzhavets" <bderzhavets@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, =?ISO-8859-1?Q?Pasi_K=E4r?=@xxxxxxxxx
Date: Saturday, July 25, 2009, 7:14 AM
Dear All,

I am trying to install OpenSolaris 2009.06 32-bit paravirtualized guest on OpenSUSE 11.1 32-bit paravirt-ops enabled Xen 3.4.1-rc8 Dom 0 Kernel 2.6.30-rc6.

However, I am getting an opensolaris console login prompt. There is no GNOME DE for me to launch the GUI installer for OpenSolaris. I am using the OpenSolaris LiveCD 32-bit.

I noticed under the guest domain configuration there is a parameter called 'extra' kernel parameter. Does the 'nowin' argument stand for no graphical windows?

http://4.bp.blogspot.com/_zzjv8MCM2sk/SmoT4kZta-I/AAAAAAAAAE0/xxUGuNunPoY/s1600-h/01.jpeg

http://4.bp.blogspot.com/_zzjv8MCM2sk/SmoT5YG2sNI/AAAAAAAAAFM/H0ntFt6LCx4/s1600-h/04.jpeg

http://2.bp.blogspot.com/_zzjv8MCM2sk/SmoT5uzjF6I/AAAAAAAAAFU/2Y3KNWPUwWk/s1600-h/05.jpeg

Then I also get the "invalid disk device number (768)" error. Do I need to use xvda instead of hda?

Thank you very much.

--

Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering)
BEng(Hons)(Mechanical Engineering)

Technical Support Engineer

Information Technology Department

Asiasoft Online Pte Ltd

Tampines Central 1 #04-01
Tampines Plaza


 Singapore
 529541

 Republic of
 Singapore

Mobile Phone: +65-9648-9798

MSN: teoenming@xxxxxxxxxxx 


Teo En Ming wrote:
As a matter of fact, our servers are either Dell PowerEdge 1950/2950 and IBM xSeries.
 
I am just testing it out on our lab PC first.
 
Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering) BEng(Hons)(Mechanical Engineering)
Technical Support Engineer
Information Technology Department
Asiasoft Online Pte Ltd
Tampines Central 1 #04-01 Tampines Plaza
Singapore 529541
Republic of Singapore
Mobile Phone
: +65-9648-9798
MSN: teoenming@xxxxxxxxxxx
 
-----Original Message-----
From: "Teo En Ming" < enming.teo@xxxxxxxxxxxxxxx >
To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>, "Pasi Kärkkäinen" <pasik@xxxxxx>
Cc: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Date: Sat, 25 Jul 2009 02:27:02 +0800
Subject: Re: Re[8]: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel
Dear Boris,
 
My next step will be a 64-bit Xen Dom 0 host.
 
Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering) BEng(Hons)(Mechanical Engineering)
Technical Support Engineer
Information Technology Department
Asiasoft Online Pte Ltd
Tampines Central 1 #04-01 Tampines Plaza
Singapore 529541
Republic of Singapore
Mobile Phone
: +65-9648-9798
MSN: teoenming@xxxxxxxxxxx
 
-----Original Message-----
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
To: Pasi Kärkkäinen <pasik@xxxxxx>, enming.teo@xxxxxxxxxxxxxxx
Cc: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Date: Fri, 24 Jul 2009 10:57:49 -0700 (PDT)
Subject: Re: Re[8]: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel
Teo, it is up to you how to manage, if you just having fun.
Otherwise, downloading 64-bit OpenSuse 11.1 ISO image
takes just 12-14 hr even at slow ADSL speed ( like 100 KB/sec).
Install takes 30 minutes and brings you to the trusted results, instead
of wasting a lot of time in case of business environment assignment.
Pasi has 32-bit experience due to hardware limitations, which you don't
have.

Boris.

--- On Fri, 7/24/09, Teo En Ming < enming.teo@xxxxxxxxxxxxxxx > wrote:

From: Teo En Ming < enming.teo@xxxxxxxxxxxxxxx >
Subject: Re: Re[8]: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel
To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>, "Pasi Kärkkäinen" <pasik@xxxxxx>
Cc: "Sander Eikelenboom" <linux@xxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Date: Friday, July 24, 2009, 12:56 PM
Dear Boris,
 
My colleague installed OpenSUSE 11.1 32-bit on the Core 2 Duo machine in our labs. Please see my earlier replies in the same topic.
 
I was too lazy to reformat and install 64-bit OpenSUSE, so I proceeded with Xen Dom 0 pvops kernel compilation on 32-bit Linux host.
 
I admit I am getting a lot of headache. Haha.
 
Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering) BEng(Hons)(Mechanical Engineering)
Technical Support Engineer
Information Technology Department
Asiasoft Online Pte Ltd
Tampines Central 1 #04-01 Tampines Plaza
Singapore 529541
Republic of Singapore
Mobile Phone
: +65-9648-9798
MSN: teoenming@xxxxxxxxxxx
 
-----Original Message-----
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
To: enming.teo@xxxxxxxxxxxxxxx , Pasi Kärkkäinen <pasik@xxxxxx>
Cc: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Date: Fri, 24 Jul 2009 09:57:18 -0700 (PDT)
Subject: Re: Re[8]: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel
Once again, i don't see any reason to to run 32-bit OS on Core2Duo,
unless you like Xen head ache. Core development (PVOPS) is obviously
running in 64-bit environment.

Boris.

--- On Fri, 7/24/09, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:

From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Subject: Re: Re[8]: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel
To: enming.teo@xxxxxxxxxxxxxxx , "Pasi Kärkkäinen" <pasik@xxxxxx>
Cc: "Sander Eikelenboom" <linux@xxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Date: Friday, July 24, 2009, 12:47 PM
>After doing the above, I re-installed back the Xen hypervisor, libraries and tools, and also >the kernel, initrd, and modules. Then I proceeded to reboot my machine. After rebooting, > my CentOS 4.7 32-bit PV guest is still able to start and run!

Why it wouldn't ? If your image stays  the same.
> I am still very puzzled! What causes the PV guest initially cannot start? Then what >subsequently causes the PV guest to suddenly be able to start and run???
 

That is not supposed to happen. I would suggest clean OS (without any built in xen presence) install , followed by  Xen 3.4.1+pvops kernel clean install.

Boris.

--- On Fri, 7/24/09, Teo En Ming < enming.teo@xxxxxxxxxxxxxxx > wrote:

From: Teo En Ming < enming.teo@xxxxxxxxxxxxxxx >
Subject: Re: Re[8]: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel
To: "Teo En Ming" < enming.teo@xxxxxxxxxxxxxxx >, "Pasi Kärkkäinen" <pasik@xxxxxx>
Cc: "Sander Eikelenboom" <linux@xxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Date: Friday, July 24, 2009, 12:19 PM
Dear All,
 
I am very puzzled. In investigating the cause of the sudden success of the CentOS 4.7 32-bit PV guest being able to run, I have uninstalled virt-manager and all of its dependencies:
 
docbook
python-gtk-vnc
xen-libs 3.3.1
scrollkeeper
xen-tools 3.3.1
libvirt 0.4.6
libvirt-python
vm-install 0.3.24
 
Then I proceeded to "make uninstall" in xen-3.4-testing source tree, which also removed my self compiled Xen Dom 0 pvops enabled kernel, initrd and kernel modules.
 
After doing the above, I re-installed back the Xen hypervisor, libraries and tools, and also the kernel, initrd, and modules. Then I proceeded to reboot my machine. After rebooting, my CentOS 4.7 32-bit PV guest is still able to start and run!
 
I am still very puzzled! What causes the PV guest initially cannot start? Then what subsequently causes the PV guest to suddenly be able to start and run???
 
***scratches head***
 
Anyway my CentOS 4.7 guest domain is now running. I shall now proceed to virtualize OpenSolaris 2009.06.
 
Thank you.
 
Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering) BEng(Hons)(Mechanical Engineering)
Technical Support Engineer
Information Technology Department
Asiasoft Online Pte Ltd
Tampines Central 1 #04-01 Tampines Plaza
Singapore 529541
Republic of Singapore
Mobile Phone
: +65-9648-9798
MSN: teoenming@xxxxxxxxxxx
 
-----Original Message-----
From: "Teo En Ming" < enming.teo@xxxxxxxxxxxxxxx >
To: "Teo En Ming" < enming.teo@xxxxxxxxxxxxxxx >, "Pasi Kärkkäinen" <pasik@xxxxxx>
Cc: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Date: Fri, 24 Jul 2009 22:54:26 +0800
Subject: Re: Re[8]: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel
Hi Pasi,
 
It's very strange. Suddenly my CentOS 4.7 32-bit PV guest is able to start!!! Previously it refuses to start at all.
 
I think I must have changed something in Dom 0 when I attempted "yast --install virt-manager". This action might have solved the problem. When I tried to install virt-manager, it also tries to install xen-libs-3.3.1 and xen-tools-3.3.1 as dependencies. However, I started off my Xen Dom 0 pvops kernel install with Xen 3.4.1 rc8 branch.
 
I need to investigate more why suddenly my CentOS 4.7 32-bit PV guest is able to start.
 
Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering) BEng(Hons)(Mechanical Engineering)
Technical Support Engineer
Information Technology Department
Asiasoft Online Pte Ltd
Tampines Central 1 #04-01 Tampines Plaza
Singapore 529541
Republic of Singapore
Mobile Phone
: +65-9648-9798
MSN: teoenming@xxxxxxxxxxx
 
-----Original Message-----
From: "Teo En Ming" < enming.teo@xxxxxxxxxxxxxxx >
To: "Pasi Kärkkäinen" <pasik@xxxxxx>
Cc: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Date: Fri, 24 Jul 2009 21:54:00 +0800
Subject: Re: Re[8]: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel
Hi Pasi,
 
I realized that Fedora 10 32-bit anaconda installer does not install PAE kernel after mounting the guest disk image file. I mounted the guest disk image file using losetup and kpartx which adds device nodes to /dev/mapper. I examined the /boot directory after mounting the guest disk image file and found no PAE vmlinuz and initrd.
 
Still using the mounted Fedora 10 32-bit guest disk image file, I changed root to the guest disk filesystems and attempted to install the PAE kernel. Then I modified menu.lst to boot the PAE kernel. After modifying the grub configuration of the guest domain, I un-mounted the guest filesystem.
 
I proceeded to boot the F10 32-bit guest, since I changed to PAE kernel. It is able to boot now (since the PAE kernel is xen-aware) but then it complains cannot mount /dev/root. Probably something to do with the PAE initrd file.

 
Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering) BEng(Hons)(Mechanical Engineering)
Technical Support Engineer
Information Technology Department
Asiasoft Online Pte Ltd
Tampines Central 1 #04-01 Tampines Plaza
Singapore 529541
Republic of Singapore
Mobile Phone
: +65-9648-9798
MSN: teoenming@xxxxxxxxxxx
 
-----Original Message-----
From: Pasi Kärkkäinen <pasik@xxxxxx>
To: Teo En Ming < enming.teo@xxxxxxxxxxxxxxx >
Cc: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Date: Fri, 24 Jul 2009 16:31:19 +0300
Subject: Re: Re[8]: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel
On Fri, Jul 24, 2009 at 08:37:09PM +0800, Teo En Ming wrote:
> Hi
>
> I attempted to install Fedora 10 32-bit PV guest using
> images/pxeboot/vmlinuz-PAE and images/pxeboot/initrd-PAE.img from the F10
> media. The non-PAE kernel could not load the installer. I finished my Fedora
> 10 32-bit PV guest installation but it also cannot boot up after
> installation, same as the CentOS 4.7 PV guest installation.
>

Fedora 10 installer has a bug, as a default it installs non-PAE kernel for
xen domU. You need to use a kickstart script (like this) to fix it:
http://pasik.reaktio.net/fedora/f10-xen-domu-ks.cfg

The important lines being:

-kernel
kernel-PAE

(Fedora 10 and Fedora 11 default kernels are compiled with pv_ops Xen domU
support enabled, so there's no need for separate kernel-xen with these distros).

Fedora 11 doesn't have that installer bug, so it installs right
out-of-the-box as Xen domU.

What's the error you get when you start the guest after installation?
Please paste the "xm log" as text.

I don't have any problems with CentOS 5.3 dom0.

-- Pasi

-----Inline Attachment Follows-----
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
 

-----Inline Attachment Follows-----
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
 

-----Inline Attachment Follows-----
_______________________________________________
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

  
 

-----Inline Attachment Follows-----

No virus found in this outgoing message.
Checked by AVG - www.avg.com
Version: 8.5.392 / Virus Database: 270.13.29/2260 - Release Date: 07/25/09 01:48:00

-----Inline Attachment Follows-----
_______________________________________________
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

  
 

-----Inline Attachment Follows-----

No virus found in this outgoing message.
Checked by AVG - www.avg.com
Version: 8.5.392 / Virus Database: 270.13.29/2260 - Release Date: 07/25/09 01:48:00

-----Inline Attachment Follows-----
_______________________________________________
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

  
 


 

    






No virus found in this outgoing message.

Checked by AVG - 




www.avg.com


Version: 8.5.392 / Virus Database: 270.13.30/2262 - Release Date: 07/25/09
18:01:00



  

    




_______________________________________________

Xen-devel mailing list

Xen-devel@xxxxxxxxxxxxxxxxxxx

    
http://lists.xensource.com/xen-devel

  
 

-----Inline Attachment Follows-----

No virus found in this outgoing message.
Checked by AVG - www.avg.com
Version: 8.5.392 / Virus Database: 270.13.30/2262 - Release Date: 07/25/09 18:01:00

-----Inline Attachment Follows-----
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
 
 

-----Inline Attachment Follows-----

No virus found in this outgoing message.
Checked by AVG - www.avg.com
Version: 8.5.392 / Virus Database: 270.13.30/2262 - Release Date: 07/25/09 18:01:00
 
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.339 / Virus Database: 270.13.24/2255 - Release Date: 07/22/09 18:00:00

-----Inline Attachment Follows-----

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



-----Inline Attachment Follows-----

_______________________________________________
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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.