search for: busing

Hi all, I wrote a pass (attached). But I get a runtime error: buse at buse-VB:~/Desktop/llvm-2.7/lib/Transforms/CG_CFG$ opt-2.7 -load ../../../Release/lib/_CG_CFGGen.so -CG_CFGGen < ../../../buse/simpleCode.bc > /dev/null 0xa7bae0: 0 libLLVM-2.7.so.1 0x00007f4a8b6add1f 1 libLLVM-2.7.so.1 0x00007f4a8b6ae36d 2 libpthread.so.0 0x00007f4a8aa98b40 3 _CG_CFGGen.so 0x00007f4a8995891f 4

The target VM will have several buses to which disks can be attached. Commonly it will have an IDE bus, and possibly a virtio-blk "bus" (not really a bus) and/or a SCSI bus. Virt-v2v does not model this at the moment. Disks are just added to the output XML in the order that we write them, and so they can move around with respect to the target VM. This commit introduces the idea that

Hi, I saw that Xen support a translation between device/intx to GSI for a single PCI bus, I thought about adding multiple PCI bus support but disregard the bus information so the same device/intx on different buses will be OR wired to the same GSI, sounds reasonable? What other things do I need to support in Xen in order to add multiple PCI buses, assuming that secondary buses holds only

On 12/20/18 9:20 AM, Daniel P. Berrangé wrote: > On Thu, Dec 20, 2018 at 03:15:34PM +0100, Riccardo Ravaioli wrote: >> Hi, >> >> My goal is to assign PCI addresses to a number of devices (network >> interfaces, disks and PCI devices in PCI-passthrough) without delegating to >> libvirt the generation of those values. This should give me more control >> and for

I am trying to create a QEMU MIPS guest, so that I can test some code for big-endian safety. Every attempt to create a MIPS guest is giving me an error: Unable to complete install: 'XML error: No PCI buses available' It seems like this is a known issue. https://www.redhat.com/archives/libvir-list/2016-May/msg00197.html However, I am still getting this on a fully updated Fedora

Hi, My goal is to assign PCI addresses to a number of devices (network interfaces, disks and PCI devices in PCI-passthrough) without delegating to libvirt the generation of those values. This should give me more control and for sure more predictability over the hardware configuration of a virtual machine and consequently the name of the interfaces in it. I'm using libvirt 4.3.0 to create

On 2014-10-22 10:44, Michael S. Tsirkin wrote: > On Wed, Oct 08, 2014 at 11:04:28AM +0200, Cornelia Huck wrote: >> On Tue, 07 Oct 2014 18:24:22 -0700 >> Andy Lutomirski <luto at amacapital.net> wrote: >> >>> On 10/07/2014 07:39 AM, Cornelia Huck wrote: >>>> This patchset aims to get us some way to implement virtio-1 compliant >>>> and

On 2014-10-22 10:44, Michael S. Tsirkin wrote: > On Wed, Oct 08, 2014 at 11:04:28AM +0200, Cornelia Huck wrote: >> On Tue, 07 Oct 2014 18:24:22 -0700 >> Andy Lutomirski <luto at amacapital.net> wrote: >> >>> On 10/07/2014 07:39 AM, Cornelia Huck wrote: >>>> This patchset aims to get us some way to implement virtio-1 compliant >>>> and

On Mon, Mar 13, 2017 at 04:23:38PM -0500, Ian Pilcher wrote: > I am trying to create a QEMU MIPS guest, so that I can test some code > for big-endian safety. You are probably better off using PPC64 which is big-endian and much more widely tested in libvirt than MIPS, so actually likely to work reliably. > Every attempt to create a MIPS guest is giving me an error: > > Unable to

On Tue, 2017-03-14 at 09:18 -0500, Ian Pilcher wrote: > > You are probably better off using PPC64 which is big-endian and much more > > widely tested in libvirt than MIPS, so actually likely to work reliably. >  > I did try that, but I wasn't able to get past errors about the > machine type not supporting IDE (or something like that).  I finally > just gave up and use

On 03/14/2017 05:59 AM, Daniel P. Berrange wrote: > You are probably better off using PPC64 which is big-endian and much more > widely tested in libvirt than MIPS, so actually likely to work reliably. I did try that, but I wasn't able to get past errors about the machine type not supporting IDE (or something like that). I finally just gave up and use qemu-system-ppc directly, along

Move most of open_guestfs to Types, so a common function to open a Guestfs handle is available. Since it does not do all the things the old open_guestfs did, the two operations have been moved to the only place requiring them. This function has been placed in Types and not Utils, as will be needed by other functions in Types; Utils uses Types, so this avoids a circular dependency. ---

In include/sys/pci.h we have #define MAX_PCI_BUSES 255 and struct pci_bus_list { struct pci_bus pci_bus[MAX_PCI_BUSES]; uint8_t count; }; And in lib/pci/scan.c for (bus = 0; bus <= MAX_PCI_BUSES; bus++) { pci_bus_list->pci_bus[bus].pci_device_count = 0; Fix possible overflows and introduce MAX_PCI_FUNC. - Sebastian Index: syslinux-20080611/com32/lib/pci/scan.c

Remove "(void)cfgtype;" from com32/lib/pci/scan.c. - Sebastian Index: syslinux-3.74-pre11-2-g4fc8259/com32/lib/pci/scan.c =================================================================== --- syslinux-3.74-pre11-2-g4fc8259.orig/com32/lib/pci/scan.c +++ syslinux-3.74-pre11-2-g4fc8259/com32/lib/pci/scan.c @@ -441,7 +441,6 @@ struct pci_domain *pci_scan(void) int cfgtype;

On 2014-10-22 22:34, Benjamin Herrenschmidt wrote: > On Wed, 2014-10-22 at 16:17 +0200, Jan Kiszka wrote: >> I thought about this again, and I'm not sure anymore if we can use >> ACPI >> to "black-list" the incompatible virtio devices. Reason: hotplug. To >> my >> understanding, the ACPI DRHD tables won't change during runtime when a >>

On 2014-10-22 22:34, Benjamin Herrenschmidt wrote: > On Wed, 2014-10-22 at 16:17 +0200, Jan Kiszka wrote: >> I thought about this again, and I'm not sure anymore if we can use >> ACPI >> to "black-list" the incompatible virtio devices. Reason: hotplug. To >> my >> understanding, the ACPI DRHD tables won't change during runtime when a >>

This is... odd. Got a 6.8 box, a Dell R320 lspci tells me 01:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS 2008 [Falcon] (rev 03) so it *should* accept an SAS drive. I've got a Cheetah that's a few years old, and having pulled it out of another server (in the datecenter), I put it in this box to zero it out for reuse... and the box refuses to see the drive. *Nothing* in

I'm having some trouble here - need some help! I've just bought a TE405p (32-bit 5V), but cannot get it working in a dell 6450. The dell has (from tech specs) "three peer PCI buses: two 64-bit buses and one 32-bit bus Expansion slots seven hot-pluggable PCI slots (two 64-bit/66 MHz, four 64-bit/33 MHz, and one 32-bit/33 MHz)" I cannot get the card working in any of the slots.

_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel

This patch series adds stable bus and slot numbers for removable drives (CDs and floppies) when the guest is converted using virt-v2v or virt-p2v. Previously we were a bit random about this. After this patch series, the bus and slot numbers and preserved if at all possible. BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1238053 Rich.