Well,   I just found that devfsadm does not refresh the device list in /dev/dsk, however, a reboot -- -r of the HVM domain does.

After rebooting the solarisHVM1 domain I can see the newly added disk.  Yeah !!!!!


J. Cardozo

-------- Original Message --------
Subject: [Fwd: Unable to block-attach to HVM domain]
Date: Wed, 25 Jun 2008 17:01:58 -0700
From: [EMAIL PROTECTED]
To: [email protected]


jkeil,

Thanks for the hint.  I tried with no success.  Here is what I run

# xm list
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0  5547    16     r-----  63198.4
solarisHVM1                                 23 12288     1     r-----   1265.0
solarisPV1                                  21 12288     4     -b----    275.3
# xm block-attach solarisHVM1 file:/domains/solarisHVM1/disk1.img hdc w
# xm block-list solarisHVM1
Vdev  BE handle state evt-ch ring-ref BE-path
768    0    0     1      -1     -1    /local/domain/0/backend/vbd/23/768
5632    0    0     1      -1     -1    /local/domain/0/backend/vbd/23/5632


However, when I search for the new device on the solarisHVM1 domain, I can not see it

solarisHVM1#ls /dev/dsk
c0d0p0     c0d0s1     c0d0s15    c0d0s7     c1t0d0p3   c1t0d0s12  c1t0d0s4
c0d0p1     c0d0s10    c0d0s2     c0d0s8     c1t0d0p4   c1t0d0s13  c1t0d0s5
c0d0p2     c0d0s11    c0d0s3     c0d0s9     c1t0d0s0   c1t0d0s14  c1t0d0s6
c0d0p3     c0d0s12    c0d0s4     c1t0d0p0   c1t0d0s1   c1t0d0s15  c1t0d0s7
c0d0p4     c0d0s13    c0d0s5     c1t0d0p1   c1t0d0s10  c1t0d0s2   c1t0d0s8
c0d0s0     c0d0s14    c0d0s6     c1t0d0p2   c1t0d0s11  c1t0d0s3   c1t0d0s9
solarisHVM1# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
       0. c0d0 <DEFAULT cyl 4565 alt 2 hd 255 sec 63>
          /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1/[EMAIL PROTECTED]/[EMAIL PROTECTED],0
Specify disk (enter its number):


I run devfsadm, and still do not see the device on solarisHVM1.  I have to note however, that the steps I described on my original posting do work on PV domains., therefore I guess this is an issue only with HVM domains

Anyother thing I might be doing wrong on the HVM domain ??

thanks,



J. Cardozo





> I'm running snv_90 and created a Solaris 10 u4 HVM (solarisHVM1) guest domain.
> I'm following this procedure to add a block device to my guest domain:
> # xm block-attach solarisHVM1 file:/dom1/disk1.img 2 w

For a HVM domU, you must use something like hda, hdb, hdc, hdd
as the FrontDev, not "2".

Try
xm block-attach solarisHVM1 file:/dom1/disk1.img hdc w

-------- Original Message --------
Subject: Unable to block-attach to HVM domain
Date: Wed, 18 Jun 2008 09:29:29 -0700
From: [EMAIL PROTECTED]
To: [email protected]


Hi,

I'm running snv_90 and created a Solaris 10 u4 HVM (solarisHVM1) guest domain.   I'm following this procedure to add a block device to my guest domain:

# xm block-list solarisHVM1
Vdev  BE handle state evt-ch ring-ref BE-path
768    0    0     1      -1     -1    /local/domain/0/backend/vbd/9/768

Create the image file
#dd if=/dev/zero of=/dom1/disk1.img bs=1024k seek=8192 count=1

Add block device
#xm block-attach solarisHVM1 file:/dom1/disk1.img 2 w

List block devices
#xm block-list solarisHVM1
Vdev  BE handle state evt-ch ring-ref BE-path
768    0    0     1      -1     -1    /local/domain/0/backend/vbd/10/768
2      0    0     1      -1     -1    /local/domain/0/backend/vbd/10/2

some output from
#xm list solarisHVM1 -l
(device
        (vbd
            (uname file:/domains/solarisHVM1/root.img)
            (uuid d843dcb0-3a20-ef2d-919d-6247a7a9dd21)
            (mode w)
            (dev hda:disk)
            (backend 0)
            (bootable 1)
        )
    )
    (device
        (vbd
            (uname file:/dom1/disk1.img)
            (uuid 6347a698-d345-0dba-709e-5155a0e60c4c)
            (mode w)
            (dev 2:disk)
            (backend 0)
            (bootable 0)
        )



After running devfsadm in my guest domain, the new device does not show up
# ls /dev/dsk
c0d0p0     c0d0s1     c0d0s15    c0d0s7     c1t0d0p3   c1t0d0s12  c1t0d0s4
c0d0p1     c0d0s10    c0d0s2     c0d0s8     c1t0d0p4   c1t0d0s13  c1t0d0s5
c0d0p2     c0d0s11    c0d0s3     c0d0s9     c1t0d0s0   c1t0d0s14  c1t0d0s6
c0d0p3     c0d0s12    c0d0s4     c1t0d0p0   c1t0d0s1   c1t0d0s15  c1t0d0s7
c0d0p4     c0d0s13    c0d0s5     c1t0d0p1   c1t0d0s10  c1t0d0s2   c1t0d0s8
c0d0s0     c0d0s14    c0d0s6     c1t0d0p2   c1t0d0s11  c1t0d0s3   c1t0d0s9

I tried different options, including adding the device while the domain was down and rebooting the solarisHVM1 domain, but nothing seem to work.  Previous to running snv_90 I was running svn_82 and that I was being affected by bug 6656611, which was fixed in snv_85.  However, I can not get it to work.

Any ideas,hints, suggestions, or corrections (if I'm doing something wrong) on how to solve this issue are much appreciated.

Thanks,


Jairo Cardozo

-- 
+-----------------------------------------------+
	Jairo Cardozo H
	Benchmark Engineer
	Sun  Solution Centers
		
	[EMAIL PROTECTED]
	Ext:   87013	
	Phone:	650-786-7013
+-----------------------------------------------+

-- 
+-----------------------------------------------+
	Jairo Cardozo H
	Benchmark Engineer
	Sun  Solution Centers
		
	[EMAIL PROTECTED]
	Ext:   87013	
	Phone:	650-786-7013
+-----------------------------------------------+


_______________________________________________
xen-discuss mailing list
[email protected]

Reply via email to