Re: [Xen-users] Problem with direct pass two (whole) raw disks to vm

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Fri, 2014-04-25 at 22:29 +0930, Jason Yu wrote:
> Many thanks Ian!!!
> 
> 
> >>> If you only care about PV access to /dev/sd{a,b} (as opposed to
> emulated IDE) then you could also try putting them on xvde and xvdf
> (out of the say of the IDE stuff). That might help.
> Could you please advise how to do this as Iâm quite new to Xen? Do I
> simply do this in .cfg like this? 
> 
> 
> disk = [ "file:/etc/xen/images/NAS-OMV.img,hda,w",
> "phy:/dev/sda,xvde,w", "phy:/dev/sdb,xvdf,w" ]

Yes.

> >>> Does the 1 (additional) disk case work regardless of whether you
> use sda or sdb?
> Yes, I tried passing both sda and sdb individually. I could see each
> of them in domU (openmediavault web GUI). The start up time of the
> domU was swfit.

OK, so it isn't that one of hte disks is faulty or anything.

> >>> Here you have hda, hdb and hdd.
> I noticed this as well. (I think it was a typographical error.)So I
> edited the cfg again and created the vm (with two disks). Same
> problem. VM got stuck in a count down( see 1st email thread) and I
> couldnât log into the web GUI. 
> 
> 
> ============ part of NAS-OMV.cfg ==============
> disk = [ "file:/etc/xen/images/NAS-OMV.img,hda,w",
> "phy:/dev/sda,hdb,w", "phy:/dev/sdb,hdc,w" ]
> 
> 
> Soon after creating the vm, I ran this:
> 
> 
> root@UB-XEN:/etc/xen# xenstore-ls -fp

There were two domains here, domid 1 == "convirt" and domid 3 ==
"NAS-OVM", I've assumed domid 3 is the problem domain.

> /local/domain/0/backend/qdisk/3 = ""   (n0)
> /local/domain/0/backend/qdisk/3/768 = ""   (n0,r3)
> /local/domain/0/backend/qdisk/3/768/frontend = 
> "/local/domain/3/device/vbd/768"   (n0,r3)
> /local/domain/0/backend/qdisk/3/768/params = 
> "aio:/etc/xen/images/NAS-OMV.img"   (n0,r3)
> /local/domain/0/backend/qdisk/3/768/frontend-id = "3"   (n0,r3)
> /local/domain/0/backend/qdisk/3/768/online = "1"   (n0,r3)
> /local/domain/0/backend/qdisk/3/768/removable = "0"   (n0,r3)
> /local/domain/0/backend/qdisk/3/768/bootable = "1"   (n0,r3)
> /local/domain/0/backend/qdisk/3/768/state = "4"   (n0,r3)
> /local/domain/0/backend/qdisk/3/768/dev = "hda"   (n0,r3)
> /local/domain/0/backend/qdisk/3/768/type = "qdisk"   (n0,r3)
> /local/domain/0/backend/qdisk/3/768/mode = "w"   (n0,r3)
> /local/domain/0/backend/qdisk/3/768/device-type = "disk"   (n0,r3)
> /local/domain/0/backend/qdisk/3/768/feature-flush-cache = "1"   (n0,r3)
> /local/domain/0/backend/qdisk/3/768/feature-persistent = "1"   (n0,r3)
> /local/domain/0/backend/qdisk/3/768/info = "0"   (n0,r3)
> /local/domain/0/backend/qdisk/3/768/hotplug-status = "connected"   (n0,r3)
> /local/domain/0/backend/qdisk/3/768/sector-size = "512"   (n0,r3)
> /local/domain/0/backend/qdisk/3/768/sectors = "10485760"   (n0,r3)

Here is the qdisk backend for the rootfs .img file, it is in state 4 ==
XenBusConnected.

