From: Zhigang Wang <zhigang.x.wang@oracle.com>
To: James Song <jsong@novell.com>
Cc: dongdong.zhang@intel.com, xen-devel@lists.xensource.com
Subject: Re: pvgrub
Date: Fri, 10 Oct 2008 15:31:13 +0800 [thread overview]
Message-ID: <48EF04C1.70503@oracle.com> (raw)
In-Reply-To: <48EF8EC20200002000005328@lucius.provo.novell.com>
James Song wrote:
> fdisk -l:
>
> Disk /dev/sda: 120.0 GB, 120034123776 bytes
> 255 heads, 63 sectors/track, 14593 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Disk identifier: 0x4b3ff212
>
> Device Boot Start End Blocks Id System
> /dev/sda1 1 10 80293+ de Dell Utility
> /dev/sda2 11 6146 49287420 7 HPFS/NTFS
> /dev/sda3 6147 6538 3148740 82 Linux swap /
> Solaris
> /dev/sda4 * 6539 14593 64701787+ f W95 Ext'd (LBA)
> /dev/sda5 11761 14593 22756041 83 Linux
> /dev/sda6 6539 11760 41945652 83 Linux
>
> Partition table entries are not in disk order
>
>
> df :
>
> /dev/sda6 41286768 29801560 9387928 77% /
> udev 529448 1048 528400 1% /dev
>
> anything wrong?
does "(hd0,5)/boot/grub/menu.lst" exist?
you can try:
grubdom>configfile (hd0,5)/boot/grub/menu.lst
because:
> Partition table entries are not in disk order
I'm not sure whether it will affect grub to determine the disk order. please
try: (hd0,4)/boot/grub/menu.lst
thanks,
zhigang
>
>
> best regards,
> -- James
>>>> "Zhang, Dongdong" <dongdong.zhang@intel.com> 08��10��10�� ���� 14:55 >>>
> James,
> if you see "grubdom>", this maybe grub can't find its config file
> Check your harddisk partition number to make sure that is correct or
> check the position of grub config file
>
>
> Regards,
> Dongdong Zhang
>
> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of James Song
> Sent: 2008��10��10�� 14:47
> To: zhigang.x.wang@oracle.com
> Cc: xen-devel@lists.xensource.com
> Subject: �� Re: [Xen-devel] about pvgrub
>
> Thank Zhigang Wang for your response. I have test pvgrub with this
> config file:
>
> #pv-config
> kernel = "/usr/lib/xen/boot/pv-grub-x86_32.gz"
> extra = "(hd0,5)/boot/grub/menu.lst"
> memory = 512
> name = "ExampleDomain"
> disk = [ 'file:/var/lib/xen/images/opensuse11-1/disk0,xvda,w' ]
> vif = [ "bridge=eth0" ]
> root = "/dev/sda5 ro"
>
> start pvgrub with "xm cr pv-config -c"
> only see the grub command line like this:
> GNU GRUB version 0.97 (524288K 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>
>
>
> what's wrong?
>
> --- Song Wei
>
>
>
> best regards,
> -- James
>>>> Zhigang Wang <zhigang.x.wang@oracle.com> 08��10��09�� ���� 19:20 >>>
> This should due to the bad virtual framebuffer support in xenfb.
>
> see bug: http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1365
>
> you can try without:
>
>> vfb = [ 'type=vnc,vnclisten=127.0.0.1,vncdisplay=1' ]
>
> zhigang
>
> James Song wrote:
>> Hi,
>> I test pvgrub on xen-3.3.0. After starting pvgrub with "xm cr
> xmexample.pv-grub", I can see nothing but qemu window. With "xm li" , I
> can see this domain is running:
>> Name ID Mem VCPUs
> State Time(s)
>> Domain-0 0 1024 2
> r----- 173.0
>> ExampleDomain 3 512 1
> r----- 18.7
>> #config file
>> kernel = "/usr/lib/xen/boot/pv-grub.gz"
>> extra = "(hd0,5)/boot/grub/menu.lst"
>> memory = 512
>> name = "ExampleDomain"
>> boot = "d"
>> disk = [ 'file:/var/lib/xen/images/opensuse11/disk0,xvda,w' ]
>> vif = [ "bridge=eth0" ]
>> vfb = [ 'type=vnc,vnclisten=127.0.0.1,vncdisplay=1' ]
>>
>>
>> #grub file
>> default 0
>> timeout 8
>> gfxmenu (hd0,5)/boot/message
>> ###Don't change this comment - YaST2 identifier: Original name: xen###
>> title Xen -- openSUSE 11.0 - 2.6.26-14
>> root (hd0,5)
>> kernel /boot/xen.gz dom0_mem=1024M
>> module /boot/vmlinuz-2.6.26-14-xen
> root=/dev/disk/by-id/scsi-SATA_ST9120823ASG_5NJ0WTL5-part6
> resume=/dev/sda3 splash=silent showopts vga=0x314
>> module /boot/initrd-2.6.26-14-xen
>>
>> ###Don't change this comment - YaST2 identifier: Original name:
> linux###
>> title openSUSE 11.0 - 2.6.25.5-1.1 (pae)
>> root (hd0,5)
>> kernel /boot/vmlinuz-2.6.25.5-1.1-pae
> root=/dev/disk/by-id/scsi-SATA_ST9120823ASG_5NJ0WTL5-part6
> resume=/dev/sda3 splash=silent showopts vga=0x314
>> initrd /boot/initrd-2.6.25.5-1.1-pae
>>
>> ###Don't change this comment - YaST2 identifier: Original name:
> failsafe###
>> title Failsafe -- openSUSE 11.0 - 2.6.25.5-1.1
>> root (hd0,5)
>> kernel /boot/vmlinuz-2.6.25.5-1.1-pae
> root=/dev/disk/by-id/scsi-SATA_ST9120823ASG_5NJ0WTL5-part6 showopts
> ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off
> x11failsafe vga=0x314
>> initrd /boot/initrd-2.6.25.5-1.1-pae
>>
>>
>> the messge " xm dmesg", from the message , it's seems that hvmdom
> have not running.
>>
>> (XEN) Xen version 3.3.0_18314_02-5 (james@site) (gcc version 4.3.1
> 20080507 (prerelease) [gcc-4_3-branch revision 135036] (SUSE Linux) )
> Wed Oct 8 11:55:57 CST 2008
>> (XEN) Latest ChangeSet: 18314
>> (XEN) Command line: dom0_mem=1024M
>> (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 - 000000000009f000 (usable)
>> (XEN) 000000000009f000 - 00000000000a0000 (reserved)
>> (XEN) 0000000000100000 - 000000007f65b800 (usable)
>> (XEN) 000000007f65b800 - 0000000080000000 (reserved)
>> (XEN) 00000000f8000000 - 00000000fc000000 (reserved)
>> (XEN) 00000000fec00000 - 00000000fec10000 (reserved)
>> (XEN) > (XEN) 00000000feda0000 - 00000000feda6000 (reserved)
>> (XEN) 00000000fee00000 - 00000000fee10000 (reserved)
>> (XEN) 00000000ffe00000 - 0000000100000000 (reserved)
>> (XEN) System RAM: 2037MB (2086888kB)
>> (XEN) ACPI: RSDP 000FBB00, 0024 (r2 DELL )
>> (XEN) ACPI: XSDT 7F65D200, 0064 (r1 DELL M08 27D80614 ASL
> 61)
>> (XEN) ACPI: FACP 7F65D09C, 00F4 (r4 DELL M08 27D80614 ASL
> 61)
>> (XEN) ACPI: DSDT 7F65D800, 614C (r2 INT430 SYSFexxx 1001 INTL
> 20050624)
>> (XEN) ACPI: FACS 7F66C000, 0040
>> (XEN) ACPI: HPET 7F65D300, 0038 (r1 DELL M08 1 ASL
> 61)
>> (XEN) ACPI: APIC 7F65D400, 0068 (r1 DELL M08 27D80614 ASL
> 47)
>> (XEN) ACPI: ASF! 7F65D000, 007E (r32 DELL M08 27D80614 ASL
> 61)
>> (XEN) ACPI: MCFG 7F65D3C0, 003E (r16 DELL M08 27D80614 ASL
> 61)
>> (XEN) ACPI: TCPA 7F65D700, 0032 (r1 0 ASL
> 0)
>> (XEN) ACPI: SLIC 7F65D49C, 0176 (r1 DELL M08 27D80614 ASL
> 61)
>> (XEN) ACPI: SSDT 7F65B9C0, 04CC (r1 PmRef CpuPm 3000 INTL
> 20050624)
>> (XEN) Xen heap: 9MB (9768kB)
>> (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 2, 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 1995.097 MHz processor.
>> (XEN) HVM: VMX enabled
>> (XEN) CPU0: Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz stepping
> 0d
>> (XEN) Booting processor 1/1 eip 8c000
>> (XEN) CPU1: Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz stepping
> 0d
>> (XEN) Total of 2 processors activated.
>> (XEN) ENABLING IO-APIC IRQs
>> (XEN) -> Using old 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 0x100000 -> 0x554000
>> (XEN) PHYSICAL MEMORY ARRANGEMENT:
>> (XEN) Dom0 alloc.: 000000003c000000->000000003e000000 (253952 pages
> to be allocated)
>> (XEN) VIRTUAL MEMORY ARRANGEMENT:
>> (XEN) Loaded kernel: c0100000->c0554000
>> (XEN) Init. ramdisk: c0554000->c0f35e00
>> (XEN) Phys-Mach map: c0f36000->c1036000
>> (XEN) Start info: c1036000->c1036474
>> (XEN) Page tables: c1037000->c1046000
>> (XEN) Boot stack: c1046000->c1047000
>> (XEN) TOTAL: c0000000->c1400000
>> (XEN) ENTRY ADDRESS: c0100000
>> (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 104kB init memory
>>
>>
>>
>> what's wrong I make?
>>
>> best regards,
>> -- James
>>
>> _______________________________________________
>> 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
>
next prev parent reply other threads:[~2008-10-10 7:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-10 7:20 re: RE: re: Re: about pvgrub James Song
2008-10-10 7:31 ` Zhigang Wang [this message]
2008-10-10 7:38 ` pvgrub Zhang, Dongdong
-- strict thread matches above, loose matches on Subject: below --
2010-04-02 17:21 pvgrub David P. Quigley
2010-04-02 18:30 ` pvgrub Samuel Thibault
2010-04-02 18:31 ` pvgrub David P. Quigley
2010-04-02 18:41 ` pvgrub David P. Quigley
2010-04-02 18:45 ` pvgrub Jeremy Fitzhardinge
2010-04-02 18:51 ` pvgrub David P. Quigley
2010-04-02 19:03 ` pvgrub Jeremy Fitzhardinge
2010-04-02 19:01 ` pvgrub David P. Quigley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48EF04C1.70503@oracle.com \
--to=zhigang.x.wang@oracle.com \
--cc=dongdong.zhang@intel.com \
--cc=jsong@novell.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.