search for: config_pci_xen

...en version compatibility (4.0.0 and later) ---> After xen confiuration, please make sure that .config has the following parameter configuration: * CONFIG_XEN=y * CONFIG_XEN_MAX_DOMAIN_MEMORY=32 * CONFIG_XEN_SAVE_RESTORE=y * CONFIG_XEN_DOM0=y * CONFIG_XEN_PRIVILEGED_GUEST=y * CONFIG_XEN_PCI=y * CONFIG_PCI_XEN=y * CONFIG_XEN_BLKDEV_FRONTEND=m * CONFIG_NETXEN_NIC=m * CONFIG_XEN_NETDEV_FRONTEND=m * CONFIG_XEN_KBDDEV_FRONTEND=m * CONFIG_HVC_XEN=y * CONFIG_XEN_FBDEV_FRONTEND=m * CONFIG_XEN_BALLOON=y * CONFIG_XEN_SCRUB_PAGES=y * CONFIG_XEN_DEV_EVTCHN=y * CONFIG_XEN_BACKEND=y * CONFIG_XEN_BLKDEV_BACKEND=y * CO...

...0 console=hvc0 earlyprintk=xen module /archlinux/kernel26-my.img My dom0 kernel compilation options (grep -i xen .config): CONFIG_XEN=y CONFIG_XEN_DOM0=y CONFIG_XEN_PRIVILEGED_GUEST=y CONFIG_XEN_PVHVM=y CONFIG_XEN_MAX_DOMAIN_MEMORY=128 CONFIG_XEN_SAVE_RESTORE=y # CONFIG_XEN_DEBUG_FS is not set CONFIG_PCI_XEN=y CONFIG_XEN_PCIDEV_FRONTEND=m CONFIG_XEN_BLKDEV_FRONTEND=m CONFIG_NETXEN_NIC=m CONFIG_XEN_NETDEV_FRONTEND=m CONFIG_XEN_KBDDEV_FRONTEND=y CONFIG_HVC_XEN=y CONFIG_XEN_FBDEV_FRONTEND=y # Xen driver support CONFIG_XEN_BALLOON=y CONFIG_XEN_SCRUB_PAGES=y CONFIG_XEN_DEV_EVTCHN=y CONFIG_XEN_BACKEND=y CONF...

Hi, everyone! We google a lot, but can''t find how to config the pvscsi on our ubuntu13.04 PV on HVM.There are some links http://wiki.xen.org/wiki/Paravirtualized_SCSI http://wiki.xen.org/wiki/Xen_Configuration_File_Options And we use the config option above Configure PVSCSI devices vscsi = [ ''/dev/sdc, 0:0:0:0'' ] I pass sdc to the hvm, but in our pvhvm (ubuntu13.04)

Hi All, xen stable-2.6.31/master doesn''t seem to compile: CC [M] drivers/watchdog/w83877f_wdt.o CC [M] drivers/watchdog/w83977f_wdt.o CC [M] drivers/watchdog/machzwd.o CC [M] drivers/watchdog/sbc_epx_c3.o CC [M] drivers/watchdog/wm8350_wdt.o CC [M] drivers/watchdog/softdog.o CC drivers/xen/grant-table.o CC drivers/xen/features.o CC

...39; ] # vif = [ ''ip=78.46.97.66, vifname=veth1'' ] # none for now Here are some details on the Dom0 kernel (grepping for "xen"): CONFIG_XEN=y CONFIG_XEN_DOM0=y CONFIG_XEN_PRIVILEGED_GUEST=y CONFIG_XEN_PVHVM=y CONFIG_XEN_MAX_DOMAIN_MEMORY=500 CONFIG_XEN_SAVE_RESTORE=y CONFIG_PCI_XEN=y CONFIG_XEN_PCIDEV_FRONTEND=y # CONFIG_XEN_BLKDEV_FRONTEND is not set CONFIG_XEN_BLKDEV_BACKEND=y # CONFIG_XEN_NETDEV_FRONTEND is not set CONFIG_XEN_NETDEV_BACKEND=y CONFIG_INPUT_XEN_KBDDEV_FRONTEND=y CONFIG_HVC_XEN=y CONFIG_HVC_XEN_FRONTEND=y # CONFIG_XEN_WDT is not set # CONFIG_XEN_FBDEV_FRONTEN...

