Re: [Xen-users] ubuntu13.04 host and ubuntu13.04 guest how to config the pvscsi

[é æ <altman87120@xxxxxxxxx>]

Thanks! 

But all we use is kernel 3.8.0-19-generic. Does this kernel include the 
scsifront/scsiback support? If not, how can we change add the support?

And this is our config file

root@ubuntu:/vm/config# cat ubuntu-i386-hvm.cfg 

builder="hvm"
name = "ubuntu-hvm"
cpus=["6","7"]
vcpus=2

memory = 8000
pae=1
acpi=1
apic=1

disk = ['phy:/vm/ubuntu-i386-hvm.raw,xvda,rw','phy:/dev/sdc,xvdb,rw']
#vif  = ['bridge=br0']
#vscsi = [ '/dev/sdc, 0:0:0:0' ]
vnc=1
vnclisten="0.0.0.0"
boot="dc"
pci = [ '06:10.1' ]
xen_platform_pci=1

the output of xl -vvv create domain.config
----------------------------------
Parsing config from ubuntu-i386-hvm.cfg
libxl: debug: libxl_create.c:1174:do_domain_create: ao 0x1015af0: create: 
how=(nil) callback=(nil) poller=0x1015b50
libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda 
spec.backend=unknown
libxl: debug: libxl_device.c:175:disk_try_backend: Disk vdev=xvda, backend phy 
unsuitable as phys path not a block device
libxl: debug: libxl_device.c:184:disk_try_backend: Disk vdev=xvda, backend tap 
unsuitable because blktap not available
libxl: debug: libxl_device.c:265:libxl__device_disk_set_backend: Disk 
vdev=xvda, using backend qdisk
libxl: debug: libxl_create.c:677:initiate_domain_create: running bootloader
libxl: debug: libxl_bootloader.c:321:libxl__bootloader_run: not a PV domain, 
skipping bootloader
libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch 
w=0x1015f00: deregister unregistered
xc: detail: elf_parse_binary: phdr: paddr=0x100000 memsz=0x7c348
xc: detail: elf_parse_binary: memory: 0x100000 -> 0x17c348
xc: info: VIRTUAL MEMORY ARRANGEMENT:
  Loader:        0000000000100000->000000000017c348
  TOTAL:         0000000000000000->00000001f3800000
  ENTRY ADDRESS: 0000000000100608
xc: info: PHYSICAL MEMORY ALLOCATION:
  4KB PAGES: 0x0000000000000200
  2MB PAGES: 0x000000000000039b
  1GB PAGES: 0x0000000000000006
xc: detail: elf_load_binary: phdr 0 at 0x0x7f59a863e000 -> 0x0x7f59a86b11e0
libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda 
spec.backend=qdisk
libxl: debug: libxl_dm.c:1142:libxl__spawn_local_dm: Spawning device-model 
/usr/lib/xen-4.2/bin/qemu-dm with arguments:
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   
/usr/lib/xen-4.2/bin/qemu-dm
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   -d
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   4
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   -domain-name
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   ubuntu-hvm
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   -vnc
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   0.0.0.0:0
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   -vncunused
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   -videoram
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   8
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   -boot
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   dc
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   -acpi
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   -vcpus
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   2
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   -vcpu_avail
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   0x03
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   -net
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   none
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   -M
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   xenfv
libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch w=0x1016138 
wpath=/local/domain/0/device-model/4/state token=3/0: register slotnum=3
libxl: debug: libxl_create.c:1187:do_domain_create: ao 0x1015af0: inprogress: 
poller=0x1015b50, flags=i
libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x1016138 
wpath=/local/domain/0/device-model/4/state token=3/0: event 
epath=/local/domain/0/device-model/4/state
libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x1016138 
wpath=/local/domain/0/device-model/4/state token=3/0: event 
epath=/local/domain/0/device-model/4/state
libxl: debug: libxl_event.c:549:libxl__ev_xswatch_deregister: watch w=0x1016138 
wpath=/local/domain/0/device-model/4/state token=3/0: deregister slotnum=3
libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch 
w=0x1016138: deregister unregistered
libxl: debug: libxl_pci.c:85:libxl__create_pci_backend: Creating pci backend
libxl: debug: libxl_event.c:1667:libxl__ao_progress_report: ao 0x1015af0: 
progress report: ignored
libxl: debug: libxl_event.c:1499:libxl__ao_complete: ao 0x1015af0: complete, 
rc=0
libxl: debug: libxl_event.c:1471:libxl__ao__destroy: ao 0x1015af0: destroy
Daemon running with PID 4296
xc: debug: hypercall buffer: total allocations:681 total releases:681
xc: debug: hypercall buffer: current allocations:0 maximum allocations:2
xc: debug: hypercall buffer: cache current size:2
xc: debug: hypercall buffer: cache hits:677 misses:2 toobig:2



On 2013-4-26, at äå4:43, Wei Liu <wei.liu2@xxxxxxxxxx> wrote:

> On Fri, Apr 26, 2013 at 07:26:50AM +0100, é æ wrote:
>> Hi, everyone!
> [...]
>> 
>> root@ubuntu-hvm:/home/zdht# dmesg |egrep '(xen|front)'
>> [    0.000000] Netfront and the Xen platform PCI driver have been compiled 
>> for this kernel: unplug emulated NICs.
>> [    0.000000] Blkfront and the Xen platform PCI driver have been compiled 
>> for this kernel: unplug emulated disks.
>> [    0.214429] xen/balloon: Initialising balloon driver.
>> [    0.216042] xen-balloon: Initialising balloon driver.
>> [    0.604023] Switching to clocksource xen
>> [    0.611813] xen: --> pirq=16 -> irq=8 (gsi=8)
>> [    0.611880] xen: --> pirq=17 -> irq=12 (gsi=12)
>> [    0.611925] xen: --> pirq=18 -> irq=1 (gsi=1)
>> [    0.611970] xen: --> pirq=19 -> irq=6 (gsi=6)
>> [    0.612022] xen: --> pirq=20 -> irq=4 (gsi=4)
>> [    0.612105] xen: --> pirq=21 -> irq=7 (gsi=7)
>> [    1.140448] xen: --> pirq=22 -> irq=28 (gsi=28)
>> [    1.198538] blkfront: xvda: barrier: enabled
>> 
> 
> Can you confirm if your kernel has scsifront / scsiback support?
> 
> Also have a look at xenstore-ls output, look for pvscsi related node.
> 'xl -vvv create domain.config' can give you more info.
> 
> 
> Wei.
> 
>> 
>> Does anyone can tell me why there is no scsifront and no use the  
>> vscsi=['/dev/sdc, 0:0:0:0'] in our configuration ?
>> 
> 
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@xxxxxxxxxxxxx
>> http://lists.xen.org/xen-users
> 


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