thr3ads.net - Xen users - [Xen-devel] Scrubbing free ram [Apr 2010]

If this information is useful, please help other people find it:
Share via:

ilish ilish

2010-Apr-22 21:54 UTC

[Xen-devel] Scrubbing free ram

Hi everyone,

I am working on a project whose goal is evaluating
the performance of the vTPM Manager. For this project I am using Xen
4.1, Kernel 2.6.31.13 with Fedora11. I I finished all installation and
configuration parts. Now I need to boot the system with Xen but while
booting, it is freezing at the step "scrubbing free ram". What can be
cause this problem and how can I figure it out? I really appreciate if
you can help me.


Thanks for your time and help.
Best,
 		 	   		  
_________________________________________________________________
Hotmail: Microsoft tarafından sağlanan güvenlikle, güçlü ve Ücretsiz e-posta.
https://signup.live.com/signup.aspx?id=60969

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

Pasi Kärkkäinen

2010-Apr-23 06:14 UTC

head link

Re: [Xen-devel] Scrubbing free ram

On Thu, Apr 22, 2010 at 09:54:30PM +0000, ilish ilish
wrote:>    Hi everyone,
> 
>    I am working on a project whose goal is evaluating the performance of
the
>    vTPM Manager. For this project I am using Xen 4.1, Kernel 2.6.31.13 with
>    Fedora11. I I finished all installation and configuration parts. Now I
>    need to boot the system with Xen but while booting, it is freezing at
the
>    step "scrubbing free ram". What can be cause this problem and
how can I
>    figure it out? I really appreciate if you can help me.
> 
Please paste your grub.conf.

Also please check this wiki page:
http://wiki.xensource.com/xenwiki/XenSerialConsole

and:
http://wiki.xensource.com/xenwiki/XenParavirtOps

-- Pasi


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

ilish ilish

2010-Apr-23 06:54 UTC

head link

RE: [Xen-users] Re: [Xen-devel] Scrubbing free ram

Thank you very much for your concern about my issue. After sending email to
xen-devel, I switch to Debian 5 to install Xen, I do not have any problems but I
am still very curious about the problem. Since I installed Debian now, I just
have this part of my grub.conf entry of Fedora:
title pv_ops dom0-test (2.6.29) with serial console
    root         (hd0,2)
    kernel       /boot/xen-4.0.0-rc6.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
    module       /boot/vmlinuz-2.6.29-xen-r4 ro
root=UUID=e173017f-7b9a-4111-acf7-b9f0d02a8936 console=hvc0 earlyprintk=xen
nomodeset initcall_debug debug loglevel=10
    module       /boot/initrd-2.6.29-xen-r4.img

I also want to ask you something about Debian 5+Xen 4.0 . I booted with Xen in
my Debian installed machine. However there is a problem about the eth0. Xen 4.0
did not recognize my eth0. I do not know what to do about this. Do you have any
idea about this?
Thank you again very much for your time and help.
Ilhan> Date: Fri, 23 Apr 2010 09:14:12 +0300
> From: pasik@iki.fi
> To: ilishim@hotmail.com
> CC: xen-devel@lists.xensource.com; xen-users@lists.xensource.com
> Subject: [Xen-users] Re: [Xen-devel] Scrubbing free ram
> 
> On Thu, Apr 22, 2010 at 09:54:30PM +0000, ilish ilish wrote:
> >    Hi everyone,
> > 
> >    I am working on a project whose goal is evaluating the performance
of the
> >    vTPM Manager. For this project I am using Xen 4.1, Kernel 2.6.31.13
with
> >    Fedora11. I I finished all installation and configuration parts.
Now I
> >    need to boot the system with Xen but while booting, it is freezing
at the
> >    step "scrubbing free ram". What can be cause this problem
and how can I
> >    figure it out? I really appreciate if you can help me.
> > 
> 
> Please paste your grub.conf.
> 
> Also please check this wiki page:
> http://wiki.xensource.com/xenwiki/XenSerialConsole
> 
> and:
> http://wiki.xensource.com/xenwiki/XenParavirtOps
> 
> -- Pasi
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users 		 	   		  
Hotmail: Microsoft tarafından sağlanan güvenlikle, güçlü ve Ücretsiz e-posta.
Hemen edinin.
_________________________________________________________________
Hotmail: Güçlü İSTENMEYEN POSTA koruması ile güvenilir e-posta.
https://signup.live.com/signup.aspx?id=60969

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

Pasi Kärkkäinen

2010-Apr-23 07:03 UTC

head link

Re: [Xen-users] Re: [Xen-devel] Scrubbing free ram

On Fri, Apr 23, 2010 at 06:52:42AM +0000, ilish ilish
wrote:>    Hi Pasi,
>    Thank you very much for your concern about my issue. After sending email
>    to xen-devel, I switch to Debian 5 to install Xen, I do not have any
>    problems but I am still very curious about the problem. Since I
installed
>    Debian now, I just have this part of my grub.conf entry:
>    title pv_ops dom0-test (2.6.29) with serial console
>        root         (hd0,2)
>        kernel       /boot/xen-4.0.0-rc6.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
>        module       /boot/vmlinuz-2.6.29-xen-r4 ro
>    root=UUID=e173017f-7b9a-4111-acf7-b9f0d02a8936 console=hvc0
>    earlyprintk=xen nomodeset! initcall_debug debug loglevel=10
>        module       /boot/initrd-2.6.29-xen-r4.img
>    Could you please help me about my issue?

Please update to 4.0.0 final, or even 4.0.1-rc version.. 
many bugs fixed after 4.0.0-rc6.
>    I also want to ask you something about Debian 5+Xen 4.0 . I booted with
>    Xen in my Debian installed machine. However there is a problem about the
>    eth0. Xen 4.0 did not recognize my eth0. I do not know what to do about
>    this. Do you have any idea about this?
>    Thank you again very much for your time and help.
>
Xen doesn''t have drivers for hardware/nics. It''s the Linux
dom0 kernel that has the NIC driver.
Does "lspci -v" list the nic (when booted to Xen dom0)? 

Also please paste your dmesg.

Also is there a specific reason you''re using 2.6.29-xen-r4 (xenlinux)
kernel
instead of the pvops dom0 kernel? 

-- Pasi
>    Ilhan
>    > Date: Fri, 23 Apr 2010 09:14:12 +0300
>    > From: pasik@iki.fi
>    > To: ilishim@hotmail.com
>    > CC: xen-devel@lists.xensource.com; xen-users@lists.xensource.com
>    > Subject: [Xen-users] Re: [Xen-devel] Scrubbing free ram
>    >
>    > On Thu, Apr 22, 2010 at 09:54:30PM +0000, ilish ilish wrote:
>    > > Hi everyone,
>    > >
>    > > I am working on a project whose goal is evaluating the pe!
rformance
>    of the
>    > > vTPM Manager. For this project I am using Xen 4.1, Kernel
2.6.31.13
>    with
>    > > Fedora11. I I finished all installation and configuration
parts. Now I
>    > > need to boot the system with Xen but while booting, it is
freezing at
>    the
>    > > step "scrubbing free ram". What can be cause this
problem and how can
>    I
>    > > figure it out? I really appreciate if you can help me.
>    > >
>    >
>    > Please paste your grub.conf.
>    >
>    > Also please check this wiki page:
>    > http://wiki.xensource.com/xenwiki/XenSerialConsole
>    >
>    > and:
>    > http://wiki.xensource.com/xenwiki/XenParavirtOps
>    >
>    > -- Pasi
>    >
>    >

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

Pasi Kärkkäinen

2010-Apr-23 08:02 UTC

head link

Re: [Xen-users] Re: [Xen-devel] Scrubbing free ram

On Fri, Apr 23, 2010 at 07:28:49AM +0000, ilish ilish
wrote:>    Hi again,
>    Thank you very much. First there is no specific reason for
>    using 2.6.29-xen-r4. And I will try lspci -v, and send you the output of
>    that.
>    By the way I am new in this area and actually do not know pvops dom0
>    kernel is. Is this a specific kernel version?
pvops dom0 is the default dom0 kernel in Xen 4.0.0.

See these wiki pages:
	- http://wiki.xensource.com/xenwiki/Xen4.0
	- http://wiki.xensource.com/xenwiki/XenDom0Kernels
	- http://wiki.xensource.com/xenwiki/XenParavirtOps

-- Pasi
>    Ilhan
>    > Date: Fri, 23 Apr 2010 10:03:05 +0300
>    > From: pasik@iki.fi
>    > To: ilishim@hotmail.com
>    > CC: xen-users@lists.xensource.com
>    > Subject: Re: [Xen-users] Re: [Xen-devel] Scrubbing free ram
>    >
>    > On Fri, Apr 23, 2010 at 06:52:42AM +0000, ilish ilish wrote:
>    > > Hi Pasi,
>    > > Thank you very much for your concern about my issue. After
sending
>    email
>    > > to xen-devel, I switch to Debian 5 to install Xen, I do not
have any
>    > > problems but I am still very curious about the problem. Since
I
>    installed
>    > > Debian now, I just ha! ve this part of my grub.conf entry:
>    > > title pv_ops dom0-test (2.6.29) with serial console
>    > > root (hd0,2)
>    > > kernel /boot/xen-4.0.0-rc6.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
>    > > module /boot/vmlinuz-2.6.29-xen-r4 ro
>    > > root=UUID=e173017f-7b9a-4111-acf7-b9f0d02a8936 console=hvc0
>    > > earlyprintk=xen nomodeset! initcall_debug debug loglevel=10
>    > > module /boot/initrd-2.6.29-xen-r4.img
>    > > Could you please help me about my issue?
>    >
>    >
>    > Please update to 4.0.0 final, or even 4.0.1-rc version..
>    > many bugs fixed after 4.0.0-rc6.
>    >
>    > > I also want to ask you something about Debian 5+Xen 4.0 . I
booted
>    with
>    > > Xen in my Debian installe! d machine. However there is a
problem about
>    the
>    > > eth0. Xen 4.0 did not recognize my eth0. I do not know what to
do
>    about
>    > > this. Do you have any idea about this?
>    > > Thank you again very much for your time and help.
>    > >
>    >
>    > Xen doesn''t have drivers for hardware/nics. It''s
the Linux dom0 kernel
>    that has the NIC driver.
>    > Does "lspci -v" list the nic (when booted to Xen dom0)?
>    >
>    > Also please paste your dmesg.
>    >
>    > Also is there a specific reason you''re using 2.6.29-xen-r4
(xenlinux)
>    kernel
>    > instead of the pvops dom0 kernel?
>    >
>    > -- Pasi
>    >
>    > > Ilhan
>    > > > Date: Fri, 23 Apr 2010 09:14:12 +0300
>    > > > From: pasik@iki.fi
>    > > > To: ilishim@hotmail.com
>    > > > CC: xen-devel@lists.xensource.com;
xen-users@lists.xensource.com
>    > > > Subject: [Xen-users] Re: [Xen-devel] Scrubbing free ram
>    > > >
>    > > > On Thu, Apr 22, 2010 a! t 09:54:30PM +0000, ilish ilish
wrote:
>    > > > > Hi everyone,
>    > > > >
>    > > > > I am working on a project whose goal is evaluating
the pe!
>    rformance
>    > > of the
>    > > > > vTPM Manager. For this project I am using Xen 4.1,
Kernel
>    2.6.31.13
>    > > with
>    > > > > Fedora11. I I finished all installation and
configuration parts.
>    Now I
>    > > > > need to boot the system with Xen but while booting,
it is freezing
>    at
>    > > the
>    > > > > step "scrubbing free ram". What can be
cause this problem and how
>    can
>    > > I
>    > > > > figure it out? I really appreciate if you can help
me.
>    > > > >
>    > > >
>    > > > Please paste your grub.conf.
>    > > >
>    > > > Also please check this wiki page:
>    > > > http://wiki.xensource.com/xenwiki/XenSerialConsol! e
>    > > >
>    > > > and:
>    > > > http://wiki.xensource.com/xenwiki/XenParavirtOps
>    > > >
>    > > > -- Pasi
>    > > >
>    > > >
>    >
> 
>   
--------------------------------------------------------------------------
> 
>    Hotmail: Microsoft*un güçlü ÝSTENMEYEN POSTA korumasý ile güvenilir
>    e-posta. [1]Hemen kaydolun.
> 
> References
> 
>    Visible links
>    1. https://signup.live.com/signup.aspx?id=60969
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Sander Eikelenboom

2010-Apr-23 08:11 UTC

head link

Re: [Xen-users] Re: [Xen-devel] Scrubbing free ram

Hello ilish,

Did your network card work with the fedora install ? And if yes, what kernel
version that you use there ?
Could be it isn''t supported yet in the 2.6.29 kernel ?

What does lspci -vk show as your network card ?

--

Sander


Friday, April 23, 2010, 8:54:12 AM, you wrote:


> Thank you very much for your concern about my issue. After sending email to
xen-devel, I switch to Debian 5 to install Xen, I do not have any problems but I
am still very curious about the problem. Since I installed Debian now, I just
have this part of my grub.conf entry of Fedora:
> title pv_ops dom0-test (2.6.29) with serial console
>     root         (hd0,2)
>     kernel       /boot/xen-4.0.0-rc6.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
>     module       /boot/vmlinuz-2.6.29-xen-r4 ro
root=UUID=e173017f-7b9a-4111-acf7-b9f0d02a8936 console=hvc0 earlyprintk=xen
nomodeset initcall_debug debug loglevel=10
>     module       /boot/initrd-2.6.29-xen-r4.img
> I also want to ask you something about Debian 5+Xen 4.0 . I booted with Xen
in my Debian installed machine. However there is a problem about the eth0. Xen
4.0 did not recognize my eth0. I do not know what to do about this. Do you have
any idea about this?
> Thank you again very much for your time and help.
> Ilhan
>> Date: Fri, 23 Apr 2010 09:14:12 +0300
>> From: pasik@iki.fi
>> To: ilishim@hotmail.com
>> CC: xen-devel@lists.xensource.com; xen-users@lists.xensource.com
>> Subject: [Xen-users] Re: [Xen-devel] Scrubbing free ram
>> 
>> On Thu, Apr 22, 2010 at 09:54:30PM +0000, ilish ilish wrote:
>> >    Hi everyone,
>> > 
>> >    I am working on a project whose goal is evaluating the
performance of the
>> >    vTPM Manager. For this project I am using Xen 4.1, Kernel
2.6.31.13 with
>> >    Fedora11. I I finished all installation and configuration
parts. Now I
>> >    need to boot the system with Xen but while booting, it is
freezing at the
>> >    step "scrubbing free ram". What can be cause this
problem and how can I
>> >    figure it out? I really appreciate if you can help me.
>> > 
>> 
>> Please paste your grub.conf.
>> 
>> Also please check this wiki page:
>> http://wiki.xensource.com/xenwiki/XenSerialConsole
>> 
>> and:
>> http://wiki.xensource.com/xenwiki/XenParavirtOps
>> 
>> -- Pasi
>> 
>> 
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xensource.com
>> http://lists.xensource.com/xen-users
>                                           
> Hotmail: Microsoft tarafından sağlanan güvenlikle, güçlü ve Ücretsiz
e-posta. Hemen edinin.
> _________________________________________________________________
> Hotmail: Güçlü İSTENMEYEN POSTA koruması ile güvenilir e-posta.
> https://signup.live.com/signup.aspx?id=60969


-- 
Best regards,
 Sander                            mailto:linux@eikelenboom.it


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

ilish ilish

2010-Apr-23 15:59 UTC

head link

RE: [Xen-users] Re: [Xen-devel] Scrubbing free ram

Hi,

This is the output when I tried lspci -v command in the terminal on my Xen boot.

