xen discuss - Sep 2009 - Help needed with debian lenny PV domU on 2009.06 xvm dom0

I''ve been trying to create a para virtualised debian Lenny domU on osol
2009.06 dom0.  I used this blog post as a guide (changed where appropriate to
match my setup and version of debian etch):

http://blog.adventuresinopensolaris.com/2008/07/xvm-pv-of-debian-distros.html

I had no problems whatsoever installing lenny and getting a running hvm domU,
but when I tried to build a PV version and get to this line:-

pfexec virsh attach-disk lenny-hvm /dev/zvol/dsk/rpool/xvm/lenny-01-xvba hdb

I get an error basically saying the block device is not present.  I''m
at work now so can''t give the verbose output, but I did double check my
commands and the paths to the zvols etc are correct.  Is there any reason why I
would get an error and if not can someone direct me to some other docs that
document this process? - as usual, I can''t find anything with google
because it returns scads of useless Virtualbox resources!


Many thanks,

Matt.
-- 
This message posted from opensolaris.org

Matt wrote:
> I''ve been trying to create a para virtualised debian Lenny domU on
 > osol 2009.06 dom0.  I used this blog post as a guide (changed where
 > appropriate to match my setup and version of debian
etch):
> 
>
http://blog.adventuresinopensolaris.com/2008/07/xvm-pv-of-debian-distros.html
> 
> I had no problems whatsoever installing lenny and getting a running hvm
domU,
 > but when I tried to build a PV version and get to this
line:-
> 
> pfexec virsh attach-disk lenny-hvm /dev/zvol/dsk/rpool/xvm/lenny-01-xvba
hdb

Should you use xvd* instead of hd*?

   pfexec virsh attach-disk lenny-hvm /dev/zvol/dsk/rpool/xvm/lenny-01-xvba xvda

> I get an error basically saying the block device is not present. 
I''m at work
 > now so can''t give the verbose output, but I did double check my
commands and
 > the paths to the zvols etc are correct.  Is there any reason why I would
get
 > an error and if not can someone direct me to some other docs that document
 > this process? - as usual, I can''t find anything with google
because it returns
 > scads of useless Virtualbox resources!

The log file /var/log/xen/xpvd-event.log should give you more details
around what was the underlying problem.




MRJ

Thanks.

I must have made a mistake somewhere.  After some playing around I managed to do
it.  I ended up destroying the previous zvol, creating a fresh zvol and
attaching it like this:

pfexec zfs create -V 4G rpool/xvm/lenny-01-xvdb
pfexec virsh attach-disk lenny-hvm /dev/zvol/dsk/rpool/xvm/lenny-01-xvdb xvdb

Is the naming convention for disks in xvm xvda, xvdb, xvdc, etc?

Cheers,

Matt.
-- 
This message posted from opensolaris.org

Matt wrote:
> Thanks.
> 
> I must have made a mistake somewhere.  After some playing around I managed
to do it.  I ended up destroying the previous zvol, creating a fresh zvol and
attaching it like this:
> 
> pfexec zfs create -V 4G rpool/xvm/lenny-01-xvdb
> pfexec virsh attach-disk lenny-hvm /dev/zvol/dsk/rpool/xvm/lenny-01-xvdb
xvdb
> 
> Is the naming convention for disks in xvm xvda, xvdb, xvdc, etc?
For PV guests, yes..



MRJ

> Cheers,
> 
> Matt.

Thank you.

I pasted in the wrong line above. It should have been:

pfexec virsh attach-disk lenny-hvm /dev/zvol/dsk/rpool/xvm/lenny-01-xvdb hdb

M.
-- 
This message posted from opensolaris.org