From mboxrd@z Thu Jan 1 00:00:00 1970 From: mail ignored <0.bugs.only.0@gmail.com> Subject: Re: Re: follow up to a pciback "pv pci-passthrough co-assigned problem" Date: Sat, 23 Jan 2010 09:36:53 -0800 Message-ID: References: <20100123123042.GG2861@reaktio.net> <20100123164850.GT2861@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20100123164850.GT2861@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: xen-devel@lists.xensource.com, weidong.han@intel.com List-Id: xen-devel@lists.xenproject.org On Sat, Jan 23, 2010 at 8:48 AM, Pasi K=E4rkk=E4inen wrote: > How does Xen 4.0 (xen-unstable) fail for you? well, wasn't going to make this an issue -- as I'm not yet committed to Xen 4 (*suse's flavor, anyway) until it's a bit more widely-used & stable, but -- since you asked, zypper dup -r XEN4 cp /etc/xend-config.sxp.XEN4 /etc/xend-config.sxp reboot uname -rp 2.6.31.8-0.1-xen x86_64 rpm -qa | grep -i xen-4 xen-4.0.0_20809_01-28.2.x86_64 xm dmesg ... (XEN) Xen version 4.0.0_20809_01-28.2 (abuild@) (gcc version 4.4.1 [gcc-4_4-branch revision 150839] (SUSE Linux) ) Wed Jan 20 01:09:45 UTC 2010 (XEN) Latest ChangeSet: 20809 (XEN) Command line: loglvl=3Dall loglvl_guest=3Dall apic_verbosity=3Ddebu= g dom0_mem=3D1024M vga=3Dgfx-1280x1024x32 console=3Dvga,com1 com1=3D57600,8n1 iommu=3D1 dom0_max_vcpus=3D4 dom0_vcpus_pin=3Dtrue sched=3Dcredit cpuidle cpufreq=3Dxen clocksource=3Dacpi numa=3Don ... @ any/all vm launch, i'd get some message xm create -c /home/xen/vm/test.cfg Using config file "/home/xen/vm/test.cfg". Error: Domain 'test' does not exist. xend log -> http://pastebin.com/d6c5d3100. if something 'in there' is informative, hth! drop back to xen3x, all's OK again. >> > With Xen 3.3, or 3.4, you can apply a "disable FLR" patch, which also = makes it work: > Are you sure you installed the new patched xen tools after applying the p= atch? > And restarted xend? i backed up my production xen/util tree, and applied the patch directly there. after reboot, @ xm create -c test.cfg i get Error: pci: 0000:04:07.0 must be co-assigned to the same guest with 0000:04:06.0