debian:/home/b649# lspci -v
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller
Hub (rev 07)
Subsystem: Sony Corporation Device 9033
Flags: bus master, fast devsel, latency 0
Capabilities: [e0] Vendor Specific Information <?>
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset
Integrated Graphics Controller (rev 07) (prog-if 00 [VGA controller])
Subsystem: Sony Corporation Device 9033
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at d0000000 (64-bit, non-prefetchable) [size=4M]
Memory at c0000000 (64-bit, prefetchable) [size=256M]
I/O ports at 9140 [size=8]
Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
Capabilities: [d0] Power Management version 3
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated
Graphics Controller (rev 07)
Subsystem: Sony Corporation Device 9033
Flags: bus master, fast devsel, latency 0
Memory at d0400000 (64-bit, non-prefetchable) [size=1M]
Capabilities: [d0] Power Management version 3
00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #4 (rev 03) (prog-if 00 [UHCI])
Subsystem: Sony Corporation Device 9033
Flags: bus master, medium devsel, latency 0, IRQ 17
I/O ports at 90e0 [size=32]
Capabilities: [50] PCIe advanced features <?>
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd
00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #5 (rev 03) (prog-if 00 [UHCI])
Subsystem: Sony Corporation Device 9033
Flags: bus master, medium devsel, latency 0, IRQ 21
I/O ports at 90c0 [size=32]
Capabilities: [50] PCIe advanced features <?>
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd
00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #6 (rev 03) (prog-if 00 [UHCI])
Subsystem: Sony Corporation Device 9033
Flags: bus master, medium devsel, latency 0, IRQ 19
I/O ports at 90a0 [size=32]
Capabilities: [50] PCIe advanced features <?>
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd
00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI
Controller #2 (rev 03) (prog-if 20 [EHCI])
Subsystem: Sony Corporation Device 9033
Flags: bus master, medium devsel, latency 0, IRQ 19
Memory at d5604c00 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Capabilities: [98] PCIe advanced features <?>
Kernel driver in use: ehci_hcd
Kernel modules: ehci-hcd
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller
(rev 03)
Subsystem: Sony Corporation Device 9033
Flags: bus master, fast devsel, latency 0, IRQ 22
Memory at d5600000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Virtual Channel <?>
Capabilities: [130] Root Complex Link <?>
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1
(rev 03) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 00008000-00008fff
Memory behind bridge: d4100000-d54fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
Capabilities: [90] Subsystem: Sony Corporation Device 9033
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel <?>
Capabilities: [180] Root Complex Link <?>
Kernel modules: shpchp
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2
(rev 03) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=03, sec-latency=0
I/O behind bridge: 00007000-00007fff
Memory behind bridge: d2d00000-d40fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
Capabilities: [90] Subsystem: Sony Corporation Device 9033
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel <?>
Capabilities: [180] Root Complex Link <?>
Kernel modules: shpchp
00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3
(rev 03) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
I/O behind bridge: 00006000-00006fff
Memory behind bridge: d1900000-d2cfffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
Capabilities: [90] Subsystem: Sony Corporation Device 9033
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel <?>
Capabilities: [180] Root Complex Link <?>
Kernel modules: shpchp
00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4
(rev 03) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=05, subordinate=05, sec-latency=0
I/O behind bridge: 00005000-00005fff
Memory behind bridge: d0500000-d18fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
Capabilities: [90] Subsystem: Sony Corporation Device 9033
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel <?>
Capabilities: [180] Root Complex Link <?>
Kernel modules: shpchp
00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #1 (rev 03) (prog-if 00 [UHCI])
Subsystem: Sony Corporation Device 9033
Flags: bus master, medium devsel, latency 0, IRQ 20
I/O ports at 9080 [size=32]
Capabilities: [50] PCIe advanced features <?>
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd
00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #2 (rev 03) (prog-if 00 [UHCI])
Subsystem: Sony Corporation Device 9033
Flags: bus master, medium devsel, latency 0, IRQ 19
I/O ports at 9060 [size=32]
Capabilities: [50] PCIe advanced features <?>
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #3 (rev 03) (prog-if 00 [UHCI])
Subsystem: Sony Corporation Device 9033
Flags: bus master, medium devsel, latency 0, IRQ 18
I/O ports at 9040 [size=32]
Capabilities: [50] PCIe advanced features <?>
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd
00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI
Controller #1 (rev 03) (prog-if 20 [EHCI])
Subsystem: Sony Corporation Device 9033
Flags: bus master, medium devsel, latency 0, IRQ 20
Memory at d5604800 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Capabilities: [98] PCIe advanced features <?>
Kernel driver in use: ehci_hcd
Kernel modules: ehci-hcd
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) (prog-if
01 [Subtractive decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=06, subordinate=06, sec-latency=32
Memory behind bridge: d5500000-d55fffff
Capabilities: [50] Subsystem: Sony Corporation Device 9033
00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03)
Subsystem: Sony Corporation Device 9033
Flags: bus master, medium devsel, latency 0
Capabilities: [e0] Vendor Specific Information <?>
Kernel modules: iTCO_wdt
00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev
03) (prog-if 01 [AHCI 1.0])
Subsystem: Sony Corporation Device 9033
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 1279
I/O ports at 9130 [size=8]
I/O ports at 9120 [size=4]
I/O ports at 9110 [size=8]
I/O ports at 9100 [size=4]
I/O ports at 9020 [size=32]
Memory at d5604000 (32-bit, non-prefetchable) [size=2K]
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/4 Enable+
Capabilities: [70] Power Management version 3
Capabilities: [a8] SATA HBA <?>
Capabilities: [b0] PCIe advanced features <?>
Kernel driver in use: ahci
Kernel modules: ahci
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
Subsystem: Sony Corporation Device 9033
Flags: medium devsel, IRQ 19
Memory at d5605000 (64-bit, non-prefetchable) [size=256]
I/O ports at 9000 [size=32]
Kernel driver in use: i801_smbus
Kernel modules: i2c-i801
01:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040 PCI-E Fast
Ethernet Controller (rev 12)
Subsystem: Sony Corporation Device 9033
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at d4100000 (64-bit, non-prefetchable) [size=16K]
I/O ports at 8000 [size=256]
Capabilities: [48] Power Management version 3
Capabilities: [5c] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Capabilities: [c0] Express Legacy Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting <?>
Capabilities: [130] Device Serial Number 00-1d-ba-ff-ff-26-a8-b9
04:00.0 Network controller: Intel Corporation Wireless WiFi Link 5100
Subsystem: Intel Corporation Device 1301
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at d1900000 (64-bit, non-prefetchable) [size=8K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Capabilities: [e0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting <?>
Capabilities: [140] Device Serial Number 36-b3-83-ff-ff-5d-21-00
06:03.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05)
(prog-if 10 [OHCI])
Subsystem: Sony Corporation Device 9033
Flags: bus master, medium devsel, latency 32, IRQ 17
Memory at d5500000 (32-bit, non-prefetchable) [size=2K]
Capabilities: [dc] Power Management version 2
Kernel driver in use: ohci1394
Kernel modules: ohci1394
06:03.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host
Adapter (rev 22)
Subsystem: Sony Corporation Device 9033
Flags: bus master, medium devsel, latency 32, IRQ 16
Memory at d5500900 (32-bit, non-prefetchable) [size=256]
Capabilities: [80] Power Management version 2
Kernel driver in use: sdhci
Kernel modules: sdhci
06:03.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter
(rev 12)
Subsystem: Sony Corporation Device 9033
Flags: bus master, medium devsel, latency 32, IRQ 4
Memory at d5500800 (32-bit, non-prefetchable) [size=256]
Capabilities: [80] Power Management version 2

 > Date: Fri, 23 Apr 2010 11:02:01 +0300
> From: pasik@iki.fi
> To: ilishim@hotmail.com
> CC: xen-users@lists.xensource.com
> Subject: Re: [Xen-users] Re: [Xen-devel] Scrubbing free ram
> 
> On Fri, Apr 23, 2010 at 07:28:49AM +0000, ilish ilish wrote:
> > Hi again,
> > Thank you very much. First there is no specific reason for
> > using 2.6.29-xen-r4. And I will try lspci -v, and send you the output
of
> > that.
> > By the way I am new in this area and actually do not know pvops dom0
> > kernel is. Is this a specific kernel version?
> 
> pvops dom0 is the default dom0 kernel in Xen 4.0.0.
> 
> See these wiki pages:
> - http://wiki.xensource.com/xenwiki/Xen4.0
> - http://wiki.xensource.com/xenwiki/XenDom0Kernels
> - http://wiki.xensource.com/xenwiki/XenParavirtOps
> 
> -- Pasi
> 
> > Ilhan
> > > Date: Fri, 23 Apr 2010 10:03:05 +0300
> > > From: pasik@iki.fi
> > > To: ilishim@hotmail.com
> > > CC: xen-users@lists.xensource.com
> > > Subject: Re: [Xen-users] Re: [Xen-devel] Scrubbing free ram
> > >
> > > On Fri, Apr 23, 2010 at 06:52:42AM +0000, ilish ilish wrote:
> > > > Hi Pasi,
> > > > Thank you very much for your concern about my issue. After
sending
> > email
> > > > to xen-devel, I switch to Debian 5 to install Xen, I do not
have any
> > > > problems but I am still very curious about the problem.
Since I
> > installed
> > > > Debian now, I just ha! ve this part of my grub.conf entry:
> > > > title pv_ops dom0-test (2.6.29) with serial console
> > > > root (hd0,2)
> > > > kernel /boot/xen-4.0.0-rc6.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
> > > > module /boot/vmlinuz-2.6.29-xen-r4 ro
> > > > root=UUID=e173017f-7b9a-4111-acf7-b9f0d02a8936 console=hvc0
> > > > earlyprintk=xen nomodeset! initcall_debug debug loglevel=10
> > > > module /boot/initrd-2.6.29-xen-r4.img
> > > > Could you please help me about my issue?
> > >
> > >
> > > Please update to 4.0.0 final, or even 4.0.1-rc version..
> > > many bugs fixed after 4.0.0-rc6.
> > >
> > > > I also want to ask you something about Debian 5+Xen 4.0 . I
booted
> > with
> > > > Xen in my Debian installe! d machine. However there is a
problem about
> > the
> > > > eth0. Xen 4.0 did not recognize my eth0. I do not know what
to do
> > about
> > > > this. Do you have any idea about this?
> > > > Thank you again very much for your time and help.
> > > >
> > >
> > > Xen doesn't have drivers for hardware/nics. It's the
Linux dom0 kernel
> > that has the NIC driver.
> > > Does "lspci -v" list the nic (when booted to Xen dom0)?
> > >
> > > Also please paste your dmesg.
> > >
> > > Also is there a specific reason you're using 2.6.29-xen-r4
(xenlinux)
> > kernel
> > > instead of the pvops dom0 kernel?
> > >
> > > -- Pasi
> > >
> > > > Ilhan
> > > > > Date: Fri, 23 Apr 2010 09:14:12 +0300
> > > > > From: pasik@iki.fi
> > > > > To: ilishim@hotmail.com
> > > > > CC: xen-devel@lists.xensource.com;
xen-users@lists.xensource.com
> > > > > Subject: [Xen-users] Re: [Xen-devel] Scrubbing free ram
> > > > >
> > > > > On Thu, Apr 22, 2010 a! t 09:54:30PM +0000, ilish ilish
wrote:
> > > > > > Hi everyone,
> > > > > >
> > > > > > I am working on a project whose goal is evaluating
the pe!
> > rformance
> > > > of the
> > > > > > vTPM Manager. For this project I am using Xen 4.1,
Kernel
> > 2.6.31.13
> > > > with
> > > > > > Fedora11. I I finished all installation and
configuration parts.
> > Now I
> > > > > > need to boot the system with Xen but while
booting, it is freezing
> > at
> > > > the
> > > > > > step "scrubbing free ram". What can be
cause this problem and how
> > can
> > > > I
> > > > > > figure it out? I really appreciate if you can help
me.
> > > > > >
> > > > >
> > > > > Please paste your grub.conf.
> > > > >
> > > > > Also please check this wiki page:
> > > > > http://wiki.xensource.com/xenwiki/XenSerialConsol! e
> > > > >
> > > > > and:
> > > > > http://wiki.xensource.com/xenwiki/XenParavirtOps
> > > > >
> > > > > -- Pasi
> > > > >
> > > > >
> > >
> > 
> >
--------------------------------------------------------------------------
> > 
> > Hotmail: Microsoft*un güçlü ÝSTENMEYEN POSTA korumasý ile güvenilir
> > e-posta. [1]Hemen kaydolun.
> > 
> > References
> > 
> > Visible links
> > 1. https://signup.live.com/signup.aspx?id=60969 		 	   		  
_________________________________________________________________
Hareket Halindeyken E-postanız ve Çok Daha Fazlası. Windows Live Hotmail'i
Ücretsiz Edinin.
https://signup.live.com/signup.aspx?id=60969

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

Sander Eikelenboom

2010-Apr-23 16:59 UTC

head link

Re: [Xen-users] Re: [Xen-devel] Scrubbing free ram

ok so it works fine with exactly the same kernel but booting without xen?
Verifying to see if its build in, could be done by looking for the appropiate
.config file for your kernel version in /boot/
And doing something like

cat .config-2.6.x | grep SKY2


> It works fine actually without booting Xen hypervisor. Actually I have
several sources those explain compiling Xen and kernel, since I am new in this
area I don''t exactly know if compiled this driver or not. I am
wondering if it is possible to check now whether I compiled this driver.
>  
> Thank you so much 
>  
> Ilhan 
>  
>> Date: Fri, 23 Apr 2010 18:37:49 +0200
>> From: linux@eikelenboom.it
>> To: ilishim@hotmail.com
>> Subject: Re: [Xen-users] Re: [Xen-devel] Scrubbing free ram
>> 
>> Hello ilish,
>> 
>> When I google on the Marvell 88E8040, there seem to be some problems
with the sky2 driver even with more recent linux kernels.
>> Does the network card work when you boot the kernel on bare metal (so
without the xen hypervisor) ?
>> If it doesnt it probably hasnt got to do with xen specifically ( are
you sure you have compiled this driver in (or as module)) ?
>> 
>> Another shot you have is trying one of the pvops kernels, see
http://wiki.xensource.com/xenwiki/XenParavirtOps how to get and compile one.
>> 
>> --
>> Sander
>> 
>> Friday, April 23, 2010, 5:59:47 PM, you wrote:
>> 
>> 
>> > Hi,
>> > 
>> > This is the output when I tried lspci -v command in the terminal
on my Xen boot.
>> > 
>> > 
>> > debian:/home/b649# lspci -v
>> > 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset
Memory Controller Hub (rev 07)
>> > Subsystem: Sony Corporation Device 9033
>> > Flags: bus master, fast devsel, latency 0
>> > Capabilities: [e0] Vendor Specific Information <?>
>> > 00:02.0 VGA compatible controller: Intel Corporation Mobile 4
Series Chipset Integrated Graphics Controller (rev 07) (prog-if 00 [VGA
controller])
>> > Subsystem: Sony Corporation Device 9033
>> > Flags: bus master, fast devsel, latency 0, IRQ 11
>> > Memory at d0000000 (64-bit, non-prefetchable) [size=4M]
>> > Memory at c0000000 (64-bit, prefetchable) [size=256M]
>> > I/O ports at 9140 [size=8]
>> > Capabilities: [90] Message Signalled Interrupts: Mask- 64bit-
Queue=0/0 Enable-
>> > Capabilities: [d0] Power Management version 3
>> > 00:02.1 Display controller: Intel Corporation Mobile 4 Series
Chipset Integrated Graphics Controller (rev 07)
>> > Subsystem: Sony Corporation Device 9033
>> > Flags: bus master, fast devsel, latency 0
>> > Memory at d0400000 (64-bit, non-prefetchable) [size=1M]
>> > Capabilities: [d0] Power Management version 3
>> > 00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB
UHCI Controller #4 (rev 03) (prog-if 00 [UHCI])
>> > Subsystem: Sony Corporation Device 9033
>> > Flags: bus master, medium devsel, latency 0, IRQ 17
>> > I/O ports at 90e0 [size=32]
>> > Capabilities: [50] PCIe advanced features <?>
>> > Kernel driver in use: uhci_hcd
>> > Kernel modules: uhci-hcd
>> > 00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB
UHCI Controller #5 (rev 03) (prog-if 00 [UHCI])
>> > Subsystem: Sony Corporation Device 9033
>> > Flags: bus master, medium devsel, latency 0, IRQ 21
>> > I/O ports at 90c0 [size=32]
>> > Capabilities: [50] PCIe advanced features <?>
>> > Kernel driver in use: uhci_hcd
>> > Kernel modules: uhci-hcd
>> > 00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB
UHCI Controller #6 (rev 03) (prog-if 00 [UHCI])
>> > Subsystem: Sony Corporation Device 9033
>> > Flags: bus master, medium devsel, latency 0, IRQ 19
>> > I/O ports at 90a0 [size=32]
>> > Capabilities: [50] PCIe advanced features <?>
>> > Kernel driver in use: uhci_hcd
>> > Kernel modules: uhci-hcd
>> > 00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family)
USB2 EHCI Controller #2 (rev 03) (prog-if 20 [EHCI])
>> > Subsystem: Sony Corporation Device 9033
>> > Flags: bus master, medium devsel, latency 0, IRQ 19
>> > Memory at d5604c00 (32-bit, non-prefetchable) [size=1K]
>> > Capabilities: [50] Power Management version 2
>> > Capabilities: [58] Debug port: BAR=1 offset=00a0
>> > Capabilities: [98] PCIe advanced features <?>
>> > Kernel driver in use: ehci_hcd
>> > Kernel modules: ehci-hcd
>> > 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD
Audio Controller (rev 03)
>> > Subsystem: Sony Corporation Device 9033
>> > Flags: bus master, fast devsel, latency 0, IRQ 22
>> > Memory at d5600000 (64-bit, non-prefetchable) [size=16K]
>> > Capabilities: [50] Power Management version 2
>> > Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+
Queue=0/0 Enable-
>> > Capabilities: [70] Express Root Complex Integrated Endpoint, MSI
00
>> > Capabilities: [100] Virtual Channel <?>
>> > Capabilities: [130] Root Complex Link <?>
>> > Kernel driver in use: HDA Intel
>> > Kernel modules: snd-hda-intel
>> > 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI
Express Port 1 (rev 03) (prog-if 00 [Normal decode])
>> > Flags: bus master, fast devsel, latency 0
>> > Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
>> > I/O behind bridge: 00008000-00008fff
>> > Memory behind bridge: d4100000-d54fffff
>> > Capabilities: [40] Express Root Port (Slot+), MSI 00
>> > Capabilities: [80] Message Signalled Interrupts: Mask- 64bit-
Queue=0/0 Enable-
>> > Capabilities: [90] Subsystem: Sony Corporation Device 9033
>> > Capabilities: [a0] Power Management version 2
>> > Capabilities: [100] Virtual Channel <?>
>> > Capabilities: [180] Root Complex Link <?>
>> > Kernel modules: shpchp
>> > 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI
Express Port 2 (rev 03) (prog-if 00 [Normal decode])
>> > Flags: bus master, fast devsel, latency 0
>> > Bus: primary=00, secondary=02, subordinate=03, sec-latency=0
>> > I/O behind bridge: 00007000-00007fff
>> > Memory behind bridge: d2d00000-d40fffff
>> > Capabilities: [40] Express Root Port (Slot+), MSI 00
>> > Capabilities: [80] Message Signalled Interrupts: Mask- 64bit-
Queue=0/0 Enable-
>> > Capabilities: [90] Subsystem: Sony Corporation Device 9033
>> > Capabilities: [a0] Power Management version 2
>> > Capabilities: [100] Virtual Channel <?>
>> > Capabilities: [180] Root Complex Link <?>
>> > Kernel modules: shpchp
>> > 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI
Express Port 3 (rev 03) (prog-if 00 [Normal decode])
>> > Flags: bus master, fast devsel, latency 0
>> > Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
>> > I/O behind bridge: 00006000-00006fff
>> > Memory behind bridge: d1900000-d2cfffff
>> > Capabilities: [40] Express Root Port (Slot+), MSI 00
>> > Capabilities: [80] Message Signalled Interrupts: Mask- 64bit-
Queue=0/0 Enable-
>> > Capabilities: [90] Subsystem: Sony Corporation Device 9033
>> > Capabilities: [a0] Power Management version 2
>> > Capabilities: [100] Virtual Channel <?>
>> > Capabilities: [180] Root Complex Link <?>
>> > Kernel modules: shpchp
>> > 00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI
Express Port 4 (rev 03) (prog-if 00 [Normal decode])
>> > Flags: bus master, fast devsel, latency 0
>> > Bus: primary=00, secondary=05, subordinate=05, sec-latency=0
>> > I/O behind bridge: 00005000-00005fff
>> > Memory behind bridge: d0500000-d18fffff
>> > Capabilities: [40] Express Root Port (Slot+), MSI 00
>> > Capabilities: [80] Message Signalled Interrupts: Mask- 64bit-
Queue=0/0 Enable-
>> > Capabilities: [90] Subsystem: Sony Corporation Device 9033
>> > Capabilities: [a0] Power Management version 2
>> > Capabilities: [100] Virtual Channel <?>
>> > Capabilities: [180] Root Complex Link <?>
>> > Kernel modules: shpchp
>> > 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB
UHCI Controller #1 (rev 03) (prog-if 00 [UHCI])
>> > Subsystem: Sony Corporation Device 9033
>> > Flags: bus master, medium devsel, latency 0, IRQ 20
>> > I/O ports at 9080 [size=32]
>> > Capabilities: [50] PCIe advanced features <?>
>> > Kernel driver in use: uhci_hcd
>> > Kernel modules: uhci-hcd
>> > 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB
UHCI Controller #2 (rev 03) (prog-if 00 [UHCI])
>> > Subsystem: Sony Corporation Device 9033
>> > Flags: bus master, medium devsel, latency 0, IRQ 19
>> > I/O ports at 9060 [size=32]
>> > Capabilities: [50] PCIe advanced features <?>
>> > Kernel driver in use: uhci_hcd
>> > Kernel modules: uhci-hcd
>> > 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB
UHCI Controller #3 (rev 03) (prog-if 00 [UHCI])
>> > Subsystem: Sony Corporation Device 9033
>> > Flags: bus master, medium devsel, latency 0, IRQ 18
>> > I/O ports at 9040 [size=32]
>> > Capabilities: [50] PCIe advanced features <?>
>> > Kernel driver in use: uhci_hcd
>> > Kernel modules: uhci-hcd
>> > 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family)
USB2 EHCI Controller #1 (rev 03) (prog-if 20 [EHCI])
>> > Subsystem: Sony Corporation Device 9033
>> > Flags: bus master, medium devsel, latency 0, IRQ 20
>> > Memory at d5604800 (32-bit, non-prefetchable) [size=1K]
>> > Capabilities: [50] Power Management version 2
>> > Capabilities: [58] Debug port: BAR=1 offset=00a0
>> > Capabilities: [98] PCIe advanced features <?>
>> > Kernel driver in use: ehci_hcd
>> > Kernel modules: ehci-hcd
>> > 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev
93) (prog-if 01 [Subtractive decode])
>> > Flags: bus master, fast devsel, latency 0
>> > Bus: primary=00, secondary=06, subordinate=06, sec-latency=32
>> > Memory behind bridge: d5500000-d55fffff
>> > Capabilities: [50] Subsystem: Sony Corporation Device 9033
>> > 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface
Controller (rev 03)
>> > Subsystem: Sony Corporation Device 9033
>> > Flags: bus master, medium devsel, latency 0
>> > Capabilities: [e0] Vendor Specific Information <?>
>> > Kernel modules: iTCO_wdt
>> > 00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI
Controller (rev 03) (prog-if 01 [AHCI 1.0])
>> > Subsystem: Sony Corporation Device 9033
>> > Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 1279
>> > I/O ports at 9130 [size=8]
>> > I/O ports at 9120 [size=4]
>> > I/O ports at 9110 [size=8]
>> > I/O ports at 9100 [size=4]
>> > I/O ports at 9020 [size=32]
>> > Memory at d5604000 (32-bit, non-prefetchable) [size=2K]
>> > Capabilities: [80] Message Signalled Interrupts: Mask- 64bit-
Queue=0/4 Enable+
>> > Capabilities: [70] Power Management version 3
>> > Capabilities: [a8] SATA HBA <?>
>> > Capabilities: [b0] PCIe advanced features <?>
>> > Kernel driver in use: ahci
>> > Kernel modules: ahci
>> > 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus
Controller (rev 03)
>> > Subsystem: Sony Corporation Device 9033
>> > Flags: medium devsel, IRQ 19
>> > Memory at d5605000 (64-bit, non-prefetchable) [size=256]
>> > I/O ports at 9000 [size=32]
>> > Kernel driver in use: i801_smbus
>> > Kernel modules: i2c-i801
>> > 01:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040
PCI-E Fast Ethernet Controller (rev 12)
>> > Subsystem: Sony Corporation Device 9033
>> > Flags: bus master, fast devsel, latency 0, IRQ 11
>> > Memory at d4100000 (64-bit, non-prefetchable) [size=16K]
>> > I/O ports at 8000 [size=256]
>> > Capabilities: [48] Power Management version 3
>> > Capabilities: [5c] Message Signalled Interrupts: Mask- 64bit+
Queue=0/0 Enable-
>> > Capabilities: [c0] Express Legacy Endpoint, MSI 00
>> > Capabilities: [100] Advanced Error Reporting <?>
>> > Capabilities: [130] Device Serial Number 00-1d-ba-ff-ff-26-a8-b9
>> > 04:00.0 Network controller: Intel Corporation Wireless WiFi Link
5100
>> > Subsystem: Intel Corporation Device 1301
>> > Flags: bus master, fast devsel, latency 0, IRQ 11
>> > Memory at d1900000 (64-bit, non-prefetchable) [size=8K]
>> > Capabilities: [c8] Power Management version 3
>> > Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+
Queue=0/0 Enable-
>> > Capabilities: [e0] Express Endpoint, MSI 00
>> > Capabilities: [100] Advanced Error Reporting <?>
>> > Capabilities: [140] Device Serial Number 36-b3-83-ff-ff-5d-21-00
>> > 06:03.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394
Controller (rev 05) (prog-if 10 [OHCI])
>> > Subsystem: Sony Corporation Device 9033
>> > Flags: bus master, medium devsel, latency 32, IRQ 17
>> > Memory at d5500000 (32-bit, non-prefetchable) [size=2K]
>> > Capabilities: [dc] Power Management version 2
>> > Kernel driver in use: ohci1394
>> > Kernel modules: ohci1394
>> > 06:03.1 SD Host controller: Ricoh Co Ltd R5C822
SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22)
>> > Subsystem: Sony Corporation Device 9033
>> > Flags: bus master, medium devsel, latency 32, IRQ 16
>> > Memory at d5500900 (32-bit, non-prefetchable) [size=256]
>> > Capabilities: [80] Power Management version 2
>> > Kernel driver in use: sdhci
>> > Kernel modules: sdhci
>> > 06:03.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus
Host Adapter (rev 12)
>> > Subsystem: Sony Corporation Device 9033
>> > Flags: bus master, medium devsel, latency 32, IRQ 4
>> > Memory at d5500800 (32-bit, non-prefetchable) [size=256]
>> > Capabilities: [80] Power Management version 2
>> > 
>> 
>> > 
>> >> Date: Fri, 23 Apr 2010 11:02:01 +0300
>> >> From: pasik@iki.fi
>> >> To: ilishim@hotmail.com
>> >> CC: xen-users@lists.xensource.com
>> >> Subject: Re: [Xen-users] Re: [Xen-devel] Scrubbing free ram
>> >> 
>> >> On Fri, Apr 23, 2010 at 07:28:49AM +0000, ilish ilish wrote:
>> >> > Hi again,
>> >> > Thank you very much. First there is no specific reason
for
>> >> > using 2.6.29-xen-r4. And I will try lspci -v, and send
you the output of
>> >> > that.
>> >> > By the way I am new in this area and actually do not know
pvops dom0
>> >> > kernel is. Is this a specific kernel version?
>> >> 
>> >> pvops dom0 is the default dom0 kernel in Xen 4.0.0.
>> >> 
>> >> See these wiki pages:
>> >> - http://wiki.xensource.com/xenwiki/Xen4.0
>> >> - http://wiki.xensource.com/xenwiki/XenDom0Kernels
>> >> - http://wiki.xensource.com/xenwiki/XenParavirtOps
>> >> 
>> >> -- Pasi
>> >> 
>> >> > Ilhan
>> >> > > Date: Fri, 23 Apr 2010 10:03:05 +0300
>> >> > > From: pasik@iki.fi
>> >> > > To: ilishim@hotmail.com
>> >> > > CC: xen-users@lists.xensource.com
>> >> > > Subject: Re: [Xen-users] Re: [Xen-devel] Scrubbing
free ram
>> >> > >
>> >> > > On Fri, Apr 23, 2010 at 06:52:42AM +0000, ilish
ilish wrote:
>> >> > > > Hi Pasi,
>> >> > > > Thank you very much for your concern about my
issue. After sending
>> >> > email
>> >> > > > to xen-devel, I switch to Debian 5 to install
Xen, I do not have any
>> >> > > > problems but I am still very curious about the
problem. Since I
>> >> > installed
>> >> > > > Debian now, I just ha! ve this part of my
grub.conf entry:
>> >> > > > title pv_ops dom0-test (2.6.29) with serial
console
>> >> > > > root (hd0,2)
>> >> > > > kernel /boot/xen-4.0.0-rc6.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
>> >> > > > module /boot/vmlinuz-2.6.29-xen-r4 ro
>> >> > > > root=UUID=e173017f-7b9a-4111-acf7-b9f0d02a8936
console=hvc0
>> >> > > > earlyprintk=xen nomodeset! initcall_debug debug
loglevel=10
>> >> > > > module /boot/initrd-2.6.29-xen-r4.img
>> >> > > > Could you please help me about my issue?
>> >> > >
>> >> > >
>> >> > > Please update to 4.0.0 final, or even 4.0.1-rc
version..
>> >> > > many bugs fixed after 4.0.0-rc6.
>> >> > >
>> >> > > > I also want to ask you something about Debian
5+Xen 4.0 . I booted
>> >> > with
>> >> > > > Xen in my Debian installe! d machine. However
there is a problem about
>> >> > the
>> >> > > > eth0. Xen 4.0 did not recognize my eth0. I do
not know what to do
>> >> > about
>> >> > > > this. Do you have any idea about this?
>> >> > > > Thank you again very much for your time and
help.
>> >> > > >
>> >> > >
>> >> > > Xen doesn''t have drivers for hardware/nics.
It''s the Linux dom0 kernel
>> >> > that has the NIC driver.
>> >> > > Does "lspci -v" list the nic (when booted
to Xen dom0)?
>> >> > >
>> >> > > Also please paste your dmesg.
>> >> > >
>> >> > > Also is there a specific reason you''re
using 2.6.29-xen-r4 (xenlinux)
>> >> > kernel
>> >> > > instead of the pvops dom0 kernel?
>> >> > >
>> >> > > -- Pasi
>> >> > >
>> >> > > > Ilhan
>> >> > > > > Date: Fri, 23 Apr 2010 09:14:12 +0300
>> >> > > > > From: pasik@iki.fi
>> >> > > > > To: ilishim@hotmail.com
>> >> > > > > CC: xen-devel@lists.xensource.com;
xen-users@lists.xensource.com
>> >> > > > > Subject: [Xen-users] Re: [Xen-devel]
Scrubbing free ram
>> >> > > > >
>> >> > > > > On Thu, Apr 22, 2010 a! t 09:54:30PM
+0000, ilish ilish wrote:
>> >> > > > > > Hi everyone,
>> >> > > > > >
>> >> > > > > > I am working on a project whose goal
is evaluating the pe!
>> >> > rformance
>> >> > > > of the
>> >> > > > > > vTPM Manager. For this project I am
using Xen 4.1, Kernel
>> >> > 2.6.31.13
>> >> > > > with
>> >> > > > > > Fedora11. I I finished all
installation and configuration parts.
>> >> > Now I
>> >> > > > > > need to boot the system with Xen but
while booting, it is freezing
>> >> > at
>> >> > > > the
>> >> > > > > > step "scrubbing free ram".
What can be cause this problem and how
>> >> > can
>> >> > > > I
>> >> > > > > > figure it out? I really appreciate if
you can help me.
>> >> > > > > >
>> >> > > > >
>> >> > > > > Please paste your grub.conf.
>> >> > > > >
>> >> > > > > Also please check this wiki page:
>> >> > > > >
http://wiki.xensource.com/xenwiki/XenSerialConsol! e
>> >> > > > >
>> >> > > > > and:
>> >> > > > >
http://wiki.xensource.com/xenwiki/XenParavirtOps
>> >> > > > >
>> >> > > > > -- Pasi
>> >> > > > >
>> >> > > > >
>> >> > >
>> >> > 
>> >> >
--------------------------------------------------------------------------
>> >> > 
>> >> > Hotmail: Microsoft*un güçlü ÝSTENMEYEN POSTA korumasý ile
güvenilir
>> >> > e-posta. [1]Hemen kaydolun.
>> >> > 
>> >> > References
>> >> > 
>> >> > Visible links
>> >> > 1. https://signup.live.com/signup.aspx?id=60969
>> > 
>> > _________________________________________________________________
>> > Hareket Halindeyken E-postanız ve Çok Daha Fazlası. Windows Live
Hotmail''i Ücretsiz Edinin.
>> > https://signup.live.com/signup.aspx?id=60969
>> 
>> 
>> 
>> -- 
>> Best regards,
>> Sander mailto:linux@eikelenboom.it
>> 
>                                           
> _________________________________________________________________
> Hotmail: Microsoft’un güçlü İSTENMEYEN POSTA koruması ile güvenilir
e-posta.
> https://signup.live.com/signup.aspx?id=60969


