Scrubbing free ram

Scrubbing free ram

[ilish ilish]

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



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

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

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

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

Re: Scrubbing free ram

[Pasi Kärkkäinen]

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

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

[ilish ilish]

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



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

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

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

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

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

[Sander Eikelenboom]

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

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

[ilish ilish]

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


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

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

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

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

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

[Sander Eikelenboom]

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

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

[Sander Eikelenboom]

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

Re: Scrubbing free ram

[BEI GUAN]

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

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
>

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

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

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

Re: Scrubbing free ram

[Keir Fraser]

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

Re: Scrubbing free ram

[BEI GUAN]

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

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

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

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

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

Re: Scrubbing free ram

[Keir Fraser]

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

Re: Scrubbing free ram

[Keir Fraser]

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

Re: Scrubbing free ram

[BEI GUAN]

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

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

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

[-- Attachment #2: 1.jpg --]
[-- Type: image/jpeg, Size: 365497 bytes --]

[-- Attachment #3: 2.jpg --]
[-- Type: image/jpeg, Size: 212671 bytes --]

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

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

Re: Scrubbing free ram

[Konrad Rzeszutek Wilk]

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

Re: Scrubbing free ram

[Bei Guan]

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

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
>

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

[-- Attachment #2: error msg of starting PV DomU --]
[-- Type: application/octet-stream, Size: 15026 bytes --]

[root@localhost ubuntu-32]# xm create ubuntu.9-04.x86.xen3.cfg -c
Using config file "./ubuntu.9-04.x86.xen3.cfg".
Started domain ubuntu.9-04 (id=1)
                                 [    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 2.6.31.13 (root@localhost.localdomain) (gcc version 4.4.1 20090725 (Red Hat 4.4.1-2) (GCC) ) #1 SMP Tue May 4 18:15:12 CST 2010
[    0.000000] Command line: root=/dev/sda1 ro ip=:127.0.255.255::::eth0:dhcp 
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Centaur CentaurHauls
[    0.000000] ACPI in unprivileged domain disabled
[    0.000000] released 0 pages of unused memory
[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  Xen: 0000000000000000 - 00000000000a0000 (usable)
[    0.000000]  Xen: 00000000000a0000 - 0000000000100000 (reserved)
[    0.000000]  Xen: 0000000000100000 - 0000000010000000 (usable)
[    0.000000] DMI not present or invalid.
[    0.000000] last_pfn = 0x10000 max_arch_pfn = 0x400000000
[    0.000000] Scanning 1 areas for low memory corruption
[    0.000000] modified physical RAM map:
[    0.000000]  modified: 0000000000000000 - 0000000000001000 (usable)
[    0.000000]  modified: 0000000000001000 - 0000000000006000 (reserved)
[    0.000000]  modified: 0000000000006000 - 00000000000a0000 (usable)
[    0.000000]  modified: 00000000000a0000 - 0000000000100000 (reserved)
[    0.000000]  modified: 0000000000100000 - 0000000010000000 (usable)
[    0.000000] init_memory_mapping: 0000000000000000-0000000010000000
[    0.000000] (6 early reservations) ==> bootmem [0000000000 - 0010000000]
[    0.000000]   #0 [0000000000 - 0000001000]   BIOS data page ==> [0000000000 - 0000001000]
[    0.000000]   #1 [0001b93000 - 0001ba6000]   XEN PAGETABLES ==> [0001b93000 - 0001ba6000]
[    0.000000]   #2 [0000006000 - 0000008000]       TRAMPOLINE ==> [0000006000 - 0000008000]
[    0.000000]   #3 [0001000000 - 0001aef1f4]    TEXT DATA BSS ==> [0001000000 - 0001aef1f4]
[    0.000000]   #4 [0001b10000 - 0001b93000]   XEN START INFO ==> [0001b10000 - 0001b93000]
[    0.000000]   #5 [0000008000 - 0000074000]          PGTABLE ==> [0000008000 - 0000074000]
[    0.000000] Zone PFN ranges:
[    0.000000]   DMA      0x00000000 -> 0x00001000
[    0.000000]   DMA32    0x00001000 -> 0x00100000
[    0.000000]   Normal   0x00100000 -> 0x00100000
[    0.000000] Movable zone start PFN for each node
[    0.000000] early_node_map[3] active PFN ranges
[    0.000000]     0: 0x00000000 -> 0x00000001
[    0.000000]     0: 0x00000006 -> 0x000000a0
[    0.000000]     0: 0x00000100 -> 0x00010000
[    0.000000] SMP: Allowing 1 CPUs, 0 hotplug CPUs
[    0.000000] No local APIC present
[    0.000000] APIC: disable apic facility
[    0.000000] PM: Registered nosave memory: 0000000000001000 - 0000000000006000
[    0.000000] PM: Registered nosave memory: 00000000000a0000 - 0000000000100000
[    0.000000] Allocating PCI resources starting at 10000000 (gap: 10000000:f0000000)
[    0.000000] NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:1 nr_node_ids:1
[    0.000000] PERCPU: Allocated 22 4k pages, static data 88160 bytes
[    0.000000] Xen: using vcpu_info placement
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 64428
[    0.000000] Kernel command line: root=/dev/sda1 ro ip=:127.0.255.255::::eth0:dhcp 
[    0.000000] PID hash table entries: 1024 (order: 10, 8192 bytes)
[    0.000000] Dentry cache hash table entries: 32768 (order: 6, 262144 bytes)
[    0.000000] Inode-cache hash table entries: 16384 (order: 5, 131072 bytes)
[    0.000000] Initializing CPU#0
[    0.000000] Checking aperture...
[    0.000000] No AGP bridge found
[    0.000000] Memory: 245060k/262144k available (5739k kernel code, 404k absent, 16376k reserved, 3763k data, 572k init)
[    0.000000] SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS:4352 nr_irqs:256
[    0.000000] Detected 2660.072 MHz processor.
[    0.000999] Console: colour dummy device 80x25
[    0.000999] console [tty0] enabled
[    0.000999] console [hvc0] enabled
[    0.000999] installing Xen timer for CPU 0
[    0.000999] xen: vcpu_time_info placement not supported
[    0.000999] Calibrating delay loop (skipped), value calculated using timer frequency.. 5320.14 BogoMIPS (lpj=2660072)
[    0.000999] Security Framework initialized
[    0.000999] SELinux:  Initializing.
[    0.000999] Mount-cache hash table entries: 256
[    0.000999] Initializing cgroup subsys ns
[    0.000999] Initializing cgroup subsys cpuacct
[    0.000999] Initializing cgroup subsys freezer
[    0.000999] CPU: L1 I cache: 32K, L1 D cache: 32K
[    0.000999] CPU: L2 cache: 3072K
[    0.000999] CPU: Unsupported number of siblings 4
[    0.000999] Performance Counters: unsupported p6 CPU model 23 no PMU driver, software counters only.
[    0.000999] SMP alternatives: switching to UP code
[    0.001059] Freeing SMP alternatives: 39k freed
[    0.001247] cpu 0 spinlock event irq 254
[    0.001620] Brought up 1 CPUs
[    0.003047] Booting paravirtualized kernel on Xen
[    0.003063] Xen version: 4.0.0 (preserve-AD)
[    0.003666] Grant tables using version 2 layout.
[    0.003701] Grant table initialized
[    0.023388] Time: 165:165:165  Date: 165/165/65
[    0.023631] NET: Registered protocol family 16
[    0.024763] xenbus_probe wake_waiting
[    0.024789] xenbus_probe_init ok
[    0.026995] PCI: setting up Xen PCI frontend stub
[    0.064982] bio: create slab <bio-0> at 0
[    0.065493] ACPI: Interpreter disabled.
[    0.066224] xenbus_probe_backend_init bus registered ok
[    0.066241] xenbus_probe_devices backend
[    0.067113] xenbus_probe_devices failed xenbus_directory
[    0.067113] backend_probe_and_watch devices probed ok
[    0.067113] backend_probe_and_watch watch add ok ok
[    0.067113] backend_probe_and_watch all done
[    0.067266] xenbus_probe_frontend_init bus registered ok
[    0.067282] xenbus_probe_devices device
[    0.067304] xenbus_probe_devices 1/3 vbd
[    0.067304] xenbus_probe_device_type type vbd
[    0.068052] xenbus_probe_device_type 1/1 2049
[    0.068247] xenbus_probe_device_type done
[    0.068262] xenbus_probe_devices 2/3 vif
[    0.068276] xenbus_probe_device_type type vif
[    0.068299] xenbus_probe_device_type 1/1 0
[    0.068299] xenbus_probe_device_type done
[    0.068299] xenbus_probe_devices 3/3 console
[    0.068299] xenbus_probe_device_type type console
[    0.068299] xenbus_probe_device_type 1/1 0
[    0.069190] xenbus_probe_device_type done
[    0.069205] xenbus_probe_devices done
[    0.069219] frontend_probe_and_watch devices probed ok
[    0.069245] frontend_probe_and_watch watch add ok ok
[    0.069245] frontend_probe_and_watch all done
[    0.069245] xen_balloon: Initialising balloon driver with page order 0.
[    0.070756] SCSI subsystem initialized
[    0.072096] usbcore: registered new interface driver usbfs
[    0.072304] usbcore: registered new interface driver hub
[    0.072564] usbcore: registered new device driver usb
[    0.073828] PCI: System does not support PCI
[    0.073845] PCI: System does not support PCI
[    0.074882] cfg80211: Using static regulatory domain info
[    0.074899] cfg80211: Regulatory domain: US
[    0.074913] 	(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[    0.074929] 	(2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
[    0.074988] 	(5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[    0.074988] 	(5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[    0.074988] 	(5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[    0.074988] 	(5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[    0.074988] 	(5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[    0.075093] cfg80211: Calling CRDA for country: US
[    0.075283] NetLabel: Initializing
[    0.075298] NetLabel:  domain hash size = 128
[    0.075312] NetLabel:  protocols = UNLABELED CIPSOv4
[    0.075349] NetLabel:  unlabeled traffic allowed by default
[    0.076598] Xen: Initializing Xen DMA ops
[    0.083723] pnp: PnP ACPI: disabled
[    0.086882] NET: Registered protocol family 2
[    0.087610] IP route cache hash table entries: 2048 (order: 2, 16384 bytes)
[    0.089821] TCP established hash table entries: 8192 (order: 5, 131072 bytes)
[    0.089872] TCP bind hash table entries: 8192 (order: 5, 131072 bytes)
[    0.089918] TCP: Hash tables configured (established 8192 bind 8192)
[    0.089936] TCP reno registered
[    0.090329] NET: Registered protocol family 1
[    0.090585] kvm: no hardware support
[    0.090602] has_svm: not amd
[    0.090616] kvm: no hardware support
[    0.091549] platform rtc_cmos: registered platform RTC device (no PNP device found)
[    0.093437] microcode: no support for this CPU vendor
[    0.093454] Scanning for low memory corruption every 60 seconds
[    0.094588] audit: initializing netlink socket (disabled)
[    0.094623] type=2000 audit(1273071195.128:1): initialized
[    0.102342] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[    0.116352] VFS: Disk quotas dquot_6.5.2
[    0.116980] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.121526] msgmni has been set to 479
[    0.124490] alg: No test for stdrng (krng)
[    0.124999] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[    0.125066] io scheduler noop registered
[    0.125082] io scheduler anticipatory registered
[    0.125099] io scheduler deadline registered
[    0.125141] io scheduler cfq registered (default)
[    0.125700] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[    0.126892] Event-channel device installed.
[    0.131336] blktap_device_init: blktap device major 253
[    0.131367] blktap_ring_init: blktap ring major: 251
[    0.132747] registering netback
[    0.150594] Non-volatile memory driver v1.3
[    0.150665] Linux agpgart interface v0.103
[    0.151137] [drm] Initialized drm 1.1.0 20060810
[    0.151205] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    0.162465] brd: module loaded
[    0.167232] loop: module loaded
[    0.170755] input: Macintosh mouse button emulation as /devices/virtual/input/input0
[    0.174839] Intel(R) PRO/1000 Network Driver - version 7.3.21-k3-NAPI
[    0.174859] Copyright (c) 1999-2006 Intel Corporation.
[    0.175095] blkfront: xvda1: barriers enabled
[    0.175351] e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2
[    0.175368] e1000e: Copyright (c) 1999-2008 Intel Corporation.
[    0.176309] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
[    0.176326] e100: Copyright(c) 1999-2006 Intel Corporation
[    0.177196] sky2 driver version 1.23
[    0.177567] Initialising Xen virtual ethernet driver.
[    0.182480] console [netcon0] enabled
[    0.182501] netconsole: network logging started
[    0.182516] Fusion MPT base driver 3.04.10
[    0.182530] Copyright (c) 1999-2008 LSI Corporation
[    0.182578] Fusion MPT FC Host driver 3.04.10
[    0.182772] Fusion MPT misc device (ioctl) driver 3.04.10
[    0.183136] mptctl: Registered with Fusion MPT base driver
[    0.183152] mptctl: /dev/mptctl @ (major,minor=10,220)
[    0.184353] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    0.274700] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    0.274979] uhci_hcd: USB Universal Host Controller Interface driver
[    0.275835] usbcore: registered new interface driver usblp
[    0.275856] Initializing USB Mass Storage driver...
[    0.276327] usbcore: registered new interface driver usb-storage
[    0.276347] USB Mass Storage support registered.
[    0.276809] usbcore: registered new interface driver libusual
[    0.278371] PNP: No PS/2 controller found. Probing ports directly.
[    0.279012] i8042.c: No controller found.
[    0.279809] mice: PS/2 mouse device common for all mice
[    0.281338] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0
[    0.283587] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com
[    0.283965] cpuidle: using governor ladder
[    0.283981] cpuidle: using governor menu
[    0.289600] usbcore: registered new interface driver hiddev
[    0.289798] usbcore: registered new interface driver usbhid
[    0.289819] usbhid: v2.6:USB HID core driver
[    0.290166] Advanced Linux Sound Architecture Driver Version 1.0.20.
[    0.292325] ALSA device list:
[    0.292341]   No soundcards found.
[    0.292523] Netfilter messages via NETLINK v0.30.
[    0.292580] nf_conntrack version 0.5.0 (1996 buckets, 7984 max)
[    0.293952] ctnetlink v0.93: registering with nfnetlink.
[    0.301812] ip_tables: (C) 2000-2006 Netfilter Core Team
[    0.301855] TCP cubic registered
[    0.301870] Initializing XFRM netlink socket
[    0.303000] NET: Registered protocol family 10
[    0.317809] ip6_tables: (C) 2000-2006 Netfilter Core Team
[    0.318300] IPv6 over IPv4 tunneling driver
[    0.326894] NET: Registered protocol family 17
[    0.328758] RPC: Registered udp transport module.
[    0.328776] RPC: Registered tcp transport module.
[    0.329632] registered taskstats version 1
[    0.329683] XENBUS: Device with no driver: device/console/0
[    0.329724]   Magic number: 1:252:3141
[    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


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

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

Re: Scrubbing free ram

[Konrad Rzeszutek Wilk]

On Wed, May 05, 2010 at 03:00:42PM +0800, Bei Guan wrote:
> Hi, Konrad,
> 
> Thank you for your reply.
> 
> I think it is hard to solve the problem of installing xen4.0 on
> fedora11_x86-32bit. Because everytime I install xen4.0 and reboot, my screen
> stopped at the below messages and did not to print anything.
> 
> (XEN) traps.c:2309:d0 Domain attempted WRMSR 000002ff from 00000000:00000c06
> > to 00000000:00000000.

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

xen-4.0.gz dom0_mem=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.

Re: Scrubbing free ram

[Bei Guan]

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

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

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

[-- Attachment #2: message of creating pv DomU --]
[-- Type: application/octet-stream, Size: 15925 bytes --]

[root@localhost ubuntu-32]# xm create ubuntu.9-04.x86.xen3.cfg -c
Using config file "./ubuntu.9-04.x86.xen3.cfg".
Started domain ubuntu.9-04 (id=1)
                                 [    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 2.6.31.13 (root@localhost.localdomain) (gcc version 4.4.1 20090725 (Red Hat 4.4.1-2) (GCC) ) #1 SMP Tue May 4 18:15:12 CST 2010
[    0.000000] Command line: root=/dev/xvda1 ro xencons=tty
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Centaur CentaurHauls
[    0.000000] ACPI in unprivileged domain disabled
[    0.000000] released 0 pages of unused memory
[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  Xen: 0000000000000000 - 00000000000a0000 (usable)
[    0.000000]  Xen: 00000000000a0000 - 0000000000100000 (reserved)
[    0.000000]  Xen: 0000000000100000 - 0000000010000000 (usable)
[    0.000000] DMI not present or invalid.
[    0.000000] last_pfn = 0x10000 max_arch_pfn = 0x400000000
[    0.000000] Scanning 1 areas for low memory corruption
[    0.000000] modified physical RAM map:
[    0.000000]  modified: 0000000000000000 - 0000000000001000 (usable)
[    0.000000]  modified: 0000000000001000 - 0000000000006000 (reserved)
[    0.000000]  modified: 0000000000006000 - 00000000000a0000 (usable)
[    0.000000]  modified: 00000000000a0000 - 0000000000100000 (reserved)
[    0.000000]  modified: 0000000000100000 - 0000000010000000 (usable)
[    0.000000] init_memory_mapping: 0000000000000000-0000000010000000
[    0.000000] (6 early reservations) ==> bootmem [0000000000 - 0010000000]
[    0.000000]   #0 [0000000000 - 0000001000]   BIOS data page ==> [0000000000 - 0000001000]
[    0.000000]   #1 [0001b93000 - 0001ba6000]   XEN PAGETABLES ==> [0001b93000 - 0001ba6000]
[    0.000000]   #2 [0000006000 - 0000008000]       TRAMPOLINE ==> [0000006000 - 0000008000]
[    0.000000]   #3 [0001000000 - 0001aef1f4]    TEXT DATA BSS ==> [0001000000 - 0001aef1f4]
[    0.000000]   #4 [0001b10000 - 0001b93000]   XEN START INFO ==> [0001b10000 - 0001b93000]
[    0.000000]   #5 [0000008000 - 0000074000]          PGTABLE ==> [0000008000 - 0000074000]
[    0.000000] Zone PFN ranges:
[    0.000000]   DMA      0x00000000 -> 0x00001000
[    0.000000]   DMA32    0x00001000 -> 0x00100000
[    0.000000]   Normal   0x00100000 -> 0x00100000
[    0.000000] Movable zone start PFN for each node
[    0.000000] early_node_map[3] active PFN ranges
[    0.000000]     0: 0x00000000 -> 0x00000001
[    0.000000]     0: 0x00000006 -> 0x000000a0
[    0.000000]     0: 0x00000100 -> 0x00010000
[    0.000000] SMP: Allowing 1 CPUs, 0 hotplug CPUs
[    0.000000] No local APIC present
[    0.000000] APIC: disable apic facility
[    0.000000] PM: Registered nosave memory: 0000000000001000 - 0000000000006000
[    0.000000] PM: Registered nosave memory: 00000000000a0000 - 0000000000100000
[    0.000000] Allocating PCI resources starting at 10000000 (gap: 10000000:f0000000)
[    0.000000] NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:1 nr_node_ids:1
[    0.000000] PERCPU: Allocated 22 4k pages, static data 88160 bytes
[    0.000000] Xen: using vcpu_info placement
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 64428
[    0.000000] Kernel command line: root=/dev/xvda1 ro xencons=tty
[    0.000000] PID hash table entries: 1024 (order: 10, 8192 bytes)
[    0.000000] Dentry cache hash table entries: 32768 (order: 6, 262144 bytes)
[    0.000000] Inode-cache hash table entries: 16384 (order: 5, 131072 bytes)
[    0.000000] Initializing CPU#0
[    0.000000] Checking aperture...
[    0.000000] No AGP bridge found
[    0.000000] Memory: 245060k/262144k available (5739k kernel code, 404k absent, 16376k reserved, 3763k data, 572k init)
[    0.000000] SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS:4352 nr_irqs:256
[    0.000000] Detected 2660.076 MHz processor.
[    0.000999] Console: colour dummy device 80x25
[    0.000999] console [tty0] enabled
[    0.000999] console [hvc0] enabled
[    0.000999] installing Xen timer for CPU 0
[    0.000999] xen: vcpu_time_info placement not supported
[    0.000999] Calibrating delay loop (skipped), value calculated using timer frequency.. 5320.15 BogoMIPS (lpj=2660076)
[    0.000999] Security Framework initialized
[    0.000999] SELinux:  Initializing.
[    0.000999] Mount-cache hash table entries: 256
[    0.000999] Initializing cgroup subsys ns
[    0.000999] Initializing cgroup subsys cpuacct
[    0.000999] Initializing cgroup subsys freezer
[    0.000999] CPU: L1 I cache: 32K, L1 D cache: 32K
[    0.000999] CPU: L2 cache: 3072K
[    0.000999] CPU: Unsupported number of siblings 4
[    0.000999] Performance Counters: unsupported p6 CPU model 23 no PMU driver, software counters only.
[    0.000999] SMP alternatives: switching to UP code
[    0.001820] Freeing SMP alternatives: 39k freed
[    0.001999] cpu 0 spinlock event irq 254
[    0.002370] Brought up 1 CPUs
[    0.003780] Booting paravirtualized kernel on Xen
[    0.003797] Xen version: 4.0.0 (preserve-AD)
[    0.004419] Grant tables using version 2 layout.
[    0.004454] Grant table initialized
[    0.024138] Time: 165:165:165  Date: 165/165/65
[    0.024370] NET: Registered protocol family 16
[    0.025496] xenbus_probe wake_waiting
[    0.025521] xenbus_probe_init ok
[    0.026995] PCI: setting up Xen PCI frontend stub
[    0.064990] bio: create slab <bio-0> at 0
[    0.065494] ACPI: Interpreter disabled.
[    0.066333] xenbus_probe_backend_init bus registered ok
[    0.066349] xenbus_probe_devices backend
[    0.083078] xenbus_probe_devices failed xenbus_directory
[    0.083078] backend_probe_and_watch devices probed ok
[    0.083103] backend_probe_and_watch watch add ok ok
[    0.083103] backend_probe_and_watch all done
[    0.083386] xenbus_probe_frontend_init bus registered ok
[    0.083407] xenbus_probe_devices device
[    0.083438] xenbus_probe_devices 1/3 vbd
[    0.083438] xenbus_probe_device_type type vbd
[    0.084055] xenbus_probe_device_type 1/1 51713
[    0.084297] xenbus_probe_device_type done
[    0.084317] xenbus_probe_devices 2/3 vif
[    0.084335] xenbus_probe_device_type type vif
[    0.084367] xenbus_probe_device_type 1/1 0
[    0.085067] xenbus_probe_device_type done
[    0.085087] xenbus_probe_devices 3/3 console
[    0.085106] xenbus_probe_device_type type console
[    0.085137] xenbus_probe_device_type 1/1 0
[    0.085293] xenbus_probe_device_type done
[    0.085312] xenbus_probe_devices done
[    0.085331] frontend_probe_and_watch devices probed ok
[    0.085367] frontend_probe_and_watch watch add ok ok
[    0.085367] frontend_probe_and_watch all done
[    0.085367] xen_balloon: Initialising balloon driver with page order 0.
[    0.087729] SCSI subsystem initialized
[    0.089456] usbcore: registered new interface driver usbfs
[    0.089731] usbcore: registered new interface driver hub
[    0.090121] usbcore: registered new device driver usb
[    0.091782] PCI: System does not support PCI
[    0.091803] PCI: System does not support PCI
[    0.093167] cfg80211: Using static regulatory domain info
[    0.093189] cfg80211: Regulatory domain: US
[    0.093207] 	(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[    0.093230] 	(2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
[    0.093985] 	(5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[    0.093985] 	(5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[    0.093985] 	(5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[    0.093985] 	(5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[    0.093985] 	(5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[    0.094060] cfg80211: Calling CRDA for country: US
[    0.094243] NetLabel: Initializing
[    0.094259] NetLabel:  domain hash size = 128
[    0.094273] NetLabel:  protocols = UNLABELED CIPSOv4
[    0.094308] NetLabel:  unlabeled traffic allowed by default
[    0.095514] Xen: Initializing Xen DMA ops
[    0.102618] pnp: PnP ACPI: disabled
[    0.105773] NET: Registered protocol family 2
[    0.106514] IP route cache hash table entries: 2048 (order: 2, 16384 bytes)
[    0.108734] TCP established hash table entries: 8192 (order: 5, 131072 bytes)
[    0.108789] TCP bind hash table entries: 8192 (order: 5, 131072 bytes)
[    0.108838] TCP: Hash tables configured (established 8192 bind 8192)
[    0.108856] TCP reno registered
[    0.109250] NET: Registered protocol family 1
[    0.109509] kvm: no hardware support
[    0.109526] has_svm: not amd
[    0.109540] kvm: no hardware support
[    0.110475] platform rtc_cmos: registered platform RTC device (no PNP device found)
[    0.112363] microcode: no support for this CPU vendor
[    0.112380] Scanning for low memory corruption every 60 seconds
[    0.113522] audit: initializing netlink socket (disabled)
[    0.113556] type=2000 audit(1273138381.153:1): initialized
[    0.121304] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[    0.135309] VFS: Disk quotas dquot_6.5.2
[    0.135940] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.140484] msgmni has been set to 479
[    0.143426] alg: No test for stdrng (krng)
[    0.143926] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[    0.143945] io scheduler noop registered
[    0.143961] io scheduler anticipatory registered
[    0.143977] io scheduler deadline registered
[    0.144069] io scheduler cfq registered (default)
[    0.144628] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[    0.145810] Event-channel device installed.
[    0.149759] blktap_device_init: blktap device major 253
[    0.149789] blktap_ring_init: blktap ring major: 251
[    0.150934] registering netback
[    0.168794] Non-volatile memory driver v1.3
[    0.168866] Linux agpgart interface v0.103
[    0.169333] [drm] Initialized drm 1.1.0 20060810
[    0.169401] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    0.180637] brd: module loaded
[    0.185368] loop: module loaded
[    0.189598] input: Macintosh mouse button emulation as /devices/virtual/input/input0
[    0.193358] blkfront: xvda1: barriers enabled
[    0.193982] Intel(R) PRO/1000 Network Driver - version 7.3.21-k3-NAPI
[    0.193998] Copyright (c) 1999-2006 Intel Corporation.
[    0.194555] e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2
[    0.194571] e1000e: Copyright (c) 1999-2008 Intel Corporation.
[    0.195266] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
[    0.195282] e100: Copyright(c) 1999-2006 Intel Corporation
[    0.195831] sky2 driver version 1.23
[    0.196280] Initialising Xen virtual ethernet driver.
[    0.201323] console [netcon0] enabled
[    0.201344] netconsole: network logging started
[    0.201358] Fusion MPT base driver 3.04.10
[    0.201372] Copyright (c) 1999-2008 LSI Corporation
[    0.201432] Fusion MPT FC Host driver 3.04.10
[    0.201696] Fusion MPT misc device (ioctl) driver 3.04.10
[    0.201899] mptctl: Registered with Fusion MPT base driver
[    0.201914] mptctl: /dev/mptctl @ (major,minor=10,220)
[    0.203170] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    0.203418] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    0.295160] uhci_hcd: USB Universal Host Controller Interface driver
[    0.295933] usbcore: registered new interface driver usblp
[    0.295954] Initializing USB Mass Storage driver...
[    0.296244] usbcore: registered new interface driver usb-storage
[    0.296264] USB Mass Storage support registered.
[    0.296496] usbcore: registered new interface driver libusual
[    0.297926] PNP: No PS/2 controller found. Probing ports directly.
[    0.298026] i8042.c: No controller found.
[    0.299877] mice: PS/2 mouse device common for all mice
[    0.301396] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0
[    0.303704] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com
[    0.304161] cpuidle: using governor ladder
[    0.304177] cpuidle: using governor menu
[    0.309702] usbcore: registered new interface driver hiddev
[    0.309906] usbcore: registered new interface driver usbhid
[    0.309927] usbhid: v2.6:USB HID core driver
[    0.310264] Advanced Linux Sound Architecture Driver Version 1.0.20.
[    0.312415] ALSA device list:
[    0.312431]   No soundcards found.
[    0.312609] Netfilter messages via NETLINK v0.30.
[    0.312668] nf_conntrack version 0.5.0 (1996 buckets, 7984 max)
[    0.314101] ctnetlink v0.93: registering with nfnetlink.
[    0.321893] ip_tables: (C) 2000-2006 Netfilter Core Team
[    0.321932] TCP cubic registered
[    0.321947] Initializing XFRM netlink socket
[    0.323115] NET: Registered protocol family 10
[    0.337970] ip6_tables: (C) 2000-2006 Netfilter Core Team
[    0.338464] IPv6 over IPv4 tunneling driver
[    0.347093] NET: Registered protocol family 17
[    0.348923] RPC: Registered udp transport module.
[    0.348940] RPC: Registered tcp transport module.
[    0.349796] registered taskstats version 1
[    0.349846] XENBUS: Device with no driver: device/console/0
[    0.349887]   Magic number: 1:252:3141
[    0.350101] md: Waiting for all devices to be available before autodetect
[    0.350117] md: If you don't use raid, use raid=noautodetect
[    0.350800] md: Autodetecting RAID arrays.
[    0.350815] md: Scanned 0 and added 0 devices.
[    0.350829] md: autorun ...
[    0.350842] md: ... autorun DONE.
[    0.351625] EXT3-fs: INFO: recovery required on readonly filesystem.
[    0.351647] EXT3-fs: write access will be enabled during recovery.
[    0.449953] kjournald starting.  Commit interval 5 seconds
[    0.450065] EXT3-fs: recovery complete.
[    0.450324] EXT3-fs: mounted filesystem with writeback data mode.
[    0.450385] VFS: Mounted root (ext3 filesystem) readonly on device 202:1.
[    0.451126] Freeing unused kernel memory: 572k freed
[    0.451313] Write protecting the kernel read-only data: 8544k
 * Filesystem type 'fusectl' is not supported. Skipping mount.
 * Setting preliminary keymap...                                         [ OK ] 
 * Starting kernel event manager...                                      [ OK ] 
 * Loading hardware drivers...                                           [ OK ] 
 * Loading kernel modules...                                                     * Loading manual drivers...                                                                           [ OK ] 
 * Setting kernel variables (/etc/sysctl.conf)...                        [ OK ] 
 * Setting kernel variables (/etc/sysctl.d/10-console-messages.conf)...  [ OK ] 
 * Setting kernel variables (/etc/sysctl.d/10-network-security.conf)...  [ OK ] 
 * Activating swap...                                                    [ OK ] 
 * Checking file systems...                                                     fsck 1.41.4 (27-Jan-2009)
                                                                         [ OK ]
 * Mounting local filesystems...                                                [mntent]: warning: no final newline at the end of /etc/fstab
                                                                         [ OK ]
 * Activating swapfile swap...                                           [ OK ] 
 * Configuring network interfaces...                                     [ OK ] 
 * Setting up console font and keymap...                                 [ OK ] 
 * Starting system log daemon...                                         [ OK ] 
 * Starting kernel log daemon...                                         [ OK ] 
 * Starting OpenBSD Secure Shell server sshd                             [ OK ] 
 * Restarting OpenBSD Secure Shell server sshd
   ...done.



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

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

Re: Scrubbing free ram

[Bei Guan]

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

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

> On Wed, May 05, 2010 at 03:00:42PM +0800, Bei Guan wrote:
> > Hi, Konrad,
> >
> > Thank you for your reply.
> >
> > I think it is hard to solve the problem of installing xen4.0 on
> > fedora11_x86-32bit. Because everytime I install xen4.0 and reboot, my
> screen
> > stopped at the below messages and did not to print anything.
> >
> > (XEN) traps.c:2309:d0 Domain attempted WRMSR 000002ff from
> 00000000:00000c06
> > > to 00000000:00000000.
>
> Right. And if you used the Linux and Xen kernel command line options to
> enable more debug option that Pasi and I've pointed you to
> you would have seen more. They are in
> http://wiki.xensource.com/xenwiki/XenParavirtOps under the section
> titled "Are there more debugging options I could enable to troubleshoot
> booting problems?" where it gives you an example:
>
> xen-4.0.gz dom0_mem=1024M loglvl=all guest_loglvl=all sync_console
> console_to_ring com1=115200,8n1 console=com1 lapic=debug
> apic_verbosity=debug apic=debug iommu=off
>
> vmlinuz-2.6.32.9 ro root=/dev/vg00/lv01 console=hvc0 earlyprintk=xen
> nomodeset initcall_debug debug loglevel=10
>
> >
> >
> >
> > Now, I change my domain0 OS to fedora11_x86-64bit and I can successfully
> > install the xen 4.0. However I have another problem. When I running the
>
> So you solved your problem by building the 64-bit Dom0. Is your
> userspace 64-bit or is it 32-bit? When you say 'change my domain0' was
> that a re-install of Fedora Core 11?
>
> > command "xend start", I got the error messages:
> >
> > [root@localhost ~]# xend start
> > ERROR Internal error: Could not obtain handle on privileged command
>
> Run 'modprobe xenfs' and 'modprobe xen-evtchn'
>
> > interface (2 = No such file or directory)
> > Traceback (most recent call last):
> >   File "/usr/sbin/xend", line 36, in <module>
> >     from xen.xend.server import SrvDaemon
> >   File "usr/lib64/python2.6/site-packages/xen/xend/server/SrvDaemon.py",
> > line 26, in <module>
> >   File "usr/lib64/python2.6/site-packages/xen/xend/server/relocate.py",
> line
> > 28, in <module>
> >   File "usr/lib64/python2.6/site-packages/xen/xend/XendDomain.py", line
> 36,
> > in <module>
> >   File "usr/lib64/python2.6/site-packages/xen/xend/XendCheckpoint.py",
> line
> > 20, in <module>
> >   File "usr/lib64/python2.6/site-packages/xen/xend/image.py", line 46, in
> > <module>
> > xen.lowlevel.xc.Error: (1, 'Internal error', 'Could not obtain handle on
> > privileged command interface (2 = No such file or directory)')
> >
> > I googled the problem and found it seems to be a bug, which refered here:
> > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1436
> >
> >
> >
> > If I running another command "/etc/init.d/xend start", it can
> successfully
> > start the xend service. But I can not create a PV DomU or HVM DomU. The
> > error message as following.
>
> That one is fairly easy. You don't have the right 'root' entry for your
> guest (you are missing the right root="/dev/<something, something>").
>
> It looks to be that you are trying to do '/dev/sda1' but since you
> changed your disk=['...'] entry to have 'xvda', it should be
> '/dev/xvda1'
>
> >
> > 1. Error of starting a PV DomU
> > [root@localhost ubuntu-32]# xm create ubuntu.9-04.x86.xen3.cfg -c
> > ……  ……
> > [    1.831122] Sending DHCP requests ...
> > [   14.320061] ... timed out!
> > [   75.986391] IP-Config: Reopening network devices...
> > [   77.488086] Sending DHCP requests ...
> > [   93.965059] ... timed out!
> > [  165.740440] IP-Config: Auto-configuration of network failed.
> > [  165.740565] md: Waiting for all devices to be available before
> autodetect
> > [  165.740587] md: If you don't use raid, use raid=noautodetect
> > [  165.741555] md: Autodetecting RAID arrays.
> > [  165.741577] md: Scanned 0 and added 0 devices.
> > [  165.741596] md: autorun ...
> > [  165.741614] md: ... autorun DONE.
> > [  165.741921] Root-NFS: No NFS server available, giving up.
> > [  165.741984] VFS: Unable to mount root fs via NFS, trying floppy.
> > [  165.742429] VFS: Cannot open root device "sda1" or unknown-block(2,0)
> > [  165.742452] Please append a correct "root=" boot option; here are the
> > available partitions:
> > [  165.742529] ca01         1025024 xvda1 driver: vbd
>
>                                      ^^^^ - use that one instead of
> sda1
>
> > [  165.742566] Kernel panic - not syncing: VFS: Unable to mount root fs
> on
> > unknown-block(2,0)
> > [  165.742590] Pid: 1, comm: swapper Not tainted 2.6.31.13 #1
> > [  165.742610] Call Trace:
> > [  165.742642]  [<ffffffff81591fd2>] panic+0x75/0x130
> > [  165.742674]  [<ffffffff8195fafe>] mount_block_root+0x1ce/0x1e5
> > [  165.742705]  [<ffffffff8195fb80>] mount_root+0x6b/0x8b
> > [  165.742734]  [<ffffffff8195fd10>] prepare_namespace+0x170/0x19d
> > [  165.742765]  [<ffffffff8195efc0>] kernel_init+0x1b5/0x1c5
> > [  165.742797]  [<ffffffff81033dea>] child_rip+0xa/0x20
> > [  165.742827]  [<ffffffff81032fa7>] ? int_ret_from_sys_call+0x7/0x1b
> > [  165.742858]  [<ffffffff8103375d>] ? retint_restore_args+0x5/0x6
> > [  165.742889]  [<ffffffff81033de0>] ? child_rip+0x0/0x20
> >
> > (Attached is the complete messages)
> >
> > 2. Error of starting a HVM DomU
> > [root@localhost windowsxp]# xm create winxp2_xen4.hvm
> > Using config file "./winxp2_xen4.hvm".
> > Error: Domain 'WinXP_HVMDomain' does not exist.
> >
> > ("WinXP_HVMDomain" is my HVM DomU name)
>
> No idea without cranking up some debug options. Look up
> http://wiki.xensource.com/xenwiki/XenParavirtOps at the debug option.
>


I have solved the problem about creating a HVM DomU just by adding
"CONFIG_TUN=m" in the kernel config file and rebuild the linux kernel.

The detail error about creating a hvm domU, which is in the file
/var/log/xen/qemu-dm-WinXP_HVMDomain.log, is listed as below.

[root@localhost xen]# cat qemu-dm-WinXP_HVMDomain.log
domid: 2
warning: could not open /dev/net/tun: no virtual network emulation
Could not initialize device 'tap'

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

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

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

Re: Scrubbing free ram

[Bei Guan]

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

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

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

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

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

Re: Scrubbing free ram

[Keir Fraser]

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

Re: Scrubbing free ram

[Konrad Rzeszutek Wilk]

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

Re: Scrubbing free ram

[Pasi Kärkkäinen]

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

Re: Scrubbing free ram

[Konrad Rzeszutek Wilk]

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

Re: Scrubbing free ram

[Gerry Reno]

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