search for: remove_id

...> the user should do: > > 1) echo ssss:bb:dd.f > /sys/bus/pci/devices/ssss:bb:dd.f/driver/unbind > 2) echo vvvv dddd > /sys/bus/pci/drivers/vfio-pci/new_id > 3) echo ssss:bb:dd.f > /sys/bus/pci/drivers/vfio-pci/bind > 4) echo vvvv dddd > /sys/bus/pci/drivers/vfio-pci/remove_id > > There are actually a number of ways you can do this and the default > autoprobe behavior really makes step 3) unnecessary as the driver core > will probe any unbound devices as soon as a new_id is added to vfio-pci. > That can be changed by: > > # echo 0 > /sys/bus/pci...

...> the user should do: > > 1) echo ssss:bb:dd.f > /sys/bus/pci/devices/ssss:bb:dd.f/driver/unbind > 2) echo vvvv dddd > /sys/bus/pci/drivers/vfio-pci/new_id > 3) echo ssss:bb:dd.f > /sys/bus/pci/drivers/vfio-pci/bind > 4) echo vvvv dddd > /sys/bus/pci/drivers/vfio-pci/remove_id > > There are actually a number of ways you can do this and the default > autoprobe behavior really makes step 3) unnecessary as the driver core > will probe any unbound devices as soon as a new_id is added to vfio-pci. > That can be changed by: > > # echo 0 > /sys/bus/pci...

Alex, I'm trying to think through how binding/unbinding of devices will work with VFIO for platform devices and have a couple of questions about how vfio-pci works. When you bind a device to vfio-pci, e.g.: # echo 1102 0002 > /sys/bus/pci/drivers/vfio-pci/new_id ...I understand that the echo into 'new_id' tells the vfio pci driver that it now handles the specified PCI ID. But

Alex, I'm trying to think through how binding/unbinding of devices will work with VFIO for platform devices and have a couple of questions about how vfio-pci works. When you bind a device to vfio-pci, e.g.: # echo 1102 0002 > /sys/bus/pci/drivers/vfio-pci/new_id ...I understand that the echo into 'new_id' tells the vfio pci driver that it now handles the specified PCI ID. But

...ort though. To bind a device, the user should do: 1) echo ssss:bb:dd.f > /sys/bus/pci/devices/ssss:bb:dd.f/driver/unbind 2) echo vvvv dddd > /sys/bus/pci/drivers/vfio-pci/new_id 3) echo ssss:bb:dd.f > /sys/bus/pci/drivers/vfio-pci/bind 4) echo vvvv dddd > /sys/bus/pci/drivers/vfio-pci/remove_id There are actually a number of ways you can do this and the default autoprobe behavior really makes step 3) unnecessary as the driver core will probe any unbound devices as soon as a new_id is added to vfio-pci. That can be changed by: # echo 0 > /sys/bus/pci/drivers_autoprobe But then we hav...

...t 0 Nov 10 09:55 module -> ../../../../module/pciback --w------- 1 root root 4096 Nov 10 09:55 new_id --w------- 1 root root 4096 Nov 10 09:55 new_slot -rw------- 1 root root 0 Nov 10 08:35 permissive -rw------- 1 root root 0 Nov 10 08:35 quirks --w------- 1 root root 4096 Nov 10 09:55 remove_id --w------- 1 root root 4096 Nov 10 09:55 remove_slot -r-------- 1 root root 4096 Nov 10 09:55 slots --w------- 1 root root 4096 Nov 10 09:55 unbind # Script do create the initrds KVER="2.6.18-164.6.1.el5xen" mkinitrd -f --omit-scsi-modules --omit-raid-modules \ --with=e1000e --with=xen...