-- 
Best regards,
 Sander                            mailto:linux@eikelenboom.it


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

Sander Eikelenboom

2010-Apr-23 17:23 UTC

head link

Re: [Xen-users] Re: [Xen-devel] Scrubbing free ram

And if you boot the 2.6.18 kernel you use for xen, but without loading the xen
hypervisor, does the network card work then ?
Probably your 2.6.18 kernelsversion of sky2 doesnt support your newer marvell
yukon network card.

The xen-4.0.0-rc6 is that coming from a debian package ?

I still would recommend you compiling a pvops kernel with the sky2 drivers as
explained in steps on http://wiki.xensource.com/xenwiki/XenParavirtOps
These are recent kernels, and should provide the best hardware support for newer
hardware.

--
Sander

> Actually I with my Debian I am using 2.6.26 kernel verison, however for
Dom0 I am using 2.6.18 as my kenel. Can I use my actual Debian kernel, on which
the network card is working, fir my Dom0? If yes I do need to make some changes
on the config file, is that right?
>  
>> Date: Fri, 23 Apr 2010 18:59:35 +0200
>> From: linux@eikelenboom.it
>> To: ilishim@hotmail.com
>> CC: xen-devel@lists.xensource.com
>> Subject: Re: [Xen-users] Re: [Xen-devel] Scrubbing free ram
>> 
>> ok so it works fine with exactly the same kernel but booting without
xen?
>> Verifying to see if its build in, could be done by looking for the
appropiate .config file for your kernel version in /boot/
>> And doing something like
>> 
>> cat .config-2.6.x | grep SKY2
>> 
>> 
>> 
>> > It works fine actually without booting Xen hypervisor. Actually I
have several sources those explain compiling Xen and kernel, since I am new in
this area I don''t exactly know if compiled this driver or not. I am
wondering if it is possible to check now whether I compiled this driver.
>> 
>> > 
>> 
>> > Thank you so much 
>> 
>> > 
>> 
>> > Ilhan 
>> > 
>> >> Date: Fri, 23 Apr 2010 18:37:49 +0200
>> >> From: linux@eikelenboom.it
>> >> To: ilishim@hotmail.com
>> >> Subject: Re: [Xen-users] Re: [Xen-devel] Scrubbing free ram
>> >> 
>> >> Hello ilish,
>> >> 
>> >> When I google on the Marvell 88E8040, there seem to be some
problems with the sky2 driver even with more recent linux kernels.
>> >> Does the network card work when you boot the kernel on bare
metal (so without the xen hypervisor) ?
>> >> If it doesnt it probably hasnt got to do with xen specifically
( are you sure you have compiled this driver in (or as module)) ?
>> >> 
>> >> Another shot you have is trying one of the pvops kernels, see
http://wiki.xensource.com/xenwiki/XenParavirtOps how to get and compile one.
>> >> 
>> >> --
>> >> Sander
>> >> 
>> >> Friday, April 23, 2010, 5:59:47 PM, you wrote:
>> >> 
>> >> 
>> >> > Hi,
>> >> > 
>> >> > This is the output when I tried lspci -v command in the
terminal on my Xen boot.
>> >> > 
>> >> > 
>> >> > debian:/home/b649# lspci -v
>> >> > 00:00.0 Host bridge: Intel Corporation Mobile 4 Series
Chipset Memory Controller Hub (rev 07)
>> >> > Subsystem: Sony Corporation Device 9033
>> >> > Flags: bus master, fast devsel, latency 0
>> >> > Capabilities: [e0] Vendor Specific Information <?>
>> >> > 00:02.0 VGA compatible controller: Intel Corporation
Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) (prog-if 00 [VGA
controller])
>> >> > Subsystem: Sony Corporation Device 9033
>> >> > Flags: bus master, fast devsel, latency 0, IRQ 11
>> >> > Memory at d0000000 (64-bit, non-prefetchable) [size=4M]
>> >> > Memory at c0000000 (64-bit, prefetchable) [size=256M]
>> >> > I/O ports at 9140 [size=8]
>> >> > Capabilities: [90] Message Signalled Interrupts: Mask-
64bit- Queue=0/0 Enable-
>> >> > Capabilities: [d0] Power Management version 3
>> >> > 00:02.1 Display controller: Intel Corporation Mobile 4
Series Chipset Integrated Graphics Controller (rev 07)
>> >> > Subsystem: Sony Corporation Device 9033
>> >> > Flags: bus master, fast devsel, latency 0
>> >> > Memory at d0400000 (64-bit, non-prefetchable) [size=1M]
>> >> > Capabilities: [d0] Power Management version 3
>> >> > 00:1a.0 USB Controller: Intel Corporation 82801I (ICH9
Family) USB UHCI Controller #4 (rev 03) (prog-if 00 [UHCI])
>> >> > Subsystem: Sony Corporation Device 9033
>> >> > Flags: bus master, medium devsel, latency 0, IRQ 17
>> >> > I/O ports at 90e0 [size=32]
>> >> > Capabilities: [50] PCIe advanced features <?>
>> >> > Kernel driver in use: uhci_hcd
>> >> > Kernel modules: uhci-hcd
>> >> > 00:1a.1 USB Controller: Intel Corporation 82801I (ICH9
Family) USB UHCI Controller #5 (rev 03) (prog-if 00 [UHCI])
>> >> > Subsystem: Sony Corporation Device 9033
>> >> > Flags: bus master, medium devsel, latency 0, IRQ 21
>> >> > I/O ports at 90c0 [size=32]
>> >> > Capabilities: [50] PCIe advanced features <?>
>> >> > Kernel driver in use: uhci_hcd
>> >> > Kernel modules: uhci-hcd
>> >> > 00:1a.2 USB Controller: Intel Corporation 82801I (ICH9
Family) USB UHCI Controller #6 (rev 03) (prog-if 00 [UHCI])
>> >> > Subsystem: Sony Corporation Device 9033
>> >> > Flags: bus master, medium devsel, latency 0, IRQ 19
>> >> > I/O ports at 90a0 [size=32]
>> >> > Capabilities: [50] PCIe advanced features <?>
>> >> > Kernel driver in use: uhci_hcd
>> >> > Kernel modules: uhci-hcd
>> >> > 00:1a.7 USB Controller: Intel Corporation 82801I (ICH9
Family) USB2 EHCI Controller #2 (rev 03) (prog-if 20 [EHCI])
>> >> > Subsystem: Sony Corporation Device 9033
>> >> > Flags: bus master, medium devsel, latency 0, IRQ 19
>> >> > Memory at d5604c00 (32-bit, non-prefetchable) [size=1K]
>> >> > Capabilities: [50] Power Management version 2
>> >> > Capabilities: [58] Debug port: BAR=1 offset=00a0
>> >> > Capabilities: [98] PCIe advanced features <?>
>> >> > Kernel driver in use: ehci_hcd
>> >> > Kernel modules: ehci-hcd
>> >> > 00:1b.0 Audio device: Intel Corporation 82801I (ICH9
Family) HD Audio Controller (rev 03)
>> >> > Subsystem: Sony Corporation Device 9033
>> >> > Flags: bus master, fast devsel, latency 0, IRQ 22
>> >> > Memory at d5600000 (64-bit, non-prefetchable) [size=16K]
>> >> > Capabilities: [50] Power Management version 2
>> >> > Capabilities: [60] Message Signalled Interrupts: Mask-
64bit+ Queue=0/0 Enable-
>> >> > Capabilities: [70] Express Root Complex Integrated
Endpoint, MSI 00
>> >> > Capabilities: [100] Virtual Channel <?>
>> >> > Capabilities: [130] Root Complex Link <?>
>> >> > Kernel driver in use: HDA Intel
>> >> > Kernel modules: snd-hda-intel
>> >> > 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9
Family) PCI Express Port 1 (rev 03) (prog-if 00 [Normal decode])
>> >> > Flags: bus master, fast devsel, latency 0
>> >> > Bus: primary=00, secondary=01, subordinate=01,
sec-latency=0
>> >> > I/O behind bridge: 00008000-00008fff
>> >> > Memory behind bridge: d4100000-d54fffff
>> >> > Capabilities: [40] Express Root Port (Slot+), MSI 00
>> >> > Capabilities: [80] Message Signalled Interrupts: Mask-
64bit- Queue=0/0 Enable-
>> >> > Capabilities: [90] Subsystem: Sony Corporation Device
9033
>> >> > Capabilities: [a0] Power Management version 2
>> >> > Capabilities: [100] Virtual Channel <?>
>> >> > Capabilities: [180] Root Complex Link <?>
>> >> > Kernel modules: shpchp
>> >> > 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9
Family) PCI Express Port 2 (rev 03) (prog-if 00 [Normal decode])
>> >> > Flags: bus master, fast devsel, latency 0
>> >> > Bus: primary=00, secondary=02, subordinate=03,
sec-latency=0
>> >> > I/O behind bridge: 00007000-00007fff
>> >> > Memory behind bridge: d2d00000-d40fffff
>> >> > Capabilities: [40] Express Root Port (Slot+), MSI 00
>> >> > Capabilities: [80] Message Signalled Interrupts: Mask-
64bit- Queue=0/0 Enable-
>> >> > Capabilities: [90] Subsystem: Sony Corporation Device
9033
>> >> > Capabilities: [a0] Power Management version 2
>> >> > Capabilities: [100] Virtual Channel <?>
>> >> > Capabilities: [180] Root Complex Link <?>
>> >> > Kernel modules: shpchp
>> >> > 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9
Family) PCI Express Port 3 (rev 03) (prog-if 00 [Normal decode])
>> >> > Flags: bus master, fast devsel, latency 0
>> >> > Bus: primary=00, secondary=04, subordinate=04,
sec-latency=0
>> >> > I/O behind bridge: 00006000-00006fff
>> >> > Memory behind bridge: d1900000-d2cfffff
>> >> > Capabilities: [40] Express Root Port (Slot+), MSI 00
>> >> > Capabilities: [80] Message Signalled Interrupts: Mask-
64bit- Queue=0/0 Enable-
>> >> > Capabilities: [90] Subsystem: Sony Corporation Device
9033
>> >> > Capabilities: [a0] Power Management version 2
>> >> > Capabilities: [100] Virtual Channel <?>
>> >> > Capabilities: [180] Root Complex Link <?>
>> >> > Kernel modules: shpchp
>> >> > 00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9
Family) PCI Express Port 4 (rev 03) (prog-if 00 [Normal decode])
>> >> > Flags: bus master, fast devsel, latency 0
>> >> > Bus: primary=00, secondary=05, subordinate=05,
sec-latency=0
>> >> > I/O behind bridge: 00005000-00005fff
>> >> > Memory behind bridge: d0500000-d18fffff
>> >> > Capabilities: [40] Express Root Port (Slot+), MSI 00
>> >> > Capabilities: [80] Message Signalled Interrupts: Mask-
64bit- Queue=0/0 Enable-
>> >> > Capabilities: [90] Subsystem: Sony Corporation Device
9033
>> >> > Capabilities: [a0] Power Management version 2
>> >> > Capabilities: [100] Virtual Channel <?>
>> >> > Capabilities: [180] Root Complex Link <?>
>> >> > Kernel modules: shpchp
>> >> > 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9
Family) USB UHCI Controller #1 (rev 03) (prog-if 00 [UHCI])
>> >> > Subsystem: Sony Corporation Device 9033
>> >> > Flags: bus master, medium devsel, latency 0, IRQ 20
>> >> > I/O ports at 9080 [size=32]
>> >> > Capabilities: [50] PCIe advanced features <?>
>> >> > Kernel driver in use: uhci_hcd
>> >> > Kernel modules: uhci-hcd
>> >> > 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9
Family) USB UHCI Controller #2 (rev 03) (prog-if 00 [UHCI])
>> >> > Subsystem: Sony Corporation Device 9033
>> >> > Flags: bus master, medium devsel, latency 0, IRQ 19
>> >> > I/O ports at 9060 [size=32]
>> >> > Capabilities: [50] PCIe advanced features <?>
>> >> > Kernel driver in use: uhci_hcd
>> >> > Kernel modules: uhci-hcd
>> >> > 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9
Family) USB UHCI Controller #3 (rev 03) (prog-if 00 [UHCI])
>> >> > Subsystem: Sony Corporation Device 9033
>> >> > Flags: bus master, medium devsel, latency 0, IRQ 18
>> >> > I/O ports at 9040 [size=32]
>> >> > Capabilities: [50] PCIe advanced features <?>
>> >> > Kernel driver in use: uhci_hcd
>> >> > Kernel modules: uhci-hcd
>> >> > 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9
Family) USB2 EHCI Controller #1 (rev 03) (prog-if 20 [EHCI])
>> >> > Subsystem: Sony Corporation Device 9033
>> >> > Flags: bus master, medium devsel, latency 0, IRQ 20
>> >> > Memory at d5604800 (32-bit, non-prefetchable) [size=1K]
>> >> > Capabilities: [50] Power Management version 2
>> >> > Capabilities: [58] Debug port: BAR=1 offset=00a0
>> >> > Capabilities: [98] PCIe advanced features <?>
>> >> > Kernel driver in use: ehci_hcd
>> >> > Kernel modules: ehci-hcd
>> >> > 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI
Bridge (rev 93) (prog-if 01 [Subtractive decode])
>> >> > Flags: bus master, fast devsel, latency 0
>> >> > Bus: primary=00, secondary=06, subordinate=06,
sec-latency=32
>> >> > Memory behind bridge: d5500000-d55fffff
>> >> > Capabilities: [50] Subsystem: Sony Corporation Device
9033
>> >> > 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface
Controller (rev 03)
>> >> > Subsystem: Sony Corporation Device 9033
>> >> > Flags: bus master, medium devsel, latency 0
>> >> > Capabilities: [e0] Vendor Specific Information <?>
>> >> > Kernel modules: iTCO_wdt
>> >> > 00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA
AHCI Controller (rev 03) (prog-if 01 [AHCI 1.0])
>> >> > Subsystem: Sony Corporation Device 9033
>> >> > Flags: bus master, 66MHz, medium devsel, latency 0, IRQ
1279
>> >> > I/O ports at 9130 [size=8]
>> >> > I/O ports at 9120 [size=4]
>> >> > I/O ports at 9110 [size=8]
>> >> > I/O ports at 9100 [size=4]
>> >> > I/O ports at 9020 [size=32]
>> >> > Memory at d5604000 (32-bit, non-prefetchable) [size=2K]
>> >> > Capabilities: [80] Message Signalled Interrupts: Mask-
64bit- Queue=0/4 Enable+
>> >> > Capabilities: [70] Power Management version 3
>> >> > Capabilities: [a8] SATA HBA <?>
>> >> > Capabilities: [b0] PCIe advanced features <?>
>> >> > Kernel driver in use: ahci
>> >> > Kernel modules: ahci
>> >> > 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family)
SMBus Controller (rev 03)
>> >> > Subsystem: Sony Corporation Device 9033
>> >> > Flags: medium devsel, IRQ 19
>> >> > Memory at d5605000 (64-bit, non-prefetchable) [size=256]
>> >> > I/O ports at 9000 [size=32]
>> >> > Kernel driver in use: i801_smbus
>> >> > Kernel modules: i2c-i801
>> >> > 01:00.0 Ethernet controller: Marvell Technology Group
Ltd. 88E8040 PCI-E Fast Ethernet Controller (rev 12)
>> >> > Subsystem: Sony Corporation Device 9033
>> >> > Flags: bus master, fast devsel, latency 0, IRQ 11
>> >> > Memory at d4100000 (64-bit, non-prefetchable) [size=16K]
>> >> > I/O ports at 8000 [size=256]
>> >> > Capabilities: [48] Power Management version 3
>> >> > Capabilities: [5c] Message Signalled Interrupts: Mask-
64bit+ Queue=0/0 Enable-
>> >> > Capabilities: [c0] Express Legacy Endpoint, MSI 00
>> >> > Capabilities: [100] Advanced Error Reporting <?>
>> >> > Capabilities: [130] Device Serial Number
00-1d-ba-ff-ff-26-a8-b9
>> >> > 04:00.0 Network controller: Intel Corporation Wireless
WiFi Link 5100
>> >> > Subsystem: Intel Corporation Device 1301
>> >> > Flags: bus master, fast devsel, latency 0, IRQ 11
>> >> > Memory at d1900000 (64-bit, non-prefetchable) [size=8K]
>> >> > Capabilities: [c8] Power Management version 3
>> >> > Capabilities: [d0] Message Signalled Interrupts: Mask-
64bit+ Queue=0/0 Enable-
>> >> > Capabilities: [e0] Express Endpoint, MSI 00
>> >> > Capabilities: [100] Advanced Error Reporting <?>
>> >> > Capabilities: [140] Device Serial Number
36-b3-83-ff-ff-5d-21-00
>> >> > 06:03.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE
1394 Controller (rev 05) (prog-if 10 [OHCI])
>> >> > Subsystem: Sony Corporation Device 9033
>> >> > Flags: bus master, medium devsel, latency 32, IRQ 17
>> >> > Memory at d5500000 (32-bit, non-prefetchable) [size=2K]
>> >> > Capabilities: [dc] Power Management version 2
>> >> > Kernel driver in use: ohci1394
>> >> > Kernel modules: ohci1394
>> >> > 06:03.1 SD Host controller: Ricoh Co Ltd R5C822
SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22)
>> >> > Subsystem: Sony Corporation Device 9033
>> >> > Flags: bus master, medium devsel, latency 32, IRQ 16
>> >> > Memory at d5500900 (32-bit, non-prefetchable) [size=256]
>> >> > Capabilities: [80] Power Management version 2
>> >> > Kernel driver in use: sdhci
>> >> > Kernel modules: sdhci
>> >> > 06:03.2 System peripheral: Ricoh Co Ltd R5C592 Memory
Stick Bus Host Adapter (rev 12)
>> >> > Subsystem: Sony Corporation Device 9033
>> >> > Flags: bus master, medium devsel, latency 32, IRQ 4
>> >> > Memory at d5500800 (32-bit, non-prefetchable) [size=256]
>> >> > Capabilities: [80] Power Management version 2
>> >> > 
>> >> 
>> >> > 
>> >> >> Date: Fri, 23 Apr 2010 11:02:01 +0300
>> >> >> From: pasik@iki.fi
>> >> >> To: ilishim@hotmail.com
>> >> >> CC: xen-users@lists.xensource.com
>> >> >> Subject: Re: [Xen-users] Re: [Xen-devel] Scrubbing
free ram
>> >> >> 
>> >> >> On Fri, Apr 23, 2010 at 07:28:49AM +0000, ilish ilish
wrote:
>> >> >> > Hi again,
>> >> >> > Thank you very much. First there is no specific
reason for
>> >> >> > using 2.6.29-xen-r4. And I will try lspci -v,
and send you the output of
>> >> >> > that.
>> >> >> > By the way I am new in this area and actually do
not know pvops dom0
>> >> >> > kernel is. Is this a specific kernel version?
>> >> >> 
>> >> >> pvops dom0 is the default dom0 kernel in Xen 4.0.0.
>> >> >> 
>> >> >> See these wiki pages:
>> >> >> - http://wiki.xensource.com/xenwiki/Xen4.0
>> >> >> - http://wiki.xensource.com/xenwiki/XenDom0Kernels
>> >> >> - http://wiki.xensource.com/xenwiki/XenParavirtOps
>> >> >> 
>> >> >> -- Pasi
>> >> >> 
>> >> >> > Ilhan
>> >> >> > > Date: Fri, 23 Apr 2010 10:03:05 +0300
>> >> >> > > From: pasik@iki.fi
>> >> >> > > To: ilishim@hotmail.com
>> >> >> > > CC: xen-users@lists.xensource.com
>> >> >> > > Subject: Re: [Xen-users] Re: [Xen-devel]
Scrubbing free ram
>> >> >> > >
>> >> >> > > On Fri, Apr 23, 2010 at 06:52:42AM +0000,
ilish ilish wrote:
>> >> >> > > > Hi Pasi,
>> >> >> > > > Thank you very much for your concern
about my issue. After sending
>> >> >> > email
>> >> >> > > > to xen-devel, I switch to Debian 5 to
install Xen, I do not have any
>> >> >> > > > problems but I am still very curious
about the problem. Since I
>> >> >> > installed
>> >> >> > > > Debian now, I just ha! ve this part of
my grub.conf entry:
>> >> >> > > > title pv_ops dom0-test (2.6.29) with
serial console
>> >> >> > > > root (hd0,2)
>> >> >> > > > kernel /boot/xen-4.0.0-rc6.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
>> >> >> > > > module /boot/vmlinuz-2.6.29-xen-r4 ro
>> >> >> > > >
root=UUID=e173017f-7b9a-4111-acf7-b9f0d02a8936 console=hvc0
>> >> >> > > > earlyprintk=xen nomodeset!
initcall_debug debug loglevel=10
>> >> >> > > > module /boot/initrd-2.6.29-xen-r4.img
>> >> >> > > > Could you please help me about my
issue?
>> >> >> > >
>> >> >> > >
>> >> >> > > Please update to 4.0.0 final, or even
4.0.1-rc version..
>> >> >> > > many bugs fixed after 4.0.0-rc6.
>> >> >> > >
>> >> >> > > > I also want to ask you something about
Debian 5+Xen 4.0 . I booted
>> >> >> > with
>> >> >> > > > Xen in my Debian installe! d machine.
However there is a problem about
>> >> >> > the
>> >> >> > > > eth0. Xen 4.0 did not recognize my
eth0. I do not know what to do
>> >> >> > about
>> >> >> > > > this. Do you have any idea about this?
>> >> >> > > > Thank you again very much for your
time and help.
>> >> >> > > >
>> >> >> > >
>> >> >> > > Xen doesn''t have drivers for
hardware/nics. It''s the Linux dom0 kernel
>> >> >> > that has the NIC driver.
>> >> >> > > Does "lspci -v" list the nic
(when booted to Xen dom0)?
>> >> >> > >
>> >> >> > > Also please paste your dmesg.
>> >> >> > >
>> >> >> > > Also is there a specific reason
you''re using 2.6.29-xen-r4 (xenlinux)
>> >> >> > kernel
>> >> >> > > instead of the pvops dom0 kernel?
>> >> >> > >
>> >> >> > > -- Pasi
>> >> >> > >
>> >> >> > > > Ilhan
>> >> >> > > > > Date: Fri, 23 Apr 2010 09:14:12
+0300
>> >> >> > > > > From: pasik@iki.fi
>> >> >> > > > > To: ilishim@hotmail.com
>> >> >> > > > > CC:
xen-devel@lists.xensource.com; xen-users@lists.xensource.com
>> >> >> > > > > Subject: [Xen-users] Re:
[Xen-devel] Scrubbing free ram
>> >> >> > > > >
>> >> >> > > > > On Thu, Apr 22, 2010 a! t
09:54:30PM +0000, ilish ilish wrote:
>> >> >> > > > > > Hi everyone,
>> >> >> > > > > >
>> >> >> > > > > > I am working on a project
whose goal is evaluating the pe!
>> >> >> > rformance
>> >> >> > > > of the
>> >> >> > > > > > vTPM Manager. For this
project I am using Xen 4.1, Kernel
>> >> >> > 2.6.31.13
>> >> >> > > > with
>> >> >> > > > > > Fedora11. I I finished all
installation and configuration parts.
>> >> >> > Now I
>> >> >> > > > > > need to boot the system with
Xen but while booting, it is freezing
>> >> >> > at
>> >> >> > > > the
>> >> >> > > > > > step "scrubbing free
ram". What can be cause this problem and how
>> >> >> > can
>> >> >> > > > I
>> >> >> > > > > > figure it out? I really
appreciate if you can help me.
>> >> >> > > > > >
>> >> >> > > > >
>> >> >> > > > > Please paste your grub.conf.
>> >> >> > > > >
>> >> >> > > > > Also please check this wiki page:
>> >> >> > > > >
http://wiki.xensource.com/xenwiki/XenSerialConsol! e
>> >> >> > > > >
>> >> >> > > > > and:
>> >> >> > > > >
http://wiki.xensource.com/xenwiki/XenParavirtOps
>> >> >> > > > >
>> >> >> > > > > -- Pasi
>> >> >> > > > >
>> >> >> > > > >
>> >> >> > >
>> >> >> > 
>> >> >> >
--------------------------------------------------------------------------
>> >> >> > 
>> >> >> > Hotmail: Microsoft*un güçlü ÝSTENMEYEN POSTA
korumasý ile güvenilir
>> >> >> > e-posta. [1]Hemen kaydolun.
>> >> >> > 
>> >> >> > References
>> >> >> > 
>> >> >> > Visible links
>> >> >> > 1. https://signup.live.com/signup.aspx?id=60969
>> >> > 
>> >> >
_________________________________________________________________
>> >> > Hareket Halindeyken E-postanız ve Çok Daha Fazlası.
Windows Live Hotmail''i Ücretsiz Edinin.
>> >> > https://signup.live.com/signup.aspx?id=60969
>> >> 
>> >> 
>> >> 
>> >> -- 
>> >> Best regards,
>> >> Sander mailto:linux@eikelenboom.it
>> >> 
>> > 
>> > _________________________________________________________________
>> > Hotmail: Microsoft’un güçlü İSTENMEYEN POSTA koruması ile
güvenilir e-posta.
>> > https://signup.live.com/signup.aspx?id=60969
>> 
>> 
>> 
>> -- 
>> Best regards,
>> Sander mailto:linux@eikelenboom.it
>> 
>                                           
> _________________________________________________________________
> Hotmail: Ücretsiz, güvenilir ve zengin e-posta servisi.
> https://signup.live.com/signup.aspx?id=60969


