http://blog.gmane.org/gmane.comp.emulators.xen.devel hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.emulators.xen.devel/131454 <pre>Hi Pasi, Thanks a lot for the info! I will try it. Kenneth ________________________________________ From: Pasi Kärkkäinen [pasik&lt; at &gt;iki.fi] Sent: Wednesday, May 23, 2012 11:18 PM To: Kenneth Wong Cc: xen-devel&lt; at &gt;lists.xen.org Subject: Re: [Xen-devel] Loading PCIe Device Driver at Dom0 On Wed, May 23, 2012 at 07:41:34PM -0700, Kenneth Wong wrote: PCI/DMA APIs are the Linux kernel APIs, not Xen specific. Quick googling reveals: http://www.mjmwired.net/kernel/Documentation/DMA-API.txt http://www.mjmwired.net/kernel/Documentation/DMA-API-HOWTO.txt </pre> Kenneth Wong 2012-05-24T07:10:57 http://permalink.gmane.org/gmane.comp.emulators.xen.devel/131453 <pre> Sorry for the misunderstanding, I mean the GUI doesn't work when dom0 is loaded. That is, at the login screen it freezes so I can't go on. dom0 works fine without the GUI. I tried to start X manually and the GUI loads but it's frozen so there's no possible use of it. </pre> eva 2012-05-24T07:10:51 http://permalink.gmane.org/gmane.comp.emulators.xen.devel/131452 <pre> PCI/DMA APIs are the Linux kernel APIs, not Xen specific. Quick googling reveals: http://www.mjmwired.net/kernel/Documentation/DMA-API.txt http://www.mjmwired.net/kernel/Documentation/DMA-API-HOWTO.txt </pre> Pasi Kärkkäinen 2012-05-24T06:18:06 http://permalink.gmane.org/gmane.comp.emulators.xen.devel/131451 <pre>flight 12968 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/12968/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking): test-amd64-amd64-xl-sedf 10 guest-saverestore fail pass in 12967 test-amd64-amd64-xl-qemuu-win7-amd64 12 guest-localmigrate/x10 fail pass in 12967 Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-pcipt-intel 9 guest-start fail never pass test-amd64-i386-rhel6hvm-intel 11 leak-check/check fail never pass test-amd64-i386-qemuu-rhel6hvm-amd 11 leak-check/check fail never pass test-amd64-i386-qemuu-rhel6hvm-intel 11 leak-check/check fail never pass test-amd64-i386-xend-winxpsp3 16 leak-check/check fail never pass test-i386-i386-xl-qemuu-winxpsp3 13 guest-stop fail never pass test-amd64-amd64-win 16 leak-check/check fail never pass test-amd64-i386-win-vcpus1 16 leak-check/check fail never pass test-amd64-i386-rhel6hvm-amd 11 leak-check/check fail never pass test-amd64-i386-xl-win7-amd64 13 guest-stop fail never pass test-i386-i386-xl-winxpsp3 13 guest-stop fail never pass test-amd64-amd64-xl-qemuu-winxpsp3 13 guest-stop fail never pass test-amd64-amd64-xl-winxpsp3 13 guest-stop fail never pass test-amd64-i386-xl-winxpsp3-vcpus1 13 guest-stop fail never pass test-amd64-i386-xl-win-vcpus1 13 guest-stop fail never pass test-amd64-amd64-xl-win7-amd64 13 guest-stop fail never pass test-amd64-i386-win 16 leak-check/check fail never pass test-i386-i386-win 16 leak-check/check fail never pass test-i386-i386-xl-win 13 guest-stop fail never pass test-amd64-amd64-xl-win 13 guest-stop fail never pass test-amd64-amd64-xl-qemuu-win7-amd64 13 guest-stop fail in 12967 never pass version targeted for testing: xen 69c3ae25bb1d baseline version: xen 69c3ae25bb1d jobs: build-amd64 pass build-i386 pass build-amd64-oldkern pass build-i386-oldkern pass build-amd64-pvops pass build-i386-pvops pass test-amd64-amd64-xl pass test-amd64-i386-xl pass test-i386-i386-xl pass test-amd64-i386-rhel6hvm-amd fail test-amd64-i386-qemuu-rhel6hvm-amd fail test-amd64-amd64-xl-qemuu-win7-amd64 fail test-amd64-amd64-xl-win7-amd64 fail test-amd64-i386-xl-win7-amd64 fail test-amd64-i386-xl-credit2 pass test-amd64-amd64-xl-pcipt-intel fail test-amd64-i386-rhel6hvm-intel fail test-amd64-i386-qemuu-rhel6hvm-intel fail test-amd64-i386-xl-multivcpu pass test-amd64-amd64-pair pass test-amd64-i386-pair pass test-i386-i386-pair pass test-amd64-amd64-xl-sedf-pin pass test-amd64-amd64-pv pass test-amd64-i386-pv pass test-i386-i386-pv pass test-amd64-amd64-xl-sedf fail test-amd64-i386-win-vcpus1 fail test-amd64-i386-xl-win-vcpus1 fail test-amd64-i386-xl-winxpsp3-vcpus1 fail test-amd64-amd64-win fail test-amd64-i386-win fail test-i386-i386-win fail test-amd64-amd64-xl-win fail test-i386-i386-xl-win fail test-amd64-amd64-xl-qemuu-winxpsp3 fail test-i386-i386-xl-qemuu-winxpsp3 fail test-amd64-i386-xend-winxpsp3 fail test-amd64-amd64-xl-winxpsp3 fail test-i386-i386-xl-winxpsp3 fail ------------------------------------------------------------ sg-report-flight on woking.cam.xci-test.com logs: /home/xc_osstest/logs images: /home/xc_osstest/images Logs, config files, etc. are available at http://www.chiark.greenend.org.uk/~xensrcts/logs Test harness code can be found at http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary Published tested tree is already up to date. </pre> xen.org 2012-05-24T06:13:23 http://permalink.gmane.org/gmane.comp.emulators.xen.devel/131450 <pre>Sorry for late reply, I am not on this mail these days because of my work. I further test qxl-vga and I think I figure out the problem in some extend. If using qxl device, the default memory size of vga is 64M. Which will cause xen_ram_alloc(qemu/xen-all.c) fails. The exact reason is xc_domain_populate_physmap_exact fails, because xen-hypervisor fail, it's because of alloc_domheap_pages(d, a-&gt;extent_order, a-&gt;memflags) fails in hypervisor. I am not very familiar with xen's memory management, Does 64M exceed xen's heap space in this context? xl dmesg: (XEN) page_alloc.c:1284:d0 Over-allocation for domain 22: 98561 &gt; 98560 (XEN) memory.c:131:d0 Could not allocate order=0 extent: id=22 memflags=0 (2328 of 16384) (XEN) HVM22: HVM Loader (XEN) HVM22: Detected Xen v4.2-unstable (XEN) HVM22: Xenbus rings &lt; at &gt;0xfeffc000, event channel 3 (XEN) HVM22: System requested SeaBIOS (XEN) HVM22: CPU speed is 2660 MHz Qemu log appended: char device redirected to /dev/pts/9 do_spice_init: starting 0.7.1 spice_server_add_interface: SPICE_INTERFACE_KEYBOARD spice_server_add_interface: SPICE_INTERFACE_MOUSE ram_size: 67108864 // 64M for qxl qemu: hardware error: xen: failed to populate ram at 17800000 // by xen_ram_alloc CPU #0: EAX=00000000 EBX=00000000 ECX=00000000 EDX=00000633 ESI=00000000 EDI=00000000 EBP=00000000 ESP=00000000 EIP=0000fff0 EFL=00000002 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES =0000 00000000 0000ffff 00009300 CS =f000 ffff0000 0000ffff 00009b00 SS =0000 00000000 0000ffff 00009300 DS =0000 00000000 0000ffff 00009300 FS =0000 00000000 0000ffff 00009300 GS =0000 00000000 0000ffff 00009300 LDT=0000 00000000 0000ffff 00008200 TR =0000 00000000 0000ffff 00008b00 GDT= 00000000 0000ffff IDT= 00000000 0000ffff CR0=60000010 CR2=00000000 CR3=00000000 CR4=00000000 DR0=00000000 DR1=00000000 DR2=00000000 DR3=00000000 DR6=ffff0ff0 DR7=00000400 EFER=0000000000000000 FCW=037f FSW=0000 [ST=0] FTW=00 MXCSR=00001f80 FPR0=0000000000000000 0000 FPR1=0000000000000000 0000 FPR2=0000000000000000 0000 FPR3=0000000000000000 0000 FPR4=0000000000000000 0000 FPR5=0000000000000000 0000 FPR6=0000000000000000 0000 FPR7=0000000000000000 0000 XMM00=00000000000000000000000000000000 XMM01=00000000000000000000000000000000 XMM02=00000000000000000000000000000000 XMM03=00000000000000000000000000000000 XMM04=00000000000000000000000000000000 XMM05=00000000000000000000000000000000 XMM06=00000000000000000000000000000000 XMM07=00000000000000000000000000000000 On Fri, May 4, 2012 at 4:30 PM, Ian Campbell &lt;Ian.Campbell&lt; at &gt;citrix.com&gt; wrote: </pre> ZhouPeng 2012-05-24T03:13:01 http://permalink.gmane.org/gmane.comp.emulators.xen.devel/131449 <pre>Hi Konrad and others, Oh, there are Xen/dom0 specific APIs for PCI and DMA? May I ask the names and where can I can more info on the APIs? Many thanks! Kenneth ________________________________________ From: Konrad Rzeszutek Wilk [konrad.wilk&lt; at &gt;oracle.com] Sent: Wednesday, May 23, 2012 5:17 PM To: Kenneth Wong Cc: xen-devel&lt; at &gt;lists.xen.org Subject: Re: [Xen-devel] Loading PCIe Device Driver at Dom0 On Wed, May 23, 2012 at 04:43:55PM -0700, Kenneth Wong wrote: The 2). You do need to use the PCI API (or the DMA API). </pre> Kenneth Wong 2012-05-24T02:41:34 http://permalink.gmane.org/gmane.comp.emulators.xen.devel/131448 <pre>Yes. We are using xen-pciback recently, and it works fine. If Xen will not to support 'pci-stub' in future, we can close that bug. </pre> Ren, Yongjie 2012-05-24T01:51:15 http://permalink.gmane.org/gmane.comp.emulators.xen.devel/131447 <pre> The 2). You do need to use the PCI API (or the DMA API). </pre> Konrad Rzeszutek Wilk 2012-05-24T00:17:12 http://permalink.gmane.org/gmane.comp.emulators.xen.devel/131446 <pre>Dear all, I have a PCIe device driver that I have been using on various Linux distributions and Kernel versions (2.6.x - 3.x.y) successfully all along. I recently set up a Xen environment with Linux Mint 12 and Xen Hypervisor 4.1. When I boot to Linux Mint, my driver still load (via insmod manually) successfully at Dom0 without any issue. I can do reads and write to the hardware device. But once booted to Xen, the driver failed to complete the driver load (via insmod manually) at Dom 0 and the console just hangs. From my debug messages, it appears it hangs because the driver doesn't receive any interrupt after a command is sent to the hardware device by writing a parameter to the mapped register. Once that register is written, the device is expected to DMA the command from the buffer allocated by the driver. The things that I can only think of that might have caused the problem are 1) IRQ mapping issue, or 2) DMA mapping issue, which I am not sure. What the driver does: Set up a command buffer: Buf_t *buf = kmalloc(BUF_SIZE*sizeof(buf_t), GFP_KERNEL); unsigned long buf_addr = __pa(buf); unsigned int buf_addr_low = (unsigned int)buf_addr; Tell device about the buffer: iowrite32(buf_addr_low, dev-&gt;pci_reg_map + BUF_ADR__LOW); Set up IRQ: if (pci_find_capability(dev, PCI_CAP_ID_MSI) &amp;&amp; (!pci_enable_msi(dev))) { if (request_irq(dev-&gt;irq, func_msi_interrupt, IRQF_SHARED, DRIVER_NAME, my_dev)) { return -ENODEV; } my_dev-&gt;intr_mode = INTERRUPT_MSI; } Ask device to fetch command from buffer (Expect interrupt after this after device fetched the command from buf. But interrupt did not happen.): iowrite32(buf_offset, dev-&gt;pci_reg_map + FETCH_CMD_REG); From dmesg, it looks like IRQ initialization is complete. [ 241.743769] My_driver initialization [ 241.743787] xen: registering gsi 16 triggering 0 polarity 1 [ 241.743793] xen_map_pirq_gsi: returning irq 16 for gsi 16 [ 241.743795] xen: --&gt; pirq=16 -&gt; irq=16 (gsi=16) [ 241.743801] Already setup the GSI :16 [ 241.743805] my-driver 0000:02:00.0: PCI INT A -&gt; GSI 16 (level, low) -&gt; IRQ 16 [ 241.743815] my-driver 0000:02:00.0: setting latency timer to 64 /proc/interrupts: CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7 ...... ...... 339: 0 0 0 0 0 0 0 0 xen-pirq-msi my-driver ...... ...... Any idea what might cause the problem? Is there anything we have to be enable/disable, use different functions, or do differently in drivers written for Xen Dom0 environment regarding the following? 1) Allocating a DMA buffer in driver to allow the device to DMA stuffs. 2) Requesting MSI irq. Please advise! Thanks a lot in advance!! Kenneth _______________________________________________ Xen-devel mailing list Xen-devel&lt; at &gt;lists.xen.org http://lists.xen.org/xen-devel </pre> Kenneth Wong 2012-05-23T23:43:55 http://permalink.gmane.org/gmane.comp.emulators.xen.devel/131445 <pre>flight 12967 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/12967/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-pcipt-intel 9 guest-start fail never pass test-amd64-i386-rhel6hvm-intel 11 leak-check/check fail never pass test-amd64-i386-qemuu-rhel6hvm-intel 11 leak-check/check fail never pass test-amd64-i386-qemuu-rhel6hvm-amd 11 leak-check/check fail never pass test-i386-i386-xl-qemuu-winxpsp3 13 guest-stop fail never pass test-amd64-i386-xend-winxpsp3 16 leak-check/check fail never pass test-amd64-amd64-win 16 leak-check/check fail never pass test-amd64-i386-win-vcpus1 16 leak-check/check fail never pass test-amd64-i386-rhel6hvm-amd 11 leak-check/check fail never pass test-amd64-i386-xl-win7-amd64 13 guest-stop fail never pass test-i386-i386-xl-winxpsp3 13 guest-stop fail never pass test-amd64-amd64-xl-qemuu-winxpsp3 13 guest-stop fail never pass test-amd64-amd64-xl-qemuu-win7-amd64 13 guest-stop fail never pass test-amd64-amd64-xl-winxpsp3 13 guest-stop fail never pass test-amd64-i386-xl-winxpsp3-vcpus1 13 guest-stop fail never pass test-amd64-i386-xl-win-vcpus1 13 guest-stop fail never pass test-amd64-amd64-xl-win7-amd64 13 guest-stop fail never pass test-amd64-i386-win 16 leak-check/check fail never pass test-i386-i386-win 16 leak-check/check fail never pass test-i386-i386-xl-win 13 guest-stop fail never pass test-amd64-amd64-xl-win 13 guest-stop fail never pass version targeted for testing: xen 69c3ae25bb1d baseline version: xen 340062faf298 jobs: build-amd64 pass build-i386 pass build-amd64-oldkern pass build-i386-oldkern pass build-amd64-pvops pass build-i386-pvops pass test-amd64-amd64-xl pass test-amd64-i386-xl pass test-i386-i386-xl pass test-amd64-i386-rhel6hvm-amd fail test-amd64-i386-qemuu-rhel6hvm-amd fail test-amd64-amd64-xl-qemuu-win7-amd64 fail test-amd64-amd64-xl-win7-amd64 fail test-amd64-i386-xl-win7-amd64 fail test-amd64-i386-xl-credit2 pass test-amd64-amd64-xl-pcipt-intel fail test-amd64-i386-rhel6hvm-intel fail test-amd64-i386-qemuu-rhel6hvm-intel fail test-amd64-i386-xl-multivcpu pass test-amd64-amd64-pair pass test-amd64-i386-pair pass test-i386-i386-pair pass test-amd64-amd64-xl-sedf-pin pass test-amd64-amd64-pv pass test-amd64-i386-pv pass test-i386-i386-pv pass test-amd64-amd64-xl-sedf pass test-amd64-i386-win-vcpus1 fail test-amd64-i386-xl-win-vcpus1 fail test-amd64-i386-xl-winxpsp3-vcpus1 fail test-amd64-amd64-win fail test-amd64-i386-win fail test-i386-i386-win fail test-amd64-amd64-xl-win fail test-i386-i386-xl-win fail test-amd64-amd64-xl-qemuu-winxpsp3 fail test-i386-i386-xl-qemuu-winxpsp3 fail test-amd64-i386-xend-winxpsp3 fail test-amd64-amd64-xl-winxpsp3 fail test-i386-i386-xl-winxpsp3 fail ------------------------------------------------------------ sg-report-flight on woking.cam.xci-test.com logs: /home/xc_osstest/logs images: /home/xc_osstest/images Logs, config files, etc. are available at http://www.chiark.greenend.org.uk/~xensrcts/logs Test harness code can be found at http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary Pushing revision : + branch=xen-unstable + revision=69c3ae25bb1d + . cri-lock-repos ++ . cri-common +++ umask 002 +++ getconfig Repos +++ perl -e ' use Osstest; readconfigonly(); print $c{Repos} or die $!; ' ++ repos=/export/home/osstest/repos ++ repos_lock=/export/home/osstest/repos/lock ++ '[' x '!=' x/export/home/osstest/repos/lock ']' ++ OSSTEST_REPOS_LOCK_LOCKED=/export/home/osstest/repos/lock ++ exec with-lock-ex -w /export/home/osstest/repos/lock ./ap-push xen-unstable 69c3ae25bb1d + branch=xen-unstable + revision=69c3ae25bb1d + . cri-lock-repos ++ . cri-common +++ umask 002 +++ getconfig Repos +++ perl -e ' use Osstest; readconfigonly(); print $c{Repos} or die $!; ' ++ repos=/export/home/osstest/repos ++ repos_lock=/export/home/osstest/repos/lock ++ '[' x/export/home/osstest/repos/lock '!=' x/export/home/osstest/repos/lock ']' + . cri-common ++ umask 002 + select_xenbranch + case "$branch" in + tree=xen + xenbranch=xen-unstable + '[' xxen = xlinux ']' + linuxbranch=linux + : master + : tested/2.6.39.x + . ap-common ++ : xen&lt; at &gt;xenbits.xensource.com ++ : http://xenbits.xen.org/staging/xen-unstable.hg ++ : git://xenbits.xen.org/staging/qemu-xen-unstable.git ++ : git://git.kernel.org ++ : git://git.kernel.org/pub/scm/linux/kernel/git ++ : git ++ : git://xenbits.xen.org/linux-pvops.git ++ : master ++ : xen&lt; at &gt;xenbits.xensource.com:git/linux-pvops.git ++ : git://xenbits.xen.org/linux-pvops.git ++ : master ++ : git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git ++ : tested/2.6.39.x ++ : daily-cron.xen-unstable ++ : http://hg.uk.xensource.com/carbon/trunk/linux-2.6.27 ++ : git://xenbits.xen.org/staging/qemu-upstream-unstable.git ++ : daily-cron.xen-unstable + TREE_LINUX=xen&lt; at &gt;xenbits.xensource.com:git/linux-pvops.git + TREE_QEMU_UPSTREAM=xen&lt; at &gt;xenbits.xensource.com:git/qemu-upstream-unstable.git + info_linux_tree xen-unstable + case $1 in + return 1 + case "$branch" in + cd /export/home/osstest/repos/xen-unstable.hg + hg push -r 69c3ae25bb1d ssh://xen&lt; at &gt;xenbits.xensource.com/HG/xen-unstable.hg pushing to ssh://xen&lt; at &gt;xenbits.xensource.com/HG/xen-unstable.hg searching for changes remote: adding changesets remote: adding manifests remote: adding file changes remote: added 2 changesets with 3 changes to 2 files </pre> xen.org 2012-05-23T22:05:18 http://permalink.gmane.org/gmane.comp.emulators.xen.devel/131444 <pre>On Wed, 2012-05-23 at 20:28 +0100, George Dunlap wrote: Yep, I really don't like that either. I agree... Some mechanism for providing the user at least with a warning would be useful. According to my personal taste, that would be quite ugly, not to mention that every time we might be adding/removing/modifying a scheduler, we would need to update this Frankenstein-struct, potentially affecting all the other ones... :-( I agree again: the fact that, right now, _almost_ all the existing schedulers have a parameter called weight with _almost_ the same meaning shouldn't allow us to assume that to be true now and forever. For what it counts, I'm all for option #2, i.e., each scheduler with its own struct, set of helper functions, xl sub-command, etc. Something like 'credit.cap = XX', 'credit2.weight = XX' or 'sedf.period = XXX' would be nice, for discriminating them in the config file. It'd remain to decide what to do with things like 'weight = XX', which we need to support for backward compatibility, but I guess almost anything is fine, provided we warn the user about what's happening and ask him to update the syntax. Just my 2 cents. :-) Regards, Dario </pre> Dario Faggioli 2012-05-23T21:19:35 http://permalink.gmane.org/gmane.comp.emulators.xen.devel/131443 <pre> Acked-by: George Dunlap &lt;george.dunlap&lt; at &gt;eu.citrix.com&gt; </pre> George Dunlap 2012-05-23T19:49:32 http://permalink.gmane.org/gmane.comp.emulators.xen.devel/131442 <pre> I'm not a fan of putting state-changes and conditionals in the same expression and relying on prefix/postifx precedence to sort things out. It seems like it's laying a trap for some poor tired programmer in the future to make a thinko. Would it really be that bad to just write "for(i--; i&gt;0; i--)"? :-) Actually -- walk me through this one. Won't this fail to call libxl_cpupoolinfo_dispose() on element 0? -G </pre> George Dunlap 2012-05-23T19:47:00 http://permalink.gmane.org/gmane.comp.emulators.xen.devel/131440 <pre>On Wed, May 23, 2012 at 8:28 PM, George Dunlap &lt;George.Dunlap&lt; at &gt;eu.citrix.com&gt; wrote: Er, in case this wasn't clear, I meant specifying the scheduler with the parameter in the config file. -George </pre> George Dunlap 2012-05-23T19:34:21 http://permalink.gmane.org/gmane.comp.emulators.xen.devel/131439 <pre> Overall the idea of the patch looks good. There's just the thing about shoving all the various schedulers' parameters into one struct. One fall-out from it is that if you specify weight in your config file (or during domain creation), it will set the weight for credit or credit2, but use the defaults for sedf. This might be nice; but we're implicitly baking in an assumption that parameters with the same name have to have roughly similar meanings across all schedulers. Furthermore, if someone sets a "cap" in the config file, for example, but starts the VM in a pool running credit2, should we really just silently ignore it, or should we alert the user in some way? In any case, this patch only takes things half-way. If we're really going to have One Struct to Rule Them All, we don't need different domain_set/domain_get functions for the different schedulers -- we just need a libxl_sched_domain_get(), which will both figure out what scheduler the domain is running, and fill in the appropriate parameters, and a libxl_sched_domain_set(), which will check to see that you've asked for the right scheduler (or marked "unknown" if you aren't afraid), and set what it can set. We could also have a unified "xl sched" command that would set various parameters without the user having to know what scheduler was currently running (perhaps throwing a warning if you're trying to set a parameter that doesn't exist for that scheduler). I'm not really sure which way I think is best. I can see the advantage of not having to know which scheduler is actually running, but I'm a bit wary of baking in assumptions about the equivalence of parameters; it seems like it could lead to some nasty surprises. But I think whichever way we choose, we should take it to its logical conclusion. Which in the "One Struct" way, would mean having a single domain_get/domain_set function, and in the "separate struct" way would probably mean specifying the scheduler -- i.e., "credit_weight", "credit2_weight" or something like that. (Obviously we need xm compatibility, but we can throw a warning to encourage people to change their config files.) -George </pre> George Dunlap 2012-05-23T19:28:31 http://permalink.gmane.org/gmane.comp.emulators.xen.devel/131438 <pre>Thanks for the clarification. PCI passthrough should be easier to setup. Regards, </pre> jocelyn.falempe< at >free.fr 2012-05-23T19:25:56 http://permalink.gmane.org/gmane.comp.emulators.xen.devel/131437 <pre> Awesome! Alpine Linux is great for lightweight systems. :) I am in the final stages of preparing a Ubuntu Linux based Dom0 LiveCD/USB. I should have it ready sometime this week hopefully, $dayjob has been getting in the way. Joseph. </pre> Joseph Glanville 2012-05-23T19:25:43 http://permalink.gmane.org/gmane.comp.emulators.xen.devel/131436 <pre> Yes. Xen can hotplug CPUs, memory and disk devices. The PV disk infrastructure also support dynamically resizing the volumes exposed to the guest. These sorts of questions are usually best leveled at the xen-users list as there are more people there that can give more indepth (and useful!) answers. :) Joseph. </pre> Joseph Glanville 2012-05-23T19:22:18 http://permalink.gmane.org/gmane.comp.emulators.xen.devel/131435 <pre> PCI passthrough will be enough. VGA passthrough is used when you want to pass through a primary display adapter and have VGA/VESA working in the guest. Jean _______________________________________________ Xen-devel mailing list Xen-devel&lt; at &gt;lists.xen.org http://lists.xen.org/xen-devel </pre> Jean Guyader 2012-05-23T18:29:13 http://permalink.gmane.org/gmane.comp.emulators.xen.devel/131434 <pre>Hi, I'm trying get the following configuration working with Xen VGA passthrough (no more dual-boot for gaming !): Core i7 3770 (with Vt-d) ASRock z77 Pro4-M Sapphire Radeon HD 7950 my goal is to have a Linux Dom0 using the intel HD 3000 gfx integrated in the CPU, connected to 1 display, and a Win7 DomU, using the Radeon 7950, connected to another display. I installed Ubuntu 12.04, and xen 4.1.2 from the packages. - Do I need VGA passthrough, or PCI passthrough might be enough in my case ? (Dom0 doesn't use the Radeon, and I saw some reports with 3D graphics with PCI passthrough). - Do I need to extract the VGA Bios ? I think it is only required for NVIDA cards, but I didn't find a clear statement. - Do I need to add vga passthrough patches ? which version to use for xen 4.1.2 ? my xen is able to boot a HVM 64bit win8 consumer preview (but there are no driver for 7950, so I will go back to win7). also I added this in grub : GRUB_CMDLINE_LINUX="quiet splash xen-pciback.permissive xen-pciback.hide=(01:00.0)(01:00.1) pci=resource_alignment=01:00.0;01:00.1" ~# xm pci-list-assignable-device 0000:01:00.0 0000:01:00.1 so normally I should be able to pass the graphic cards to the HVM. Any help greatly appreciated, Regards, </pre> jocelyn.falempe< at >free.fr 2012-05-23T18:18:53 http://permalink.gmane.org/gmane.comp.emulators.xen.devel/131432 <pre>flight 12965 linux-3.0 real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/12965/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking): test-amd64-amd64-pair 16 guest-start fail pass in 12954 test-amd64-amd64-xl-sedf 9 guest-start fail pass in 12954 test-amd64-amd64-win 12 guest-localmigrate/x10 fail in 12954 pass in 12965 Regressions which are regarded as allowable (not blocking): test-amd64-i386-qemuu-rhel6hvm-amd 9 guest-start.2 fail in 12954 like 12826 test-amd64-i386-qemuu-rhel6hvm-intel 9 guest-start.2 fail in 12954 like 12826 Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-pcipt-intel 8 debian-fixup fail never pass test-amd64-i386-xl-winxpsp3-vcpus1 13 guest-stop fail never pass test-amd64-i386-xend-winxpsp3 16 leak-check/check fail never pass test-amd64-amd64-xl-winxpsp3 13 guest-stop fail never pass test-amd64-amd64-xl-win7-amd64 13 guest-stop fail never pass test-i386-i386-xl-qemuu-winxpsp3 13 guest-stop fail never pass test-amd64-amd64-xl-qemuu-win7-amd64 12 guest-localmigrate/x10 fail never pass test-amd64-i386-win 16 leak-check/check fail never pass test-amd64-i386-xl-win-vcpus1 13 guest-stop fail never pass test-i386-i386-win 16 leak-check/check fail never pass test-amd64-i386-win-vcpus1 16 leak-check/check fail never pass test-amd64-i386-xl-win7-amd64 13 guest-stop fail never pass test-amd64-amd64-xl-qemuu-winxpsp3 12 guest-localmigrate/x10 fail never pass test-i386-i386-xl-win 13 guest-stop fail never pass test-i386-i386-xl-winxpsp3 13 guest-stop fail never pass test-amd64-amd64-win 16 leak-check/check fail never pass test-amd64-amd64-xl-win 13 guest-stop fail never pass version targeted for testing: linux 091ce3d38e5e57cf7dd44d66335725910e928f59 baseline version: linux bea37381fd9a34c6660e5195d31beea86aa3dda3 jobs: build-amd64 pass build-i386 pass build-amd64-pvops pass build-i386-pvops pass test-amd64-amd64-xl pass test-amd64-i386-xl pass test-i386-i386-xl pass test-amd64-i386-rhel6hvm-amd pass test-amd64-i386-qemuu-rhel6hvm-amd pass test-amd64-amd64-xl-qemuu-win7-amd64 fail test-amd64-amd64-xl-win7-amd64 fail test-amd64-i386-xl-win7-amd64 fail test-amd64-i386-xl-credit2 pass test-amd64-amd64-xl-pcipt-intel fail test-amd64-i386-rhel6hvm-intel pass test-amd64-i386-qemuu-rhel6hvm-intel pass test-amd64-i386-xl-multivcpu pass test-amd64-amd64-pair fail test-amd64-i386-pair pass test-i386-i386-pair pass test-amd64-amd64-xl-sedf-pin pass test-amd64-amd64-pv pass test-amd64-i386-pv pass test-i386-i386-pv pass test-amd64-amd64-xl-sedf fail test-amd64-i386-win-vcpus1 fail test-amd64-i386-xl-win-vcpus1 fail test-amd64-i386-xl-winxpsp3-vcpus1 fail test-amd64-amd64-win fail test-amd64-i386-win fail test-i386-i386-win fail test-amd64-amd64-xl-win fail test-i386-i386-xl-win fail test-amd64-amd64-xl-qemuu-winxpsp3 fail test-i386-i386-xl-qemuu-winxpsp3 fail test-amd64-i386-xend-winxpsp3 fail test-amd64-amd64-xl-winxpsp3 fail test-i386-i386-xl-winxpsp3 fail ------------------------------------------------------------ sg-report-flight on woking.cam.xci-test.com logs: /home/xc_osstest/logs images: /home/xc_osstest/images Logs, config files, etc. are available at http://www.chiark.greenend.org.uk/~xensrcts/logs Test harness code can be found at http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary Pushing revision : + branch=linux-3.0 + revision=091ce3d38e5e57cf7dd44d66335725910e928f59 + . cri-lock-repos ++ . cri-common +++ umask 002 +++ getconfig Repos +++ perl -e ' use Osstest; readconfigonly(); print $c{Repos} or die $!; ' ++ repos=/export/home/osstest/repos ++ repos_lock=/export/home/osstest/repos/lock ++ '[' x '!=' x/export/home/osstest/repos/lock ']' ++ OSSTEST_REPOS_LOCK_LOCKED=/export/home/osstest/repos/lock ++ exec with-lock-ex -w /export/home/osstest/repos/lock ./ap-push linux-3.0 091ce3d38e5e57cf7dd44d66335725910e928f59 + branch=linux-3.0 + revision=091ce3d38e5e57cf7dd44d66335725910e928f59 + . cri-lock-repos ++ . cri-common +++ umask 002 +++ getconfig Repos +++ perl -e ' use Osstest; readconfigonly(); print $c{Repos} or die $!; ' ++ repos=/export/home/osstest/repos ++ repos_lock=/export/home/osstest/repos/lock ++ '[' x/export/home/osstest/repos/lock '!=' x/export/home/osstest/repos/lock ']' + . cri-common ++ umask 002 + select_xenbranch + case "$branch" in + tree=linux + xenbranch=xen-unstable + '[' xlinux = xlinux ']' + linuxbranch=linux-3.0 + : master + : tested/2.6.39.x + . ap-common ++ : xen&lt; at &gt;xenbits.xensource.com ++ : http://xenbits.xen.org/staging/xen-unstable.hg ++ : git://xenbits.xen.org/staging/qemu-xen-unstable.git ++ : git://git.kernel.org ++ : git://git.kernel.org/pub/scm/linux/kernel/git ++ : git ++ : git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git ++ : master ++ : xen&lt; at &gt;xenbits.xensource.com:git/linux-pvops.git ++ : git://xenbits.xen.org/linux-pvops.git ++ : master ++ : git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git ++ : tested/2.6.39.x ++ : daily-cron.linux-3.0 ++ : http://hg.uk.xensource.com/carbon/trunk/linux-2.6.27 ++ : git://xenbits.xen.org/staging/qemu-upstream-unstable.git ++ : daily-cron.linux-3.0 + TREE_LINUX=xen&lt; at &gt;xenbits.xensource.com:git/linux-pvops.git + TREE_QEMU_UPSTREAM=xen&lt; at &gt;xenbits.xensource.com:git/qemu-upstream-unstable.git + info_linux_tree linux-3.0 + case $1 in + : git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git + : linux-3.0.y + : linux-3.0.y + : git + : git + : git://xenbits.xen.org/linux-pvops.git + : xen&lt; at &gt;xenbits.xensource.com:git/linux-pvops.git + : tested/linux-3.0 + : tested/linux-3.0 + return 0 + cd /export/home/osstest/repos/linux + git push xen&lt; at &gt;xenbits.xensource.com:git/linux-pvops.git 091ce3d38e5e57cf7dd44d66335725910e928f59:tested/linux-3.0 Counting objects: 1 Counting objects: 424, done. Compressing objects: 1% (1/55) Compressing objects: 3% (2/55) Compressing objects: 5% (3/55) Compressing objects: 7% (4/55) Compressing objects: 9% (5/55) Compressing objects: 10% (6/55) Compressing objects: 12% (7/55) Compressing objects: 14% (8/55) Compressing objects: 16% (9/55) Compressing objects: 18% (10/55) Compressing objects: 20% (11/55) Compressing objects: 21% (12/55) Compressing objects: 23% (13/55) Compressing objects: 25% (14/55) Compressing objects: 27% (15/55) Compressing objects: 29% (16/55) Compressing objects: 30% (17/55) Compressing objects: 32% (18/55) Compressing objects: 34% (19/55) Compressing objects: 36% (20/55) Compressing objects: 38% (21/55) Compressing objects: 40% (22/55) Compressing objects: 41% (23/55) Compressing objects: 43% (24/55) Compressing objects: 45% (25/55) Compressing objects: 47% (26/55) Compressing objects: 49% (27/55) Compressing objects: 50% (28/55) Compressing objects: 52% (29/55) Compressing objects: 54% (30/55) Compressing objects: 56% (31/55) Compressing objects: 58% (32/55) Compressing objects: 60% (33/55) Compressing objects: 61% (34/55) Compressing objects: 63% (35/55) Compressing objects: 65% (36/55) Compressing objects: 67% (37/55) Compressing objects: 69% (38/55) Compressing objects: 70% (39/55) Compressing objects: 72% (40/55) Compressing objects: 74% (41/55) Compressing objects: 76% (42/55) Compressing objects: 78% (43/55) Compressing objects: 80% (44/55) Compressing objects: 81% (45/55) Compressing objects: 83% (46/55) Compressing objects: 85% (47/55) Compressing objects: 87% (48/55) Compressing objects: 89% (49/55) Compressing objects: 90% (50/55) Compressing objects: 92% (51/55) Compressing objects: 94% (52/55) Compressing objects: 96% (53/55) Compressing objects: 98% (54/55) Compressing objects: 100% (55/55) Compressing objects: 100% (55/55), done. Writing objects: 0% (1/309) Writing objects: 1% (4/309) Writing objects: 2% (7/309) Writing objects: 3% (10/309) Writing objects: 4% (13/309) Writing objects: 5% (16/309) Writing objects: 6% (19/309) Writing objects: 7% (22/309) Writing objects: 8% (25/309) Writing objects: 9% (28/309) Writing objects: 10% (31/309) Writing objects: 11% (34/309) Writing objects: 12% (38/309) Writing objects: 13% (41/309) Writing objects: 14% (44/309) Writing objects: 15% (47/309) Writing objects: 16% (50/309) Writing objects: 17% (53/309) Writing objects: 18% (56/309) Writing objects: 19% (59/309) Writing objects: 20% (62/309) Writing objects: 21% (65/309) Writing objects: 22% (68/309) Writing objects: 23% (72/309) Writing objects: 24% (75/309) Writing objects: 25% (78/309) Writing objects: 26% (81/309) Writing objects: 27% (84/309) Writing objects: 28% (87/309) Writing objects: 29% (90/309) Writing objects: 30% (93/309) Writing objects: 31% (96/309) Writing objects: 32% (99/309) Writing objects: 33% (102/309) Writing objects: 34% (106/309) Writing objects: 35% (109/309) Writing objects: 36% (112/309) Writing objects: 37% (115/309) Writing objects: 38% (118/309) Writing objects: 39% (121/309) Writing objects: 40% (124/309) Writing objects: 41% (127/309) Writing objects: 42% (130/309) Writing objects: 43% (133/309) Writing objects: 44% (136/309) Writing objects: 45% (140/309) Writing objects: 46% (143/309) Writing objects: 47% (146/309) Writing objects: 48% (149/309) Writing objects: 49% (152/309) Writing objects: 50% (155/309) Writing objects: 51% (158/309) Writing objects: 52% (161/309) Writing objects: 53% (164/309) Writing objects: 54% (167/309) Writing objects: 55% (170/309) Writing objects: 56% (174/309) Writing objects: 57% (177/309) Writing objects: 58% (180/309) Writing objects: 59% (183/309) Writing objects: 60% (186/309) Writing objects: 61% (189/309) Writing objects: 62% (192/309) Writing objects: 63% (195/309) Writing objects: 64% (198/309) Writing objects: 65% (201/309) Writing objects: 66% (204/309) Writing objects: 67% (208/309) Writing objects: 68% (211/309) Writing objects: 69% (214/309) Writing objects: 70% (217/309) Writing objects: 71% (220/309) Writing objects: 72% (223/309) Writing objects: 73% (226/309) Writing objects: 74% (229/309) Writing objects: 75% (232/309) Writing objects: 76% (235/309) Writing objects: 77% (238/309) Writing objects: 78% (242/309) Writing objects: 79% (245/309) Writing objects: 80% (248/309) Writing objects: 81% (251/309) Writing objects: 82% (254/309) Writing objects: 83% (257/309) Writing objects: 84% (260/309) Writing objects: 85% (263/309) Writing objects: 86% (266/309) Writing objects: 87% (269/309) Writing objects: 88% (272/309) Writing objects: 89% (276/309) Writing objects: 90% (279/309) Writing objects: 91% (282/309) Writing objects: 92% (285/309) Writing objects: 93% (288/309) Writing objects: 94% (291/309) Writing objects: 95% (294/309) Writing objects: 96% (297/309) Writing objects: 97% (300/309) Writing objects: 98% (303/309) Writing objects: 99% (306/309) Writing objects: 100% (309/309) Writing objects: 100% (309/309), 81.85 KiB, done. Total 309 (delta 253), reused 309 (delta 253) To xen&lt; at &gt;xenbits.xensource.com:git/linux-pvops.git bea3738..091ce3d 091ce3d38e5e57cf7dd44d66335725910e928f59 -&gt; tested/linux-3.0 + exit 0 </pre> xen.org 2012-05-23T17:55:31 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.emulators.xen.devel