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

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

To: "Teo En Ming" <enming.teo@xxxxxxxxxxxxxxx>, "Sander Eikelenboom" <linux@xxxxxxxxxxxxxx>
From: "Teo En Ming" <enming.teo@xxxxxxxxxxxxxxx>
Date: Fri, 24 Jul 2009 02:43:31 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 23 Jul 2009 11:55:49 -0700
List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi Sander,

Switching back to pv_grub, I get:

    GNU GRUB version 0.97 (2097152K lower / 0K upper memory)

       [ Minimal BASH-like line editing is supported.   For
         the   first   word, TAB lists possible command
         completions. Anywhere else TAB lists the possible
         completions of a device/filename. ]

grubdom>

grubdom> find menu.lst

Error 15: File not found

grubdom>

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

Technical Support Engineer

Information Technology Department
Asiasoft Online Pte Ltd
Tampines Central 1 #04-01 Tampines Plaza
Singapore 529541

Republic of Singapore
Mobile Phone: +65-9648-9798
MSN: teoenming@xxxxxxxxxxx

-----Original Message-----
From: "Teo En Ming" <enming.teo@xxxxxxxxxxxxxxx>
To: "Teo En Ming" <enming.teo@xxxxxxxxxxxxxxx>, "Sander Eikelenboom" <linux@xxxxxxxxxxxxxx>
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Date: Fri, 24 Jul 2009 02:24:39 +0800
Subject: Re: Re[8]: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel

Hi Sander,

Using pygrub, I started my guest domain and I got this in /var/log/xen/xend.log:

[2009-07-24 02:24:13 6122] DEBUG (XendDomainInfo:92) XendDomainInfo.create(['vm', ['name', 'ga-nfs'], ['memory', 2048], ['vcpus', 2], ['on_xend_start', 'ignore'], ['on_xend_stop', 'ignore'], ['bootloader', '/usr/bin/pygrub'], ['bootloader_args', '-q'], ['image', ['linux', ['videoram', 4]]], ['s3_integrity', 1], ['device', ['vbd', ['uname', 'file:/home/enming/ga-nfs.img'],['dev', 'xvda'], ['mode', 'w']]], ['device', ['vif', ['bridge', 'eth0']]], ['device', ['vkbd']], ['device', ['vfb', ['vnc', '1'], ['display', ':0.0'], ['xauthority', '/root/.xauthWI0zdY']]]])
[2009-07-24 02:24:13 6122] DEBUG (XendDomainInfo:2296) XendDomainInfo.constructDomain
[2009-07-24 02:24:13 6122] DEBUG (balloon:166) Balloon: 2105420 KiB free; need 4096; done.
[2009-07-24 02:24:13 6122] DEBUG (XendDomain:452) Adding Domain: 31
[2009-07-24 02:24:13 6122] DEBUG (XendDomainInfo:2497) XendDomainInfo.initDomain: 31 256
[2009-07-24 02:24:13 14519] DEBUG (XendBootloader:113) Launching bootloader as ['/usr/bin/pygrub', '--output=/var/run/xend/boot/xenbl.18551', '-q', '/home/enming/ga-nfs.img'].
[2009-07-24 02:25:48 6122] DEBUG (XendDomainInfo:2724) XendDomainInfo.destroy: domid=31
[2009-07-24 02:25:48 6122] DEBUG (XendDomainInfo:2204) No device model
[2009-07-24 02:25:48 6122] DEBUG (XendDomainInfo:2206) Releasing devices

I had to manually destroy the guest domain.

Here is my xend-debug.log:

Xend started at Thu Jul 23 18:21:02 2009.
/usr/lib/python2.6/site-packages/xen/xend/XendAPI.py:544: DeprecationWarning: object.__new__() takes no parameters
return object.__new__(cls, *args, **kwds)
Xend started at Thu Jul 23 19:31:23 2009.
/usr/lib/python2.6/site-packages/xen/xend/XendAPI.py:544: DeprecationWarning: object.__new__() takes no parameters
return object.__new__(cls, *args, **kwds)
ERROR Invalid kernel: xc_dom_find_loader: no loader found

My "xm dmesg" output is:

__ __            _____ _ _    _             ___
\ \/ /___ _ __   |___ /| || | / |   _ __ ___( _ )
\ // _ \ '_ \    |_ \| || |_ | |__| '__/ __/ _ \
/ \ __/ | | | ___) |__   _|| |__| | | (_| (_) |
/_/\_\___|_| |_| |____(_) |_|(_)_| |_| \___\___/

(XEN) Xen version 3.4.1-rc8 (root@site) (gcc version 4.3.2 [gcc-4_3-branch revision 141291] (SUSE Linux) ) Wed Jul 22 17:26:11 SGT 2009
(XEN) Latest ChangeSet: Mon Jul 20 12:40:56 2009 +0100 19699:5fd322b3f9be
(XEN) Command line:
(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 - 000000000009e800 (usable)
(XEN) 000000000009e800 - 00000000000a0000 (reserved)
(XEN) 00000000000f0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000cfe90000 (usable)
(XEN) 00000000cfe90000 - 00000000cfee3000 (ACPI NVS)
(XEN) 00000000cfee3000 - 00000000cfef0000 (ACPI data)
(XEN) 00000000cfef0000 - 00000000cff00000 (reserved)
(XEN) 00000000e0000000 - 00000000f0000000 (reserved)
(XEN) 00000000fec00000 - 0000000100000000 (reserved)
(XEN) System RAM: 3326MB (3406008kB)
(XEN) ACPI: RSDP 000F97A0, 0024 (r2 DELL )
(XEN) ACPI: XSDT CFEE3080, 005C (r1 DELL    FX09    42302E31 AWRD        0)
(XEN) ACPI: FACP CFEE7200, 00F4 (r3 DELL    FX09    42302E31 AWRD        0)
(XEN) ACPI: DSDT CFEE3200, 3FFC (r1 DELL   AWRDACPI     1000 MSFT 3000000)
(XEN) ACPI: FACS CFE90000, 0040
(XEN) ACPI: HPET CFEE73C0, 0038 (r1 DELL    FX09    42302E31 AWRD       98)
(XEN) ACPI: MCFG CFEE7400, 003C (r1 DELL    FX09    42302E31 AWRD        0)
(XEN) ACPI: SLIC CFEE7440, 0176 (r1 DELL    FX09    42302E31 AWRD        0)
(XEN) ACPI: DMY2 CFEE75C0, 0080 (r1 DELL    FX09    42302E31 AWRD        0)
(XEN) ACPI: APIC CFEE7300, 0084 (r1 DELL    FX09    42302E31 AWRD        0)
(XEN) ACPI: SSDT CFEE7CA0, 0380 (r1 PmRef    CpuPm     3000 INTL 20040311)
(XEN) Xen heap: 9MB (9744kB)
(XEN) Domain heap initialised
(XEN) Processor #0 6:15 APIC version 20
(XEN) Processor #1 6:15 APIC version 20
(XEN) IOAPIC[0]: apic_id 4, 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 2327.535 MHz processor.
(XEN) VMX: Supported advanced features:
(XEN) - APIC MMIO access virtualisation
(XEN) - APIC TPR shadow
(XEN) - Virtual NMI
(XEN) - MSR direct-access bitmap
(XEN) HVM: VMX enabled
(XEN) CPU0: Intel(R) Core(TM)2 Duo CPU     E6550 @ 2.33GHz stepping 0b
(XEN) Booting processor 1/1 eip 8c000
(XEN) CPU1: Intel(R) Core(TM)2 Duo CPU     E6550 @ 2.33GHz stepping 0b
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) checking TSC synchronization across 2 CPUs: passed.
(XEN) Platform timer is 14.318MHz HPET
(XEN) Brought up 2 CPUs
(XEN) I/O virtualisation disabled
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen kernel: 32-bit, PAE, lsb
(XEN) Dom0 kernel: 32-bit, PAE, lsb, paddr 0x400000 -> 0xabb000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.:   000000003c000000->000000003e000000 (801554 pages to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: c0400000->c0abb000
(XEN) Init. ramdisk: c0abb000->c1579600
(XEN) Phys-Mach map: c157a000->c1890c48
(XEN) Start info:    c1891000->c189147c
(XEN) Page tables:   c1892000->c18a5000
(XEN) Boot stack:    c18a5000->c18a6000
(XEN) TOTAL:         c0000000->c1c00000
(XEN) ENTRY ADDRESS: c087e000
(XEN) Dom0 has maximum 2 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 120kB init memory.
(XEN) ioapic_guest_write: apic=0, pin=2, old_irq=0, new_irq=-1
(XEN) ioapic_guest_write: old_entry=000009f0, new_entry=00010900
(XEN) ioapic_guest_write: Attempt to remove IO-APIC pin of in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=0, old_irq=-1, new_irq=0
(XEN) ioapic_guest_write: old_entry=00010900, new_entry=000009f0
(XEN) ioapic_guest_write: Attempt to add IO-APIC pin for in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=19, old_irq=19, new_irq=19
(XEN) ioapic_guest_write: old_entry=0000a9a0, new_entry=0001a9a0
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=19, old_irq=19, new_irq=19
(XEN) ioapic_guest_write: old_entry=0000a9a0, new_entry=0001a9a0
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=23, old_irq=23, new_irq=23
(XEN) ioapic_guest_write: old_entry=0000a9b0, new_entry=0001a9b0
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=19, old_irq=19, new_irq=19
(XEN) ioapic_guest_write: old_entry=0000a9a0, new_entry=0001a9a0
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=18, old_irq=18, new_irq=18
(XEN) ioapic_guest_write: old_entry=0000a9a8, new_entry=0001a9a8
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=18, old_irq=18, new_irq=18
(XEN) ioapic_guest_write: old_entry=0000a9a8, new_entry=0001a9a8
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) mm.c:739:d3 Non-privileged (3) attempt to map I/O space 00000000
(XEN) mm.c:739:d3 Non-privileged (3) attempt to map I/O space 00000000
(XEN) mm.c:739:d3 Non-privileged (3) attempt to map I/O space 00000000
(XEN) mm.c:739:d3 Non-privileged (3) attempt to map I/O space 00000000
(XEN) mm.c:806:d3 Error getting mfn 3fff (pfn 469e) from L1 entry 0000000003fff063 for l1e_owner=3, pg_owner=32753
(XEN) mm.c:739:d3 Non-privileged (3) attempt to map I/O space 0000009f
(XEN) mm.c:739:d3 Non-privileged (3) attempt to map I/O space 000000f0
(XEN) mm.c:739:d3 Non-privileged (3) attempt to map I/O space 000000e0
(XEN) mm.c:739:d3 Non-privileged (3) attempt to map I/O space 00000000

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

Technical Support Engineer

Information Technology Department
Asiasoft Online Pte Ltd
Tampines Central 1 #04-01 Tampines Plaza
Singapore 529541

Republic of Singapore
Mobile Phone: +65-9648-9798
MSN: teoenming@xxxxxxxxxxx

-----Original Message-----
From: "Teo En Ming" <enming.teo@xxxxxxxxxxxxxxx>
To: "Sander Eikelenboom" <linux@xxxxxxxxxxxxxx>
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Date: Fri, 24 Jul 2009 02:08:13 +0800
Subject: Re: Re[8]: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel

Hi Sander,

When I switched to PV_GRUB (stubdom), I get a black screen in my vncviewer when I started my CentOS 4.7 PV guest domain. See screenshot here: http://1.bp.blogspot.com/_zzjv8MCM2sk/SmioB47zMOI/AAAAAAAAAC0/7SHkAH9w3DI/s1600-h/xen20.jpeg

When I used "xm create -c", all I see is the grubdom prompt, which probably explains the black screen.

I will now switch from pv_grub to pygrub.

My CentOS 4.7 32-bit PV guest domU config is as follows. Please see screenshots:

http://3.bp.blogspot.com/_zzjv8MCM2sk/SmioCKrY-3I/AAAAAAAAAC8/Ptba4UEBY88/s1600-h/xen21.jpeg

http://4.bp.blogspot.com/_zzjv8MCM2sk/SmioCTiIEYI/AAAAAAAAADE/LQZiRKxGEns/s1600-h/xen22.jpeg

Of particular interest is this block of statements in the menu.lst of my domU:

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/xvda2
#          initrd /initrd-version.img
#boot=/dev/xvda

I will try to check the xend.log and also the Xen kernel messages and see what shows up.

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

Technical Support Engineer

Information Technology Department
Asiasoft Online Pte Ltd
Tampines Central 1 #04-01 Tampines Plaza
Singapore 529541

Republic of Singapore
Mobile Phone: +65-9648-9798
MSN: teoenming@xxxxxxxxxxx

-----Original Message-----
From: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>
To: "Teo En Ming" <enming.teo@xxxxxxxxxxxxxxx>
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Date: Thu, 23 Jul 2009 20:09:00 +0200
Subject: Re[8]: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel

Hmm could you try without the path, so "find menu.lst" only ?

No errors in xend.log / xm dmesg / dmesg about the disk image ?

Thursday, July 23, 2009, 7:46:43 PM, you wrote:

> Hi Sander

> I tried the find command in the grubdom prompt. Here are the results.

> GNU GRUB version 0.97 (2097152K lower / 0K upper memory)

> [ Minimal BASH-like line editing is supported. For
> the first word, TAB lists possible command
> completions. Anywhere else TAB lists the possible
> completions of a device/filename. ]

grubdom>>

grubdom>> find /boot/gr
> Error 21: Selected disk does not exist

grubdom>> find /boot/grub/menu.lst

> Error 15: File not found

grubdom>> find /boot/vmlinuz
> Error 21: Selected disk does not exist

grubdom>> find /boot/vmlinuz*

> Error 15: File not found

grubdom>>

> My domU config is

> name="ga-nfs-Centos-4.7-Paravirtualized"
> memory=2048
> disk = ['file:/home/enming/ga-nfs.img,xvda,w' ]
> vif = [ 'bridge=eth0' ]
> vfb = [ 'type=vnc']
> vcpus=2
> kernel = '/usr/lib/xen/boot/pv-grub-x86_32.gz'
> extra = '(hd0,0)/boot/grub/menu.lst'

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

> Technical Support Engineer

> Information Technology Department
>
> Asiasoft Online Pte Ltd
>
> Tampines Central 1 #04-01 Tampines Plaza
>
> Singapore 529541

> Republic of Singapore
>
> Mobile Phone: +65-9648-9798
>
> MSN: teoenming@xxxxxxxxxxx

> -----Original Message-----

> From: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>

> To: "Teo En Ming" <enming.teo@xxxxxxxxxxxxxxx>

> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, jeremy.fitzhardinge@xxxxxxxxxx

> Date: Thu, 23 Jul 2009 19:45:05 +0200

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

> Hmm hard to say if things are correct, since i can't see if and how thing

> are partitioned in the .img file.

> Could be the hd(0,0) is not correct.

> You could try to find out if things are correct by using the "find" option

> from the grubdom prompt and try to find the "menu.lst" and or the

> vmlinuz........ file.

> It should return the right hd(?,?) to use.

> Thursday, July 23, 2009, 7:17:35 PM, you wrote:

>> Nope, just a grubdom prompt.

>> PV-grub config for domU is:

>> name="ga-nfs-Centos-4.7-Paravirtualized"

>> memory=2048

>> disk = ['file:/home/enming/ga-nfs.img,xvda,w' ]

>> vif = [ 'bridge=eth0' ]

>> vfb = [ 'type=vnc']

>> vcpus=2

>> kernel = '/usr/lib/xen/boot/pv-grub-x86_32.gz'

>> extra = '(hd0,0)/boot/grub/menu.lst'

>> #bootloader = "/usr/bin/pygrub"

>> Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering)