-- 
Best regards,
 Sander                            mailto:linux@eikelenboom.it


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

Keir Fraser

2010-Apr-28 04:55 UTC

head link

Re: [Xen-devel] Scrubbing free ram

Do things work if you add no-bootscrub to the Xen command line?

 -- Keir

On 28/04/2010 13:49, "BEI GUAN" <gbtju85@gmail.com> wrote:
> Dear Pasi,
> 
> I have the same problem as ilish had when I installed xen 4.0 on fedora 11
> today. I rebooted the Xen. The screen just stopped at "Scrubbing Free
RAM:",
> and then the computer reboot again. My grub.conf as following.
> 
> title Xen-4.0 (Linux kernel 2.6.31.13)
>     root (hd0,10)
>     kernel /boot/xen-4.0.gz dom0_mem=1024M loglvl=all guest_loglvl=all
>     module /boot/vmlinuz-2.6.31.13 root=/dev/sda1 ro nomodeset
>     module /boot/initrd-2.6.31.13.img
> 
> I also made "root=/dev/sda11" and "root=LABEL=/" and to
try. However, I still
> doesn''t work. Your any reply is appreciated.
> 
> Thank you very much.
> 
> Gavin Guan
> 
> 
> 
> 
> 2010/4/23 Pasi Kärkkäinen <pasik@iki.fi>
>> On Thu, Apr 22, 2010 at 09:54:30PM +0000, ilish ilish wrote:
>>>    Hi everyone,
>>> 
>>>    I am working on a project whose goal is evaluating the
performance of the
>>>    vTPM Manager. For this project I am using Xen 4.1, Kernel
2.6.31.13 with
>>>    Fedora11. I I finished all installation and configuration parts.
Now I
>>>    need to boot the system with Xen but while booting, it is
freezing at the
>>>    step "scrubbing free ram". What can be cause this
problem and how can I
>>>    figure it out? I really appreciate if you can help me.
>>> 
>> 
>> Please paste your grub.conf.
>> 
>> Also please check this wiki page:
>> http://wiki.xensource.com/xenwiki/XenSerialConsole
>> 
>> and:
>> http://wiki.xensource.com/xenwiki/XenParavirtOps
>> 
>> -- Pasi
>> 
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
> 
> 


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

