search for: tschwing

Hello! I'm having problems getting PCI pass-through to work. This is on a AMD64 system, paravirtualized with xen-hypervisor-4.0-amd64 4.0.0-1~experimental.1, dom0: linux-image-2.6.32-5-xen-amd64 2.6.32-12. From IRC, earlier today: <tschwinge> waldi: Aren't the Debian xen domU-capable kernels supposed to contain the PCI frontend (needed for PCI pass-through)? I'm getting: PCI: System does not support PCI <tschwinge> waldi: ... both when using linux-image-2.6.32-3-686-bigmem and linux-image-2.6.32-5-xen-686 for t...

Hello! I'm having problems getting PCI pass-through to work. This is on a AMD64 system, paravirtualized with xen-hypervisor-4.0-amd64 4.0.0-1~experimental.1, dom0: linux-image-2.6.32-5-xen-amd64 2.6.32-12. From IRC, earlier today: <tschwinge> waldi: Aren't the Debian xen domU-capable kernels supposed to contain the PCI frontend (needed for PCI pass-through)? I'm getting: PCI: System does not support PCI <tschwinge> waldi: ... both when using linux-image-2.6.32-3-686-bigmem and linux-image-2.6.32-5-xen-686 for t...

...Automatically generated email from bts, devscripts version 2.9.26 > close 388152 Bug#388152: xen-hypervisor-3.0.2-1-i386: should run `update-grub' 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Thomas Schwinge <tschwinge at gnu.org> > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)

http://bugs.freedesktop.org/show_bug.cgi?id=26980 Summary: GT230M/nouveau: X server hangs spontaneously Product: xorg Version: 7.5 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

Hello! I updated a Xen domU using linux-image-2.6.24-1-xen-686, adapted the Xen configuration (add ``extra = "console=hvc0"'' and use xvdX devices -- where is all this documented, by the way?) and it boots and I can log in via SSH, but I don't get a login session anymore on the domU's Xen console. Is this a known issue? Regards, Thomas -------------- next part

Package: xen-hypervisor-3.0.2-1-i386 Version: 3.0.2-3+hg9762-1 Followup-For: Bug #385934 Hello! For me, the new upload of xen-hypervisor-3.0.2-1-i386, version 3.0.2-3+hg9762-1, does _not_ fix this issue. I'm still seeing the same problem as it was originally reported in this very bug report. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (900,

Package: xen-hypervisor-3.0.2-1-i386 Version: 3.0.2-3+hg9762-1 Severity: wishlist Hello! Shouldn't `update-grub' be run automatically after installing a `xen-hypervisor-*' package? -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (900, 'testing'), (800, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to

Hello! One month ago I created a patch and submitted it to the Debian `bridge-utils' package's tracker: <http://bugs.debian.org/405215>. I thought it may be helpful for others to know about it and wanted to inform you this way, as the `bridge-utils' maintainers didn't make any attempts so far to comment on it or even include it. I use it this way: dom0's

Hello! I recently upgraded a number of Debian testing packages (three days ago) and just now rebooted the system, with the effect that the Xen domUs don't know their `eth0' devices anymore: #v+ # ifconfig eth0 eth0: error fetching interface information: Device not found #v- I'm using xen-hypervisor-3.0.3-1-i386-pae 3.0.3-0-2 and upgraded linux-image-2.6.18-4-xen-686 from

Package: udev Severity: important X-Debbugs-CC: pkg-xen-devel@lists.alioth.debian.org Hello! When installing the udev package in a Xen domU, ``strange'' things happen. The following is a bit of guesswork, some hard facts are probably missing, but I hope that the udev and / or Xen maintainers can make some sense out of it. I'm for now happy with having a usable Xen server again...

Hello! This might be a FAQ, but I didn't manage to find an answer somewhere: why doesn't the linux-image-2.6.16-2-xen-686 (at least that one; that's the one I installed) create a accompanying initrd.img, but the user has to do it himself? (Like me, having troubles with the version of initramfs-tools from testing, resolved by upgrading that one to unstable's version.) Also, why