xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Kuhne <stefan.kuhne@gmx.net>
To: xen-devel@lists.xensource.com
Subject: Re: 2.6.31.6 pv_ops from xen-4.0.0-rc1 hangs by DomU initrd
Date: Tue, 26 Jan 2010 20:28:20 +0100	[thread overview]
Message-ID: <4B5F4254.4080107@access.denied> (raw)
In-Reply-To: <20100126191915.GB2861@reaktio.net>


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

Pasi Kärkkäinen schrieb:
> On Tue, Jan 26, 2010 at 08:13:45PM +0100, Stefan Kuhne wrote:
>> Pasi Kärkkäinen schrieb:
>>> On Tue, Jan 26, 2010 at 06:41:23PM +0100, Stefan Kuhne wrote:
>>>> Pasi Kärkkäinen schrieb:
>>>>
>>>>> extra = "console=hvc0"
>>>>>
>>>> I've added to extra but same result.
>>>>
>>> Did you remove the netconsole? Also try with more memory..
>>>
>> I've reduce my config to minimum:
>>
>> eisxen # cat /etc/xen/xm/xmTest-Eis2
>> #  -*- mode: python; -*-
>> #============================================================================
>> # Python configuration setup for 'xm create'.
>> # This script sets the parameters used when a domain is created using
>> 'xm create'.
>> # You use a separate script for each domain you want to create, or
>> # you can set the parameters for the domain on the xm command line.
>> #============================================================================
>>
>> kernel = "/boot/vmlinuz-xen"
>> ramdisk = "/boot/initrd-xen.gz"
>> memory = 256
>> name = "Test-Eis2"
>>
>> disk = [ 'phy:/dev/vg/Test-Eis2,hda1,w',
>> 'phy:/dev/vg/Test-Eis2-swap,hda2,w' ]
>>
>> root = "/dev/hda1"
>>
>> extra = "ro quiet console=hvc0 " #xencons=tty1"
>> eisxen #
>>
>> But nothing happens.
>>
> 
> Remove "quiet".
> Also, how did you generate the initrd?
> 
echo ""
  mecho -info "Create initrd ..."
  echo ""

  cd ${INITRD_DIR}
  find ./ | cpio -H newc -o > ${INSTALL_PATH}/boot/initrd-${KERNEL_VERSION}
  cpio=$?

  if [ ${cpio} == 0 ]
  then
    gzip -f ${INSTALL_PATH}/boot/initrd-${KERNEL_VERSION}
    gzip=$?
  fi

This is the same initrd like Dom0.

>> Can i run an old DomU Kernel on pv_ops Kernel?
>>
> 
> Yes you can. Xen hypervisor is the compatibility layer there.
> domUs talk to Xen, not directly to dom0.
> 
Than i'll test an older DomU Kernel.

Stefan Kuhne


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 552 bytes --]

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

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

  parent reply	other threads:[~2010-01-26 19:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-26 14:16 2.6.31.6 pv_ops from xen-4.0.0-rc1 hangs by DomU initrd Stefan Kuhne
2010-01-26 14:24 ` Pasi Kärkkäinen
2010-01-26 16:27   ` Stefan Kuhne
2010-01-26 16:27     ` Konrad Rzeszutek Wilk
2010-01-26 16:34     ` Pasi Kärkkäinen
2010-01-26 17:28       ` Stefan Kuhne
2010-01-26 17:32         ` Pasi Kärkkäinen
2010-01-26 17:41           ` Stefan Kuhne
2010-01-26 17:40             ` Konrad Rzeszutek Wilk
2010-01-26 17:52             ` Pasi Kärkkäinen
     [not found]               ` <4B5F3EE9.8040307@access.denied>
     [not found]                 ` <20100126191915.GB2861@reaktio.net>
2010-01-26 19:28                   ` Stefan Kuhne [this message]
2010-01-26 20:00                     ` Konrad Rzeszutek Wilk
2010-01-28 13:00 ` Stefan Kuhne

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=4B5F4254.4080107@access.denied \
    --to=stefan.kuhne@gmx.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).