[Pkg-xen-devel] Bug#702369: Bug#702369: Bug#702369: Bug#702369: can't install wheezy from template

[Daniel Pocock]

On 06/03/13 16:05, Thomas Goirand wrote:
> On 03/06/2013 06:10 PM, Ian Campbell wrote:
>   
>> On Wed, 2013-03-06 at 10:10 +0100, Daniel Pocock wrote:
>>     
>>> The domU boots as a PV, but the login prompt is never displayed.  I can
>>> view the console boot messages with VNC, but no login prompt appears in
>>> the console.  The machine is otherwise working fine and can't be
>>> accessed with an ssh login.  I think this has something to do with
>>> inittab and the terminal device names changing. 
>>>       
>> Correct, you need to adda getty on hvc0, e.g:
>>
>> H0:23:respawn:/sbin/getty -L hvc0 115200 vt102
>>     
> Ian, do you think it would make sense to have such line in the inittab
> by default in Debian? It's always annoying Debian domU users, IMO (and
> not only with XAPI).
>
>   

Alternatively, it may be useful to display some message "boot completed,
no getty defined for this console" to give the user a hint.


>> Unfortunately that probably means you need to flip back to HVM mode to
>> change it, or use kpartx etc to mount the guests fs from dom0.
>>
>> Ian.
>>     
> What's the most easy way to mount an XAPI domU partition, in an ext SR,
> from the dom0? How to locate the device path? (I've done it often for PV
> or HVM domUs with non-XAPI Xen Debian systems)
>   

One way would be to export it back to a raw device, modify it and import
it again.  However, I suspect that approach would not be popular.  Many
power-users who are accustomed to hacking away at their LV filesystems
with tools like kpartx are going to be facing an awkward adjustment to
the XCP world (I still haven't disentangled myself from the nested VG
problem).

As we get closer to wheezy, it might be worthwhile putting together a
cheat-sheet mapping these common xm/xl activities to their xe
equivalents.  I'll be happy to contribute to that after having gained a
little more experience with it.