similar to: Nova-s2 pci-passthrough not properly working

I'm trying to find out why I am unable to access public shares on host mythbe (from host mythbe) due to a NT_STATUS_BAD_NETWORK_NAME error. I am able to access home shares. I've checked all of the host setup issues I know about (smb.conf, directory permissions, iptables, selinux) but I don't see any problems. Can anyone spot a problem or suggest where I could investigate? Below is

For some reason I can't ping or communicate with two of my machines that have static IP's on my lan. My mythbe and mythfe are both set to have static ip's in the event of some sort of power problem the wife can stillwatch tv. After installing CentOS5, I can't communicate with those two machines. I read through the release notes and the docs on dhcp, but I can't seem to see

Hello, Does anyone could tell me how can I use pciback under Ubuntu ? I''ve got a telephony card for Asterisk and I find this document : http://www.crc.id.au/fedora-core-6-xen-and-asterisk/ What happens seems that pciback module is unavailable under Ubuntu or compiled into the kernel ? Any tips are welcome Regards _______________________________________________ Xen-users mailing

Hi! i notice a serious regression with 3.5 as Dom0 kernel (3.4 was rock stable): 1st: only the GPU PCI Passthrough works, the PCI USB Controller is not recognized within the DomU (HVM Win7 64) Dom0 cmdline is: ro root=LABEL=dom0root xen-pciback.hide=(08:00.0)(08:00.1)(00:1d.0)(00:1d.1)(00:1d.2)(00:1d.7) security=apparmor noirqdebug nouveau.msi=1 Only 8:00.0 and 8:00.1 get passed through

I have one xen machine where dom0 libata and pcibacked domU eth0 share a physical IRQ. I thought that the disk was bad (cause the system was crashing and giveing me disk errors) and replaced it with an IDE disk connected to a pcibacked SATA-IDE combo card. Problem seems to have gone away. The machine runs stably and hasn''t crashed yet. Now I have another machine where I pciback usb.

Hi All, This might be a stupid question, but I have two PCI devices that I want to pass-thru to a PV domU. I can pass one of them, but not both. I''m sure it''s a stupid syntax issue within my configuration file. When I do a "lspci" in the domU, (CentOS 5.1), only one of the devices shows up. (e.g.) 00:00.0 Multimedia video controller: Internext Compression Inc

The manual says rsync can be used as an improved cp command. If S1 and S2 are (local) source files or directories and T is an (local) existing directory, is it safe to think that $ rsync -r S1 S2 T does the same thing as $ cp -r S1 S2 T , assuming no trailing slashes in S1, S2? -- View this message in context:

Add a way to disable the timer IRQ routing check via a boot option. The VMI timer code uses this to avoid triggering the pester Mingo code, which probes for some very unusual and broken motherboard routings. It fires 100% of the time when using a paravirtual delay mechanism instead of using a realtime delay, since there is no elapsed real time, and the 4 timer IRQs have not yet been delivered.

Add a way to disable the timer IRQ routing check via a boot option. The VMI timer code uses this to avoid triggering the pester Mingo code, which probes for some very unusual and broken motherboard routings. It fires 100% of the time when using a paravirtual delay mechanism instead of using a realtime delay, since there is no elapsed real time, and the 4 timer IRQs have not yet been delivered.

Hi, I have recently upgraded from CentOS 5.1 too 5.2 and now run Xen 3.0.3. What would be the best way to upgrade too Xen 3.2.1 ? I presume I would also need to change my network settings for xenbr0 aswell ? Any help would be greatfully appreciated. Regards, -- --[ UxBoD ]-- // PGP Key: "curl -s http://www.splatnix.net/uxbod.asc | gpg --import" // Fingerprint: F57A 0CBD DD19 79E9

Despite what Keir said on your timing requirements, I guess you get the famous co-assignment message. See at the end of this: http://www.nabble.com/xen-3.3.0-pv-pci-passthrough-co-assigned-problem-td20008460.html BR, Carsten. ----- Originalnachricht ----- Von: mdlabriola@yahoo.com Gesendet: Mit, 15.4.2009 13:56 An: xen-devel <xen-devel@lists.xensource.com> Betreff: [Xen-devel] 3rd party

Hi, anybody has experience with ${subject} server (intel E7520 based)? I red some incompatible problems with new intel mb chipsets and digium cards, but I don't remember which chipsets on black list. A -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part

There seems to be several problems in this kickstart cd document. I guess this was copied from RedHat''s documentation. Can someone please direct me or my comments to the right person? http://www.centos.org/docs/5/html/Installation_Guide-en-US/ch02s04.html#s2-steps-make-cd this command (in the documentation) needs a space in it: cp -r

I am submitting the patch which supports more Capability Structures and Device Specific Registers for passthrough device. In Xen 3.3 unstable, qemu-dm supports Configuration Header, MSI Capability Structure, and MSI-X Capability Structure. But qemu-dm does not support PCI Express Capability Structure, Device Specific Registers, etc (writing them is ignored). To support various I/O devices, I

On 32e, we create one guest, then hotplug attach one NIC to guest, guest can not get IP address via dhcp, guest qemu log shows "libpci read error. No emulation ". Here is the bug entry: One 32e, hotplug attaching VT-d NIC to guest failed. http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1316. -- haicheng _______________________________________________ Xen-devel mailing list

I assigned FC-HBA to guest domain, but it did not work. FC-HBA seems to write its internal memory which is mapped to host memory space via pci transaction. But there is no mapping in IOMMU''s page table, so that page fault occurs in IOMMU. I think that MMIO resource mapped via p2m table should be mapped via IOMMU''s page table too. In other word, XEN_DOMCTL_memory_mapping

Hi, >From my reading about nova interface to libvirt, I came to know it uses a libvirt driver module to communicate with host libvirt. I was wondering if there are any compatibility matrix available between the nova libvirt driver and the libvirt installed in the host ? Thanks Arvind -------------- next part -------------- An HTML attachment was scrubbed... URL:

On 07/01/2013 01:27 PM, Maciej Ga?kiewicz wrote: > Hello > > I have a question about live migration when libvirt requires sasl > authentication. I have managed to configure remote access for user nova > with sasl enabled (credentials stored in auth.conf - > https://review.openstack.org/#/c/12706/). It looks like live migration do > not use these credentials at all. What is

On 07/02/2013 10:13 AM, Maciej Gałkiewicz wrote: > On 2 July 2013 09:58, Martin Kletzander <mkletzan@redhat.com> wrote: > >> I'd say this is a problem with sasl, nothing else. "No mechanism found" >> may mean that libraries for configured mechanism aren't found or unknown >> mechanism is being requested. I doubt that access to those libraries

On 2 July 2013 10:36, Martin Kletzander <mkletzan@redhat.com> wrote: > I couldn't know you were able to do that. Since I presume you are using > the same server and client to check that, I must fallback to default > questions like "SELinux?". Or some OpenStack config which I > (unfortunately) know almost nothing about. Last thing that occurs on my > mind is