* re： RE: re： Re: about pvgrub
@ 2008-10-10 7:20 James Song
2008-10-10 7:31 ` pvgrub Zhigang Wang
0 siblings, 1 reply; 11+ messages in thread
From: James Song @ 2008-10-10 7:20 UTC (permalink / raw)
To: dongdong.zhang, zhigang.x.wang; +Cc: xen-devel
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?
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
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: pvgrub
2008-10-10 7:20 re： RE: re： Re: about pvgrub James Song
@ 2008-10-10 7:31 ` Zhigang Wang
2008-10-10 7:38 ` pvgrub Zhang, Dongdong
0 siblings, 1 reply; 11+ messages in thread
From: Zhigang Wang @ 2008-10-10 7:31 UTC (permalink / raw)
To: James Song; +Cc: dongdong.zhang, xen-devel
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
>
^ permalink raw reply [flat|nested] 11+ messages in thread
* RE: pvgrub
2008-10-10 7:31 ` pvgrub Zhigang Wang
@ 2008-10-10 7:38 ` Zhang, Dongdong
0 siblings, 0 replies; 11+ messages in thread
From: Zhang, Dongdong @ 2008-10-10 7:38 UTC (permalink / raw)
To: Zhigang Wang, James Song; +Cc: xen-devel@lists.xensource.com
[-- Attachment #1: Type: text/plain, Size: 9908 bytes --]
>extra = "(hd0,5)/boot/grub/menu.lst"
(hd0,5) that's /dev/sda6
grubdom>configfile (hd0, ## now you can try to used "tab" to select the partition you want
Regards,
Dongdong Zhang
-----Original Message-----
From: Zhigang Wang [mailto:zhigang.x.wang@oracle.com]
Sent: 2008年10月10日 15:31
To: James Song
Cc: Zhang, Dongdong; xen-devel@lists.xensource.com
Subject: Re: pvgrub
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
>
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 11+ messages in thread
* pvgrub
@ 2010-04-02 17:21 David P. Quigley
2010-04-02 18:30 ` pvgrub Samuel Thibault
2010-04-02 18:45 ` pvgrub Jeremy Fitzhardinge
0 siblings, 2 replies; 11+ messages in thread
From: David P. Quigley @ 2010-04-02 17:21 UTC (permalink / raw)
To: xen-devel
So a little bit of background.
I have a vm which I know boots properly as an HVM and I want to run it
as a paravirt guest. It is a fedora 11 based image that I built from a
kickstart so I know the kernel has paravirt guest support. I have built
the latest xen-unstable tree including the stub domains to get pvgrub to
attempt to boot from. My domU config has the following lines in it.
kernel = "/usr/lib/xen/boot/pv-grub-x86_64.gz"
extra = "(hd0,0)/boot/grub/menu.lst"
If I remove my storage devices from the config it boots into the grub
console so I know the stub domain is working. When I leave the the
storage devices in and boot with xm create -c <configfile> I get the
output below and then it hangs.
Is there any additional debug information that I can grab to try to
figure this out?
Dave
# xm create -c domU-pv.conf
/usr/lib64/python2.6/site-packages/xen/xm/group.py:23: DeprecationWarning: the sets module is deprecated
from sets import Set
Using config file "./domU-pv.conf".
Started domain SEHostStorage (id=8)
Xen Minimal OS!
start_info: 0xaa6000(VA)
nr_pages: 0x20000
shared_inf: 0xbfa56000(MA)
pt_base: 0xaa9000(VA)
nr_pt_frames: 0x9
mfn_list: 0x9a6000(VA)
mod_start: 0x0(VA)
mod_len: 0
flags: 0x0
cmd_line: (hd0,0)/boot/grub/menu.lst
stack: 0x965980-0x985980
MM: Init
_text: 0x0(VA)
_etext: 0x69774(VA)
_erodata: 0x8f000(VA)
_edata: 0x97ae0(VA)
stack start: 0x965980(VA)
_end: 0x9a5f88(VA)
start_pfn: ab5
max_pfn: 20000
Mapping memory range 0xc00000 - 0x20000000
setting 0x0-0x8f000 readonly
skipped 0x1000
MM: Initialise page allocator for baf000(baf000)-20000000(20000000)
MM: done
Demand map pfns at 20001000-2020001000.
Heap resides at 2020002000-4020002000.
Initialising timer interface
Initialising console ... done.
gnttab_table mapped at 0x20001000.
Initialising scheduler
Thread "Idle": pointer: 0x2020002050, stack: 0xcc0000
Initialising xenbus
Thread "xenstore": pointer: 0x2020002800, stack: 0xcd0000
Dummy main: start_info=0x985a80
Thread "main": pointer: 0x2020002fb0, stack: 0xce0000
Thread "pcifront": pointer: 0x2020003760, stack: 0xcf0000
"main" "(hd0,0)/boot/grub/menu.lst"
pcifront_watches: waiting for backend path to appear device/pci/0/backend
vbd 768 is hd0
******************* BLKFRONT for device/vbd/768 **********
backend at /local/domain/0/backend/vbd/8/768
Failed to read /local/domain/0/backend/vbd/8/768/feature-flush-cache.
2097152 sectors of 512 bytes
**************************
vbd 5632 is hd1
******************* BLKFRONT for device/vbd/5632 **********
backend at /local/domain/0/backend/vbd/8/5632
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: pvgrub
2010-04-02 17:21 pvgrub David P. Quigley
@ 2010-04-02 18:30 ` Samuel Thibault
2010-04-02 18:31 ` pvgrub David P. Quigley
2010-04-02 18:45 ` pvgrub Jeremy Fitzhardinge
1 sibling, 1 reply; 11+ messages in thread
From: Samuel Thibault @ 2010-04-02 18:30 UTC (permalink / raw)
To: David P. Quigley; +Cc: xen-devel
David P. Quigley, le Fri 02 Apr 2010 13:21:00 -0400, a écrit :
> Is there any additional debug information that I can grab to try to
> figure this out?
The usual /var/log/xen logs, and please post your disk stanza.
Samuel
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: pvgrub
2010-04-02 18:30 ` pvgrub Samuel Thibault
@ 2010-04-02 18:31 ` David P. Quigley
2010-04-02 18:41 ` pvgrub David P. Quigley
0 siblings, 1 reply; 11+ messages in thread
From: David P. Quigley @ 2010-04-02 18:31 UTC (permalink / raw)
To: Samuel Thibault; +Cc: xen-devel
disk =
[ 'tap:tapdisk:aio:/home/dpquigl/SEHostStorage/SEHostStorage-sda.raw,hda,w', ',hdc:cdrom,r' ]
/var/log/xen/qemu-dm-SEHostStorage.log
domid: 2
config qemu network with xen bridge for tap2.0 virbr0
Watching /local/domain/0/device-model/2/logdirty/cmd
Watching /local/domain/0/device-model/2/command
char device redirected to /dev/pts/1
qemu_map_cache_init nr_buckets = 10000 size 4194304
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = 2d27fc2a-1326-d314-9ba0-d9fa2c032902
Time offset set 0
populating video RAM at ff000000
mapping video RAM from ff000000
Register xen platform.
Done register platform.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
xs_read(/local/domain/0/device-model/2/xen_extended_power_mgmt): read error
xs_read(): vncpasswd get error. /vm/2d27fc2a-1326-d314-9ba0-d9fa2c032902/vncpasswd.
medium change watch on `hdc' (index: 1):
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
Log-dirty: no command yet.
xs_read(/local/domain/2/log-throttling): read error
qemu: ignoring not-understood drive `/local/domain/2/log-throttling'
medium change watch on `/local/domain/2/log-throttling' - unknown device, ignored
cirrus vga map change while on lfb mode
mapping vram to f0000000 - f0400000
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state.
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
track_dirty_vram(f0000000, 26) failed (-1, 1)
shutdown requested in cpu_handle_ioreq
Issued domain 2 poweroff
/var/log/xen/xend.log
[Snip non related messages]
[2010-04-02 13:14:10 2013] WARNING (XendConfig:892) Unconverted key: dgid
[2010-04-02 13:14:10 2013] DEBUG (XendDomainInfo:101) XendDomainInfo.create(['vm', ['name', 'SEHostStorage'], ['memory', 512], ['on_xend_start', 'ignore'], ['on_xend_stop', 'ignore'], ['vcpus', 1], ['oos', 1], ['dgid', 32767], ['image', ['linux', ['kernel', '/usr/lib/xen/boot/pv-grub-x86_64.gz'], ['videoram', 4], ['serial', 'pty'], ['args', '(hd0,0)/boot/grub/menu.lst'], ['tsc_mode', 0], ['nomigrate', 0]]], ['s3_integrity', 1], ['security', [['access_control', ['policy', ''], ['label', 'system_u:object_r:domU_t']]]], ['device', ['tap2', ['uname', 'tap:tapdisk:aio:/home/dpquigl/SEHostStorage/SEHostStorage-sda.raw'], ['dev', 'hda'], ['mode', 'w']]], ['device', ['vbd', ['uname', ''], ['dev', 'hdc:cdrom'], ['mode', 'r']]], ['device', ['vif', ['bridge', 'virbr0'], ['type', 'ioemu']]]])
[2010-04-02 13:14:10 2013] DEBUG (XendDomainInfo:405) DEBUG: initialized XendDomainInfo: domNone, grp32767
[2010-04-02 13:14:10 2013] DEBUG (XendDomainInfo:2534) XendDomainInfo.constructDomain
[2010-04-02 13:14:10 2013] DEBUG (balloon:220) Balloon: 1695336 KiB free; need 16384; done.
[2010-04-02 13:14:10 2013] DEBUG (XendDomain:472) Adding Domain: 8
[2010-04-02 13:14:10 2013] DEBUG (XendDomainInfo:2844) XendDomainInfo.initDomain: 8 256
[2010-04-02 13:14:10 2013] DEBUG (XendDomainInfo:2871) _initDomain:shadow_memory=0x0, memory_static_max=0x20000000, memory_static_min=0x0.
[2010-04-02 13:14:11 2013] INFO (image:182) buildDomain os=linux dom=8 vcpus=1
[2010-04-02 13:14:11 2013] DEBUG (image:721) domid = 8
[2010-04-02 13:14:11 2013] DEBUG (image:722) grpid = 32767
[2010-04-02 13:14:11 2013] DEBUG (image:723) memsize = 512
[2010-04-02 13:14:11 2013] DEBUG (image:724) image = /usr/lib/xen/boot/pv-grub-x86_64.gz
[2010-04-02 13:14:11 2013] DEBUG (image:725) store_evtchn = 1
[2010-04-02 13:14:11 2013] DEBUG (image:726) console_evtchn = 2
[2010-04-02 13:14:11 2013] DEBUG (image:727) cmdline = (hd0,0)/boot/grub/menu.lst
[2010-04-02 13:14:11 2013] DEBUG (image:728) ramdisk =
[2010-04-02 13:14:11 2013] DEBUG (image:729) vcpus = 1
[2010-04-02 13:14:11 2013] DEBUG (image:730) features =
[2010-04-02 13:14:11 2013] DEBUG (image:731) flags = 0
[2010-04-02 13:14:11 2013] DEBUG (image:732) superpages = 0
[2010-04-02 13:14:11 2013] INFO (XendDomainInfo:2393) createDevice: tap2 : {'bootable': 1, 'uname': 'tap:tapdisk:aio:/home/dpquigl/SEHostStorage/SEHostStorage-sda.raw', 'mode': 'w', 'dev': 'hda', 'uuid': 'd756c8cb-4bc6-cf8d-e555-93de6da1452c'}
[2010-04-02 13:14:11 2013] DEBUG (DevController:95) DevController: writing {'virtual-device': '768', 'device-type': 'disk', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/8/768'} to /local/domain/8/device/vbd/768.
[2010-04-02 13:14:11 2013] DEBUG (DevController:97) DevController: writing {'domain': 'SEHostStorage', 'frontend': '/local/domain/8/device/vbd/768', 'uuid': 'd756c8cb-4bc6-cf8d-e555-93de6da1452c', 'bootable': '1', 'dev': 'hda', 'state': '1', 'params': '/dev/xen/blktap-2/tapdev0', 'mode': 'w', 'online': '1', 'frontend-id': '8', 'type': 'phy', 'tapdisk-params': 'tapdisk:aio:/home/dpquigl/SEHostStorage/SEHostStorage-sda.raw'} to /local/domain/0/backend/vbd/8/768.
[2010-04-02 13:14:11 2013] INFO (XendDomainInfo:2393) createDevice: vbd : {'uuid': 'e36493e6-fb26-6c9b-39ea-f304ff9d50e0', 'bootable': 0, 'driver': 'paravirtualised', 'dev': 'hdc:cdrom', 'uname': '', 'mode': 'r'}
[2010-04-02 13:14:11 2013] DEBUG (DevController:95) DevController: writing {'virtual-device': '5632', 'device-type': 'cdrom', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/8/5632'} to /local/domain/8/device/vbd/5632.
[2010-04-02 13:14:11 2013] DEBUG (DevController:97) DevController: writing {'domain': 'SEHostStorage', 'frontend': '/local/domain/8/device/vbd/5632', 'uuid': 'e36493e6-fb26-6c9b-39ea-f304ff9d50e0', 'bootable': '0', 'dev': 'hdc', 'state': '1', 'params': '', 'mode': 'r', 'online': '1', 'frontend-id': '8', 'type': ''} to /local/domain/0/backend/vbd/8/5632.
[2010-04-02 13:14:11 2013] INFO (XendDomainInfo:2393) createDevice: vif : {'bridge': 'virbr0', 'mac': '00:16:3e:68:2a:c8', 'type': 'ioemu', 'uuid': '43590daf-6064-3982-a628-d57b1a40d5ad'}
[2010-04-02 13:14:11 2013] DEBUG (DevController:95) DevController: writing {'protocol': 'x86_64-abi', 'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/vif/8/0'} to /local/domain/8/device/vif/0.
[2010-04-02 13:14:11 2013] DEBUG (DevController:97) DevController: writing {'bridge': 'virbr0', 'domain': 'SEHostStorage', 'handle': '0', 'uuid': '43590daf-6064-3982-a628-d57b1a40d5ad', 'script': '/etc/xen/scripts/vif-nat', 'mac': '00:16:3e:68:2a:c8', 'frontend-id': '8', 'state': '1', 'online': '1', 'frontend': '/local/domain/8/device/vif/0', 'type': 'ioemu'} to /local/domain/0/backend/vif/8/0.
[2010-04-02 13:14:11 2013] DEBUG (XendDomainInfo:3426) Storing VM details: {'on_xend_stop': 'ignore', 'shadow_memory': '0', 'uuid': '945900d5-5025-01d0-9516-f67334b4feb0', 'on_reboot': 'restart', 'start_time': '1270228451.38', 'on_poweroff': 'destroy', 'bootloader_args': '', 'on_xend_start': 'ignore', 'on_crash': 'restart', 'xend/restart_count': '0', 'vcpus': '1', 'dguuid': 'ffffffff-ffff-ffff-ffff-ffffffffffff', 'vcpu_avail': '1', 'dgid': '32767', 'bootloader': '', 'image': "(linux (kernel /usr/lib/xen/boot/pv-grub-x86_64.gz) (args '(hd0,0)/boot/grub/menu.lst') (superpages 0) (videoram 4) (pci ()) (serial pty) (nomigrate 0) (tsc_mode 0) (notes))", 'name': 'SEHostStorage'}
[2010-04-02 13:14:11 2013] DEBUG (XendDomainInfo:1811) Storing domain details: {'console/ring-ref': '2157652', 'console/port': '2', 'control/platform-feature-multiprocessor-suspend': '1', 'description': '', 'console/limit': '1048576', 'vm': '/vm/945900d5-5025-01d0-9516-f67334b4feb0', 'domid': '8', 'security_label': 'system_u:object_r:domU_t', 'cpu/0/availability': 'online', 'memory/target': '524288', 'dguuid': 'ffffffff-ffff-ffff-ffff-ffffffffffff', 'store/ring-ref': '2157653', 'dgid': '32767', 'console/type': 'xenconsoled', 'store/port': '1', 'name': 'SEHostStorage'}
[2010-04-02 13:14:11 2013] DEBUG (DevController:95) DevController: writing {'protocol': 'x86_64-abi', 'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/console/8/0'} to /local/domain/8/device/console/0.
[2010-04-02 13:14:11 2013] DEBUG (DevController:97) DevController: writing {'domain': 'SEHostStorage', 'frontend': '/local/domain/8/device/console/0', 'uuid': '14cf280a-d76e-36e2-b85b-fae8851c15f4', 'frontend-id': '8', 'state': '1', 'location': '2', 'online': '1', 'protocol': 'vt100'} to /local/domain/0/backend/console/8/0.
[2010-04-02 13:14:11 2013] DEBUG (DevController:139) Waiting for devices tap2.
[2010-04-02 13:14:11 2013] DEBUG (XendDomainInfo:1898) XendDomainInfo.handleShutdownWatch
[2010-04-02 13:14:11 2013] DEBUG (DevController:144) Waiting for 768.
[2010-04-02 13:14:11 2013] DEBUG (XendDomainInfo:1903) DEBUG: stashing dom8 dgid: 32767 (32767)
[2010-04-02 13:14:11 2013] DEBUG (DevController:628) hotplugStatusCallback /local/domain/0/backend/vbd/8/768/hotplug-status.
[2010-04-02 13:14:11 2013] DEBUG (DevController:642) hotplugStatusCallback 1.
[2010-04-02 13:14:11 2013] DEBUG (DevController:139) Waiting for devices vif.
[2010-04-02 13:14:11 2013] DEBUG (DevController:144) Waiting for 0.
[2010-04-02 13:14:11 2013] DEBUG (DevController:628) hotplugStatusCallback /local/domain/0/backend/vif/8/0/hotplug-status.
[2010-04-02 13:14:11 2013] DEBUG (DevController:642) hotplugStatusCallback 1.
[2010-04-02 13:14:11 2013] DEBUG (DevController:139) Waiting for devices vkbd.
[2010-04-02 13:14:11 2013] DEBUG (DevController:139) Waiting for devices ioports.
[2010-04-02 13:14:11 2013] DEBUG (DevController:139) Waiting for devices tap.
[2010-04-02 13:14:11 2013] DEBUG (DevController:139) Waiting for devices vif2.
[2010-04-02 13:14:11 2013] DEBUG (DevController:139) Waiting for devices console.
[2010-04-02 13:14:11 2013] DEBUG (DevController:144) Waiting for 0.
[2010-04-02 13:14:11 2013] DEBUG (DevController:139) Waiting for devices vscsi.
[2010-04-02 13:14:11 2013] DEBUG (DevController:139) Waiting for devices vbd.
[2010-04-02 13:14:11 2013] DEBUG (DevController:144) Waiting for 5632.
[2010-04-02 13:14:11 2013] DEBUG (DevController:628) hotplugStatusCallback /local/domain/0/backend/vbd/8/5632/hotplug-status.
[2010-04-02 13:14:12 2013] DEBUG (DevController:628) hotplugStatusCallback /local/domain/0/backend/vbd/8/5632/hotplug-status.
[2010-04-02 13:14:12 2013] DEBUG (DevController:642) hotplugStatusCallback 1.
[2010-04-02 13:14:12 2013] DEBUG (DevController:139) Waiting for devices irq.
[2010-04-02 13:14:12 2013] DEBUG (DevController:139) Waiting for devices vfb.
[2010-04-02 13:14:12 2013] DEBUG (DevController:139) Waiting for devices pci.
[2010-04-02 13:14:12 2013] DEBUG (DevController:139) Waiting for devices vusb.
[2010-04-02 13:14:12 2013] DEBUG (DevController:139) Waiting for devices vtpm.
[2010-04-02 13:14:12 2013] INFO (XendDomain:1219) Domain SEHostStorage (8) unpaused.
On Fri, 2010-04-02 at 20:30 +0200, Samuel Thibault wrote:
> David P. Quigley, le Fri 02 Apr 2010 13:21:00 -0400, a écrit :
> > Is there any additional debug information that I can grab to try to
> > figure this out?
>
> The usual /var/log/xen logs, and please post your disk stanza.
>
> Samuel
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: pvgrub
2010-04-02 18:31 ` pvgrub David P. Quigley
@ 2010-04-02 18:41 ` David P. Quigley
0 siblings, 0 replies; 11+ messages in thread
From: David P. Quigley @ 2010-04-02 18:41 UTC (permalink / raw)
To: Samuel Thibault; +Cc: xen-devel
Actually the qemu-dm-SEHostStorage.log file is wrong. I deleted all my
logs rebooted and reran the pvgrub config to get a new log file and it
doesn't seem to generate one. So I guess that the log file I pasted was
from when I ran it as an HVM. Were there any other log files needed?
Dave
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: pvgrub
2010-04-02 17:21 pvgrub David P. Quigley
2010-04-02 18:30 ` pvgrub Samuel Thibault
@ 2010-04-02 18:45 ` Jeremy Fitzhardinge
2010-04-02 18:51 ` pvgrub David P. Quigley
1 sibling, 1 reply; 11+ messages in thread
From: Jeremy Fitzhardinge @ 2010-04-02 18:45 UTC (permalink / raw)
To: David P. Quigley; +Cc: xen-devel
On 04/02/2010 10:21 AM, David P. Quigley wrote:
> So a little bit of background.
>
> I have a vm which I know boots properly as an HVM and I want to run it
> as a paravirt guest. It is a fedora 11 based image that I built from a
> kickstart so I know the kernel has paravirt guest support. I have built
> the latest xen-unstable tree including the stub domains to get pvgrub to
> attempt to boot from. My domU config has the following lines in it.
>
> kernel = "/usr/lib/xen/boot/pv-grub-x86_64.gz"
> extra = "(hd0,0)/boot/grub/menu.lst"
>
> If I remove my storage devices from the config it boots into the grub
> console so I know the stub domain is working. When I leave the the
> storage devices in and boot with xm create -c<configfile> I get the
> output below and then it hangs.
>
> Is there any additional debug information that I can grab to try to
> figure this out?
>
Make sure your /boot is ext3, not ext4. I found that pvgrub doesn't
seem to notice the "extents" feature flag, and will drop into an
infinite loop if it encounters a directory with extents (probably any
extent-based file will make it upset in some way).
J
> Dave
>
> # xm create -c domU-pv.conf
> /usr/lib64/python2.6/site-packages/xen/xm/group.py:23: DeprecationWarning: the sets module is deprecated
> from sets import Set
> Using config file "./domU-pv.conf".
> Started domain SEHostStorage (id=8)
> Xen Minimal OS!
> start_info: 0xaa6000(VA)
> nr_pages: 0x20000
> shared_inf: 0xbfa56000(MA)
> pt_base: 0xaa9000(VA)
> nr_pt_frames: 0x9
> mfn_list: 0x9a6000(VA)
> mod_start: 0x0(VA)
> mod_len: 0
> flags: 0x0
> cmd_line: (hd0,0)/boot/grub/menu.lst
> stack: 0x965980-0x985980
> MM: Init
> _text: 0x0(VA)
> _etext: 0x69774(VA)
> _erodata: 0x8f000(VA)
> _edata: 0x97ae0(VA)
> stack start: 0x965980(VA)
> _end: 0x9a5f88(VA)
> start_pfn: ab5
> max_pfn: 20000
> Mapping memory range 0xc00000 - 0x20000000
> setting 0x0-0x8f000 readonly
> skipped 0x1000
> MM: Initialise page allocator for baf000(baf000)-20000000(20000000)
> MM: done
> Demand map pfns at 20001000-2020001000.
> Heap resides at 2020002000-4020002000.
> Initialising timer interface
> Initialising console ... done.
> gnttab_table mapped at 0x20001000.
> Initialising scheduler
> Thread "Idle": pointer: 0x2020002050, stack: 0xcc0000
> Initialising xenbus
> Thread "xenstore": pointer: 0x2020002800, stack: 0xcd0000
> Dummy main: start_info=0x985a80
> Thread "main": pointer: 0x2020002fb0, stack: 0xce0000
> Thread "pcifront": pointer: 0x2020003760, stack: 0xcf0000
> "main" "(hd0,0)/boot/grub/menu.lst"
> pcifront_watches: waiting for backend path to appear device/pci/0/backend
> vbd 768 is hd0
> ******************* BLKFRONT for device/vbd/768 **********
>
>
> backend at /local/domain/0/backend/vbd/8/768
> Failed to read /local/domain/0/backend/vbd/8/768/feature-flush-cache.
> 2097152 sectors of 512 bytes
> **************************
> vbd 5632 is hd1
> ******************* BLKFRONT for device/vbd/5632 **********
>
>
> backend at /local/domain/0/backend/vbd/8/5632
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: pvgrub
2010-04-02 18:45 ` pvgrub Jeremy Fitzhardinge
@ 2010-04-02 18:51 ` David P. Quigley
2010-04-02 19:03 ` pvgrub Jeremy Fitzhardinge
0 siblings, 1 reply; 11+ messages in thread
From: David P. Quigley @ 2010-04-02 18:51 UTC (permalink / raw)
To: Jeremy Fitzhardinge; +Cc: xen-devel
So when I made the image I made 1 partition and its ext3. So the boot
information is on the same root partition as the rest of the system. I
don't know if that might be an issue. Its definitely ext3 though.
Dave
On Fri, 2010-04-02 at 11:45 -0700, Jeremy Fitzhardinge wrote:
> On 04/02/2010 10:21 AM, David P. Quigley wrote:
> > So a little bit of background.
> >
> > I have a vm which I know boots properly as an HVM and I want to run it
> > as a paravirt guest. It is a fedora 11 based image that I built from a
> > kickstart so I know the kernel has paravirt guest support. I have built
> > the latest xen-unstable tree including the stub domains to get pvgrub to
> > attempt to boot from. My domU config has the following lines in it.
> >
> > kernel = "/usr/lib/xen/boot/pv-grub-x86_64.gz"
> > extra = "(hd0,0)/boot/grub/menu.lst"
> >
> > If I remove my storage devices from the config it boots into the grub
> > console so I know the stub domain is working. When I leave the the
> > storage devices in and boot with xm create -c<configfile> I get the
> > output below and then it hangs.
> >
> > Is there any additional debug information that I can grab to try to
> > figure this out?
> >
>
> Make sure your /boot is ext3, not ext4. I found that pvgrub doesn't
> seem to notice the "extents" feature flag, and will drop into an
> infinite loop if it encounters a directory with extents (probably any
> extent-based file will make it upset in some way).
>
> J
>
> > Dave
> >
> > # xm create -c domU-pv.conf
> > /usr/lib64/python2.6/site-packages/xen/xm/group.py:23: DeprecationWarning: the sets module is deprecated
> > from sets import Set
> > Using config file "./domU-pv.conf".
> > Started domain SEHostStorage (id=8)
> > Xen Minimal OS!
> > start_info: 0xaa6000(VA)
> > nr_pages: 0x20000
> > shared_inf: 0xbfa56000(MA)
> > pt_base: 0xaa9000(VA)
> > nr_pt_frames: 0x9
> > mfn_list: 0x9a6000(VA)
> > mod_start: 0x0(VA)
> > mod_len: 0
> > flags: 0x0
> > cmd_line: (hd0,0)/boot/grub/menu.lst
> > stack: 0x965980-0x985980
> > MM: Init
> > _text: 0x0(VA)
> > _etext: 0x69774(VA)
> > _erodata: 0x8f000(VA)
> > _edata: 0x97ae0(VA)
> > stack start: 0x965980(VA)
> > _end: 0x9a5f88(VA)
> > start_pfn: ab5
> > max_pfn: 20000
> > Mapping memory range 0xc00000 - 0x20000000
> > setting 0x0-0x8f000 readonly
> > skipped 0x1000
> > MM: Initialise page allocator for baf000(baf000)-20000000(20000000)
> > MM: done
> > Demand map pfns at 20001000-2020001000.
> > Heap resides at 2020002000-4020002000.
> > Initialising timer interface
> > Initialising console ... done.
> > gnttab_table mapped at 0x20001000.
> > Initialising scheduler
> > Thread "Idle": pointer: 0x2020002050, stack: 0xcc0000
> > Initialising xenbus
> > Thread "xenstore": pointer: 0x2020002800, stack: 0xcd0000
> > Dummy main: start_info=0x985a80
> > Thread "main": pointer: 0x2020002fb0, stack: 0xce0000
> > Thread "pcifront": pointer: 0x2020003760, stack: 0xcf0000
> > "main" "(hd0,0)/boot/grub/menu.lst"
> > pcifront_watches: waiting for backend path to appear device/pci/0/backend
> > vbd 768 is hd0
> > ******************* BLKFRONT for device/vbd/768 **********
> >
> >
> > backend at /local/domain/0/backend/vbd/8/768
> > Failed to read /local/domain/0/backend/vbd/8/768/feature-flush-cache.
> > 2097152 sectors of 512 bytes
> > **************************
> > vbd 5632 is hd1
> > ******************* BLKFRONT for device/vbd/5632 **********
> >
> >
> > backend at /local/domain/0/backend/vbd/8/5632
> >
> >
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> >
> >
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: pvgrub
2010-04-02 19:03 ` pvgrub Jeremy Fitzhardinge
@ 2010-04-02 19:01 ` David P. Quigley
0 siblings, 0 replies; 11+ messages in thread
From: David P. Quigley @ 2010-04-02 19:01 UTC (permalink / raw)
To: Jeremy Fitzhardinge; +Cc: xen-devel
On Fri, 2010-04-02 at 12:03 -0700, Jeremy Fitzhardinge wrote:
> On 04/02/2010 11:51 AM, David P. Quigley wrote:
> > So when I made the image I made 1 partition and its ext3. So the boot
> > information is on the same root partition as the rest of the system. I
> > don't know if that might be an issue. Its definitely ext3 though.
> >
>
> Should be OK from that perspective then. pvgrub generally seems to be
> having reliability problems with current versions of Xen. If I use vfb
> then I can get the menu displayed, but then it crashes as soon as I
> select a kernel. If I don't have vfb then it crashes in a different way.
>
> What happens if you don't point at the menu and just drop into the grub
> command line? Does that work? Does it hang when you manually select a
> kernel and initrd?
>
> J
>
If I remove my storage entry so it doesn't have access to the menu I get
the grub command prompt. I just tried removing my extra line which
points to the menu for grub while leaving the disk line in and it hangs
the same way with the output I posted in the first email.
Dave
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: pvgrub
2010-04-02 18:51 ` pvgrub David P. Quigley
@ 2010-04-02 19:03 ` Jeremy Fitzhardinge
2010-04-02 19:01 ` pvgrub David P. Quigley
0 siblings, 1 reply; 11+ messages in thread
From: Jeremy Fitzhardinge @ 2010-04-02 19:03 UTC (permalink / raw)
To: David P. Quigley; +Cc: xen-devel
On 04/02/2010 11:51 AM, David P. Quigley wrote:
> So when I made the image I made 1 partition and its ext3. So the boot
> information is on the same root partition as the rest of the system. I
> don't know if that might be an issue. Its definitely ext3 though.
>
Should be OK from that perspective then. pvgrub generally seems to be
having reliability problems with current versions of Xen. If I use vfb
then I can get the menu displayed, but then it crashes as soon as I
select a kernel. If I don't have vfb then it crashes in a different way.
What happens if you don't point at the menu and just drop into the grub
command line? Does that work? Does it hang when you manually select a
kernel and initrd?
J
> Dave
>
> On Fri, 2010-04-02 at 11:45 -0700, Jeremy Fitzhardinge wrote:
>
>> On 04/02/2010 10:21 AM, David P. Quigley wrote:
>>
>>> So a little bit of background.
>>>
>>> I have a vm which I know boots properly as an HVM and I want to run it
>>> as a paravirt guest. It is a fedora 11 based image that I built from a
>>> kickstart so I know the kernel has paravirt guest support. I have built
>>> the latest xen-unstable tree including the stub domains to get pvgrub to
>>> attempt to boot from. My domU config has the following lines in it.
>>>
>>> kernel = "/usr/lib/xen/boot/pv-grub-x86_64.gz"
>>> extra = "(hd0,0)/boot/grub/menu.lst"
>>>
>>> If I remove my storage devices from the config it boots into the grub
>>> console so I know the stub domain is working. When I leave the the
>>> storage devices in and boot with xm create -c<configfile> I get the
>>> output below and then it hangs.
>>>
>>> Is there any additional debug information that I can grab to try to
>>> figure this out?
>>>
>>>
>> Make sure your /boot is ext3, not ext4. I found that pvgrub doesn't
>> seem to notice the "extents" feature flag, and will drop into an
>> infinite loop if it encounters a directory with extents (probably any
>> extent-based file will make it upset in some way).
>>
>> J
>>
>>
>>> Dave
>>>
>>> # xm create -c domU-pv.conf
>>> /usr/lib64/python2.6/site-packages/xen/xm/group.py:23: DeprecationWarning: the sets module is deprecated
>>> from sets import Set
>>> Using config file "./domU-pv.conf".
>>> Started domain SEHostStorage (id=8)
>>> Xen Minimal OS!
>>> start_info: 0xaa6000(VA)
>>> nr_pages: 0x20000
>>> shared_inf: 0xbfa56000(MA)
>>> pt_base: 0xaa9000(VA)
>>> nr_pt_frames: 0x9
>>> mfn_list: 0x9a6000(VA)
>>> mod_start: 0x0(VA)
>>> mod_len: 0
>>> flags: 0x0
>>> cmd_line: (hd0,0)/boot/grub/menu.lst
>>> stack: 0x965980-0x985980
>>> MM: Init
>>> _text: 0x0(VA)
>>> _etext: 0x69774(VA)
>>> _erodata: 0x8f000(VA)
>>> _edata: 0x97ae0(VA)
>>> stack start: 0x965980(VA)
>>> _end: 0x9a5f88(VA)
>>> start_pfn: ab5
>>> max_pfn: 20000
>>> Mapping memory range 0xc00000 - 0x20000000
>>> setting 0x0-0x8f000 readonly
>>> skipped 0x1000
>>> MM: Initialise page allocator for baf000(baf000)-20000000(20000000)
>>> MM: done
>>> Demand map pfns at 20001000-2020001000.
>>> Heap resides at 2020002000-4020002000.
>>> Initialising timer interface
>>> Initialising console ... done.
>>> gnttab_table mapped at 0x20001000.
>>> Initialising scheduler
>>> Thread "Idle": pointer: 0x2020002050, stack: 0xcc0000
>>> Initialising xenbus
>>> Thread "xenstore": pointer: 0x2020002800, stack: 0xcd0000
>>> Dummy main: start_info=0x985a80
>>> Thread "main": pointer: 0x2020002fb0, stack: 0xce0000
>>> Thread "pcifront": pointer: 0x2020003760, stack: 0xcf0000
>>> "main" "(hd0,0)/boot/grub/menu.lst"
>>> pcifront_watches: waiting for backend path to appear device/pci/0/backend
>>> vbd 768 is hd0
>>> ******************* BLKFRONT for device/vbd/768 **********
>>>
>>>
>>> backend at /local/domain/0/backend/vbd/8/768
>>> Failed to read /local/domain/0/backend/vbd/8/768/feature-flush-cache.
>>> 2097152 sectors of 512 bytes
>>> **************************
>>> vbd 5632 is hd1
>>> ******************* BLKFRONT for device/vbd/5632 **********
>>>
>>>
>>> backend at /local/domain/0/backend/vbd/8/5632
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xensource.com
>>> http://lists.xensource.com/xen-devel
>>>
>>>
>>>
>
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2010-04-02 19:03 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-10-10 7:20 re： RE: re： Re: about pvgrub James Song
2008-10-10 7:31 ` pvgrub Zhigang Wang
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
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.