1. 29 5月, 2013 1 次提交
  2. 22 8月, 2012 1 次提交
  3. 20 4月, 2012 1 次提交
    • K
      xen/xenbus: Add quirk to deal with misconfigured backends. · 3066616c
      Konrad Rzeszutek Wilk 提交于
      A rather annoying and common case is when booting a PVonHVM guest
      and exposing the PV KBD and PV VFB - as broken toolstacks don't
      always initialize the backends correctly.
      
      Normally The HVM guest is using the VGA driver and the emulated
      keyboard for this (though upstream version of QEMU implements
      PV KBD, but still uses a VGA driver). We provide a very basic
      two-stage wait mechanism - where we wait for 30 seconds for all
      devices, and then for 270 for all them except the two mentioned.
      
      That allows us to wait for the essential devices, like network
      or disk for the full 6 minutes.
      
      To trigger this, put this in your guest config:
      
      vfb = [ 'vnc=1, vnclisten=0.0.0.0 ,vncunused=1']
      
      instead of this:
      vnc=1
      vnclisten="0.0.0.0"
      
      CC: stable@kernel.org
      Acked-by: NStefano Stabellini <stefano.stabellini@eu.citrix.com>
      [v3: Split delay in non-essential (30 seconds) and essential
       devices per Ian and Stefano suggestion]
      [v4: Added comments per Stefano suggestion]
      Signed-off-by: NKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>
      3066616c
  4. 14 3月, 2012 1 次提交
    • S
      xen/xenbus: ignore console/0 · 42c46e6b
      Stefano Stabellini 提交于
      Unfortunately xend creates a bogus console/0 frotend/backend entry pair
      on xenstore that console backends cannot properly cope with.
      Any guest behavior that is not completely ignoring console/0 is going
      to either cause problems with xenconsoled or qemu.
      Returning 0 or -ENODEV from xencons_probe is not enough because it is
      going to cause the frontend state to become 4 or 6 respectively.
      The best possible thing we can do here is just ignore the entry from
      xenbus_probe_frontend.
      Signed-off-by: NStefano Stabellini <stefano.stabellini@eu.citrix.com>
      Signed-off-by: NKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>
      42c46e6b
  5. 05 1月, 2012 1 次提交
    • J
      Xen: consolidate and simplify struct xenbus_driver instantiation · 73db144b
      Jan Beulich 提交于
      The 'name', 'owner', and 'mod_name' members are redundant with the
      identically named fields in the 'driver' sub-structure. Rather than
      switching each instance to specify these fields explicitly, introduce
      a macro to simplify this.
      
      Eliminate further redundancy by allowing the drvname argument to
      DEFINE_XENBUS_DRIVER() to be blank (in which case the first entry from
      the ID table will be used for .driver.name).
      
      Also eliminate the questionable xenbus_register_{back,front}end()
      wrappers - their sole remaining purpose was the checking of the
      'owner' field, proper setting of which shouldn't be an issue anymore
      when the macro gets used.
      
      v2: Restore DRV_NAME for the driver name in xen-pciback.
      Signed-off-by: NJan Beulich <jbeulich@suse.com>
      Cc: Jens Axboe <axboe@kernel.dk>
      Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
      Cc: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
      Cc: Ian Campbell <ian.campbell@citrix.com>
      Cc: David S. Miller <davem@davemloft.net>
      Signed-off-by: NKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>
      73db144b
  6. 01 11月, 2011 1 次提交
  7. 01 9月, 2011 1 次提交
    • O
      xen/pv-on-hvm kexec+kdump: reset PV devices in kexec or crash kernel · 116df6f0
      Olaf Hering 提交于
      After triggering a crash dump in a HVM guest, the PV backend drivers
      will remain in Connected state. When the kdump kernel starts the PV
      drivers will skip such devices. As a result, no root device is found and
      the vmcore cant be saved.
      
      A similar situation happens after a kexec boot, here the devices will be
      in the Closed state.
      
      With this change all frontend devices with state XenbusStateConnected or
      XenbusStateClosed will be reset by changing the state file to Closing ->
      Closed -> Initializing.  This will trigger a disconnect in the backend
      drivers. Now the frontend drivers will find the backend drivers in state
      Initwait and can connect.
      Signed-off-by: NOlaf Hering <olaf@aepfle.de>
      [v2:
        - add timeout when waiting for backend state change
        (based on feedback from Ian Campell)
        - extent printk message to include backend string
        - add comment to fall-through case in xenbus_reset_frontend]
      Signed-off-by: NKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>
      116df6f0
  8. 01 7月, 2011 1 次提交
  9. 17 3月, 2011 2 次提交
  10. 06 1月, 2011 6 次提交