From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bei Guan Subject: Re: Scrubbing free ram Date: Thu, 6 May 2010 19:59:09 +0800 Message-ID: References: <20100504175835.GA32012@phenom.dumpdata.com> <20100505141224.GB19206@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1816615906==" Return-path: In-Reply-To: <20100505141224.GB19206@phenom.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: Xen Devel List-Id: xen-devel@lists.xenproject.org --===============1816615906== Content-Type: multipart/alternative; boundary=e0cb4e8873f59ffd4b0485ebabd0 --e0cb4e8873f59ffd4b0485ebabd0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable 2010/5/5 Konrad Rzeszutek Wilk > On Wed, May 05, 2010 at 03:00:42PM +0800, Bei Guan wrote: > > Hi, Konrad, > > > > Thank you for your reply. > > > > I think it is hard to solve the problem of installing xen4.0 on > > fedora11_x86-32bit. Because everytime I install xen4.0 and reboot, my > screen > > stopped at the below messages and did not to print anything. > > > > (XEN) traps.c:2309:d0 Domain attempted WRMSR 000002ff from > 00000000:00000c06 > > > to 00000000:00000000. > > Right. And if you used the Linux and Xen kernel command line options to > enable more debug option that Pasi and I've pointed you to > you would have seen more. They are in > http://wiki.xensource.com/xenwiki/XenParavirtOps under the section > titled "Are there more debugging options I could enable to troubleshoot > booting problems?" where it gives you an example: > > xen-4.0.gz dom0_mem=3D1024M loglvl=3Dall guest_loglvl=3Dall sync_console > console_to_ring com1=3D115200,8n1 console=3Dcom1 lapic=3Ddebug > apic_verbosity=3Ddebug apic=3Ddebug iommu=3Doff > > vmlinuz-2.6.32.9 ro root=3D/dev/vg00/lv01 console=3Dhvc0 earlyprintk=3Dxe= n > nomodeset initcall_debug debug loglevel=3D10 > > > > > > > > > Now, I change my domain0 OS to fedora11_x86-64bit and I can successfull= y > > install the xen 4.0. However I have another problem. When I running the > > So you solved your problem by building the 64-bit Dom0. Is your > userspace 64-bit or is it 32-bit? When you say 'change my domain0' was > that a re-install of Fedora Core 11? > > > command "xend start", I got the error messages: > > > > [root@localhost ~]# xend start > > ERROR Internal error: Could not obtain handle on privileged command > > Run 'modprobe xenfs' and 'modprobe xen-evtchn' > > > interface (2 =3D No such file or directory) > > Traceback (most recent call last): > > File "/usr/sbin/xend", line 36, in > > from xen.xend.server import SrvDaemon > > File "usr/lib64/python2.6/site-packages/xen/xend/server/SrvDaemon.py"= , > > line 26, in > > File "usr/lib64/python2.6/site-packages/xen/xend/server/relocate.py", > line > > 28, in > > File "usr/lib64/python2.6/site-packages/xen/xend/XendDomain.py", line > 36, > > in > > File "usr/lib64/python2.6/site-packages/xen/xend/XendCheckpoint.py", > line > > 20, in > > File "usr/lib64/python2.6/site-packages/xen/xend/image.py", line 46, = in > > > > xen.lowlevel.xc.Error: (1, 'Internal error', 'Could not obtain handle o= n > > privileged command interface (2 =3D No such file or directory)') > > > > I googled the problem and found it seems to be a bug, which refered her= e: > > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=3D1436 > > > > > > > > If I running another command "/etc/init.d/xend start", it can > successfully > > start the xend service. But I can not create a PV DomU or HVM DomU. The > > error message as following. > > That one is fairly easy. You don't have the right 'root' entry for your > guest (you are missing the right root=3D"/dev/"). > > It looks to be that you are trying to do '/dev/sda1' but since you > changed your disk=3D['...'] entry to have 'xvda', it should be > '/dev/xvda1' > > > > > 1. Error of starting a PV DomU > > [root@localhost ubuntu-32]# xm create ubuntu.9-04.x86.xen3.cfg -c > > =85=85 =85=85 > > [ 1.831122] Sending DHCP requests ... > > [ 14.320061] ... timed out! > > [ 75.986391] IP-Config: Reopening network devices... > > [ 77.488086] Sending DHCP requests ... > > [ 93.965059] ... timed out! > > [ 165.740440] IP-Config: Auto-configuration of network failed. > > [ 165.740565] md: Waiting for all devices to be available before > autodetect > > [ 165.740587] md: If you don't use raid, use raid=3Dnoautodetect > > [ 165.741555] md: Autodetecting RAID arrays. > > [ 165.741577] md: Scanned 0 and added 0 devices. > > [ 165.741596] md: autorun ... > > [ 165.741614] md: ... autorun DONE. > > [ 165.741921] Root-NFS: No NFS server available, giving up. > > [ 165.741984] VFS: Unable to mount root fs via NFS, trying floppy. > > [ 165.742429] VFS: Cannot open root device "sda1" or unknown-block(2,0= ) > > [ 165.742452] Please append a correct "root=3D" boot option; here are = the > > available partitions: > > [ 165.742529] ca01 1025024 xvda1 driver: vbd > > ^^^^ - use that one instead of > sda1 > > > [ 165.742566] Kernel panic - not syncing: VFS: Unable to mount root fs > on > > unknown-block(2,0) > > [ 165.742590] Pid: 1, comm: swapper Not tainted 2.6.31.13 #1 > > [ 165.742610] Call Trace: > > [ 165.742642] [] panic+0x75/0x130 > > [ 165.742674] [] mount_block_root+0x1ce/0x1e5 > > [ 165.742705] [] mount_root+0x6b/0x8b > > [ 165.742734] [] prepare_namespace+0x170/0x19d > > [ 165.742765] [] kernel_init+0x1b5/0x1c5 > > [ 165.742797] [] child_rip+0xa/0x20 > > [ 165.742827] [] ? int_ret_from_sys_call+0x7/0x1b > > [ 165.742858] [] ? retint_restore_args+0x5/0x6 > > [ 165.742889] [] ? child_rip+0x0/0x20 > > > > (Attached is the complete messages) > > > > 2. Error of starting a HVM DomU > > [root@localhost windowsxp]# xm create winxp2_xen4.hvm > > Using config file "./winxp2_xen4.hvm". > > Error: Domain 'WinXP_HVMDomain' does not exist. > > > > ("WinXP_HVMDomain" is my HVM DomU name) > > No idea without cranking up some debug options. Look up > http://wiki.xensource.com/xenwiki/XenParavirtOps at the debug option. > I have solved the problem about creating a HVM DomU just by adding "CONFIG_TUN=3Dm" in the kernel config file and rebuild the linux kernel. The detail error about creating a hvm domU, which is in the file /var/log/xen/qemu-dm-WinXP_HVMDomain.log, is listed as below. [root@localhost xen]# cat qemu-dm-WinXP_HVMDomain.log domid: 2 warning: could not open /dev/net/tun: no virtual network emulation Could not initialize device 'tap' --e0cb4e8873f59ffd4b0485ebabd0 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable

2010/5/5 Konrad Rzeszutek Wilk <konrad.wilk@oracle.com&g= t;
On Wed, May 05, 2010 at 03:00:42PM +0800, Bei Guan wrote:=
> Hi, Konrad,
>
> Thank you for your reply.
>
&= gt; I think it is hard to solve the problem of installing xen4.0 on
>= fedora11_x86-32bit. Because everytime I install xen4.0 and reboot, my scre= en
> stopped at the below messages and did not to print anything.
>> (XEN) traps.c:2309:d0 Domain attempted WRMSR 000002ff from 00000000:= 00000c06
> > to 00000000:00000000.

Right. And if you = used the Linux and Xen kernel command line options to
enable more debug option that Pasi and I've pointed you to
you would= have seen more. They are in
http://wiki.xensource.com/xenwiki/XenPa= ravirtOps under the section
titled "Are there more debugging options I could enable to troubleshoo= t
booting problems?" where it gives you an example:

xen-4.0.= gz dom0_mem=3D1024M loglvl=3Dall guest_loglvl=3Dall sync_console console_to= _ring com1=3D115200,8n1 console=3Dcom1 lapic=3Ddebug apic_verbosity=3Ddebug= apic=3Ddebug iommu=3Doff

vmlinuz-2.6.32.9 ro root=3D/dev/vg00/lv01 console=3Dhvc0 earlyprintk=3D= xen nomodeset initcall_debug debug loglevel=3D10

>
>
>
> Now, I change my domain0= OS to fedora11_x86-64bit and I can successfully
> install the xen 4.= 0. However I have another problem. When I running the

So you s= olved your problem by building the 64-bit Dom0. Is your
userspace 64-bit or is it 32-bit? When you say 'change my domain0' = was
that a re-install of Fedora Core 11?

> command "xend start", I got the error = messages:
>
> [root@localhost ~]# xend start
> ERROR Inte= rnal error: Could not obtain handle on privileged command

Run = 'modprobe xenfs' and 'modprobe xen-evtchn'