>> BEng(Hons)(Mechanical Engineering)

>> Technical Support Engineer

>> Information Technology Department

>>

>> Asiasoft Online Pte Ltd

>>

>> Tampines Central 1 #04-01 Tampines Plaza

>>

>> Singapore 529541

>> Republic of Singapore

>>

>> Mobile Phone: +65-9648-9798

>>

>> MSN: teoenming@xxxxxxxxxxx

>> -----Original Message-----

>> From: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>

>> To: "Teo En Ming" <enming.teo@xxxxxxxxxxxxxxx>

>> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, jeremy.fitzhardinge@xxxxxxxxxx

>> Date: Thu, 23 Jul 2009 19:23:41 +0200

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

>> Kernel

>> No errors/messages from grub ?

>> What is in your domU config file ?

>> Thursday, July 23, 2009, 7:06:30 PM, you wrote:

>>> I switched to using PV-Grub and used xm create -c to start the guest

>> domain.

>>> However, all I get is a grubdom prompt.

>>> Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering)

>>> BEng(Hons)(Mechanical Engineering)

>>> Technical Support Engineer

>>> Information Technology Department

>>>

>>> Asiasoft Online Pte Ltd

>>>

>>> Tampines Central 1 #04-01 Tampines Plaza

>>>

>>> Singapore 529541

