xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Bei Guan <gbtju85@gmail.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Xen Devel <xen-devel@lists.xensource.com>
Subject: Re: Scrubbing free ram
Date: Thu, 6 May 2010 19:59:09 +0800	[thread overview]
Message-ID: <p2m48beb8b21005060459m58900d0p440d98737505012@mail.gmail.com> (raw)
In-Reply-To: <20100505141224.GB19206@phenom.dumpdata.com>


[-- Attachment #1.1: Type: text/plain, Size: 6186 bytes --]

2010/5/5 Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>

> 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=1024M loglvl=all guest_loglvl=all sync_console
> console_to_ring com1=115200,8n1 console=com1 lapic=debug
> apic_verbosity=debug apic=debug iommu=off
>
> vmlinuz-2.6.32.9 ro root=/dev/vg00/lv01 console=hvc0 earlyprintk=xen
> nomodeset initcall_debug debug loglevel=10
>
> >
> >
> >
> > 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 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 = No such file or directory)
> > Traceback (most recent call last):
> >   File "/usr/sbin/xend", line 36, in <module>
> >     from xen.xend.server import SrvDaemon
> >   File "usr/lib64/python2.6/site-packages/xen/xend/server/SrvDaemon.py",
> > line 26, in <module>
> >   File "usr/lib64/python2.6/site-packages/xen/xend/server/relocate.py",
> line
> > 28, in <module>
> >   File "usr/lib64/python2.6/site-packages/xen/xend/XendDomain.py", line
> 36,
> > in <module>
> >   File "usr/lib64/python2.6/site-packages/xen/xend/XendCheckpoint.py",
> line
> > 20, in <module>
> >   File "usr/lib64/python2.6/site-packages/xen/xend/image.py", line 46, in
> > <module>
> > xen.lowlevel.xc.Error: (1, 'Internal error', 'Could not obtain handle on
> > privileged command interface (2 = No such file or directory)')
> >
> > I googled the problem and found it seems to be a bug, which refered here:
> > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1436
> >
> >
> >
> > 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="/dev/<something, something>").
>
> It looks to be that you are trying to do '/dev/sda1' but since you
> changed your disk=['...'] 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
> > ……  ……
> > [    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=noautodetect
> > [  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=" 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]  [<ffffffff81591fd2>] panic+0x75/0x130
> > [  165.742674]  [<ffffffff8195fafe>] mount_block_root+0x1ce/0x1e5
> > [  165.742705]  [<ffffffff8195fb80>] mount_root+0x6b/0x8b
> > [  165.742734]  [<ffffffff8195fd10>] prepare_namespace+0x170/0x19d
> > [  165.742765]  [<ffffffff8195efc0>] kernel_init+0x1b5/0x1c5
> > [  165.742797]  [<ffffffff81033dea>] child_rip+0xa/0x20
> > [  165.742827]  [<ffffffff81032fa7>] ? int_ret_from_sys_call+0x7/0x1b
> > [  165.742858]  [<ffffffff8103375d>] ? retint_restore_args+0x5/0x6
> > [  165.742889]  [<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_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=m" 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'

[-- Attachment #1.2: Type: text/html, Size: 7585 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

  parent reply	other threads:[~2010-05-06 11:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-22 21:54 Scrubbing free ram ilish ilish
2010-04-23  6:14 ` Pasi Kärkkäinen
2010-04-23  6:54   ` [Xen-users] " ilish ilish
2010-04-23  8:11     ` Sander Eikelenboom
     [not found]   ` <SNT139-w80E57E03A776FE982F730BC070@phx.gbl>
     [not found]     ` <20100423080201.GP1878@reaktio.net>
2010-04-23 15:59       ` Re: [Xen-devel] " ilish ilish
     [not found]         ` <11010668714.20100423183749@eikelenboom.it>
     [not found]           ` <SNT139-w3258568B43600D4D327C1CBC070@phx.gbl>
2010-04-23 16:59             ` [Xen-users] " Sander Eikelenboom
     [not found]               ` <SNT139-w34D7E31DE40A797C6C87ACBC070@phx.gbl>
2010-04-23 17:23                 ` Sander Eikelenboom
2010-04-28 12:49   ` BEI GUAN
2010-04-28  4:55     ` Keir Fraser
2010-04-28 13:35       ` BEI GUAN
2010-04-28  5:38         ` Keir Fraser
2010-04-28  5:43           ` Keir Fraser
2010-04-28 15:44             ` BEI GUAN
2010-05-04 17:58               ` Konrad Rzeszutek Wilk
2010-05-05  7:00                 ` Bei Guan
2010-05-05 14:12                   ` Konrad Rzeszutek Wilk
2010-05-06  1:48                     ` Bei Guan
2010-05-06 11:59                     ` Bei Guan [this message]
2010-04-29  8:39             ` Bei Guan
2010-04-29 12:23               ` Keir Fraser
2010-04-29 14:48               ` Konrad Rzeszutek Wilk
2010-04-29 16:24                 ` Pasi Kärkkäinen
2010-05-03 17:38                   ` Konrad Rzeszutek Wilk
2010-04-28 21:53         ` Gerry Reno

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=p2m48beb8b21005060459m58900d0p440d98737505012@mail.gmail.com \
    --to=gbtju85@gmail.com \
    --cc=konrad.wilk@oracle.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).