> /local/domain/0/backend/vbd/3 = ""   (n0)
> /local/domain/0/backend/vbd/3/832 = ""   (n0,r3)
> /local/domain/0/backend/vbd/3/832/frontend = "/local/domain/3/device/vbd/832" 
>   (n0,r3)
> /local/domain/0/backend/vbd/3/832/params = "/dev/sda"   (n0,r3)
> /local/domain/0/backend/vbd/3/832/script = "/etc/xen/scripts/block"   (n0,r3)
> /local/domain/0/backend/vbd/3/832/physical-device = "8:0"   (n0,r3)
> /local/domain/0/backend/vbd/3/832/frontend-id = "3"   (n0,r3)
> /local/domain/0/backend/vbd/3/832/online = "1"   (n0,r3)
> /local/domain/0/backend/vbd/3/832/removable = "0"   (n0,r3)
> /local/domain/0/backend/vbd/3/832/bootable = "1"   (n0,r3)
> /local/domain/0/backend/vbd/3/832/state = "4"   (n0,r3)
> /local/domain/0/backend/vbd/3/832/dev = "hdb"   (n0,r3)
> /local/domain/0/backend/vbd/3/832/type = "phy"   (n0,r3)
> /local/domain/0/backend/vbd/3/832/mode = "w"   (n0,r3)
> /local/domain/0/backend/vbd/3/832/device-type = "disk"   (n0,r3)
> /local/domain/0/backend/vbd/3/832/feature-flush-cache = "1"   (n0,r3)
> /local/domain/0/backend/vbd/3/832/feature-discard = "0"   (n0,r3)
> /local/domain/0/backend/vbd/3/832/feature-barrier = "1"   (n0,r3)
> /local/domain/0/backend/vbd/3/832/feature-persistent = "1"   (n0,r3)
> /local/domain/0/backend/vbd/3/832/feature-max-indirect-segments = "256"   
> (n0,r3)
> /local/domain/0/backend/vbd/3/832/sectors = "5860533168"   (n0,r3)
> /local/domain/0/backend/vbd/3/832/info = "0"   (n0,r3)
> /local/domain/0/backend/vbd/3/832/sector-size = "512"   (n0,r3)
> /local/domain/0/backend/vbd/3/832/physical-sector-size = "4096"   (n0,r3)
> 
> /local/domain/0/backend/vbd/3/5632 = ""   (n0,r3)
> /local/domain/0/backend/vbd/3/5632/frontend = 
> "/local/domain/3/device/vbd/5632"   (n0,r3)
> /local/domain/0/backend/vbd/3/5632/params = "/dev/sdb"   (n0,r3)
> /local/domain/0/backend/vbd/3/5632/script = "/etc/xen/scripts/block"   (n0,r3)
> /local/domain/0/backend/vbd/3/5632/physical-device = "8:10"   (n0,r3)
> /local/domain/0/backend/vbd/3/5632/frontend-id = "3"   (n0,r3)
> /local/domain/0/backend/vbd/3/5632/online = "1"   (n0,r3)
> /local/domain/0/backend/vbd/3/5632/removable = "0"   (n0,r3)
> /local/domain/0/backend/vbd/3/5632/bootable = "1"   (n0,r3)
> /local/domain/0/backend/vbd/3/5632/state = "4"   (n0,r3)
> /local/domain/0/backend/vbd/3/5632/dev = "hdc"   (n0,r3)
> /local/domain/0/backend/vbd/3/5632/type = "phy"   (n0,r3)
> /local/domain/0/backend/vbd/3/5632/mode = "w"   (n0,r3)
> /local/domain/0/backend/vbd/3/5632/device-type = "disk"   (n0,r3)
> /local/domain/0/backend/vbd/3/5632/feature-flush-cache = "1"   (n0,r3)
> /local/domain/0/backend/vbd/3/5632/feature-discard = "0"   (n0,r3)
> /local/domain/0/backend/vbd/3/5632/feature-barrier = "1"   (n0,r3)
> /local/domain/0/backend/vbd/3/5632/feature-persistent = "1"   (n0,r3)
> /local/domain/0/backend/vbd/3/5632/feature-max-indirect-segments = "256"   
> (n0,r3)
> /local/domain/0/backend/vbd/3/5632/sectors = "5860533168"   (n0,r3)
> /local/domain/0/backend/vbd/3/5632/info = "0"   (n0,r3)
> /local/domain/0/backend/vbd/3/5632/sector-size = "512"   (n0,r3)
> /local/domain/0/backend/vbd/3/5632/physical-sector-size = "4096"   (n0,r3)

Here are the two backends for the two data disks sda and sdb. Both are
in state 4, the physical-device's are 8:0 and 8:10 which are correct
AFAICT. 832==0x340 and 5632=0x1600, which are the major:minor of hdb and
hdc respectively. This all looks fine to me.


> /local/domain/3/device/vbd/768 = ""   (n3,r0)
> /local/domain/3/device/vbd/768/backend = 
> "/local/domain/0/backend/qdisk/3/768"   (n3,r0)
> /local/domain/3/device/vbd/768/backend-id = "0"   (n3,r0)
> /local/domain/3/device/vbd/768/state = "4"   (n3,r0)
> /local/domain/3/device/vbd/768/virtual-device = "768"   (n3,r0)
> /local/domain/3/device/vbd/768/device-type = "disk"   (n3,r0)
> /local/domain/3/device/vbd/768/ring-ref = "8"   (n3,r0)
> /local/domain/3/device/vbd/768/event-channel = "8"   (n3,r0)
> /local/domain/3/device/vbd/768/protocol = "x86_64-abi"   (n3,r0)

Here is the frontend for the rootfs. It is in state 4 and looks fine to
me.

> /local/domain/3/device/vbd/832 = ""   (n3,r0)
> /local/domain/3/device/vbd/832/backend = "/local/domain/0/backend/vbd/3/832"  
>  (n3,r0)
> /local/domain/3/device/vbd/832/backend-id = "0"   (n3,r0)
> /local/domain/3/device/vbd/832/state = "4"   (n3,r0)
> /local/domain/3/device/vbd/832/virtual-device = "832"   (n3,r0)
> /local/domain/3/device/vbd/832/device-type = "disk"   (n3,r0)
> /local/domain/3/device/vbd/832/ring-ref = "9"   (n3,r0)
> /local/domain/3/device/vbd/832/event-channel = "9"   (n3,r0)
> /local/domain/3/device/vbd/832/protocol = "x86_64-abi"   (n3,r0)

> /local/domain/3/device/vbd/5632 = ""   (n3,r0)
> /local/domain/3/device/vbd/5632/backend = 
> "/local/domain/0/backend/vbd/3/5632"   (n3,r0)
> /local/domain/3/device/vbd/5632/backend-id = "0"   (n3,r0)
> /local/domain/3/device/vbd/5632/state = "4"   (n3,r0)
> /local/domain/3/device/vbd/5632/virtual-device = "5632"   (n3,r0)
> /local/domain/3/device/vbd/5632/device-type = "disk"   (n3,r0)
> /local/domain/3/device/vbd/5632/ring-ref = "10"   (n3,r0)
> /local/domain/3/device/vbd/5632/event-channel = "10"   (n3,r0)
> /local/domain/3/device/vbd/5632/protocol = "x86_64-abi"   (n3,r0)

and here are the two data disks. which also look absolutely fine to me.

Is this an HVM guest? Can you gather a full dmesg from it rather than
the screenshot you posted previously please. If the thing isn't booting
enough to run dmesg then "xl console <domid> | tee log.file" might work.
Or you might need to set "serial ='pty'" in your config and then
configure the guest kernel to log to the console.

Ian.



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users