Re: [Xen-users] Xen-users Digest, Vol 128, Issue 22

[Guilherme Suzuki <suzuki.gui@xxxxxxxxx>]

Message-ID:
    <CAFLBxZaPb62YkSiyL-G0AaRO_pVPhLNN+FEPW2SA88LCm9gVaA@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset=UTF-8

Hey guys!

I saw the string and thought to be useful in the matter. I have experienced vfio PCI passthru using qemu and kvm.

In that new technique, you can reboot and shutdown the hvm without worrying the graphics card will end up in an invalid state. Please try using a PCI express 3.0 card.

The only restriction still is that you wont be able to let the hvm hibernate, cause it wont wake back up (you have the option to kill the hvm and restart it though).

Grato,

Guilherme Suzuki
Consultor em TI para projetos Microsoft
http://www.guilhermesuzuki.com
11 - 992360535

skype: suzuki.guilherme

2015-10-19 10:00 GMT-02:00 <xen-users-request@xxxxxxxxxxxxx>:

Send Xen-users mailing list submissions to
    xen-users@xxxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
    http://lists.xen.org/cgi-bin/mailman/listinfo/xen-users
or, via email, send a message with subject or body 'help' to
    xen-users-request@xxxxxxxxxxxxx

You can reach the person managing the list at
    xen-users-owner@xxxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Xen-users digest..."


Today's Topics:

 Â1. oxenstored.service and xenstored.service do not Âstarting...
   (wagnermarques)
 Â2. Re: Windows 7 PCI hotplugging (George Dunlap)
 Â3. CentOS 6 on XenCenter 6.5 - X configuration error (pietrop)
 Â4. Does XEN on ARM support allocation for physical Âcontinuous
   memory on DOM0/U? (Tom)


----------------------------------------------------------------------

Message: 1
Date: Sat, 17 Oct 2015 20:15:28 -0700 (MST)
From: wagnermarques <wagnerdocri@xxxxxxxxx>
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] oxenstored.service and xenstored.service do not
    starting...
Message-ID: <1445138128413-5729146.post@xxxxxxxxxxxxx>
Content-Type: text/plain; charset=UTF-8

Hi folks, I am a begginer with xen.

I am on fedora 22 and these services do not want to start like showed
below.
What could I try to solve this, please?

best regards


