[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Error with DRBD9 and Xen 4.6.5 with HVM Guest



On Thu, Sep 06, 2018 at 04:41:11PM +0200, Justin Pretorius wrote:
> Hello
> 
> This is my first ever email list help request, apologies if I have not 100%
> got the protocol correct.
> 
> I am currently using Xen on Ubuntu 16.04, and am using a number of PVM
> guests successfully using DRBD9 as primary root disk, but when testing an
> HVM PfSense (BSD) guest, I am having some issues.
> 
> DRBD9 is successfully set up and when creating the guest using the config as
> follows
> 
> disk=['drbd:disk1-firewall2,hda,w']
> 
> The guest will not create with the following info
> 
> xl -v create /etc/xen/firewall2.cfg
> 
> xc: detail: elf_parse_binary: phdr: paddr=0x100000 memsz=0x5b844
> xc: detail: elf_parse_binary: memory: 0x100000 -> 0x15b844
> xc: detail: VIRTUAL MEMORY ARRANGEMENT:
> xc: detail:   Loader:   0000000000100000->000000000015b844
> xc: detail:   Modules:  0000000000000000->0000000000000000
> xc: detail:   TOTAL:    0000000000000000->000000001f800000
> xc: detail:   ENTRY:    0000000000100630
> xc: detail: PHYSICAL MEMORY ALLOCATION:
> xc: detail:   4KB PAGES: 0x0000000000000200
> xc: detail:   2MB PAGES: 0x00000000000000fb
> xc: detail:   1GB PAGES: 0x0000000000000000
> xc: detail: elf_load_binary: phdr 0 at 0x7f979ffaa000 -> 0x7f979fffbdd1
> domainbuilder: detail: xc_dom_gnttab_hvm_seed: called, pfn=0xff000
> libxl: error: libxl_dm.c:1872:device_model_spawn_outcome: domain 74 device
> model: spawn failed (rc=-3)
> libxl: error: libxl_create.c:1344:domcreate_devmodel_started: device model
> did not start: -3
> libxl: error: libxl_dm.c:1987:kill_device_model: Device Model already exited
> libxl: error: libxl.c:1610:libxl__destroy_domid: non-existant domain 74
> libxl: error: libxl.c:1568:domain_destroy_callback: unable to destroy guest
> with domid 74
> libxl: error: libxl.c:1495:domain_destroy_cb: destruction of domain 74
> failed
> 
> Contents of guest log
> 
> qemu-system-i386: -drive
> file=disk1-firewall2,if=ide,index=0,media=disk,format=raw,cache=writeback:
> Could not open 'disk1-firewall2': No such file or directory

This is wrong, file= should point to some block device created by the
drbd hotplug script.

> 
> Contents of hotplug log
> 
> disk1-firewall2: State change failed: (-12) Device is held open by someone
> Command 'drbdsetup secondary disk1-firewall2' terminated with exit code 11

I'm afraid this is due to block hotplug scripts being run twice for
HVM guests, once for the PV disk and another time for the emulated
disk.

Could you please paste the full output of `xl -vvv create ...`, that
should contain all the calls to the hotplug scripts.

> And the guest is not started
> 
> If i try to attach to dom 0 :
> 
> xl block-list 0
> Vdev  BE  handle state evt-ch ring-ref BE-path
> 
> xl block-attach 0 'drbd:disk1-firewall2,hda,w'      (no errors or output)
> 
> xl block-list 0
> 
> Vdev  BE  handle state evt-ch ring-ref BE-path
> 768   0   0      4     102    8        /local/domain/0/backend/vbd/0/768
> 
> xl block-detach 0 768   (no errors or output)
> 
> xl block-list 0
> 
> Vdev  BE  handle state evt-ch ring-ref BE-path
> 
> So it mounts and unmounts fine manually, but not via the hotplug script?

When you attach to Dom0 you are also using the hotplug script.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.