Keir Fraser

2010-Apr-28 05:38 UTC

head link

Re: [Xen-devel] Scrubbing free ram

Probably something to do with dom0 building then. I would try a different
dom0 kernel just to see if that works better. But probably there is a bug
here that a developer will need to be able to reproduce to fix.

 -- Keir

On 28/04/2010 14:35, "BEI GUAN" <gbtju85@gmail.com> wrote:
> Hello Keir,
> 
> Thank you very much for your reply. As you said, I just change my grub.conf
as
> following. But it also did not work. The screen just stopped when message
> "(XEN) Dom0 has maximum 4 VCPUs" was printed, which is just
before the message
> "Scrubbing Free RAM:". And then system reboot.
> 
> title Xen-4.0 (Linux kernel 2.6.31.13)
>     root (hd0,10)
>     kernel /boot/xen-4.0.gz no-bootscrub dom0_mem=1024M loglvl=all
> guest_loglvl=all
>     module /boot/vmlinuz-2.6.31.13 root=/dev/sda1 ro nomodeset
>     module /boot/initrd-2.6.31.13.img
> 
> Thank you. Best wishes.
> 
> Gavin Guan
> 
> 
> 
> 
> 2010/4/28 Keir Fraser <keir.fraser@eu.citrix.com>
>> Do things work if you add no-bootscrub to the Xen command line?
>> 
>>  -- Keir
>> 
>> On 28/04/2010 13:49, "BEI GUAN" <gbtju85@gmail.com>
wrote:
>> 
>>> Dear Pasi,
>>> 
>>> I have the same problem as ilish had when I installed xen 4.0 on
fedora 11
>>> today. I rebooted the Xen. The screen just stopped at
"Scrubbing Free RAM:",
>>> and then the computer reboot again. My grub.conf as following.
>>> 
>>> title Xen-4.0 (Linux kernel 2.6.31.13)
>>>     root (hd0,10)
>>>     kernel /boot/xen-4.0.gz dom0_mem=1024M loglvl=all
guest_loglvl=all
>>>     module /boot/vmlinuz-2.6.31.13 root=/dev/sda1 ro nomodeset
>>>     module /boot/initrd-2.6.31.13.img
>>> 
>>> I also made "root=/dev/sda11" and
"root=LABEL=/" and to try. However, I
>>> still
>>> doesn''t work. Your any reply is appreciated.
>>> 
>>> Thank you very much.
>>> 
>>> Gavin Guan
>>> 
>>> 
>>> 
>>> 
>>> 2010/4/23 Pasi Kärkkäinen <pasik@iki.fi>
>>>> On Thu, Apr 22, 2010 at 09:54:30PM +0000, ilish ilish wrote:
>>>>>    Hi everyone,
>>>>> 
>>>>>    I am working on a project whose goal is evaluating the
performance of
>>>>> the
>>>>>    vTPM Manager. For this project I am using Xen 4.1,
Kernel 2.6.31.13
>>>>> with
>>>>>    Fedora11. I I finished all installation and
configuration parts. Now I
>>>>>    need to boot the system with Xen but while booting, it
is freezing at
>>>>> the
>>>>>    step "scrubbing free ram". What can be cause
this problem and how can I
>>>>>    figure it out? I really appreciate if you can help me.
>>>>> 
>>>> 
>>>> Please paste your grub.conf.
>>>> 
>>>> Also please check this wiki page:
>>>> http://wiki.xensource.com/xenwiki/XenSerialConsole
>>>> 
>>>> and:
>>>> http://wiki.xensource.com/xenwiki/XenParavirtOps
>>>> 
>>>> -- Pasi
>>>> 
>>>> 
>>>> _______________________________________________
>>>> Xen-devel mailing list
>>>> Xen-devel@lists.xensource.com
>>>> http://lists.xensource.com/xen-devel
>>> 
>>> 
>> 
>> 
> 
> 


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

