similar to: ioremap error during bootup

Thank you! How could the admin do to grant me with permission to run virsh as unprivileged user? Also by configurating libvirtd.conf, unix_sock_group? 2014-10-28 Allen Qiu 发件人：libvirt-users-request@redhat.com 发送时间：2014-10-28 00:00 主题：libvirt-users Digest, Vol 58, Issue 33 收件人："libvirt-users"<libvirt-users@redhat.com> 抄送： Send libvirt-users mailing list submissions to

Hi all, Do you have any recommendation about benchmarking tools on Linux virtual machine for measure the potential performance hit by virtualization, especially on multi-threads computation, since I doubt if the CentOS VM can fully make use of the 32 vCPUs (out of 64 physical cores) that I allocated to it. Regards, Allen 2014-11-05 Allen Qiu

Hi all, What is the difference between starting virt-manager by "virt-manager" and by "sudo virt-manager"? It seems that there are two copy of virt-manager running in the background. When I run "virt-manager", I got a error of "Unable to open a connection to the libvirt management daemon. Libvirt URI is: qemu:///system Verify that: - The 'libvirtd'

On Wednesday, November 5, 2014 5:53 AM, Allen Qiu <my1stbox@163.com> wrote: > Do you have any recommendation about benchmarking tools on Linux > virtual machine for measure the potential performance hit by > virtualization, especially on multi-threads computation You could try the phoronix-test-suite which is available in the [EPEL][1] repository. Cheers, Cristian Ciupitu [1]:

is_local_lowmem() treats its physical address input as a machine address; this causes agpgart to fail while calling ioremap_nocache(). X still does not load on my Athlon 64 / Via S3 Unichrome, so perhaps best not to apply just yet. Signed-off-by: Avi Kivity <avi@qumranet.com> --- xen-ioremap-fix/linux-2.6-xen-sparse/arch/i386/mm/ioremap-xen.c~ioremap 2006-06-22 20:30:20.000000000 +0300

Hello , I have installed RHEL 5 on a Intel Core Duo processor based board. It has 1 GB of physical memory. I have a driver which uses the memory reserved at the top of the high memory. Well this driver worked fine on all the previous versions of RHEL/FC and also with RHEL 5 with virtualization disabled. But with virtualization enabled , the ioremap to the memory reserved at the top of high

Hi Christoph, Thanks for your comments. I'm also replying here to your comments on the previous series. On Tuesday, March 17, 2020 10:28:35 AM EDT Christoph Hellwig wrote: > Any reason drivers can't just use pci_map_rom instead? which already > does the right thing? Some machines don't expose the video BIOS in the PCI BAR and instead only make it available via EFI boot

On Fri, Mar 13, 2020 at 06:22:58PM -0400, Mikel Rychliski wrote: > /** > + * pci_platform_rom - ioremap() the ROM image provided by the platform > * @pdev: pointer to pci device struct > * @size: pointer to receive size of pci window over ROM > + * > + * Return: kernel virtual pointer to image of ROM > + * > + * The caller is responsible for removing the mapping with

https://bugs.freedesktop.org/show_bug.cgi?id=102275 Bug ID: 102275 Summary: Laptop bootup and suspend and wake issues Product: Mesa Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau

CentOS 4.1, Xen 2.0.7. My dom0 is booting up but can''t get to the outside network because eth0 won''t start due to, apparently, Xen providing a different mac address than expected. How do I tell Xen to start eth0 at the bootup with a specific mac address that lines up with the HWADDR= line in my ifcfg-eth0? Note that a normal bootup into CentOS 4.1 outside of the Grub Xen bootup

Some chips that use system memory exclusively (e.g. GK20A) do not expose 2 BAR regions. For them only BAR1 exists, and it should be used for USERD mapping. Do not map BAR3 if its resource does not exist. Signed-off-by: Alexandre Courbot <acourbot at nvidia.com> --- drivers/gpu/drm/nouveau/core/subdev/bar/base.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git

Some chips that use system memory exclusively (e.g. GK20A) do not expose 2 BAR regions. For them only BAR1 exists, and it should be used for USERD mapping. Do not map BAR3 if its resource does not exist. Signed-off-by: Alexandre Courbot <acourbot at nvidia.com> --- drivers/gpu/drm/nouveau/core/subdev/bar/base.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git

Some chips that use system memory exclusively (e.g. GK20A) do not expose 2 BAR regions. For them only BAR1 exists, and it should be used for USERD mapping. Do not map BAR3 if its resource does not exist. Signed-off-by: Alexandre Courbot <acourbot at nvidia.com> Reviewed-by: Thierry Reding <treding at nvidia.com> --- drivers/gpu/drm/nouveau/core/subdev/bar/base.c | 6 ++++-- 1 file

Hi, ALL When I use "tap" config, the VM is OK. Than I replace disk config "tap" with "tap2", And VM hangs during bootup. I use "xm list" to list vm and find the time of hanged VM is growing fast. After VM hangs, we can not create other VMs. It prints "Error: Device 0 (vif) could not be connected. Hotplug scripts not working" . How can I fix it?

On some EFI systems, the video BIOS is provided by the EFI firmware. The boot stub code stores the physical address of the ROM image in pdev->rom. Currently we attempt to access this pointer using phys_to_virt(), which doesn't work with CONFIG_HIGHMEM. On these systems, attempting to load the radeon module on a x86_32 kernel can result in the following: BUG: unable to handle page

Hi all, Do you have any idea about this error? virsh # dumpxml csg01win7test > domain.xml error: unexpected data '>' Regards, Allen 2014-10-28 Allen Qiu

From: Mikel Rychliski <mikel at mikelr.com> [ Upstream commit 72e0ef0e5f067fd991f702f0b2635d911d0cf208 ] On some EFI systems, the video BIOS is provided by the EFI firmware. The boot stub code stores the physical address of the ROM image in pdev->rom. Currently we attempt to access this pointer using phys_to_virt(), which doesn't work with CONFIG_HIGHMEM. On these systems,

From: Mikel Rychliski <mikel at mikelr.com> [ Upstream commit 72e0ef0e5f067fd991f702f0b2635d911d0cf208 ] On some EFI systems, the video BIOS is provided by the EFI firmware. The boot stub code stores the physical address of the ROM image in pdev->rom. Currently we attempt to access this pointer using phys_to_virt(), which doesn't work with CONFIG_HIGHMEM. On these systems,

From: Mikel Rychliski <mikel at mikelr.com> [ Upstream commit 72e0ef0e5f067fd991f702f0b2635d911d0cf208 ] On some EFI systems, the video BIOS is provided by the EFI firmware. The boot stub code stores the physical address of the ROM image in pdev->rom. Currently we attempt to access this pointer using phys_to_virt(), which doesn't work with CONFIG_HIGHMEM. On these systems,

From: Mikel Rychliski <mikel at mikelr.com> [ Upstream commit 72e0ef0e5f067fd991f702f0b2635d911d0cf208 ] On some EFI systems, the video BIOS is provided by the EFI firmware. The boot stub code stores the physical address of the ROM image in pdev->rom. Currently we attempt to access this pointer using phys_to_virt(), which doesn't work with CONFIG_HIGHMEM. On these systems,