>>> Republic of Singapore

>>>

>>> Mobile Phone: +65-9648-9798

>>>

>>> MSN: teoenming@xxxxxxxxxxx

>>> -----Original Message-----

>>> From: "Teo En Ming" <enming.teo@xxxxxxxxxxxxxxx>

>>> To: "Teo En Ming" <enming.teo@xxxxxxxxxxxxxxx>, "Sander Eikelenboom"

>>> <linux@xxxxxxxxxxxxxx>

>>> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, jeremy.fitzhardinge@xxxxxxxxxx

>>> Date: Fri, 24 Jul 2009 01:03:35 +0800

>>> Subject: Re: Re[2]: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's

>>> PVOPS Kernel

>>> Hi Sander

>>> I added boot to kernel and initrd in the grub config of the centos 4.7

>>> pv guest but it still doesn't work.

>>> Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering)

>>> BEng(Hons)(Mechanical Engineering)

>>> Technical Support Engineer

>>> Information Technology Department

>>>

>>> Asiasoft Online Pte Ltd

>>>

>>> Tampines Central 1 #04-01 Tampines Plaza

>>>

>>> Singapore 529541

>>> Republic of Singapore

>>>

>>> Mobile Phone: +65-9648-9798

>>>

>>> MSN: teoenming@xxxxxxxxxxx

>>> -----Original

>>> Message-----

>>>

>>> From: "Teo En Ming" <enming.teo@xxxxxxxxxxxxxxx>

>>>

>>> To: "Sander Eikelenboom" <linux@xxxxxxxxxxxxxx>

>>>

>>> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, jeremy.fitzhardinge@xxxxxxxxxx

>>>

>>> Date: Fri, 24 Jul 2009 00:44:58 +0800

>>>

>>> Subject: Re: Re[2]: [Xen-devel] Unable to Configure Xen Dom 0 in

>>> Jeremy's PVOPS Kernel

>>>

>>>

>>> Hi Sander,

>>>

>>>

>>> The grub config in the centos 4.7 pv guest was automatically added by

>>> centos installer.

>>>

>>> Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering)

>>> BEng(Hons)(Mechanical Engineering)

>>>

>>> Technical Support Engineer

>>>

>>> Information Technology Department

>>>

>>> Asiasoft Online Pte Ltd

>>>

>>> Tampines Central 1 #04-01 Tampines Plaza

>>>

>>> Singapore 529541

>>>

>>> Republic of Singapore

>>>

>>> Mobile Phone: +65-9648-9798

>>>

>>> MSN: teoenming@xxxxxxxxxxx

>>>

>>>

>>> -----Original

>>> Message-----

>>>

>>> From: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>

>>>

>>> To: "Teo En Ming" <enming.teo@xxxxxxxxxxxxxxx>

>>>

>>> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, jeremy.fitzhardinge@xxxxxxxxxx

>>>

>>> Date: Thu, 23 Jul 2009 18:40:48 +0200

>>>

>>> Subject: Re[2]: [Xen-devel] Unable to Configure Xen Dom 0 in

>>> Jeremy's PVOPS Kernel

>>>

>>>

>>>

>>> Hello Teo,

>>>

>>>

>>> Are you sure the path in your grub menu is correct ?

>>>

>>> Shouldn't you add /boot infront of vmlinuz and initrd ?

>>>

>>>

>>> Regards,

>>>

>>>

>>> Sander

>>>

>>>

>>> Thursday, July 23, 2009, 6:13:02 PM, you wrote:

>>>

>>>

>>>> Hi!!!

>>>

>>>

>>>> I have managed to install CentOS 4.7 paravirtualized guest

>>> on Xen Dom 0

>>>

>>>> Jeremy Fitzhardinge's pv_ops kernel successfully. Please

>>> see screenshots

>>>

>>>> here:

>>>

>>>>

>>>

