On Fri, Apr 29, 2016 at 01:27:35PM +0200, Olaf Hering wrote:
> On Fri, Apr 29, Konrad Rzeszutek Wilk wrote:
>
> > On Tue, Apr 26, 2016 at 03:28:45PM +0200, Olaf Hering wrote:
> > > Why does xen_blkfront not enforce kernel device names from domU.cfg?
> > > In my PV domU.cfg I still have something l
On Fri, Apr 29, Konrad Rzeszutek Wilk wrote:
> On Tue, Apr 26, 2016 at 03:28:45PM +0200, Olaf Hering wrote:
> > Why does xen_blkfront not enforce kernel device names from domU.cfg?
> > In my PV domU.cfg I still have something like this:
> > disk=[ 'file:/path,hda,w' ]
> >
> > With pvops and xen_b
On Fri, 29 Apr 2016, Konrad Rzeszutek Wilk wrote:
> On Fri, Apr 29, 2016 at 01:29:17AM -0600, Jan Beulich wrote:
> > >>> On 29.04.16 at 08:45, wrote:
> > > On Tue, Apr 26, 2016 at 03:28:45PM +0200, Olaf Hering wrote:
> > >> Why does xen_blkfront not enforce kernel device names from domU.cfg?
> > >
On 29/04/16 10:39, David Vrabel wrote:
> On 29/04/16 08:29, Jan Beulich wrote:
> On 29.04.16 at 08:45, wrote:
>>> On Tue, Apr 26, 2016 at 03:28:45PM +0200, Olaf Hering wrote:
Why does xen_blkfront not enforce kernel device names from domU.cfg?
In my PV domU.cfg I still have something
On 29/04/16 08:29, Jan Beulich wrote:
On 29.04.16 at 08:45, wrote:
>> On Tue, Apr 26, 2016 at 03:28:45PM +0200, Olaf Hering wrote:
>>> Why does xen_blkfront not enforce kernel device names from domU.cfg?
>>> In my PV domU.cfg I still have something like this:
>>> disk=[ 'file:/path,hda,w' ]
>
On Fri, Apr 29, 2016 at 01:29:17AM -0600, Jan Beulich wrote:
> >>> On 29.04.16 at 08:45, wrote:
> > On Tue, Apr 26, 2016 at 03:28:45PM +0200, Olaf Hering wrote:
> >> Why does xen_blkfront not enforce kernel device names from domU.cfg?
> >> In my PV domU.cfg I still have something like this:
> >> d
>>> On 29.04.16 at 08:45, wrote:
> On Tue, Apr 26, 2016 at 03:28:45PM +0200, Olaf Hering wrote:
>> Why does xen_blkfront not enforce kernel device names from domU.cfg?
>> In my PV domU.cfg I still have something like this:
>> disk=[ 'file:/path,hda,w' ]
>>
>> With pvops and xen_blkfront I get xvd
On Tue, Apr 26, 2016 at 03:28:45PM +0200, Olaf Hering wrote:
> Why does xen_blkfront not enforce kernel device names from domU.cfg?
> In my PV domU.cfg I still have something like this:
> disk=[ 'file:/path,hda,w' ]
>
> With pvops and xen_blkfront I get xvda.
> With xenlinux and xenblk I get hda.
Why does xen_blkfront not enforce kernel device names from domU.cfg?
In my PV domU.cfg I still have something like this:
disk=[ 'file:/path,hda,w' ]
With pvops and xen_blkfront I get xvda.
With xenlinux and xenblk I get hda.
Olaf
___
Xen-devel mailing