Keir Fraser

2010-Apr-28 05:43 UTC

head link

Re: [Xen-devel] Scrubbing free ram

Some other options: add noreboot to Xen command line and see if anything
else does get printed before reboot. And/or connect a serial line and have
Xen log to serial console and see if any other diagnostic messages are
visible from that.

 -- Keir

On 28/04/2010 06:38, "Keir Fraser" <Keir.Fraser@eu.citrix.com>
wrote:
> Probably something to do with dom0 building then. I would try a different
> dom0 kernel just to see if that works better. But probably there is a bug
> here that a developer will need to be able to reproduce to fix.
> 
>  -- Keir
> 
> On 28/04/2010 14:35, "BEI GUAN" <gbtju85@gmail.com> wrote:
> 
>> Hello Keir,
>> 
>> Thank you very much for your reply. As you said, I just change my
grub.conf
>> as
>> following. But it also did not work. The screen just stopped when
message
>> "(XEN) Dom0 has maximum 4 VCPUs" was printed, which is just
before the
>> message
>> "Scrubbing Free RAM:". And then system reboot.
>> 
>> title Xen-4.0 (Linux kernel 2.6.31.13)
>>     root (hd0,10)
>>     kernel /boot/xen-4.0.gz no-bootscrub dom0_mem=1024M loglvl=all
>> guest_loglvl=all
>>     module /boot/vmlinuz-2.6.31.13 root=/dev/sda1 ro nomodeset
>>     module /boot/initrd-2.6.31.13.img
>> 
>> Thank you. Best wishes.
>> 
>> Gavin Guan
>> 
>> 
>> 
>> 
>> 2010/4/28 Keir Fraser <keir.fraser@eu.citrix.com>
>>> Do things work if you add no-bootscrub to the Xen command line?
>>> 
>>>  -- Keir
>>> 
>>> On 28/04/2010 13:49, "BEI GUAN" <gbtju85@gmail.com>
wrote:
>>> 
>>>> Dear Pasi,
>>>> 
>>>> I have the same problem as ilish had when I installed xen 4.0
on fedora 11
>>>> today. I rebooted the Xen. The screen just stopped at
"Scrubbing Free
>>>> RAM:",
>>>> and then the computer reboot again. My grub.conf as following.
>>>> 
>>>> title Xen-4.0 (Linux kernel 2.6.31.13)
>>>>     root (hd0,10)
>>>>     kernel /boot/xen-4.0.gz dom0_mem=1024M loglvl=all
guest_loglvl=all
>>>>     module /boot/vmlinuz-2.6.31.13 root=/dev/sda1 ro nomodeset
>>>>     module /boot/initrd-2.6.31.13.img
>>>> 
>>>> I also made "root=/dev/sda11" and
"root=LABEL=/" and to try. However, I
>>>> still
>>>> doesn''t work. Your any reply is appreciated.
>>>> 
>>>> Thank you very much.
>>>> 
>>>> Gavin Guan
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 2010/4/23 Pasi Kärkkäinen <pasik@iki.fi>
>>>>> On Thu, Apr 22, 2010 at 09:54:30PM +0000, ilish ilish
wrote:
>>>>>>    Hi everyone,
>>>>>> 
>>>>>>    I am working on a project whose goal is evaluating
the performance of
>>>>>> the
>>>>>>    vTPM Manager. For this project I am using Xen 4.1,
Kernel 2.6.31.13
>>>>>> with
>>>>>>    Fedora11. I I finished all installation and
configuration parts. Now I
>>>>>>    need to boot the system with Xen but while booting,
it is freezing at
>>>>>> the
>>>>>>    step "scrubbing free ram". What can be
cause this problem and how can
>>>>>> I
>>>>>>    figure it out? I really appreciate if you can help
me.
>>>>>> 
>>>>> 
>>>>> Please paste your grub.conf.
>>>>> 
>>>>> Also please check this wiki page:
>>>>> http://wiki.xensource.com/xenwiki/XenSerialConsole
>>>>> 
>>>>> and:
>>>>> http://wiki.xensource.com/xenwiki/XenParavirtOps
>>>>> 
>>>>> -- Pasi
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> Xen-devel mailing list
>>>>> Xen-devel@lists.xensource.com
>>>>> http://lists.xensource.com/xen-devel
>>>> 
>>>> 
>>> 
>>> 
>> 
>> 
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel


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

BEI GUAN

2010-Apr-28 12:49 UTC

head link

Re: [Xen-devel] Scrubbing free ram

Dear Pasi,

I have the same problem as ilish had when I installed xen 4.0 on fedora 11
today. I rebooted the Xen. The screen just stopped at "Scrubbing Free
RAM:",
and then the computer reboot again. My grub.conf as following.

title Xen-4.0 (Linux kernel 2.6.31.13)
    root (hd0,10)
    kernel /boot/xen-4.0.gz dom0_mem=1024M loglvl=all guest_loglvl=all
    module /boot/vmlinuz-2.6.31.13 root=/dev/sda1 ro nomodeset
    module /boot/initrd-2.6.31.13.img

I also made "root=/dev/sda11" and "root=LABEL=/" and to try.
However, I
still doesn''t work. Your any reply is appreciated.

Thank you very much.

Gavin Guan




2010/4/23 Pasi Kärkkäinen <pasik@iki.fi>
> On Thu, Apr 22, 2010 at 09:54:30PM +0000, ilish ilish wrote:
> >    Hi everyone,
> >
> >    I am working on a project whose goal is evaluating the performance
of
> the
> >    vTPM Manager. For this project I am using Xen 4.1, Kernel 2.6.31.13
> with
> >    Fedora11. I I finished all installation and configuration parts.
Now I
> >    need to boot the system with Xen but while booting, it is freezing
at
> the
> >    step "scrubbing free ram". What can be cause this problem
and how can
> I
> >    figure it out? I really appreciate if you can help me.
> >
>
> Please paste your grub.conf.
>
> Also please check this wiki page:
> http://wiki.xensource.com/xenwiki/XenSerialConsole
>
> and:
> http://wiki.xensource.com/xenwiki/XenParavirtOps
>
> -- Pasi
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>

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

BEI GUAN

2010-Apr-28 13:35 UTC

head link

Re: [Xen-devel] Scrubbing free ram

Hello Keir,

Thank you very much for your reply. As you said, I just change my grub.conf
as following. But it also did not work. The screen just stopped when message
"(XEN) Dom0 has maximum 4 VCPUs" was printed, which is just before the
message "Scrubbing Free RAM:". And then system reboot.

title Xen-4.0 (Linux kernel 2.6.31.13)
    root (hd0,10)
    kernel /boot/xen-4.0.gz no-bootscrub dom0_mem=1024M loglvl=all
guest_loglvl=all
    module /boot/vmlinuz-2.6.31.13 root=/dev/sda1 ro nomodeset
    module /boot/initrd-2.6.31.13.img

Thank you. Best wishes.

Gavin Guan




2010/4/28 Keir Fraser <keir.fraser@eu.citrix.com>
> Do things work if you add no-bootscrub to the Xen command line?
>
>  -- Keir
>
> On 28/04/2010 13:49, "BEI GUAN" <gbtju85@gmail.com> wrote:
>
> > Dear Pasi,
> >
> > I have the same problem as ilish had when I installed xen 4.0 on
fedora
> 11
> > today. I rebooted the Xen. The screen just stopped at "Scrubbing
Free
> RAM:",
> > and then the computer reboot again. My grub.conf as following.
> >
> > title Xen-4.0 (Linux kernel 2.6.31.13)
> >     root (hd0,10)
> >     kernel /boot/xen-4.0.gz dom0_mem=1024M loglvl=all guest_loglvl=all
> >     module /boot/vmlinuz-2.6.31.13 root=/dev/sda1 ro nomodeset
> >     module /boot/initrd-2.6.31.13.img
> >
> > I also made "root=/dev/sda11" and "root=LABEL=/"
and to try. However, I
> still
> > doesn''t work. Your any reply is appreciated.
> >
> > Thank you very much.
> >
> > Gavin Guan
> >
> >
> >
> >
> > 2010/4/23 Pasi Kärkkäinen <pasik@iki.fi>
> >> On Thu, Apr 22, 2010 at 09:54:30PM +0000, ilish ilish wrote:
> >>>    Hi everyone,
> >>>
> >>>    I am working on a project whose goal is evaluating the
performance
> of the
> >>>    vTPM Manager. For this project I am using Xen 4.1, Kernel
2.6.31.13
> with
> >>>    Fedora11. I I finished all installation and configuration
parts. Now
> I
> >>>    need to boot the system with Xen but while booting, it is
freezing
> at the
> >>>    step "scrubbing free ram". What can be cause this
problem and how
> can I
> >>>    figure it out? I really appreciate if you can help me.
> >>>
> >>
> >> Please paste your grub.conf.
> >>
> >> Also please check this wiki page:
> >> http://wiki.xensource.com/xenwiki/XenSerialConsole
> >>
> >> and:
> >> http://wiki.xensource.com/xenwiki/XenParavirtOps
> >>
> >> -- Pasi
> >>
> >>
> >> _______________________________________________
> >> Xen-devel mailing list
> >> Xen-devel@lists.xensource.com
> >> http://lists.xensource.com/xen-devel
> >
> >
>
>
>

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

BEI GUAN

2010-Apr-28 15:44 UTC

head link

Re: [Xen-devel] Scrubbing free ram

Hi,

Sorry, I can not get the boot message through XenSerialConsole now. However,
attached are the screenshots of the last part of boot message.
If add "no-bootscrub" on the xen command line, the message is the same
except for the last line, "(XEN) Scrubbing Free RAM:". The grub.conf
is as
following.

 title Xen-4.0 (Linux kernel 2.6.31.13)
    root (hd0,10)
    kernel /boot/xen-4.0.gz dom0_mem=1024M loglvl=all guest_loglvl=all
    module /boot/vmlinuz-2.6.31.13 root=/dev/sda1 ro nomodeset
    module /boot/initrd-2.6.31.13.img

Best wishes.

Gavin Guan





2010/4/28 Keir Fraser <keir.fraser@eu.citrix.com>
> Some other options: add noreboot to Xen command line and see if anything
> else does get printed before reboot. And/or connect a serial line and have
> Xen log to serial console and see if any other diagnostic messages are
> visible from that.
>
>  -- Keir
>
> On 28/04/2010 06:38, "Keir Fraser"
<Keir.Fraser@eu.citrix.com> wrote:
>
> > Probably something to do with dom0 building then. I would try a
different
> > dom0 kernel just to see if that works better. But probably there is a
bug
> > here that a developer will need to be able to reproduce to fix.
> >
> >  -- Keir
> >
> > On 28/04/2010 14:35, "BEI GUAN" <gbtju85@gmail.com>
wrote:
> >
> >> Hello Keir,
> >>
> >> Thank you very much for your reply. As you said, I just change my
> grub.conf
> >> as
> >> following. But it also did not work. The screen just stopped when
> message
> >> "(XEN) Dom0 has maximum 4 VCPUs" was printed, which is
just before the
> >> message
> >> "Scrubbing Free RAM:". And then system reboot.
> >>
> >> title Xen-4.0 (Linux kernel 2.6.31.13)
> >>     root (hd0,10)
> >>     kernel /boot/xen-4.0.gz no-bootscrub dom0_mem=1024M loglvl=all
> >> guest_loglvl=all
> >>     module /boot/vmlinuz-2.6.31.13 root=/dev/sda1 ro nomodeset
> >>     module /boot/initrd-2.6.31.13.img
> >>
> >> Thank you. Best wishes.
> >>
> >> Gavin Guan
> >>
> >>
> >>
> >>
> >> 2010/4/28 Keir Fraser <keir.fraser@eu.citrix.com>
> >>> Do things work if you add no-bootscrub to the Xen command
line?
> >>>
> >>>  -- Keir
> >>>
> >>> On 28/04/2010 13:49, "BEI GUAN"
<gbtju85@gmail.com> wrote:
> >>>
> >>>> Dear Pasi,
> >>>>
> >>>> I have the same problem as ilish had when I installed xen
4.0 on
> fedora 11
> >>>> today. I rebooted the Xen. The screen just stopped at
"Scrubbing Free
> >>>> RAM:",
> >>>> and then the computer reboot again. My grub.conf as
following.
> >>>>
> >>>> title Xen-4.0 (Linux kernel 2.6.31.13)
> >>>>     root (hd0,10)
> >>>>     kernel /boot/xen-4.0.gz dom0_mem=1024M loglvl=all
guest_loglvl=all
> >>>>     module /boot/vmlinuz-2.6.31.13 root=/dev/sda1 ro
nomodeset
> >>>>     module /boot/initrd-2.6.31.13.img
> >>>>
> >>>> I also made "root=/dev/sda11" and
"root=LABEL=/" and to try. However,
> I
> >>>> still
> >>>> doesn''t work. Your any reply is appreciated.
> >>>>
> >>>> Thank you very much.
> >>>>
> >>>> Gavin Guan
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> 2010/4/23 Pasi Kärkkäinen <pasik@iki.fi>
> >>>>> On Thu, Apr 22, 2010 at 09:54:30PM +0000, ilish ilish
wrote:
> >>>>>>    Hi everyone,
> >>>>>>
> >>>>>>    I am working on a project whose goal is
evaluating the
> performance of
> >>>>>> the
> >>>>>>    vTPM Manager. For this project I am using Xen
4.1, Kernel
> 2.6.31.13
> >>>>>> with
> >>>>>>    Fedora11. I I finished all installation and
configuration parts.
> Now I
> >>>>>>    need to boot the system with Xen but while
booting, it is
> freezing at
> >>>>>> the
> >>>>>>    step "scrubbing free ram". What can
be cause this problem and how
> can
> >>>>>> I
> >>>>>>    figure it out? I really appreciate if you can
help me.
> >>>>>>
> >>>>>
> >>>>> Please paste your grub.conf.
> >>>>>
> >>>>> Also please check this wiki page:
> >>>>> http://wiki.xensource.com/xenwiki/XenSerialConsole
> >>>>>
> >>>>> and:
> >>>>> http://wiki.xensource.com/xenwiki/XenParavirtOps
> >>>>>
> >>>>> -- Pasi
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> Xen-devel mailing list
> >>>>> Xen-devel@lists.xensource.com
> >>>>> http://lists.xensource.com/xen-devel
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>
> >
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
>
>
>



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

Gerry Reno

2010-Apr-28 21:53 UTC