>>
> http://teo-en-ming-aka-zhang-enming.blogspot.com/2009/07/creating-centos-47-32-bit.html
> [ http://teo-en-ming-aka-zhang-enming.blogspot.com/2009/07/creating-centos-47-32-bit.html ]

>>
> [ http://teo-en-ming-aka-zhang-enming.blogspot.com/2009/07/creating-centos-47-32-bit.html
> [ http://teo-en-ming-aka-zhang-enming.blogspot.com/2009/07/creating-centos-47-32-bit.html ]]

>>>

>>
> [ http://teo-en-ming-aka-zhang-enming.blogspot.com/2009/07/creating-centos-47-32-bit.html
> [ http://teo-en-ming-aka-zhang-enming.blogspot.com/2009/07/creating-centos-47-32-bit.html ]

>>
> [ http://teo-en-ming-aka-zhang-enming.blogspot.com/2009/07/creating-centos-47-32-bit.html
> [ http://teo-en-ming-aka-zhang-enming.blogspot.com/2009/07/creating-centos-47-32-bit.html ]]]

>>>

>>>

>>>> However, after installation of CentOS 4.7 PV, I can't

>>> start the guest

>>>

>>>> domain.

>>>

>>>

>>>> I have tried to mount/access the CentOS 4.7 guest disk

>>> image file and found

>>>

>>>> out that xenU (xen-aware) kernel and initial ramdisk

>>> images were installed.

>>>

>>>> PV Guest GRUB was also configured to boot the xenU kernel.

>>> Please see

>>>

>>>> screenshot:

>>>

>>>>

>>>

>>
> http://1.bp.blogspot.com/_zzjv8MCM2sk/SmiMcYsFzAI/AAAAAAAAACk/rYxOFDHuD00/s1600-h/xen18.jpeg
> [ http://1.bp.blogspot.com/_zzjv8MCM2sk/SmiMcYsFzAI/AAAAAAAAACk/rYxOFDHuD00/s1600-h/xen18.jpeg ]

>>
> [ http://1.bp.blogspot.com/_zzjv8MCM2sk/SmiMcYsFzAI/AAAAAAAAACk/rYxOFDHuD00/s1600-h/xen18.jpeg
> [ http://1.bp.blogspot.com/_zzjv8MCM2sk/SmiMcYsFzAI/AAAAAAAAACk/rYxOFDHuD00/s1600-h/xen18.jpeg ]]

>>>

>>
> [ http://1.bp.blogspot.com/_zzjv8MCM2sk/SmiMcYsFzAI/AAAAAAAAACk/rYxOFDHuD00/s1600-h/xen18.jpeg
> [ http://1.bp.blogspot.com/_zzjv8MCM2sk/SmiMcYsFzAI/AAAAAAAAACk/rYxOFDHuD00/s1600-h/xen18.jpeg ]

>>
> [ http://1.bp.blogspot.com/_zzjv8MCM2sk/SmiMcYsFzAI/AAAAAAAAACk/rYxOFDHuD00/s1600-h/xen18.jpeg
> [ http://1.bp.blogspot.com/_zzjv8MCM2sk/SmiMcYsFzAI/AAAAAAAAACk/rYxOFDHuD00/s1600-h/xen18.jpeg ]]]

>>>

>>>

>>>> My CentOS 4.7 PV guest domain configuration is as follows:

>>>

>>>

>>>>

>>>

>>
> http://3.bp.blogspot.com/_zzjv8MCM2sk/SmiMcrnOfEI/AAAAAAAAACs/s-xguFnf25U/s1600-h/xen19.jpeg
> [ http://3.bp.blogspot.com/_zzjv8MCM2sk/SmiMcrnOfEI/AAAAAAAAACs/s-xguFnf25U/s1600-h/xen19.jpeg ]

>>
> [ http://3.bp.blogspot.com/_zzjv8MCM2sk/SmiMcrnOfEI/AAAAAAAAACs/s-xguFnf25U/s1600-h/xen19.jpeg
> [ http://3.bp.blogspot.com/_zzjv8MCM2sk/SmiMcrnOfEI/AAAAAAAAACs/s-xguFnf25U/s1600-h/xen19.jpeg ]]

>>>

>>
> [ http://3.bp.blogspot.com/_zzjv8MCM2sk/SmiMcrnOfEI/AAAAAAAAACs/s-xguFnf25U/s1600-h/xen19.jpeg
> [ http://3.bp.blogspot.com/_zzjv8MCM2sk/SmiMcrnOfEI/AAAAAAAAACs/s-xguFnf25U/s1600-h/xen19.jpeg ]

>>
> [ http://3.bp.blogspot.com/_zzjv8MCM2sk/SmiMcrnOfEI/AAAAAAAAACs/s-xguFnf25U/s1600-h/xen19.jpeg
> [ http://3.bp.blogspot.com/_zzjv8MCM2sk/SmiMcrnOfEI/AAAAAAAAACs/s-xguFnf25U/s1600-h/xen19.jpeg ]]]

>>>

>>>

>>>> Any idea why I can't start the CentOS 4.7 PV guest after

>>> installation? Is

>>>

>>>> the guest domain configuration correct/sufficient? Please

>>> advise.

>>>

>>>

>>>> Thank you!!!

>>>

>>>

>>>> Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics

>>> Engineering)

>>>

>>>> BEng(Hons)(Mechanical Engineering)

>>>

>>>

>>>> Technical Support Engineer

>>>

>>>

>>>> Information Technology Department

>>>

>>>>

>>>

>>>> Asiasoft Online Pte Ltd

>>>

>>>>

>>>

>>>> Tampines Central 1 #04-01 Tampines Plaza

>>>

>>>>

>>>

>>>> Singapore 529541

>>>

>>>

>>>> Republic of Singapore

>>>

>>>>

>>>

>>>> Mobile Phone: +65-9648-9798

>>>

>>>>

>>>

>>>> MSN: teoenming@xxxxxxxxxxx

>>>

>>>

>>>

>>>> -----Original Message-----

>>>

>>>

>>>> From: "Teo En Ming" <enming.teo@xxxxxxxxxxxxxxx>

>>>

>>>

>>>> To: "Pasi Kärkkäinen" <pasik@xxxxxx>

>>>

>>>

>>>> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx,

>>> jeremy.fitzhardinge@xxxxxxxxxx

>>>

>>>

>>>> Date: Thu, 23 Jul 2009 19:52:23 +0800

>>>

>>>

>>>> Subject: Re: [Xen-devel] Unable to Configure Xen Dom 0 in

>>> Jeremy's PVOPS

>>>

>>>> Kernel

>>>

>>>

>>>

>>>

>>>

>>>> Dear Pasi,

>>>

>>>

>>>

>>>

>>>> Thank you!!!

>>>

>>>

>>>

>>>

>>>> I am now creating a virtual harddisk for my Xen virtual

>>> machine.

>>>

>>>> Creating a 146 GB virtual harddisk:

>>>

>>>

>>>

>>>

>>>> # dd if=/dev/zero of=/home/enming/ga-nfs.img bs=1M

>>> count=149504

>>>

>>>

>>>

>>>

>>>> I am going to run CentOS 4.7 32-bit linux on it!

>>>

>>>

>>>> Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics

>>> Engineering)

>>>

>>>> BEng(Hons)(Mechanical Engineering)

>>>

>>>

>>>> Technical Support Engineer

>>>

>>>

>>>> Information Technology Department

>>>

>>>>

>>>

>>>> Asiasoft Online Pte Ltd

>>>

>>>>

>>>

>>>> Tampines Central 1 #04-01 Tampines Plaza

>>>

>>>>

>>>

>>>> Singapore 529541

>>>

>>>

>>>> Republic of Singapore

>>>

>>>>

>>>

>>>> Mobile Phone: +65-9648-9798

>>>

>>>>

>>>

>>>> MSN: teoenming@xxxxxxxxxxx

>>>

>>>

>>>

>>>

>>>> -----Original

>>>

>>>> Message-----

>>>

>>>>

>>>

>>>> From: Pasi Kärkkäinen <pasik@xxxxxx>

>>>

>>>>

>>>

>>>> To: Teo En Ming <enming.teo@xxxxxxxxxxxxxxx>

>>>

>>>>

>>>

>>>> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx,

>>> jeremy.fitzhardinge@xxxxxxxxxx

>>>

>>>>

>>>

>>>> Date: Thu, 23 Jul 2009 13:41:28 +0300

>>>

>>>>

>>>

>>>> Subject: Re: [Xen-devel] Unable to Configure Xen Dom

>>> 0 in Jeremy's

>>>

>>>> PVOPS Kernel

>>>

>>>>

>>>

>>>

>>>>

>>>

>>>

>>>>

>>>

>>>> On Thu, Jul 23,

>>>

>>>> 2009 at 06:25:33PM +0800, Teo En Ming wrote:

>>>

>>>>

>>>

>>>>> Dear Pasi,

>>>

>>>>

>>>

>>>>>

>>>

>>>>

>>>

>>>>> I ran "mount /proc/xen" manually *after* the

>>> system booted

>>>

>>>> up, it read

>>>

>>>>

>>>

>>>>> /etc/fstab, and mounted /proc/xen

>>> successfully!!!

>>>

>>>>

>>>

>>>>>

>>>

>>>>

>>>

>>>>> Please see the last line of the following

>>> "mount" output:

>>>

>>>>

>>>

>>>>>

>>>

>>>>

>>>

>>>>> /dev/sda2 on / type ext3 (rw,acl,user_xattr)

>>>

>>>>

>>>

>>>>> /proc on /proc type proc (rw)

>>>

>>>>

>>>

>>>>> sysfs on /sys type sysfs (rw)

>>>

>>>>

>>>

>>>>> debugfs on /sys/kernel/debug type debugfs (rw)

>>>

>>>>

>>>

>>>>> udev on /dev type tmpfs (rw)

>>>

>>>>

>>>

>>>>> devpts on /dev/pts type devpts

>>> (rw,mode=0620,gid=5)

>>>

>>>>

>>>

>>>>> /dev/sda3 on /home type ext3 (rw,acl,user_xattr)

>>>

>>>>

>>>

>>>>> fusectl on /sys/fs/fuse/connections type fusectl

>>> (rw)

>>>

>>>>

>>>

>>>>> none on /proc/sys/fs/binfmt_misc type

>>> binfmt_misc (rw)

>>>

>>>>

>>>

>>>>> gvfs-fuse-daemon on /home/enming/.gvfs type

>>>

>>>> fuse.gvfs-fuse-daemon

>>>

>>>>

>>>

>>>>> (rw,nosuid,nodev,user=enming)

>>>

>>>>

>>>

>>>>> none on /proc/xen type xenfs (rw)

>>>

>>>>

>>>

>>>>>

>>>

>>>>

>>>

>>>

>>>>

>>>

>>>> Yep, now it's mounted :)

>>>

>>>>

>>>

>>>

>>>>

>>>

>>>>> It is very strange that the system did not mount

>>> /proc/xen

>>>

>>>> automatically as

>>>

>>>>

>>>

>>>>> indicated in /etc/fstab during bootup.

>>>

>>>>

>>>

>>>>>

>>>

>>>>

>>>

>>>

>>>>

>>>

>>>> Indeed.

>>>

>>>>

>>>

>>>

>>>>

>>>

>>>>> Now I am able to start xend daemon. Please see

>>>

>>>>

>>>

>>>>>

>>>

>>>>

>>>

>>
> http://2.bp.blogspot.com/_zzjv8MCM2sk/Smg7pKoH_JI/AAAAAAAAABU/TVkqEEyLzYQ/s1600-h/xen08.jpeg
> [ http://2.bp.blogspot.com/_zzjv8MCM2sk/Smg7pKoH_JI/AAAAAAAAABU/TVkqEEyLzYQ/s1600-h/xen08.jpeg ]

>>
> [ http://2.bp.blogspot.com/_zzjv8MCM2sk/Smg7pKoH_JI/AAAAAAAAABU/TVkqEEyLzYQ/s1600-h/xen08.jpeg
> [ http://2.bp.blogspot.com/_zzjv8MCM2sk/Smg7pKoH_JI/AAAAAAAAABU/TVkqEEyLzYQ/s1600-h/xen08.jpeg ]]

>>>

>>
> [ http://2.bp.blogspot.com/_zzjv8MCM2sk/Smg7pKoH_JI/AAAAAAAAABU/TVkqEEyLzYQ/s1600-h/xen08.jpeg
> [ http://2.bp.blogspot.com/_zzjv8MCM2sk/Smg7pKoH_JI/AAAAAAAAABU/TVkqEEyLzYQ/s1600-h/xen08.jpeg ]

>>
> [ http://2.bp.blogspot.com/_zzjv8MCM2sk/Smg7pKoH_JI/AAAAAAAAABU/TVkqEEyLzYQ/s1600-h/xen08.jpeg
> [ http://2.bp.blogspot.com/_zzjv8MCM2sk/Smg7pKoH_JI/AAAAAAAAABU/TVkqEEyLzYQ/s1600-h/xen08.jpeg ]]]

>>>

>>>>

>>>

>>
> [ http://2.bp.blogspot.com/_zzjv8MCM2sk/Smg7pKoH_JI/AAAAAAAAABU/TVkqEEyLzYQ/s1600-h/xen08.jpeg
> [ http://2.bp.blogspot.com/_zzjv8MCM2sk/Smg7pKoH_JI/AAAAAAAAABU/TVkqEEyLzYQ/s1600-h/xen08.jpeg ]

>>
> [ http://2.bp.blogspot.com/_zzjv8MCM2sk/Smg7pKoH_JI/AAAAAAAAABU/TVkqEEyLzYQ/s1600-h/xen08.jpeg
> [ http://2.bp.blogspot.com/_zzjv8MCM2sk/Smg7pKoH_JI/AAAAAAAAABU/TVkqEEyLzYQ/s1600-h/xen08.jpeg ]]

>>>

>>
> [ http://2.bp.blogspot.com/_zzjv8MCM2sk/Smg7pKoH_JI/AAAAAAAAABU/TVkqEEyLzYQ/s1600-h/xen08.jpeg
> [ http://2.bp.blogspot.com/_zzjv8MCM2sk/Smg7pKoH_JI/AAAAAAAAABU/TVkqEEyLzYQ/s1600-h/xen08.jpeg ]

>>
> [ http://2.bp.blogspot.com/_zzjv8MCM2sk/Smg7pKoH_JI/AAAAAAAAABU/TVkqEEyLzYQ/s1600-h/xen08.jpeg
> [ http://2.bp.blogspot.com/_zzjv8MCM2sk/Smg7pKoH_JI/AAAAAAAAABU/TVkqEEyLzYQ/s1600-h/xen08.jpeg ]]]

>>> ]

>>>

>>>

>>>>

>>>

>>>>>

>>>

>>>>

>>>

>>>>> And I can see domain 0 using the "xm list"

>>> command already!

>>>

>>>>

>>>

>>>>>

>>>

>>>>

>>>

>>>

>>>>

>>>

>>>> Congrats! :)

>>>

>>>>

>>>

>>>

>>>>

>>>

>>>>> Any ideas how to make /proc/xen automatically

>>> mounted while

>>>

>>>> booting? I

>>>

>>>>

>>>

>>>>> thought I already have the xenfs entry in

>>> /etc/fstab.

>>>

>>>>

>>>

>>>>>

>>>

>>>>

>>>

>>>>> /dev/disk/by-id/ata-ST3320620AS_9QF97Q42-part1

>>> swap

>>>

>>>> swap

>>>

>>>

>>>>

>>>

>>>>> defaults

>>>

>>>

>>>> 0 0

>>>

>>>>

>>>

>>>>> /dev/disk/by-id/ata-ST3320620AS_9QF97Q42-part2 /

>>>

>>>

>>>>

>>> ext3

>>>

>>>>

>>>

>>>>

>>>

>>>>> acl,user_xattr

>>> 1 1

>>>

>>>>

>>>

>>>>> /dev/disk/by-id/ata-ST3320620AS_9QF97Q42-part3

>>> /home

>>>

>>>> ext3

>>>

>>>

>>>>

>>>

>>>>> acl,user_xattr

>>> 1 2

>>>

>>>>

>>>

>>>>> proc

>>>

>>>

>>>> /proc

>>> proc

>>>

>>>> defaults

>>> 0

>>>

>>>>

>>>

>>>>> 0

>>>

>>>>

>>>

>>>>> sysfs

>>>

>>>

>>>> /sys

>>> sysfs

>>>

>>>> noauto

>>>

>>>

>>>> 0

>>>

>>>>

>>>

>>>>> 0

>>>

>>>>

>>>

>>>>> debugfs

>>>

>>>

>>>> /sys/kernel/debug debugfs

>>> noauto

>>>

>>>> 0

>>>

>>>>

>>>

>>>>> 0

>>>

>>>>

>>>

>>>>> devpts

>>>

>>>

>>>> /dev/pts devpts

>>>

>>>

>>>> mode=0620,gid=5 0

>>>

>>>>

>>>

>>>>> 0

>>>

>>>>

>>>

>>>>> none

>>>

>>>

>>>> /proc/xen xenfs

>>>

>>>

>>>> defaults

>>> 0

>>>

>>>>

>>>

>>>>> 0

>>>

>>>>

>>>

>>>>>

>>>

>>>>

>>>

>>>>> Seems the initscripts did not attempt to mount

>>> /proc/xen

>>>

>>>> during system

>>>

>>>>

>>>

>>>>> startup.

>>>

>>>>

>>>

>>>>>

>>>

>>>>

>>>

>>>

>>>>

>>>

>>>> That's weird.. it should be mounted automatically

>>> when it's in

>>>

>>>> fstab.

>>>

>>>>

>>>

>>>> Maybe it's because sysfs /sys is 'noauto'? Try to

>>> change that to

>>>

>>>> 'defaults'.

>>>

>>>>

>>>

>>>

>>>>

>>>

>>>>> Or should I put "mount /proc/xen" in

>>> /etc/rc.local?

>>>

>>>>

>>>

>>>>>

>>>

>>>>

>>>

>>>

>>>>

>>>

>>>> That shouldn't be necessary.

>>>

>>>>

>>>

>>>

>>>>

>>>

>>>> -- Pasi

>>>

>>>>

>>>

>>>

>>>>

>>>

>>>> _______________________________________________

>>>

>>>>

>>>

>>>> Xen-devel mailing list

>>>

>>>>

>>>

>>>> Xen-devel@xxxxxxxxxxxxxxxxxxx

>>>

>>>>

>>>

>>>> http://lists.xensource.com/xen-devel
> [http://lists.xensource.com/xen-devel]

>> [http://lists.xensource.com/xen-devel
> [http://lists.xensource.com/xen-devel]]

>>> [http://lists.xensource.com/xen-devel
> [http://lists.xensource.com/xen-devel]

>> [http://lists.xensource.com/xen-devel
> [http://lists.xensource.com/xen-devel]]]

>>>

>>>> [ http://lists.xensource.com/xen-devel
> [http://lists.xensource.com/xen-devel]

>> [http://lists.xensource.com/xen-devel
> [http://lists.xensource.com/xen-devel]]

>>> [http://lists.xensource.com/xen-devel
> [http://lists.xensource.com/xen-devel]

>> [http://lists.xensource.com/xen-devel
> [http://lists.xensource.com/xen-devel]]]]

>>>

>>>

>>>

>>>

>>> --

>>>

>>> Best regards,

>>>

>>> Sander

>>> mailto:linux@xxxxxxxxxxxxxx

>>>

>>>

>>>

>>> _______________________________________________

>>>

>>> Xen-devel mailing list

>>>

>>> Xen-devel@xxxxxxxxxxxxxxxxxxx

>>>

>>> http://lists.xensource.com/xen-devel
> [http://lists.xensource.com/xen-devel]

>> [http://lists.xensource.com/xen-devel
> [http://lists.xensource.com/xen-devel]]

>>> [http://lists.xensource.com/xen-devel
> [http://lists.xensource.com/xen-devel]

>> [http://lists.xensource.com/xen-devel
> [http://lists.xensource.com/xen-devel]]]

--
Best regards,
Sander mailto:linux@xxxxxxxxxxxxxx

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

Follow-Ups:
- Re: Re[8]: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel
  - From: Teo En Ming

References:
- Re: Re[2]: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel
  - From: Teo En Ming
- Re: Re[2]: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel
  - From: Teo En Ming
- Re[4]: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel
  - From: Sander Eikelenboom
- Re: Re[4]: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel
  - From: Teo En Ming
- Re[6]: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel
  - From: Sander Eikelenboom
- Re: Re[6]: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel
  - From: Teo En Ming
- [SPAM] Re[8]: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel
  - From: Sander Eikelenboom
- Re: Re[8]: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel
  - From: Teo En Ming
- Re: Re[8]: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel
  - From: Teo En Ming

Prev by Date: Re: Re[8]: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel
Next by Date: Re: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel
Previous by thread: Re: Re[8]: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel
Next by thread: Re: Re[8]: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel
Index(es):
- Date
- Thread