http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1757
Summary: Dom0 hangs after few hours when using pci passthrough
Product: Xen
Version: unstable
Platform: Other
OS/Version: Linux
Status: NEW
Severity: major
Priority: P2
Component: Unspecified
AssignedTo: xen-bugs@lists.xensource.com
ReportedBy: darkbasic4@gmail.com
Hi, I'm Xen 4.0.1-2 from Debian Squeeze with 2.6.32-xen in both dom0 and domU.
I don't use VT-d for pci passthrough because of bug #1644
(http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1644).
My grub.cfg:
multiboot /boot/xen-4.0-amd64.gz placeholder iommu=no
module /boot/vmlinuz-2.6.32-5-xen-amd64 placeholder
root=UUID=578ad522-e302-4ae4-b9e4-1e5628e262ba ro quiet
xen-pciback.hide=(0000:03:04.0)(0000:06:00.0)(0000:0a:06.1) console=tty0
console=ttyS0,115200n8
My domU config:
memory = 256
#routed network
vif = ['ip=public_ip, vifname=ethAST']
vcpus = 2
disk = [ 'file:/srv/xen/asterisk.img,xvda,w' ]
pci = [ '0000:03:04.0', '0000:06:00.0', '0000:0a:06.1' ]
bootloader="/usr/lib/xen-4.0/bin/pygrub"
I noticed "xm pci-list-assignable" lists only 0000:03:04.0, but I can
successfully passthrough all the three cards (two telephony cards and a network
adapter).
I can see the cards in the domU with lspci but I also can see them in the dom0,
which is quite strange.
After some time the dom0 hangs and I have to hard reboot. I have no problems if
I don't use the pci passthrough.
Maybe I can reproduce it (without having to wait for hours) starting and
stopping the virtual machine with the pci passthrough lots of time, I will try
to attach a serial console and paste the output.
--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
Summary: Dom0 hangs after few hours when using pci passthrough
Product: Xen
Version: unstable
Platform: Other
OS/Version: Linux
Status: NEW
Severity: major
Priority: P2
Component: Unspecified
AssignedTo: xen-bugs@lists.xensource.com
ReportedBy: darkbasic4@gmail.com
Hi, I'm Xen 4.0.1-2 from Debian Squeeze with 2.6.32-xen in both dom0 and domU.
I don't use VT-d for pci passthrough because of bug #1644
(http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1644).
My grub.cfg:
multiboot /boot/xen-4.0-amd64.gz placeholder iommu=no
module /boot/vmlinuz-2.6.32-5-xen-amd64 placeholder
root=UUID=578ad522-e302-4ae4-b9e4-1e5628e262ba ro quiet
xen-pciback.hide=(0000:03:04.0)(0000:06:00.0)(0000:0a:06.1) console=tty0
console=ttyS0,115200n8
My domU config:
memory = 256
#routed network
vif = ['ip=public_ip, vifname=ethAST']
vcpus = 2
disk = [ 'file:/srv/xen/asterisk.img,xvda,w' ]
pci = [ '0000:03:04.0', '0000:06:00.0', '0000:0a:06.1' ]
bootloader="/usr/lib/xen-4.0/bin/pygrub"
I noticed "xm pci-list-assignable" lists only 0000:03:04.0, but I can
successfully passthrough all the three cards (two telephony cards and a network
adapter).
I can see the cards in the domU with lspci but I also can see them in the dom0,
which is quite strange.
After some time the dom0 hangs and I have to hard reboot. I have no problems if
I don't use the pci passthrough.
Maybe I can reproduce it (without having to wait for hours) starting and
stopping the virtual machine with the pci passthrough lots of time, I will try
to attach a serial console and paste the output.
--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs