All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mickael Marchand <mikmak@freenux.org>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
	xen-devel@lists.xensource.com
Subject: Re: xen 3.4.0 & pvgrub
Date: Thu, 21 May 2009 20:53:24 +0200	[thread overview]
Message-ID: <20090521185323.GD20584@nya.freenux.org> (raw)
In-Reply-To: <20090521182207.GS5806@const.famille.thibault.fr>

On Thu, May 21, 2009 at 08:22:07PM +0200, Samuel Thibault wrote:
> Mickael Marchand, le Thu 21 May 2009 20:19:53 +0200, a écrit :
> > On Thu, May 21, 2009 at 07:22:13PM +0200, Samuel Thibault wrote:
> > > Mickael Marchand, le Tue 19 May 2009 18:01:14 +0200, a écrit :
> > > > booting the same domU with pvgrub (and same kernel inside the domU) it's
> > > > not able to find sda1 or xvda1, /dev looks empty in regards to disk
> > > > devices
> > > 
> > > Mmm, your dom0 probably has a kernel that doesn't cope well with
> > > reconnecting devices, which kernel does it have ?
> > 
> > the standard 2.6.24-24-xen from ubuntu,
> > it works fine with xen 3.3 afaict (using it in production)
> 
> With pv-grub, you mean?  I.e. with the same dom0 kernel, an upgraded
> hypervisor, and the same domU kernel, you now have issues with pv-grub
> while you didn't have any before?
> 
> Samuel

* Xen 3.3.1 :
[    0.096978] Event-channel device installed.                                                                                                                        
[    0.102662] Successfully initialized TPM backend driver.                                                                                                           
[    0.105036] netfront: Initialising virtual ethernet driver.                                                                                                        
[   19.156897] xen-vbd: registered block device major 202                                                                                                             
[   19.156918] blkfront: xvda1: barriers enabled                                                                                                                      
[    0.141005] rtc: IRQ 8 is not free.

* Xen 3.4.0 :
[    0.091188] Event-channel device installed.                                                                                                                        
[    0.096703] Successfully initialized TPM backend driver.                                                                                                           
[    0.096920] netfront: Initialising virtual ethernet driver.                                                                                                        
[    0.132989] rtc: IRQ 8 is not free. 

missing the 2 lines about xen-vbd and blkfront apparently

Mik

  parent reply	other threads:[~2009-05-21 18:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-19 16:01 xen 3.4.0 & pvgrub Mickael Marchand
2009-05-21 17:22 ` Samuel Thibault
2009-05-21 18:19   ` Mickael Marchand
2009-05-21 18:22     ` Samuel Thibault
2009-05-21 18:42       ` Mickael Marchand
2009-05-21 18:53       ` Mickael Marchand [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-05-19  9:14 Mickael Marchand

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=20090521185323.GD20584@nya.freenux.org \
    --to=mikmak@freenux.org \
    --cc=samuel.thibault@ens-lyon.org \
    --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.