...t pci_dev *dev) -{ - return -1; -} -static inline int xen_register_device_domain_owner(struct pci_dev *dev, - uint16_t domain) -{ - return -1; -} -static inline int xen_unregister_device_domain_owner(struct pci_dev *dev) -{ - return -1; -} -#endif #if defined(CONFIG_PCI_MSI) #if defined(CONFIG_PCI_XEN) diff --git a/arch/x86/pci/xen.c b/arch/x86/pci/xen.c index 492ade8..e298726 100644 --- a/arch/x86/pci/xen.c +++ b/arch/x86/pci/xen.c @@ -108,7 +108,6 @@ static int acpi_register_gsi_xen_hvm(struct device *dev, u32 gsi, false /* no mapping of GSI to PIRQ */); } -#ifdef CONFIG_XEN_DOM0 sta...

...t pci_dev *dev) -{ - return -1; -} -static inline int xen_register_device_domain_owner(struct pci_dev *dev, - uint16_t domain) -{ - return -1; -} -static inline int xen_unregister_device_domain_owner(struct pci_dev *dev) -{ - return -1; -} -#endif #if defined(CONFIG_PCI_MSI) #if defined(CONFIG_PCI_XEN) diff --git a/arch/x86/pci/xen.c b/arch/x86/pci/xen.c index 492ade8..e298726 100644 --- a/arch/x86/pci/xen.c +++ b/arch/x86/pci/xen.c @@ -108,7 +108,6 @@ static int acpi_register_gsi_xen_hvm(struct device *dev, u32 gsi, false /* no mapping of GSI to PIRQ */); } -#ifdef CONFIG_XEN_DOM0 sta...

...t pci_dev *dev) -{ - return -1; -} -static inline int xen_register_device_domain_owner(struct pci_dev *dev, - uint16_t domain) -{ - return -1; -} -static inline int xen_unregister_device_domain_owner(struct pci_dev *dev) -{ - return -1; -} -#endif #if defined(CONFIG_PCI_MSI) #if defined(CONFIG_PCI_XEN) diff --git a/arch/x86/pci/xen.c b/arch/x86/pci/xen.c index 492ade8..e298726 100644 --- a/arch/x86/pci/xen.c +++ b/arch/x86/pci/xen.c @@ -108,7 +108,6 @@ static int acpi_register_gsi_xen_hvm(struct device *dev, u32 gsi, false /* no mapping of GSI to PIRQ */); } -#ifdef CONFIG_XEN_DOM0 sta...

...ep -i xen /boot/config-2.6.32-5-xen-amd64 CONFIG_XEN=y CONFIG_XEN_MAX_DOMAIN_MEMORY=32 CONFIG_XEN_SAVE_RESTORE=y # CONFIG_XEN_DEBUG_FS is not set CONFIG_SWIOTLB_XEN=y CONFIG_MICROCODE_XEN=y CONFIG_XEN_DOM0=y CONFIG_XEN_PRIVILEGED_GUEST=y CONFIG_XEN_DOM0_PCI=y # CONFIG_XEN_PCI_PASSTHROUGH is not set CONFIG_PCI_XEN=y CONFIG_XEN_PCIDEV_FRONTEND=y CONFIG_XEN_BLKDEV_FRONTEND=m CONFIG_NETXEN_NIC=m CONFIG_XEN_NETDEV_FRONTEND=m CONFIG_XEN_KBDDEV_FRONTEND=y CONFIG_HVC_XEN=y CONFIG_XEN_FBDEV_FRONTEND=y CONFIG_XEN_BALLOON=y CONFIG_XEN_SCRUB_PAGES=y CONFIG_XEN_DEV_EVTCHN=m CONFIG_XEN_BACKEND=y CONFIG_XEN_NETDEV_BACKEND...

Hi list, I am starting a academic security related project and I was wondering if there is any documentation on compiling xen/dom0 with a recent kernel? I''ve seen a few good intentioned threads, but no real documentation so far. Any helpful pointers will be greatly appreciated! Thanks in advance, - SDG P.S: First mail, not sure if I should post it here...let me know if I am on the

