Re: Re: follow up to a pciback "pv pci-passthrough co-assigned problem"

[mail ignored <0.bugs.only.0@gmail.com>]

On Sat, Jan 23, 2010 at 8:48 AM, Pasi Kärkkäinen <pasik@iki.fi> 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=all loglvl_guest=all apic_verbosity=debug
dom0_mem=1024M vga=gfx-1280x1024x32 console=vga,com1 com1=57600,8n1
iommu=1 dom0_max_vcpus=4 dom0_vcpus_pin=true sched=credit cpuidle
cpufreq=xen clocksource=acpi numa=on
  ...

@ 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 patch?
> 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