search for: deassign

...ch is for xen-4.1-testing.hg. diff -r 3ce155e77f39 xen/arch/x86/domctl.c --- a/xen/arch/x86/domctl.c +++ b/xen/arch/x86/domctl.c @@ -873,7 +873,7 @@ long arch_do_domctl( break; } - ret = xsm_assign_device(d, domctl->u.assign_device.machine_bdf); + ret = xsm_deassign_device(d, domctl->u.assign_device.machine_bdf); if ( ret ) goto deassign_device_out;

Hi, all, The attached patches try to improve the current FLR logic. The idea is: removing the FLR logic from hypervisor and adding the improved logic in Control Panel. The current FLR logic in hypervisor has some issues: 1) Dstate transition is not guaranteed to properly clear the device state; 2) the current code for PCIe FLR is actually buggy: PCI_EXP_DEVSTA_TRPND doesn''t mean the

..."IT admins", but logic is same;)Thank you. However I have one more problem. If I create new group or user and give it UID/GID, this is immediately reachable on linux server. id user, or getent group/passwd and also wbinfo -u/-g/-i can list info about it. But if I assign group to user (or deassign), it spends a lot of time to reflect this change. nsswitch.conf is set up corectly. I tried to "net cache flush", but no luck. Tried restart winbind service and also delete winbindd_cache.tdb and winbindd_idmap.tdb files and restart winbind, but no luck. Still old groups. I even tried to...

...MU is enabled (can see that from the dmesg output). All i get on the console when i try to start the vm is the following: Fehler: internal error process exited while connecting to monitor: char device redirected to /dev/pts/3 Failed to assign device "14:00.2" : Invalid argument Failed to deassign device "14:00.2" : Invalid argument Failed to initialize assigned device host=14:00.2 SELinux ist disabled. Does anyone have any hint what could have possibly gone wrong? As an additional info: "virsh nodeddev-list" also doesn't work. I don't know if I mix that up, bu...

...version: 0.9.13 > * dmesg* > [ 158.017387] virbr0: port 1(vnet0) entered forwarding state > [ 158.017395] virbr0: port 1(vnet0) entered forwarding state > [ 158.017615] ADDRCONF(NETDEV_CHANGE): virbr0: link becomes ready > [ 158.476879] assign device 0:3:2.0 > [ 158.477080] deassign device 0:3:2.0 > [ 158.719521] virbr0: port 1(vnet0) entered disabled state > [ 158.719673] device vnet0 left promiscuous mode > any help would be greatly appreciated. mike allison -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redha...

...hing. ------------------------------------------------------------ changeset: 23111:cb22fa57ff25 tag: tip user: Tim Deegan <Tim.Deegan@citrix.com> date: Mon Jul 25 16:48:39 2011 +0100 VT-d: always clean up dpci timers. If a VM has all its PCI devices deassigned, need_iommu(d) becomes false but it might still have DPCI EOI timers that were init_timer()d but not yet kill_timer()d. That causes xen to crash later because the linked list of inactive timers gets corrupted, e.g.: (XEN) Xen call trace: (XEN) [<ffff82c480126256&gt...

...hing. ------------------------------------------------------------ changeset: 23111:cb22fa57ff25 tag: tip user: Tim Deegan <Tim.Deegan@citrix.com> date: Mon Jul 25 16:48:39 2011 +0100 VT-d: always clean up dpci timers. If a VM has all its PCI devices deassigned, need_iommu(d) becomes false but it might still have DPCI EOI timers that were init_timer()d but not yet kill_timer()d. That causes xen to crash later because the linked list of inactive timers gets corrupted, e.g.: (XEN) Xen call trace: (XEN) [<ffff82c480126256&gt...

...ed_irq_data); @@ -913,15 +849,17 @@ static void assigned_dev_update_msix(PCIDevice *pci_dev, unsigned int ctrl_pos) if (assigned_dev->irq_requested_type) { assigned_irq_data.flags = assigned_dev->irq_requested_type; - free_dev_irq_entries(assigned_dev); r = kvm_deassign_irq(kvm_context, &assigned_irq_data); /* -ENXIO means no assigned irq */ if (r && r != -ENXIO) perror("assigned_dev_update_msix: deassign irq"); } + + msix_write_config(pci_dev, address, val, len); + assigned_irq_data.flags = KVM_DEV...

...ed_irq_data); @@ -913,15 +849,17 @@ static void assigned_dev_update_msix(PCIDevice *pci_dev, unsigned int ctrl_pos) if (assigned_dev->irq_requested_type) { assigned_irq_data.flags = assigned_dev->irq_requested_type; - free_dev_irq_entries(assigned_dev); r = kvm_deassign_irq(kvm_context, &assigned_irq_data); /* -ENXIO means no assigned irq */ if (r && r != -ENXIO) perror("assigned_dev_update_msix: deassign irq"); } + + msix_write_config(pci_dev, address, val, len); + assigned_irq_data.flags = KVM_DEV...

...ed_irq_data); @@ -914,15 +848,17 @@ static void assigned_dev_update_msix(PCIDevice *pci_dev, unsigned int ctrl_pos) if (assigned_dev->irq_requested_type) { assigned_irq_data.flags = assigned_dev->irq_requested_type; - free_dev_irq_entries(assigned_dev); r = kvm_deassign_irq(kvm_context, &assigned_irq_data); /* -ENXIO means no assigned irq */ if (r && r != -ENXIO) perror("assigned_dev_update_msix: deassign irq"); } + + msix_write_config(pci_dev, address, val, len); + assigned_irq_data.flags = KVM_DEV...

...ed_irq_data); @@ -914,15 +848,17 @@ static void assigned_dev_update_msix(PCIDevice *pci_dev, unsigned int ctrl_pos) if (assigned_dev->irq_requested_type) { assigned_irq_data.flags = assigned_dev->irq_requested_type; - free_dev_irq_entries(assigned_dev); r = kvm_deassign_irq(kvm_context, &assigned_irq_data); /* -ENXIO means no assigned irq */ if (r && r != -ENXIO) perror("assigned_dev_update_msix: deassign irq"); } + + msix_write_config(pci_dev, address, val, len); + assigned_irq_data.flags = KVM_DEV...

Hi All, I''m new on ZFS, so I hope this isn''t too basic a question. I have a host where I setup ZFS. The Oracle DBAs did their thing and I know have a number of ZFS datasets with their respective clones and snapshots on serverA. I want to export some of the clones to serverB. Do I need to zone serverB to see the same LUNs as serverA? Or does it have to have preexisting,

This patch adds the function that reassign page-aligned memory resources, to dom0 linux. The function is useful when we assign I/O device to HVM domain using pci passthrough. When we assign a device to HVM domain using pci passthrough, the device needs to be assigned page-aligned memory resources. If the memory resource is not page-aligned, following error occurs. Error: pci: 0000:00:1d.7: