Re: [Xen-users] adding fourth device to pvhvm config causes DomU launch fail @ "device_disk_add: device already exists in xenstore" ?

[suse.dev@xxxxxx]

On Mon, Feb 22, 2016, at 08:30 AM, Roger Pau Monné wrote:
> Hm, what error do you get if you translate all them to xvd* except for
> the CD device?

With

        disk          = [ 'phy:/dev/VG0/tEFI,xvda,w',
                          'phy:/dev/VG0/tBOOT,xvdb,w',
                          'phy:/dev/VG0/tSWAP,xvdc,w',
                          'phy:/dev/VG0/tROOT,xvdd,w',
                          
'file:/home/test/archlinux-2016.02.01-dual.iso,hde:cdrom,r',
                        ]

launch fails

        Parsing config from ./arch.cfg
        got a tsc mode string: "default"
        libxl: error: libxl.c:2615:libxl__device_from_disk: Invalid or 
unsupported virtual disk identifier hde
        libxl: error: libxl.c:2728:device_disk_add: Invalid or unsupported 
virtual disk identifier hde
        libxl: error: libxl_create.c:1175:domcreate_launch_dm: unable to add 
disk devices
        libxl: error: libxl_dm.c:1966:kill_device_model: unable to find device 
model pid in /local/domain/12/image/device-model-pid
        libxl: error: libxl.c:1628:libxl__destroy_domid: 
libxl__destroy_device_model failed for 12
        libxl: error: libxl.c:1591:libxl__destroy_domid: non-existant domain 12
        libxl: error: libxl.c:1549:domain_destroy_callback: unable to destroy 
guest with domid 12
        libxl: error: libxl.c:1476:domain_destroy_cb: destruction of domain 12 
failed

but this works

        disk          = [ 'phy:/dev/VG0/tEFI,xvda,w',
                          'phy:/dev/VG0/tBOOT,xvdb,w',
                          'phy:/dev/VG0/tSWAP,xvdc,w',
                          'phy:/dev/VG0/tROOT,xvde,w',
                          
'file:/home/test/archlinux-2016.02.01-dual.iso,hdd:cdrom,r',
                        ]

as does

        disk          = [ 'phy:/dev/VG0/tEFI,xvdb,w',
                          'phy:/dev/VG0/tBOOT,xvdc,w',
                          'phy:/dev/VG0/tSWAP,xvdd,w',
                          'phy:/dev/VG0/tROOT,xvde,w',
                          
'file:/home/test/archlinux-2016.02.01-dual.iso,hda:cdrom,r',
                        ]

It seems like as long as hdX <= 'hdd', for any/all devices, all other devs can 
be xvdX.  I avoided, but did not test, collisions between hdX & xvdX.


> AFAICT there's some quirk on Linux when running as a PVHVM guest, and
> the CD device always has to be emulated. The reason behind this seem to
> be that using a PV CD on older Xen versions was broken:

Thanks, I've got a working solution ... still with some 'guesses'.  TBH, it's 
pretty confusing even reading the docs.

It'd be MUCH easier to be able to just use all xvdX, and be done with it.  But, 
I don't at all know if that's even possible :-/

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