...permissive > 0000:81:02.4? 0000:81:03.3? 0000:81:04.2? 0000:81:05.1? 0000:81:06.2 > 0000:81:07.1? 0000:81:08.0? 0000:81:08.7? bind?????????????? quirks > 0000:81:02.5? 0000:81:03.4? 0000:81:04.3? 0000:81:05.2? 0000:81:06.3 > 0000:81:07.2? 0000:81:08.1? 0000:81:09.0? irq_handlers?????? remove_id > 0000:81:02.6? 0000:81:03.5? 0000:81:04.4? 0000:81:05.3? 0000:81:06.4 > 0000:81:07.3? 0000:81:08.2? 0000:81:09.1? irq_handler_state? remove_slot > > [root at xen1 ~]# cat /sys/bus/pci/devices/0000\:81\:02.6/device > 0x154c > [root at xen1 ~]# cat /sys/bus/pci/devices/0000\:81\:...

...ule -> ../../../../module/xen_pciback --w------- 1 root root 4096 2010-05-07 16:35 new_id --w------- 1 root root 4096 2010-05-07 16:35 new_slot -rw------- 1 root root 4096 2010-05-07 16:35 permissive -rw------- 1 root root 4096 2010-05-07 16:35 quirks --w------- 1 root root 4096 2010-05-07 16:35 remove_id --w------- 1 root root 4096 2010-05-07 16:35 remove_slot -r-------- 1 root root 4096 2010-05-07 16:35 slots --w------- 1 root root 4096 2010-05-07 16:35 uevent --w------- 1 root root 4096 2010-05-07 16:35 unbind root@charles-dq45:~# xm pci-list-assignable-devices 0000:02:00.0 0000:01:00.0 root@ch...

...ule -> ../../../../module/xen_pciback --w------- 1 root root 4096 2010-05-07 16:35 new_id --w------- 1 root root 4096 2010-05-07 16:35 new_slot -rw------- 1 root root 4096 2010-05-07 16:35 permissive -rw------- 1 root root 4096 2010-05-07 16:35 quirks --w------- 1 root root 4096 2010-05-07 16:35 remove_id --w------- 1 root root 4096 2010-05-07 16:35 remove_slot -r-------- 1 root root 4096 2010-05-07 16:35 slots --w------- 1 root root 4096 2010-05-07 16:35 uevent --w------- 1 root root 4096 2010-05-07 16:35 unbind root@charles-dq45:~# xm pci-list-assignable-devices 0000:02:00.0 0000:01:00.0 root@ch...

Hello, I''ve recently installed a hvm domU opensuse 11 guest and I cannot set the screen resolution higher then 640x480. This seems very strange to me, because I don''t have any problem to set higher resolution on a windows 7 domU, using the following parameters in the configuration file: stdvga=1 videoram=16 What could the problem be? Is some video driver missing? -- Flavio

Hello, I''ve recently installed a hvm domU opensuse 11 guest and I cannot set the screen resolution higher then 640x480. This seems very strange to me, because I don''t have any problem to set higher resolution on a windows 7 domU, using the following parameters in the configuration file: stdvga=1 videoram=16 What could the problem be? Is some video driver missing? -- Flavio

Hello, I have been working on VGA-passthrough in the last month. When Xen was at his version 3.5 there was a few patches to make this work for some graphic cards using the patches developed by Han Weidong and posted here (http://lists.xensource.com/archives/html/xen-devel/2009-08/msg01176.html) and the same patches posted file by file are here

Hello, I have been working on VGA-passthrough in the last month. When Xen was at his version 3.5 there was a few patches to make this work for some graphic cards using the patches developed by Han Weidong and posted here (http://lists.xensource.com/archives/html/xen-devel/2009-08/msg01176.html) and the same patches posted file by file are here

Hello, It looks like upstream linux-2.6.git contains at least the following xen related new features for Linux 2.6.36: - Xen-SWIOTLB support (required for Xen PCI passthru and dom0) - Xen PV-on-HVM drivers - Xen VBD online dynamic resize of guest disks (xvd*) Congratulations! What are the plans for 2.6.37 merge window? I believe at least: - Xen PCI frontend Others? I''m going to