*systemctl start oxenstored.service*
-- A unidade oxenstored.service est? sendo iniciada.
Out 17 23:44:09 localhost.localdomain systemd[1]: Stopped The Xen xenstore.
-- Subject: A unidade xenstored.service concluiu o desligamento
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A unidade xenstored.service concluiu o desligamento.
Out 17 23:44:09 localhost.localdomain audit[1]: <audit-1131> pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s
Out 17 23:44:09 localhost.localdomain systemd[1]: Stopping The Xen
xenstore...
-- Subject: Unidade xenstored.service sendo desligado
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A unidade xenstored.service est? sendo desligada.
Out 17 23:44:09 localhost.localdomain oxenstored[3294]: Xen Storage Daemon,
version 1.0
Out 17 23:44:09 localhost.localdomain oxenstored[3294]: *Fatal error:
exception Failure("evtchn bind_interdomain failed")
Out 17 23:44:09 localhost.localdomain systemd[1]: oxenstored.service: main
process exited, code=exited, status=2/INVALIDARGUMENT*
Out 17 23:44:09 localhost.localdomain systemd[1]: Failed to start The ocaml
version of Xen xenstore.
-- Subject: A unidade oxenstored.service falhou
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A unidade oxenstored.service falhou.
--
-- O resultado ? failed.
Out 17 23:44:09 localhost.localdomain systemd[1]: Unit oxenstored.service
entered failed state.
Out 17 23:44:09 localhost.localdomain systemd[1]: oxenstored.service failed.
Out 17 23:44:09 localhost.localdomain audit[1]: <audit-1130> pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s
Out 17 23:44:09 localhost.localdomain polkitd[883]: Unregistered
Authentication Agent for unix-process:3278:436181 (system bus name :1.
lines 1785-1819/1819 (END)




* systemctl start xenstored.service*
[root@localhost administrador]# journalctl -xe
Out 18 01:00:28 localhost.localdomain systemd[1]:
[/usr/lib/systemd/system/initial-setup-text.service:21] Support for option
SysVStartP
Out 18 01:00:28 localhost.localdomain systemd[1]:
[/usr/lib/systemd/system/initial-setup-graphical.service:14] Support for
option SysVS
Out 18 01:00:32 localhost.localdomain polkitd[883]: Registered
Authentication Agent for unix-process:4662:534487 (system bus name :1.26
Out 18 01:00:32 localhost.localdomain systemd[1]: Starting The Xen
xenstore...
-- Subject: Unidade xenstored.service sendo iniciado
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A unidade xenstored.service est? sendo iniciada.
Out 18 01:00:32 localhost.localdomain xenstored[4676]: Checking store ...
Out 18 01:00:32 localhost.localdomain xenstored[4676]: Checking store
complete.
Out 18 01:00:32 localhost.localdomain xenstored[4676]: Checking store ...
Out 18 01:00:32 localhost.localdomain xenstored[4676]: Checking store
complete.
Out 18 01:00:32 localhost.localdomain xenstored[4676]:* FATAL: Failed to
initialize dom0 state: Invalid argument*
Out 18 01:00:32 localhost.localdomain xenstored[4676]: full talloc report on
'null_context' (total 96 bytes in 3 blocks)
Out 18 01:00:32 localhost.localdomain xenstored[4676]: struct domain
contains  Â96 bytes in Â2 blocks (ref 0)
Out 18 01:00:32 localhost.localdomain xenstored[4676]: /local/domain/0
contains  Â16 bytes in Â1 blocks (ref 0)
Out 18 01:00:32 localhost.localdomain systemd[1]: xenstored.service: main
process exited, code=exited, status=1/FAILURE
Out 18 01:00:32 localhost.localdomain systemd[1]: Failed to start The Xen
xenstore.
-- Subject: A unidade xenstored.service falhou
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A unidade xenstored.service falhou.
--
-- O resultado ? failed.
Out 18 01:00:32 localhost.localdomain systemd[1]: Unit xenstored.service
entered failed state.
Out 18 01:00:32 localhost.localdomain systemd[1]: xenstored.service failed.




--
View this message in context: http://xen.1045712.n5.nabble.com/oxenstored-service-and-xenstored-service-do-not-starting-tp5729146.html
Sent from the Xen - User mailing list archive at Nabble.com.



------------------------------

Message: 2
Date: Mon, 19 Oct 2015 09:50:01 +0100
From: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>
To: Charlie Mei <cmei@xxxxxxxxxxxxxx>
Cc: "xen-users@xxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxx>,    Daniel Kats
    <dbkats@xxxxxxxxx>
Subject: Re: [Xen-users] Windows 7 PCI hotplugging
Message-ID:
    <CAFLBxZaPb62YkSiyL-G0AaRO_pVPhLNN+FEPW2SA88LCm9gVaA@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset=UTF-8

On Thu, Oct 15, 2015 at 10:29 PM, Charlie Mei <cmei@xxxxxxxxxxxxxx> wrote:
> Hi,
>
> What is the current state for PCI hotplugging in Windows 7 HVM? In
> particular, I am wondering if anyone else attempted hotplugging
> graphics cards using PCI passthrough in Xen. I can successfully boot
> Windows 7 HVM on top of Xen, and have PCI passthrough working for
> graphics cards. `pci-detach` of a graphics card not acting as a
> frame-buffer works fine, but re-attaching that card crashes not just
> the DomU Windows 7, but also Xen Dom0.

Crashing dom0 is certainly a bug. If there's any chance you could get
a serial log of the dom0 crash, I'm sure we'd appreciate it.

In your description you only talk about re-attaching a PCI device, but
you don't say what happens if you hot-plug it without having first
attached it to the guest: that is, if you boot the host, boot the
guest, then do "xl pci-attach".

It's significant because if it works before the card has ever been
attached, but not after, then there may be some issue with the FLR
(function-level reset), which is supposed to set the card back into
the state it started in at boot

Â-George



------------------------------

Message: 3
Date: Mon, 19 Oct 2015 10:49:52 +0100
From: pietrop <pulsarpietro@xxxxxxx>
To: xen-users@xxxxxxxxxxxxx
Subject: [Xen-users] CentOS 6 on XenCenter 6.5 - X configuration error
Message-ID: <1445248192.23955.7.camel@xxxxxxx>
Content-Type: text/plain; charset="utf-8"

Hi all,

I have installed a new VM using the CentOS 6 template and using a
CentOS-6.4-x86_64 DVD image, the minimal installation in itself went
fine but I am having problems when trying to have an X server running,
it looks like it can't understand which graphic hardware is in use.

This is how my Xorg -configure terminates :

[233786.108] No devices to configure. Configuration failed.

Whole logfile attached as "Xorg_configure", the file startx instead
contains the output for the "startx" command.

Is there anything I can do to fix this problem ? What's the actual
issue ?

Thanks in advance,
Pietro.

-------------- next part --------------
[234667.448]
X.Org X Server 1.15.0
Release Date: 2013-12-27
[234667.448] X Protocol Version 11, Revision 0
[234667.448] Build Operating System: c6b8 2.6.32-220.el6.x86_64
[234667.448] Current Operating System: Linux pietrop-centos 2.6.32-573.7.1.el6.x86_64 #1 SMP Tue Sep 22 22:00:00 UTC 2015 x86_64
[234667.448] Kernel command line: ro root=/dev/mapper/VolGroup-lv_root rd_NO_LUKS LANG=en_US.UTF-8 rd_NO_MD console=hvc0Â KEYTABLE=us rd_LVM_LV=VolGroup/lv_swap SYSFONT=latarcyrheb-sun16 crashkernel=129M@0M rd_LVM_LV=VolGroup/lv_root rd_NO_DM rhgb quiet
[234667.449] Build Date: 23 July 2015Â 05:32:11PM
[234667.449] Build ID: xorg-x11-server 1.15.0-36.el6.centos
[234667.449] Current version of pixman: 0.32.4
[234667.449]Â Â Before reporting problems, check http://wiki.centos.org/Documentation
    to make sure that you have the latest version.
[234667.449] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[234667.449] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Oct 19 10:45:57 2015
[234667.449] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[234667.449] (==) No Layout section. Using the first Screen section.
[234667.449] (==) No screen section available. Using defaults.
[234667.449] (**) |-->Screen "Default Screen Section" (0)
[234667.449] (**) |Â Â|-->Monitor "<default monitor>"
[234667.449] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
[234667.450] (==) Automatically adding devices
[234667.450] (==) Automatically enabling devices
[234667.450] (==) Not automatically adding GPU devices
[234667.450] (==) FontPath set to:
    catalogue:/etc/X11/fontpath.d,
    built-ins
[234667.450] (==) ModulePath set to "/usr/lib64/xorg/modules"
[234667.450] (II) The server relies on HAL to provide the list of input devices.
    If no devices become available, reconfigure HAL or disable AutoAddDevices.
[234667.450] (II) Loader magic: 0x823020
[234667.450] (II) Module ABI versions:
[234667.450]Â Â X.Org ANSI C Emulation: 0.4
[234667.450]Â Â X.Org Video Driver: 15.0
[234667.450]Â Â X.Org XInput driver : 20.0
[234667.450]Â Â X.Org Server Extension : 8.0
[234667.450] Initializing built-in extension Generic Event Extension
[234667.450] Initializing built-in extension SHAPE
[234667.450] Initializing built-in extension MIT-SHM
[234667.450] Initializing built-in extension XInputExtension
[234667.450] Initializing built-in extension XTEST
[234667.450] Initializing built-in extension BIG-REQUESTS
[234667.450] Initializing built-in extension SYNC
[234667.450] Initializing built-in extension XKEYBOARD
[234667.450] Initializing built-in extension XC-MISC
[234667.450] Initializing built-in extension SECURITY
[234667.450] Initializing built-in extension XINERAMA
[234667.450] Initializing built-in extension XFIXES
[234667.450] Initializing built-in extension RENDER
[234667.450] Initializing built-in extension RANDR
[234667.450] Initializing built-in extension COMPOSITE
[234667.450] Initializing built-in extension DAMAGE
[234667.450] Initializing built-in extension MIT-SCREEN-SAVER
[234667.450] Initializing built-in extension DOUBLE-BUFFER
[234667.450] Initializing built-in extension RECORD
[234667.450] Initializing built-in extension DPMS
[234667.450] Initializing built-in extension Present
[234667.450] Initializing built-in extension X-Resource
[234667.450] Initializing built-in extension XVideo
[234667.450] Initializing built-in extension XVideo-MotionCompensation
[234667.450] Initializing built-in extension SELinux
[234667.450] Initializing built-in extension XFree86-VidModeExtension
[234667.450] Initializing built-in extension XFree86-DGA
[234667.450] Initializing built-in extension XFree86-DRI
[234667.450] Initializing built-in extension DRI2
[234667.450] (II) LoadModule: "glx"
[234667.450] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[234667.452] (II) Module glx: vendor="X.Org Foundation"
[234667.452]Â Â compiled for 1.15.0, module version = 1.0.0
[234667.452]Â Â ABI class: X.Org Server Extension, version 8.0
[234667.452] (==) AIGLX enabled
[234667.452] Loading extension GLX
[234667.452] (==) Matched modesetting as autoconfigured driver 0
[234667.452] (==) Matched fbdev as autoconfigured driver 1
[234667.452] (==) Matched vesa as autoconfigured driver 2
[234667.452] (==) Assigned the driver to the xf86ConfigLayout
[234667.452] (II) LoadModule: "modesetting"
[234667.452] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[234667.452] (II) Module modesetting: vendor="X.Org Foundation"
[234667.452]Â Â compiled for 1.15.0, module version = 0.8.0
[234667.452]Â Â Module class: X.Org Video Driver
[234667.452]Â Â ABI class: X.Org Video Driver, version 15.0
[234667.452] (II) LoadModule: "fbdev"
[234667.452] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so
[234667.453] (II) Module fbdev: vendor="X.Org Foundation"
[234667.453]Â Â compiled for 1.15.0, module version = 0.4.3
[234667.453]Â Â Module class: X.Org Video Driver
[234667.453]Â Â ABI class: X.Org Video Driver, version 15.0
[234667.453] (II) LoadModule: "vesa"
[234667.453] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
[234667.453] (II) Module vesa: vendor="X.Org Foundation"
[234667.453]Â Â compiled for 1.15.0, module version = 2.3.2
[234667.453]Â Â Module class: X.Org Video Driver
[234667.453]Â Â ABI class: X.Org Video Driver, version 15.0
[234667.453] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[234667.453] (II) FBDEV: driver for framebuffer: fbdev
[234667.453] (II) VESA: driver for VESA chipsets: vesa
[234667.453] (--) using VT number 7

[234667.456] (WW) Falling back to old probe method for modesetting
[234667.456] (EE) open /dev/dri/card0: No such file or directory
[234667.456] (WW) Falling back to old probe method for fbdev
[234667.456] (II) Loading sub module "fbdevhw"
[234667.456] (II) LoadModule: "fbdevhw"
[234667.456] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
[234667.456] (II) Module fbdevhw: vendor="X.Org Foundation"
[234667.457]Â Â compiled for 1.15.0, module version = 0.0.2
[234667.457]Â Â ABI class: X.Org Video Driver, version 15.0
[234667.481] (EE) open /dev/fb0: No such device
[234667.481] (WW) Falling back to old probe method for vesa
[234667.481] (EE) No devices detected.
[234667.481] (EE)
Fatal server error:
[234667.481] (EE) no screens found(EE)
[234667.481] (EE)
Please consult the CentOS support
    Âat http://wiki.centos.org/Documentation
Âfor help.
[234667.481] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[234667.481] (EE)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Xorg_configure.log
Type: text/x-log
Size: 14521 bytes
Desc: not available
URL: <http://lists.xen.org/archives/html/xen-users/attachments/20151019/0455b768/attachment.bin>

------------------------------

Message: 4
Date: Mon, 19 Oct 2015 11:39:36 +0000
From: Tom Ting[???] <tom_ting@xxxxxxxxxxx>
To: "xen-users@xxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxx>
Subject: [Xen-users] Does XEN on ARM support allocation for physical
    continuous memory on DOM0/U?
Message-ID:
    <E8F5944927430A4692D17F10A7A7ACFDB809BF@xxxxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="big5"

Hi All

I am currently working on our platform using Kernel 4.1 / XEN 4.6 RC.
We have question about how to allocate physical continuous memory.
I?ve checked some documents and most of them claims IOMMU is a better solution, which is not support on our platform.
Is there document or where should I check for these information??

Thanks
Tom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xen.org/archives/html/xen-users/attachments/20151019/4843ab74/attachment.html>

------------------------------

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


End of Xen-users Digest, Vol 128, Issue 22
******************************************

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