similar to: Preventing hotplug devices in HVM guests

tools/firmware: remove "_PS0/3" Method Do not expose the ACPI power management "_PS0/3" Method to guest firmware. According to section 3.4 of the APCI specification 4.0, PCI device control the device power through its own specification but not through APCI. Qemu pushes "_PS0/3" to guest will cause a mess between ACPI PM and PCI PM as a result of incorrect ACPI table

Shirish Pargaonkar wrote: > A call to wbcGetpwnam() with BUILTIN\Administrators > name (string) returns error 7 (WBC_ERR_DOMAIN_NOT_FOUND). > > I tried just Administrators and got the same error. > Same error with user (string) Everyone also. > ---- I've noticed this problem as well... In fact, every one of the well-known addresses that I manually added (and are

Hi, I sent the following e-mail to kexec-mailing list (kexec@lists.infradead.org) since subjects of makedumpfile are discussed on the mailing list. I want to inform this to xen developers since I think this function is useful for xen developers. Thanks. Itsuro Oda (see https://sourceforge.net/projects/makedumpfile/ about makedumpfile command.) Forwarded by Itsuro ODA

Hi, Please post any comments or questions if you get around to testing them. Your comments are very welcome! Best regards, -Gonglei > > >>> On 22.10.13 at 06:08, "Gonglei (Arei)" <arei.gonglei@huawei.com> > wrote: > > > Hi, guys. The new patch has been modified based on the principles you > > > suggested, thank you so much. > > >

The datasheet is available at http://download.intel.com/design/network/datashts/82599_datasheet.pdf See 'Table 9.7. VF PCIe Configuration Space' of the datasheet, the PCI Express Capability Structure of the VF of Intel 82599 10GbE Controller looks trivial, e.g., the PCI Express Capabilities Register is 0, so the Capability Version is 0 and pt_pcie_size_init() would fail. We should not

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

Hi all, if a device doesn''t support power management (pm_cap == 0) but it is acpi_pci_power_manageable() because there is a _PS0 method declared for it and _EJ0 is also declared for the slot then nobody is going to set current_state = PCI_D0 for this device. This is what I think it is happening: pci_enable_device | __pci_enable_device_flags /* here we do not set current_state

Just wanted to note that this morning that I had to (for a complete, including examples, build): 1) Move llvm/cmake/modules/LLVMLibDeps.cmake.old out of way for svn update to work 2) Modfiy llvm/examples/Makefile to remove TracingBrainF in order for a subsequent make to work Don't know if the current repository changes will fix this, or if I'm doing something else wrong. A new checkout

Well first off i doubt I even uninstalled my last one properly. To catch you guys up for what has been happening, I found this other site that talked about Wine and it seemed exactly what I have been looking for, so downloaded it using the link they had. An ejectable icon come up on my finder and from that I could easily drag and drop Wine and Wine Bottler to the App folder. YAY it worked,

Commit-ID: 0dd950265ef9c8eced83ec69e1988fd08706f667 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=0dd950265ef9c8eced83ec69e1988fd08706f667 Author: Bill Wendling <morbo at google.com> AuthorDate: Sun, 29 Mar 2020 04:38:33 -0700 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 25 Jul 2020 20:45:34 +0100 [klibc] Clean up clang warnings Add

On reboot, one out of 10 times, reboot (from hardware initialization) stops. Referring to this portion of the dmesg -v output, of a successful boot, where i have marked ">>>HERE<<<" is where the boot freezes on an unsuccessful boot. This is a constnat problem, on 6.2 as well as 6.3 unchanged. ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA33 cable=40 wire acd0: setting

- Convert the "old style" GNU field designator extension to the new style. - Use proper indexing into a string literal. - Use "%s" for the format string in "fmtstr". - Add or remove casts of the "void *" argument of ioctl. - Convert "if (!exitstatus == isor)" to "if ((!exitstatus) == isor)" which retains the current semantics, but may

Yes, really. I've got hundreds of the damn things here at home, and I want to go through them and get rid of them all. But... to do that I want to read them. I have both a 5.25" and a 3.5" drive, both are plugged in, but in the BIOS, all I see is the 3.5". Fine, I figure I'll take care of those. Nope. I see /dev/fd0 once I've booted up, but neither konqueror nor

This is a series of patches for clang compatibility: - Using flags needed flags and removing unsupported flags. - Adding support for clang's LLD linker. - Removing a variety of warnings. Bill Wendling (3): [klibc] Kbuild: use "libc.a" with clang [klibc] Kbuild: Add "-fcommon" for clang builds [klibc] Clean up clang warnings Michael Davidson (1): [klibc] Kbuild:

I'm running: localhost(6.1-P)[21] uname -a FreeBSD localhost 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #19: Wed Mar 15 07:15:25 PST 2006 root@g1-18.catwhisker.org.:/common/S2/obj/usr/src/sys/LAPTOP_30W i386 localhost(6.1-P)[22] I figured I'd grab a copy of the recent 6.1-BETA4 (disc1) ISO to try it out & hand it out to folks.... It seems to have worked, but I got a bit of a whine

Hello, I have the following hardware configuration. Tyan 2466N motherboard, 1.03 BIOS, 2 Athlon-MP 1800+ CPUs, 512MB registered ECC DRAM, Onboard 3Com NIC (xl type) Radeon 8500 AGP video card Adaptec 3210S SCSI RAID controller Comtrol RocketPort 8 port PCI serial card I have started to experience some odd system lockups in the past couple months, and it seems to be getting worse. I particular,

- Renamed IMAGE_BASE to LD_IMAGE_BASE_OPT. - Moved "-fcommon" to KLIBCREQFLAGS in scripts/Kbuild.klibc. - Remove "dash" warning fixes which have been upstreamed. - Conditionalize the inclusion of compiler flags by using the proper compiler name or "cc-option". - Added "-Werror" to "cc-option" to catch flags that cause warnings. - Retain

Thomas, Have spoken to Soren, from my bootlog he believes that the problem is in atapicam causing the system to lock up. He is happy to answer some questions but doesnt have time to delve into atapicam himself. Did you author atapicam, I have seen your name on the sourcecode, can you help me further? Whats next? Thanks Adam. -------------- next part -------------- An embedded message was

Aloha! Concisely, I''ve been trying for several days to get VGA/PCI passthrough working. Regarding VGA vs PCI passthrough, I''m not entirely certain of the difference? Does Xen perform a different set of operations when passing through a VGA card versus any PCIe card? I''ve read the wiki and it seems the answer is "yes;" however, when passing through a

Hi, I have a problem booting the Xen hypervisor on my brand new Lenovo Thinkpad T400 2765D2G (Core2 Duo P8600 CPU, 2.40GHz. 4GB RAM). I''m running Debian 5.0 (Lenny) and I use the Debian-provided xen-hypervisor-3.2-1-amd64 package. The Dom0 kernel seems to be the Xen patches ported to a 2.6.26 kernel: linux-image-2.6.26-1-xen-amd64 I can boot the hypervisor only very unrealiably: Out of