head link

Re: [Xen-devel] Scrubbing free ram

On 04/28/2010 09:35 AM, BEI GUAN wrote:> Hello Keir,
>
> Thank you very much for your reply. As you said, I just change my 
> grub.conf as following. But it also did not work. The screen just 
> stopped when message "(XEN) Dom0 has maximum 4 VCPUs" was
printed,
> which is just before the message "Scrubbing Free RAM:". And then 
> system reboot.
>
> title Xen-4.0 (Linux kernel 2.6.31.13)
>     root (hd0,10)
>     kernel /boot/xen-4.0.gz no-bootscrub dom0_mem=1024M loglvl=all 
> guest_loglvl=all
>     module /boot/vmlinuz-2.6.31.13 root=/dev/sda1 ro nomodeset
>     module /boot/initrd-2.6.31.13.img
>
> Thank you. Best wishes.
>
> Gavin Guan
>
I wonder if this is somehow related to similar problem I''ve been having
using pv_ops dom0 2.6.32.10 on my AMD hardware.  Finally I was able to 
track down where it showed BUG: soft lockup on the screen.  Nothing 
seems to get rid of this soft lockup problem.  I''ve been trying various
different settings all day.

-Gerry


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

Bei Guan

2010-Apr-29 08:39 UTC

head link

Re: [Xen-devel] Scrubbing free ram

Dear Keir,

I''ve got the boot message of Xen4.0 on fedora11. It is as following.
_  __            _  _    ___   ___
 \ \/ /___ _ __   | || |  / _ \ / _ \
  \  // _ \ ''_ \  | || |_| | | | | | |
  /  \  __/ | | | |__   _| |_| | |_| |
 /_/\_\___|_| |_|    |_|(_)___(_)___/

(XEN) Xen version 4.0.0 (root@) (gcc 版本 4.4.1 20090725 (Red Hat 4.4.1-2)
(GCC) ) Thu Apr 29 09:41:18 CST 2010
(XEN) Latest ChangeSet: unavailable
(XEN) Command line: console=com1,vga com1=9600,8n1
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) Disc information:
(XEN)  Found 1 MBR signatures
(XEN)  Found 1 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009a800 (usable)
(XEN)  00000000000f0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000cfdffc00 (usable)
(XEN)  00000000cfdffc00 - 00000000cfe53c00 (ACPI NVS)
(XEN)  00000000cfe53c00 - 00000000cfe55c00 (ACPI data)
(XEN)  00000000cfe55c00 - 00000000d0000000 (reserved)
(XEN)  00000000e0000000 - 00000000f0000000 (reserved)
(XEN)  00000000fec00000 - 00000000fed00400 (reserved)
(XEN)  00000000fed20000 - 00000000feda0000 (reserved)
(XEN)  00000000fee00000 - 00000000fef00000 (reserved)
(XEN)  00000000ffb00000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 0000000128000000 (usable)
(XEN) System RAM: 3936MB (4031228kB)
(XEN) ACPI: RSDP 000FEC00, 0024 (r2 DELL  )
(XEN) ACPI: XSDT 000FC7CB, 009C (r1 DELL    B10K          15 ASL        61)
(XEN) ACPI: FACP 000FC8FB, 00F4 (r3 DELL    B10K          15 ASL        61)
(XEN) ACPI: DSDT FFE9CFF8, 54AD (r1   DELL    dt_ex     1000 INTL 20050624)
(XEN) ACPI: FACS CFDFFC00, 0040
(XEN) ACPI: SSDT FFEA25C4, 00AA (r1   DELL    st_ex     1000 INTL 20050624)
(XEN) ACPI: APIC 000FC9EF, 0092 (r1 DELL    B10K          15 ASL        61)
(XEN) ACPI: BOOT 000FCA81, 0028 (r1 DELL    B10K          15 ASL        61)
(XEN) ACPI: ASF! 000FCAA9, 0096 (r32 DELL    B10K          15 ASL        61)
(XEN) ACPI: MCFG 000FCB3F, 003E (r1 DELL    B10K          15 ASL        61)
(XEN) ACPI: HPET 000FCB7D, 0038 (r1 DELL    B10K          15 ASL        61)
(XEN) ACPI: TCPA 000FCDD9, 0032 (r1 DELL    B10K          15 ASL        61)
(XEN) ACPI: DMAR 000FCE0B, 00D8 (r1 DELL    B10K          15 ASL        61)
(XEN) ACPI: SLIC 000FCBB5, 0176 (r1 DELL    B10K          15 ASL        61)
(XEN) ACPI: SSDT CFDFFC40, 01B7 (r1 DpgPmm  Cpu0Ist       11 INTL 20050624)
(XEN) ACPI: SSDT CFE00049, 01B7 (r1 DpgPmm  Cpu1Ist       11 INTL 20050624)
(XEN) ACPI: SSDT CFE00452, 01B7 (r1 DpgPmm  Cpu2Ist       11 INTL 20050624)
(XEN) ACPI: SSDT CFE0085B, 01B7 (r1 DpgPmm  Cpu3Ist       11 INTL 20050624)
(XEN) ACPI: SSDT CFE00C64, 0190 (r1 DpgPmm    CpuPm       10 INTL 20050624)
(XEN) Xen heap: 8MB (8852kB)
(XEN) Domain heap initialised
(XEN) Processor #0 7:7 APIC version 20
(XEN) Processor #1 7:7 APIC version 20
(XEN) Processor #2 7:7 APIC version 20
(XEN) Processor #3 7:7 APIC version 20
(XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2660.072 MHz processor.
(XEN) Initing memory sharing.
(XEN) VMX: Supported advanced features:
(XEN)  - APIC MMIO access virtualisation
(XEN)  - APIC TPR shadow
(XEN)  - Virtual NMI
(XEN)  - MSR direct-access bitmap
(XEN) HVM: ASIDs disabled.
(XEN) HVM: VMX enabled
(XEN) xsave_init: cpu0: cntxt_max_size: 0x240 and states: 00000000:00000003
(XEN) xsave_init: using cntxt_size: 0x240 and states: 00000000:00000003
(XEN) Intel VT-d Snoop Control not supported.
(XEN) Intel VT-d DMA Passthrough not supported.
(XEN) Intel VT-d Queued Invalidation not supported.
(XEN) Intel VT-d Interrupt Remapping not supported.
(XEN) I/O virtualisation enabled
(XEN) I/O virtualisation for PV guests disabled
(XEN) xsave_init: cpu1: cntxt_max_size: 0x240 and states: 00000000:00000003
(XEN) xsave_init: cpu2: cntxt_max_size: 0x240 and states: 00000000:00000003
(XEN) xsave_init: cpu3: cntxt_max_size: 0x240 and states: 00000000:00000003
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) checking TSC synchronization across 4 CPUs: passed.
(XEN) Platform timer is 14.318MHz HPET
(XEN) Brought up 4 CPUs
(XEN) *** LOADING DOMAIN 0 ***
(XEN)  Xen  kernel: 32-bit, PAE, lsb
(XEN)  Dom0 kernel: 32-bit, PAE, lsb, paddr 0x400000 -> 0xbfb000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   000000003c000000->000000003e000000 (960235 pages to be
allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: c0400000->c0bfb000
(XEN)  Init. ramdisk: c0bfb000->c1329e00
(XEN)  Phys-Mach map: c132a000->c16dbbac
(XEN)  Start info:    c16dc000->c16dc47c
(XEN)  Page tables:   c16dd000->c16ee000
(XEN)  Boot stack:    c16ee000->c16ef000
(XEN)  TOTAL:         c0000000->c1800000
(XEN)  ENTRY ADDRESS: c098d000
(XEN) Dom0 has maximum 4 VCPUs
(XEN) Scrubbing Free RAM: .done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times
to switch input to
Xen)
(XEN) Freed 136kB init memory.
mapping kernel into physical memory
about to get started...
(XEN) traps.c:2309:d0 Domain attempted WRMSR 000002ff from 00000000:00000c06
to 00000000:00000000.
(XEN) traps.c:2309:d0 Domain attempted WRMSR 00000277 from 00000501:00070406
to 00070106:00070106.


My grub.conf is:

title Xen(2.6.31.13)
    root (hd0,10)
    kernel /boot/xen.gz console=com1,vga com1=9600,8n1
    module /boot/vmlinuz-2.6.31.13 root=/dev/sda1 ro nomodeset
    module /boot/initrd-2.6.31.13.img

Would you give me more suggestions. Thank you.

Best wishes.
gavin







2010/4/28 Keir Fraser <keir.fraser@eu.citrix.com>
> Some other options: add noreboot to Xen command line and see if anything
> else does get printed before reboot. And/or connect a serial line and have
> Xen log to serial console and see if any other diagnostic messages are
> visible from that.
>
>  -- Keir
>
> On 28/04/2010 06:38, "Keir Fraser"
<Keir.Fraser@eu.citrix.com> wrote:
>
> > Probably something to do with dom0 building then. I would try a
different
> > dom0 kernel just to see if that works better. But probably there is a
bug
> > here that a developer will need to be able to reproduce to fix.
> >
> >  -- Keir
> >
> > On 28/04/2010 14:35, "BEI GUAN" <gbtju85@gmail.com>
wrote:
> >
> >> Hello Keir,
> >>
> >> Thank you very much for your reply. As you said, I just change my
> grub.conf
> >> as
> >> following. But it also did not work. The screen just stopped when
> message
> >> "(XEN) Dom0 has maximum 4 VCPUs" was printed, which is
just before the
> >> message
> >> "Scrubbing Free RAM:". And then system reboot.
> >>
> >> title Xen-4.0 (Linux kernel 2.6.31.13)
> >>     root (hd0,10)
> >>     kernel /boot/xen-4.0.gz no-bootscrub dom0_mem=1024M loglvl=all
> >> guest_loglvl=all
> >>     module /boot/vmlinuz-2.6.31.13 root=/dev/sda1 ro nomodeset
> >>     module /boot/initrd-2.6.31.13.img
> >>
> >> Thank you. Best wishes.
> >>
> >> Gavin Guan
> >>
> >>
> >>
> >>
> >> 2010/4/28 Keir Fraser <keir.fraser@eu.citrix.com>
> >>> Do things work if you add no-bootscrub to the Xen command
line?
> >>>
> >>>  -- Keir
> >>>
> >>> On 28/04/2010 13:49, "BEI GUAN"
<gbtju85@gmail.com> wrote:
> >>>
> >>>> Dear Pasi,
> >>>>
> >>>> I have the same problem as ilish had when I installed xen
4.0 on
> fedora 11
> >>>> today. I rebooted the Xen. The screen just stopped at
"Scrubbing Free
> >>>> RAM:",
> >>>> and then the computer reboot again. My grub.conf as
following.
> >>>>
> >>>> title Xen-4.0 (Linux kernel 2.6.31.13)
> >>>>     root (hd0,10)
> >>>>     kernel /boot/xen-4.0.gz dom0_mem=1024M loglvl=all
guest_loglvl=all
> >>>>     module /boot/vmlinuz-2.6.31.13 root=/dev/sda1 ro
nomodeset
> >>>>     module /boot/initrd-2.6.31.13.img
> >>>>
> >>>> I also made "root=/dev/sda11" and
"root=LABEL=/" and to try. However,
> I
> >>>> still
> >>>> doesn''t work. Your any reply is appreciated.
> >>>>
> >>>> Thank you very much.
> >>>>
> >>>> Gavin Guan
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> 2010/4/23 Pasi Kärkkäinen <pasik@iki.fi>
> >>>>> On Thu, Apr 22, 2010 at 09:54:30PM +0000, ilish ilish
wrote:
> >>>>>>    Hi everyone,
> >>>>>>
> >>>>>>    I am working on a project whose goal is
evaluating the
> performance of
> >>>>>> the
> >>>>>>    vTPM Manager. For this project I am using Xen
4.1, Kernel
> 2.6.31.13
> >>>>>> with
> >>>>>>    Fedora11. I I finished all installation and
configuration parts.
> Now I
> >>>>>>    need to boot the system with Xen but while
booting, it is
> freezing at
> >>>>>> the
> >>>>>>    step "scrubbing free ram". What can
be cause this problem and how
> can
> >>>>>> I
> >>>>>>    figure it out? I really appreciate if you can
help me.
> >>>>>>
> >>>>>
> >>>>> Please paste your grub.conf.
> >>>>>
> >>>>> Also please check this wiki page:
> >>>>> http://wiki.xensource.com/xenwiki/XenSerialConsole
> >>>>>
> >>>>> and:
> >>>>> http://wiki.xensource.com/xenwiki/XenParavirtOps
> >>>>>
> >>>>> -- Pasi
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> Xen-devel mailing list
> >>>>> Xen-devel@lists.xensource.com
> >>>>> http://lists.xensource.com/xen-devel
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>
> >
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
>
>
>

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

Keir Fraser

2010-Apr-29 12:23 UTC

head link

Re: [Xen-devel] Scrubbing free ram

On 29/04/2010 01:39, "Bei Guan" <gbtju85@gmail.com> wrote:
> (XEN) traps.c:2309:d0 Domain attempted WRMSR 000002ff from
00000000:00000c06
> to 00000000:00000000.
> (XEN) traps.c:2309:d0 Domain attempted WRMSR 00000277 from
00000501:00070406
> to 00070106:00070106.
> 
> 
> My grub.conf is:
> 
> title Xen(2.6.31.13)
>     root (hd0,10)
>     kernel /boot/xen.gz console=com1,vga com1=9600,8n1
>     module /boot/vmlinuz-2.6.31.13 root=/dev/sda1 ro nomodeset
>     module /boot/initrd-2.6.31.13.img
> 
> Would you give me more suggestions. Thank you.
Try whatever dom0 kernel it is that you were using before the switch to Xen
4.0. It should still work.

 -- Keir



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

Konrad Rzeszutek Wilk

2010-Apr-29 14:48 UTC

head link

Re: [Xen-devel] Scrubbing free ram

