similar to: [PATCH] XM on XenAPI: Enable ''xm pci-attach/detach'' via XenAPI

Currently console class''s "other_config" parameters (such as "vnclisten" and "vncpasswd") are not passed to xend when creating a domain by xm command through xen-api. The attached patch fixes this problem. Regards, ----------------------- Yosuke Iwamatsu NEC Corporation _______________________________________________ Xen-devel mailing list

Add direct pci device assignment support. This patch depends on the previous patch (1/3). ----------------------------------------- Fields for DPCI class: (RO_inst) VM PPCI hotplug_slot <- same as vslot param of pci-attach/detach. (RO_run) virtual_domain virtual_bus virtual_slot virtual_func virtual_name <- domain:bus:slot:func

This is a small fix of the error handling in device_create(). Signed-off-by: Yosuke Iwamatsu <y-iwamatsu@ab.jp.nec.com> Regards, ----------------------- Yosuke Iwamatsu NEC Corporation _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

When destroying pcifront/pciback, the following message appears in the guest linux kernel log. WARNING: g.e. still in use! WARNING: leaking g.e. and page still in use! This is caused by the wrong disconnect procedure that pcifront terminates the gnttab foreign access before pciback unmaps the ring. This patch corrects the handling of pcifront/pciback destruction sequence. Firstly pcifront

Xend doesn''t correctly work after restart, when there is a domU which owns a pci device (driver domain). This patch fixes the problem. Regards, ------------------- Yosuke Iwamatsu NEC Corporation _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi, It seems that destroying pcifront/pciback always fails on current xen. This patch fixes the problem, making pciback switch to "Closed" state after pcifront switched to "Closing" state. Regards, ------------------- Yosuke Iwamatsu NEC Corporation _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Hi, I found the following problems. xm pci-attach command and xm pci-detach command fail on inactive managed domains. An attaching patch solves the problems. # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 1024 2 r----- 51.5 vm1 512 2

Hey everyone, I realize that people asking about PCI passthrough has been thoroughly beaten to death many a time, however I couldn''t find the answer to these questions anywhere (and I''d really like to know :P) so please just bare with me. I know the GART built into AMD chipsets can act as a "mini IOMMU" and do DMA translation but not protection/isolation. However,

Is there a good reason why arguments to 'attach' and 'detach' differ so much? Yes, I know this is the documented behaviour, it just seems to violate the principle of least surprise. Examples: file = "foo.RData" df = data.frame(x=1:10,y=1:10) attach(file) # attaches the RData file 'foo.RData' attach(df) # attaches the object df Not surprising in an

[R-0.50-a3] It seems intuitive that attach( .., pos = 1) is harder than other attach()es. But still... If it ever will work, it is even more important to have detach( .... , save = "VAR.name") ~~~~~~~ -------- to be working. The documentation says that detach(.) returns invisibly. Therefore, we don't NEED the above 'save = ' argument to detach, since we can

Hi all I just encountered a problem in libvirt while was trying to attach and detach a sr-iov vf to my VM The version of my libvirt is 1.1.1-0ubuntu8.5 I tried to attach the device using following xml <interface type='hostdev' managed='yes'> <mac address='5c:01:fd:12:34:58'/> <source> <address type='pci'

''xm block-attach'' doesn''t let me assign the same backend device anymore, even if I use ''r!'' or ''w!''. I think this has changed since 3.1.1 (or maybe since 3.1.0). Is this the way it is supposed to work? Thanks James _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Drop the dummy ttm backend implementation, add a real one for TTM_PL_FLAG_TT objects. The bin/unbind callbacks will call virtio_gpu_object_{attach,detach}, to update the object state on the host side, instead of invoking those calls from the move_notify() callback. With that in place the move and move_notify callbacks are not needed any more, so drop them. Signed-off-by: Gerd Hoffmann

Drop the dummy ttm backend implementation, add a real one for TTM_PL_FLAG_TT objects. The bin/unbind callbacks will call virtio_gpu_object_{attach,detach}, to update the object state on the host side, instead of invoking those calls from the move_notify() callback. With that in place the move and move_notify callbacks are not needed any more, so drop them. Signed-off-by: Gerd Hoffmann

Hi, I know this isn't a valid use case or generally sane thing to do, but we have a bug (link, with details, below) filed for a panic against a detach-disk/attach-disk sequence of an ext4 mounted vd device on a rhel kernel. The same sequence leads to the following BUG on an upstream kernel (3.7.0-rc5+ SMP x86_64 GNU/Linux): [ 75.114951] BUG: unable to handle kernel NULL pointer

Hi, I know this isn't a valid use case or generally sane thing to do, but we have a bug (link, with details, below) filed for a panic against a detach-disk/attach-disk sequence of an ext4 mounted vd device on a rhel kernel. The same sequence leads to the following BUG on an upstream kernel (3.7.0-rc5+ SMP x86_64 GNU/Linux): [ 75.114951] BUG: unable to handle kernel NULL pointer

Hi, folks I wroted the codes below. I have the trouble with the line start from "Dir.chdir". When I run this code, the FTP of photos is successfuly done. But, the display of browser is white out. When I comment out the line start from "Dir.chdir", the trouble doesn''t happen. Is there anything wrong with my usage of "Dir.chdir"? def ftp_photo

I have a large R program that I am constantly running over and over again. At the beginning of this program, I create a hige matrix and a huge dataframe but these are constant. What I mean by constant is that, if I run the program over later, I really should just use the old matrix and dataframe ( if they exist ) that were created in a previous run so that the program doesn't have to spend

Hi Mike and Jon, If I do this: dpkg -S /usr/lib/python2.7/dist-packages/XenAPI.py then I can see that the XenAPI python package is in fact xcp-xapi. This is quite annoying, because I will need it when building OpenStack nova, but xcp-xapi depends on the Xen hypervisor, which I don't care about when building Openstack. Said in another way: I'd like to avoid having to put

I trying to right a module that will control xen function from perl but i''m having a issue trying to understand what need to be send to the function (VM ref) create (session_id s, VM record args) from xenapi.pdf. Can someone please give me a snippet of what i should be passing to the function. I search Google but nothing came with that helped. -- View this message in context: