WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

RE: [Xen-users] problem with pciback

To: "Peter Gavin" <pgavin@xxxxxxxxx>, <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] problem with pciback
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Tue, 14 Nov 2006 09:56:40 +0800
Delivery-date: Mon, 13 Nov 2006 17:57:15 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AccHZQ2kkTWTgd53TDmXcesBYbad8gAKpo1g
Thread-topic: [Xen-users] problem with pciback
Hi, Peter,
        Pciback is the mechanism to assign physical device to para-domain 
(modified), instead of for unmodified hvm domain. For the latter, you have to 
wait for ready of IOMMU.

Thanks,
Kevin

>From: Peter Gavin
>Sent: 2006年11月14日 4:48
>Hello,
>
>I'm attempting to run Windows XP in a domU using the PCs actual
>graphics card.  I believe I've set everything up correctly, including
>the pciback module etc.
>
>I've set pciback to grab the graphics card and all the USB hosts as well:
>
>(from dmesg)
>pciback 0000:00:02.0: seizing device
>pciback 0000:00:02.1: seizing device
>pciback 0000:00:1a.0: seizing device
>pciback 0000:00:1a.1: seizing device
>pciback 0000:00:1a.7: seizing device
>pciback 0000:00:1b.0: seizing device
>pciback 0000:00:1d.0: seizing device
>pciback 0000:00:1d.1: seizing device
>pciback 0000:00:1d.2: seizing device
>pciback 0000:00:1d.7: seizing device
>
>00:02.{0,1} correspond to the graphics card, the rest are USB devices.
>
>This is my winxp.hvm:
>
>kernel = "/usr/lib/xen/boot/hvmloader"
>builder='hvm'
>memory = 512
>shadow_memory = 8
>name = "winxp"
>pae=1
>vif = [ 'type=ioemu, mac=aa:00:b0:00:00:11' ]
>disk = [ 'phy:/dev/xen-domU/winxp,ioemu:hda,w',
>'file:/winxp.iso,hdc:cdrom,r' ]
>pci=[ '00:02.0', '00:02.1', '00:1a.0', '00:1a.7', '00:1b.0',
>'00:1d.0', '00:1d.1', '00:1d.2', '00:1d.7' ]
>restart = 'always'
>device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
>boot="d"
>sdl=0
>vnc=0
>stdvga=0
>nographics=1
>serial='pty'
>
>I set sdl=vnc=stdvga=0 to keep the emulated gfx device from being
>created.
>
>It looks (so far) like the windows xp domU is grabbing the devices as
>it should, but its not working the way I want :)   What I'd like to
>happen is for the monitor attached to the onboard graphics to show the
>windows installer, and to be able to use the usb mouse and keyboard
>that are attached.
>
>BTW, the machine only has the one graphics card, I'm controlling the
>dom0 with a serial terminal.  When I run xm create winxp.hvm, this is
>what I get:
>
>Using config file "/etc/xen/winxp.hvm".
>(XEN) (file=hvm.c, line=195) Allocated port 3 for hvm.
>Started domain winxp
>(XEN) vmx_do_launch(): GUEST_CR3<=00fd57a0,
>HOST_CR3<=20273000
>
>then it hangs right there. xm list gives me:
>
>winxp                                      6      512     1
>------      0.0
>
>showing that the vm is sorta running, its been created at the least.
>
>Does anyone have any ideas?
>
>Thanks,
>Pete
>
>_______________________________________________
>Xen-users mailing list
>Xen-users@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>