> interface (2 =3D No such file or directory)
&= gt; Traceback (most recent call last):
> =A0 File "/usr/sbin/xen= d", line 36, in <module>
> =A0 =A0 from xen.xend.server im= port SrvDaemon
> =A0 File "usr/lib64/python2.6/site-packages/xen/xend/server/SrvDa= emon.py",
> line 26, in <module>
> =A0 File "us= r/lib64/python2.6/site-packages/xen/xend/server/relocate.py", line
> 28, in <module>
> =A0 File "usr/lib64/python2.6/site-= packages/xen/xend/XendDomain.py", line 36,
> in <module>> =A0 File "usr/lib64/python2.6/site-packages/xen/xend/XendCheckp= oint.py", line
> 20, in <module>
> =A0 File "usr/lib64/python2.6/site-= packages/xen/xend/image.py", line 46, in
> <module>
>= ; xen.lowlevel.xc.Error: (1, 'Internal error', 'Could not obtai= n handle on
> privileged command interface (2 =3D No such file or directory)')>
> I googled the problem and found it seems to be a bug, which = refered here:
> http://bugzilla.xensource.com/bugzil= la/show_bug.cgi?id=3D1436
>
>
>
> If I running another command "/etc/init.d= /xend start", it can successfully
> start the xend service. But = I can not create a PV DomU or HVM DomU. The
> error message as follow= ing.

That one is fairly easy. You don't have the right 'root&#= 39; entry for your
guest (you are missing the right root=3D"/dev/&l= t;something, something>").

It looks to be that you are tryin= g to do '/dev/sda1' but since you
changed your disk=3D['...'] entry to have 'xvda', it should= be
'/dev/xvda1'

>
> 1. Error of starting a PV DomU
> [= root@localhost ubuntu-32]# xm create ubuntu.9-04.x86.xen3.cfg -c
> = =85=85 =A0=85=85
> [ =A0 =A01.831122] Sending DHCP requests ...
&g= t; [ =A0 14.320061] ... timed out!
> [ =A0 75.986391] IP-Config: Reopening network devices...
> [ =A0= 77.488086] Sending DHCP requests ...
> [ =A0 93.965059] ... timed ou= t!
> [ =A0165.740440] IP-Config: Auto-configuration of network failed= .
> [ =A0165.740565] md: Waiting for all devices to be available before au= todetect
> [ =A0165.740587] md: If you don't use raid, use raid= =3Dnoautodetect
> [ =A0165.741555] md: Autodetecting RAID arrays.
= > [ =A0165.741577] md: Scanned 0 and added 0 devices.
> [ =A0165.741596] md: autorun ...
> [ =A0165.741614] md: ... auto= run DONE.
> [ =A0165.741921] Root-NFS: No NFS server available, givin= g up.
> [ =A0165.741984] VFS: Unable to mount root fs via NFS, trying= floppy.
> [ =A0165.742429] VFS: Cannot open root device "sda1" or unkn= own-block(2,0)
> [ =A0165.742452] Please append a correct "root= =3D" boot option; here are the
> available partitions:
> [= =A0165.742529] ca01 =A0 =A0 =A0 =A0 1025024 xvda1 driver: vbd

=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0^^^^ - use that one instead of
sda1

> [ =A0165.7425= 66] Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(2,0)
> [ =A0165.742590] Pid: 1, = comm: swapper Not tainted 2.6.31.13 #1
> [ =A0165.742610] Call Trace:=
> [ =A0165.742642] =A0[<ffffffff81591fd2>] panic+0x75/0x130> [ =A0165.742674] =A0[<ffffffff8195fafe>] mount_block_root+0x1ce= /0x1e5
> [ =A0165.742705] =A0[<ffffffff8195fb80>] mount_root+0x6b/0x8b> [ =A0165.742734] =A0[<ffffffff8195fd10>] prepare_namespace+0x17= 0/0x19d
> [ =A0165.742765] =A0[<ffffffff8195efc0>] kernel_init+= 0x1b5/0x1c5
> [ =A0165.742797] =A0[<ffffffff81033dea>] child_rip+0xa/0x20
&= gt; [ =A0165.742827] =A0[<ffffffff81032fa7>] ? int_ret_from_sys_call+= 0x7/0x1b
> [ =A0165.742858] =A0[<ffffffff8103375d>] ? retint_re= store_args+0x5/0x6
> [ =A0165.742889] =A0[<ffffffff81033de0>] ? child_rip+0x0/0x20>
> (Attached is the complete messages)
>
> 2. Error = of starting a HVM DomU
> [root@localhost windowsxp]# xm create winxp2= _xen4.hvm
> Using config file "./winxp2_xen4.hvm".
> Error: Domain= 'WinXP_HVMDomain' does not exist.
>
> ("WinXP_HVM= Domain" is my HVM DomU name)

No idea without cranking up = some debug options. Look up
http://wiki.xensource.com/xenwiki/XenParavirtOps at the debug optio= n.

=A0
I have solved the problem about creating a HVM DomU just by adding &qu= ot;CONFIG_TUN=3Dm" in the kernel config file and rebuild the linux ker= nel.
=A0
The detail error about creating a hvm domU, which is in the file /var/= log/xen/qemu-dm-WinXP_HVMDomain.log, is listed as below.
=A0
[root@localhost xen]# cat qemu-dm-WinXP_HVMDomain.log
domid: 2
w= arning: could not open /dev/net/tun: no virtual network emulation
Could = not initialize device 'tap'
=A0
=A0
=A0
--e0cb4e8873f59ffd4b0485ebabd0-- --===============1816615906== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============1816615906==--