On Thu, Apr 29, 2010 at 04:39:45PM +0800, Bei Guan
wrote:> Dear Keir,
> 
> I''ve got the boot message of Xen4.0 on fedora11. It is as
following.
> _  __            _  _    ___   ___
>  \ \/ /___ _ __   | || |  / _ \ / _ \
>   \  // _ \ ''_ \  | || |_| | | | | | |
>   /  \  __/ | | | |__   _| |_| | |_| |
>  /_/\_\___|_| |_|    |_|(_)___(_)___/
> 
> (XEN) Xen version 4.0.0 (root@) (gcc 版本 4.4.1 20090725 (Red Hat 4.4.1-2)
> (GCC) ) Thu Apr 29 09:41:18 CST 2010
> (XEN) Latest ChangeSet: unavailable
> (XEN) Command line: console=com1,vga com1=9600,8n1
> (XEN) Video information:
> (XEN)  VGA is text mode 80x25, font 8x16
> (XEN)  VBE/DDC methods: V2; EDID transfer time: 1 seconds
> (XEN) Disc information:
> (XEN)  Found 1 MBR signatures
> (XEN)  Found 1 EDD information structures
> (XEN) Xen-e820 RAM map:
> (XEN)  0000000000000000 - 000000000009a800 (usable)
> (XEN)  00000000000f0000 - 0000000000100000 (reserved)
> (XEN)  0000000000100000 - 00000000cfdffc00 (usable)
> (XEN)  00000000cfdffc00 - 00000000cfe53c00 (ACPI NVS)
> (XEN)  00000000cfe53c00 - 00000000cfe55c00 (ACPI data)
> (XEN)  00000000cfe55c00 - 00000000d0000000 (reserved)
> (XEN)  00000000e0000000 - 00000000f0000000 (reserved)
> (XEN)  00000000fec00000 - 00000000fed00400 (reserved)
> (XEN)  00000000fed20000 - 00000000feda0000 (reserved)
> (XEN)  00000000fee00000 - 00000000fef00000 (reserved)
> (XEN)  00000000ffb00000 - 0000000100000000 (reserved)
> (XEN)  0000000100000000 - 0000000128000000 (usable)
> (XEN) System RAM: 3936MB (4031228kB)
> (XEN) ACPI: RSDP 000FEC00, 0024 (r2 DELL  )
> (XEN) ACPI: XSDT 000FC7CB, 009C (r1 DELL    B10K          15 ASL        61)
> (XEN) ACPI: FACP 000FC8FB, 00F4 (r3 DELL    B10K          15 ASL        61)
> (XEN) ACPI: DSDT FFE9CFF8, 54AD (r1   DELL    dt_ex     1000 INTL 20050624)
> (XEN) ACPI: FACS CFDFFC00, 0040
> (XEN) ACPI: SSDT FFEA25C4, 00AA (r1   DELL    st_ex     1000 INTL 20050624)
> (XEN) ACPI: APIC 000FC9EF, 0092 (r1 DELL    B10K          15 ASL        61)
> (XEN) ACPI: BOOT 000FCA81, 0028 (r1 DELL    B10K          15 ASL        61)
> (XEN) ACPI: ASF! 000FCAA9, 0096 (r32 DELL    B10K          15 ASL       
61)
> (XEN) ACPI: MCFG 000FCB3F, 003E (r1 DELL    B10K          15 ASL        61)
> (XEN) ACPI: HPET 000FCB7D, 0038 (r1 DELL    B10K          15 ASL        61)
> (XEN) ACPI: TCPA 000FCDD9, 0032 (r1 DELL    B10K          15 ASL        61)
> (XEN) ACPI: DMAR 000FCE0B, 00D8 (r1 DELL    B10K          15 ASL        61)
> (XEN) ACPI: SLIC 000FCBB5, 0176 (r1 DELL    B10K          15 ASL        61)
> (XEN) ACPI: SSDT CFDFFC40, 01B7 (r1 DpgPmm  Cpu0Ist       11 INTL 20050624)
> (XEN) ACPI: SSDT CFE00049, 01B7 (r1 DpgPmm  Cpu1Ist       11 INTL 20050624)
> (XEN) ACPI: SSDT CFE00452, 01B7 (r1 DpgPmm  Cpu2Ist       11 INTL 20050624)
> (XEN) ACPI: SSDT CFE0085B, 01B7 (r1 DpgPmm  Cpu3Ist       11 INTL 20050624)
> (XEN) ACPI: SSDT CFE00C64, 0190 (r1 DpgPmm    CpuPm       10 INTL 20050624)
> (XEN) Xen heap: 8MB (8852kB)
> (XEN) Domain heap initialised
> (XEN) Processor #0 7:7 APIC version 20
> (XEN) Processor #1 7:7 APIC version 20
> (XEN) Processor #2 7:7 APIC version 20
> (XEN) Processor #3 7:7 APIC version 20
> (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
> (XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
> (XEN) Using scheduler: SMP Credit Scheduler (credit)
> (XEN) Detected 2660.072 MHz processor.
> (XEN) Initing memory sharing.
> (XEN) VMX: Supported advanced features:
> (XEN)  - APIC MMIO access virtualisation
> (XEN)  - APIC TPR shadow
> (XEN)  - Virtual NMI
> (XEN)  - MSR direct-access bitmap
> (XEN) HVM: ASIDs disabled.
> (XEN) HVM: VMX enabled
> (XEN) xsave_init: cpu0: cntxt_max_size: 0x240 and states: 00000000:00000003
> (XEN) xsave_init: using cntxt_size: 0x240 and states: 00000000:00000003
> (XEN) Intel VT-d Snoop Control not supported.
> (XEN) Intel VT-d DMA Passthrough not supported.
> (XEN) Intel VT-d Queued Invalidation not supported.
> (XEN) Intel VT-d Interrupt Remapping not supported.
> (XEN) I/O virtualisation enabled
> (XEN) I/O virtualisation for PV guests disabled
> (XEN) xsave_init: cpu1: cntxt_max_size: 0x240 and states: 00000000:00000003
> (XEN) xsave_init: cpu2: cntxt_max_size: 0x240 and states: 00000000:00000003
> (XEN) xsave_init: cpu3: cntxt_max_size: 0x240 and states: 00000000:00000003
> (XEN) Total of 4 processors activated.
> (XEN) ENABLING IO-APIC IRQs
> (XEN)  -> Using new ACK method
> (XEN) checking TSC synchronization across 4 CPUs: passed.
> (XEN) Platform timer is 14.318MHz HPET
> (XEN) Brought up 4 CPUs
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN)  Xen  kernel: 32-bit, PAE, lsb
> (XEN)  Dom0 kernel: 32-bit, PAE, lsb, paddr 0x400000 -> 0xbfb000
> (XEN) PHYSICAL MEMORY ARRANGEMENT:
> (XEN)  Dom0 alloc.:   000000003c000000->000000003e000000 (960235 pages
to be
> allocated)
> (XEN) VIRTUAL MEMORY ARRANGEMENT:
> (XEN)  Loaded kernel: c0400000->c0bfb000
> (XEN)  Init. ramdisk: c0bfb000->c1329e00
> (XEN)  Phys-Mach map: c132a000->c16dbbac
> (XEN)  Start info:    c16dc000->c16dc47c
> (XEN)  Page tables:   c16dd000->c16ee000
> (XEN)  Boot stack:    c16ee000->c16ef000
> (XEN)  TOTAL:         c0000000->c1800000
> (XEN)  ENTRY ADDRESS: c098d000
> (XEN) Dom0 has maximum 4 VCPUs
> (XEN) Scrubbing Free RAM: .done.
> (XEN) Xen trace buffers: disabled
> (XEN) Std. Loglevel: Errors and warnings
> (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
> (XEN) Xen is relinquishing VGA console.
> (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three
times to switch input to
> Xen)
> (XEN) Freed 136kB init memory.
> mapping kernel into physical memory
> about to get started...
> (XEN) traps.c:2309:d0 Domain attempted WRMSR 000002ff from
00000000:00000c06
> to 00000000:00000000.
> (XEN) traps.c:2309:d0 Domain attempted WRMSR 00000277 from
00000501:00070406
> to 00070106:00070106.
> 
> 
> My grub.conf is:
> 
> title Xen(2.6.31.13)
>     root (hd0,10)
>     kernel /boot/xen.gz console=com1,vga com1=9600,8n1
>     module /boot/vmlinuz-2.6.31.13 root=/dev/sda1 ro nomodeset
Was this kernel boot line the same as the previous kernel you used?
Also, please consult the http://wiki.xensource.com/xenwiki/XenParavirtOps
which Pasi refered to you earlier, and look in the "Are there more
debugging
options I could enable to troubleshoot booting problems?"

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

Pasi Kärkkäinen

2010-Apr-29 16:24 UTC

head link

Re: [Xen-devel] Scrubbing free ram

On Thu, Apr 29, 2010 at 10:48:59AM -0400, Konrad Rzeszutek Wilk
wrote:> > (XEN) *** LOADING DOMAIN 0 ***
> > (XEN)  Xen  kernel: 32-bit, PAE, lsb
> > (XEN)  Dom0 kernel: 32-bit, PAE, lsb, paddr 0x400000 -> 0xbfb000
> > (XEN) PHYSICAL MEMORY ARRANGEMENT:
> > (XEN)  Dom0 alloc.:   000000003c000000->000000003e000000 (960235
pages to be
> > allocated)
> > (XEN) VIRTUAL MEMORY ARRANGEMENT:
> > (XEN)  Loaded kernel: c0400000->c0bfb000
> > (XEN)  Init. ramdisk: c0bfb000->c1329e00
> > (XEN)  Phys-Mach map: c132a000->c16dbbac
> > (XEN)  Start info:    c16dc000->c16dc47c
> > (XEN)  Page tables:   c16dd000->c16ee000
> > (XEN)  Boot stack:    c16ee000->c16ef000
> > (XEN)  TOTAL:         c0000000->c1800000
> > (XEN)  ENTRY ADDRESS: c098d000
> > (XEN) Dom0 has maximum 4 VCPUs
> > (XEN) Scrubbing Free RAM: .done.
> > (XEN) Xen trace buffers: disabled
> > (XEN) Std. Loglevel: Errors and warnings
> > (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
> > (XEN) Xen is relinquishing VGA console.
> > (XEN) *** Serial input -> DOM0 (type ''CTRL-a''
three times to switch input to
> > Xen)
> > (XEN) Freed 136kB init memory.
> > mapping kernel into physical memory
> > about to get started...
> > (XEN) traps.c:2309:d0 Domain attempted WRMSR 000002ff from
00000000:00000c06
> > to 00000000:00000000.
> > (XEN) traps.c:2309:d0 Domain attempted WRMSR 00000277 from
00000501:00070406
> > to 00070106:00070106.
> > 
> > 
> > My grub.conf is:
> > 
> > title Xen(2.6.31.13)
> >     root (hd0,10)
> >     kernel /boot/xen.gz console=com1,vga com1=9600,8n1
> >     module /boot/vmlinuz-2.6.31.13 root=/dev/sda1 ro nomodeset
> 
> Was this kernel boot line the same as the previous kernel you used?
> Also, please consult the http://wiki.xensource.com/xenwiki/XenParavirtOps
> which Pasi refered to you earlier, and look in the "Are there more
debugging
> options I could enable to troubleshoot booting problems?"
> 
I wonder if "earlyprintk=xen" for the pvops dom0 kernel would help
here..
And since you seem to be using a serial console make it "earlyprintk=xen
console=hvc0"

-- Pasi


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

Konrad Rzeszutek Wilk

2010-May-03 17:38 UTC

head link

Re: [Xen-devel] Scrubbing free ram

> > Was this kernel boot line the same as the previous kernel you used?
> > Also, please consult the
http://wiki.xensource.com/xenwiki/XenParavirtOps
> > which Pasi refered to you earlier, and look in the "Are there
more debugging
> > options I could enable to troubleshoot booting problems?"
> > 
> 
> I wonder if "earlyprintk=xen" for the pvops dom0 kernel would
help here..
The ''debug'' by itself makes Linux print by majority most of
the
warnings/errors/debugs. etc. So he should definitly use that.
> And since you seem to be using a serial console make it
"earlyprintk=xen console=hvc0"
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Konrad Rzeszutek Wilk

2010-May-04 17:58 UTC

head link

Re: [Xen-devel] Scrubbing free ram

On Wed, Apr 28, 2010 at 11:44:13PM +0800, BEI GUAN
wrote:> Hi,
> 
> Sorry, I can not get the boot message through XenSerialConsole now.
However,
> attached are the screenshots of the last part of boot message.
> If add "no-bootscrub" on the xen command line, the message is the
same
> except for the last line, "(XEN) Scrubbing Free RAM:". The
grub.conf is as
> following.
> 
>  title Xen-4.0 (Linux kernel 2.6.31.13)
>     root (hd0,10)
>     kernel /boot/xen-4.0.gz dom0_mem=1024M loglvl=all guest_loglvl=all
>     module /boot/vmlinuz-2.6.31.13 root=/dev/sda1 ro nomodeset
Add ''console=hvc0 debug''

Pasi mentioned what to look at:> > >>>>> Also please check this wiki page:
> > >>>>>
http://wiki.xensource.com/xenwiki/XenSerialConsole
Look in the section titled: "Setting up the serial console in
grub.conf''> > >>>>>
> > >>>>> and:
> > >>>>> http://wiki.xensource.com/xenwiki/XenParavirtOps
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Bei Guan

2010-May-05 07:00 UTC

head link

Re: [Xen-devel] Scrubbing free ram

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.


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
command "xend start", I got the error messages:

[root@localhost ~]# xend start
ERROR Internal error: Could not obtain handle on privileged command
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.

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
[  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)


Thank you for any reply.

Gavin Guan





2010/5/5 Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> On Wed, Apr 28, 2010 at 11:44:13PM +0800, BEI GUAN wrote:
> > Hi,
> >
> > Sorry, I can not get the boot message through XenSerialConsole now.
> However,
> > attached are the screenshots of the last part of boot message.
> > If add "no-bootscrub" on the xen command line, the message
is the same
> > except for the last line, "(XEN) Scrubbing Free RAM:". The
grub.conf is
> as
> > following.
> >
> >  title Xen-4.0 (Linux kernel 2.6.31.13)
> >     root (hd0,10)
> >     kernel /boot/xen-4.0.gz dom0_mem=1024M loglvl=all guest_loglvl=all
> >     module /boot/vmlinuz-2.6.31.13 root=/dev/sda1 ro nomodeset
>
> Add ''console=hvc0 debug''
>
> Pasi mentioned what to look at:
> > > >>>>> Also please check this wiki page:
> > > >>>>>
http://wiki.xensource.com/xenwiki/XenSerialConsole
>
> Look in the section titled: "Setting up the serial console in
grub.conf''
> > > >>>>>
> > > >>>>> and:
> > > >>>>>
http://wiki.xensource.com/xenwiki/XenParavirtOps
>


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

Konrad Rzeszutek Wilk

2010-May-05 14:12 UTC

head link

Re: [Xen-devel] Scrubbing free ram

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.

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

Bei Guan

2010-May-06 01:48 UTC

head link

Re: [Xen-devel] Scrubbing free ram

>
> >
> > 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?
>

Yes, I have re-install the 64-bit Fedora Core 11. My userspace is 64-bit
now.



> > 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''
>
>I don''t know why my Dom0 don''t have the two modules. But I can
find them in
the source of pvops kernel.
The error of  running the two commands as following.

[root@localhost ~]# modprobe xenfs
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong
into /etc/modprobe.d/.
FATAL: Module xenfs not found.
[root@localhost ~]# modprobe xen-evtchn
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong
into /etc/modprobe.d/.
FATAL: Module xen_evtchn not found.


> > 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''
>
>Yes, I solved this problem. However, I still can not create the PV domU. The
process of creating pv domU stopped at the
" * Restarting OpenBSD Secure Shell server sshd   ...done. "  Complete
messages is attached. My  PV config file is:

kernel = "/boot/vmlinuz-2.6.31.13"
memory = "256"
name = "ubuntu.9-04"
vif = ['''']
#dhcp = "dhcp"
disk =
[''file:/root/Xen/img/ubuntu-32/ubuntu.9-04.x86.img,xvda1,w'']
root = "/dev/xvda1 ro"
extra = ''xencons=tty''



> >
> > 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.
>


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

Bei Guan

2010-May-06 11:59 UTC

head link

Re: [Xen-devel] Scrubbing free ram

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''


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

Apparently Analagous Threads

Search for more apparently analagous threads

Xen users - Apr 2010 - Scrubbing free ram

[Xen-devel] Scrubbing free ram

Re: [Xen-devel] Scrubbing free ram

RE: [Xen-users] Re: [Xen-devel] Scrubbing free ram

Re: [Xen-users] Re: [Xen-devel] Scrubbing free ram

Re: [Xen-users] Re: [Xen-devel] Scrubbing free ram

Re: [Xen-users] Re: [Xen-devel] Scrubbing free ram

RE: [Xen-users] Re: [Xen-devel] Scrubbing free ram

Re: [Xen-users] Re: [Xen-devel] Scrubbing free ram

Re: [Xen-users] Re: [Xen-devel] Scrubbing free ram

Re: [Xen-devel] Scrubbing free ram

Re: [Xen-devel] Scrubbing free ram

Re: [Xen-devel] Scrubbing free ram

Re: [Xen-devel] Scrubbing free ram

Re: [Xen-devel] Scrubbing free ram

Re: [Xen-devel] Scrubbing free ram

Re: [Xen-devel] Scrubbing free ram

Re: [Xen-devel] Scrubbing free ram

Re: [Xen-devel] Scrubbing free ram

Re: [Xen-devel] Scrubbing free ram

Re: [Xen-devel] Scrubbing free ram

Re: [Xen-devel] Scrubbing free ram

Re: [Xen-devel] Scrubbing free ram

Re: [Xen-devel] Scrubbing free ram

Re: [Xen-devel] Scrubbing free ram

Re: [Xen-devel] Scrubbing free ram

Re: [Xen-devel] Scrubbing free ram

Apparently Analagous Threads