Xen Community: As many of you are aware, the Xen 4.0 hypervisor is due to ship tomorrow (shhhh, don''t tell anyone) and I wanted to get submissions underway for Xen 4.1 features. I have updated the Roadmap Wiki page (http://wiki.xensource.com/xenwiki/XenRoadMap) with a new section for Xen 4.1 features to be added. Feel free to add your ideas or send me your features and I will update the

Xen Community: As many of you are aware, the Xen 4.0 hypervisor is due to ship tomorrow (shhhh, don''t tell anyone) and I wanted to get submissions underway for Xen 4.1 features. I have updated the Roadmap Wiki page (http://wiki.xensource.com/xenwiki/XenRoadMap) with a new section for Xen 4.1 features to be added. Feel free to add your ideas or send me your features and I will update the

Hello, I''m facing a strange issue with network card PCI passthrough on my openwrt test domU. - With network PCI passthrough, DNS lookup failed for some domains (exemple, google.com) but not for other (free.fr my ISP, or my domain jbfavre.org). I can ping an IP address without any problem. - Starting domU as a "normal" (ie without PCI passthrough), no problem. As far as I can

On 12/20/2011 10:47 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20111220: drivers/xen/xenbus/xenbus_dev_backend.c:74:2: error: implicit declaration of function ''xen_initial_domain'' Full randconfig file is attached. -- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code ***

Hello, http://www.phoronix.com/scan.php?page=article&item=ubuntu_1110_xenkvm&num=1 Ubuntu 11.10 with Xen 4.1.1 and Linux 3.0. Xen seems to be doing very poorly on that benchmark. If someone has time to repeat that benchmark it would be good.. Comparing the results to those from Stefano from XenSummit 2011 NA there has be something wrong.. the results at XenSummit were pretty much the

Hello! I'm having problems getting PCI pass-through to work. This is on a AMD64 system, paravirtualized with xen-hypervisor-4.0-amd64 4.0.0-1~experimental.1, dom0: linux-image-2.6.32-5-xen-amd64 2.6.32-12. From IRC, earlier today: <tschwinge> waldi: Aren't the Debian xen domU-capable kernels supposed to contain the PCI frontend (needed for PCI pass-through)? I'm getting:

Hello! I'm having problems getting PCI pass-through to work. This is on a AMD64 system, paravirtualized with xen-hypervisor-4.0-amd64 4.0.0-1~experimental.1, dom0: linux-image-2.6.32-5-xen-amd64 2.6.32-12. From IRC, earlier today: <tschwinge> waldi: Aren't the Debian xen domU-capable kernels supposed to contain the PCI frontend (needed for PCI pass-through)? I'm getting:

Hello, i''ve a xen-4.0.0-rc1 with 2.6.31.6 pv_ops. Dom0 seams to work fine. But i can only boot "old" domU kernel. A pv_ops Kernel hangs after initrd. Regards, Stefan Kuhne _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hello, i''ve a xen-4.0.0-rc1 with 2.6.31.6 pv_ops. Dom0 seams to work fine. But i can only boot "old" domU kernel. A pv_ops Kernel hangs after initrd. Regards, Stefan Kuhne _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...MOD=y # # shared options # CONFIG_X86_SPEEDSTEP_LIB=y # # CPU Idle # CONFIG_CPU_IDLE=y # CONFIG_CPU_IDLE_GOV_LADDER is not set CONFIG_CPU_IDLE_GOV_MENU=y # CONFIG_ARCH_NEEDS_CPU_IDLE_COUPLED is not set # # Bus options (PCI etc.) # CONFIG_PCI=y CONFIG_PCI_DIRECT=y # CONFIG_PCI_MMCONFIG is not set CONFIG_PCI_XEN=y CONFIG_PCI_DOMAINS=y # CONFIG_PCI_CNB20LE_QUIRK is not set # CONFIG_PCIEPORTBUS is not set CONFIG_PCI_BUS_ADDR_T_64BIT=y # CONFIG_PCI_MSI is not set CONFIG_PCI_QUIRKS=y # CONFIG_PCI_DEBUG is not set # CONFIG_PCI_REALLOC_ENABLE_AUTO is not set CONFIG_PCI_STUB=m CONFIG_XEN_PCIDEV_FRONTEND=y CONFIG_...