similar to: track_dirty_vram(f0000000, 160) failed (-1, 22)

Occasionally I see the message '' track_dirty_vram(f0000000, 26) failed (-1, 3)'' in the qemu-dm logs as the DomU reboots. Is it a concern at all? Thanks James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

I have just attempted to boot a windows 7 vm in safe mode with networking on Xen 3.4.2 and found that it reboots a few seconds after the logon screen appears, perhaps somebody else on the list could test this and confirm that they see the same issue? The last few lines of the qemu-dm log show the following: gpe_en_write: addr=0x1f6c, val=0x8. gpe_en_write: addr=0x1f6d, val=0x0. gpe_en_write:

I am currently running three different machines with Xen and have running DomU''s on server 1 and server 2. I trying to run a new instance of Windows 2000 on Server 2 (I''ll include the specs below), but every time the install gets to "registering components" portion, the installation restarts. I try the install on my workstation and it does the same thing.

There is a race condition between XEN_DOMCTL_SHADOW_OP_ENABLE_LOGDIRTY and HVMOP_track_dirty_vram hypercall. Although HVMOP_track_dirty_vram is called many times from qemu-dm which is connected via VNC, XEN_DOMCTL_SHADOW_OP_ENABLE_LOGDIRTY is called only once from a migration process (e.g. xc_save, libxl-save-helper). So the race seldom happens, but the following cases are possible.

Hello all, Been using Xen a while, previously with Netbsd and few weeks ago changed dom0 to Gentoo linux. Change wen''t very nice, but now I''m facing strange out of resources problem in Windows XP HVM guests. At first there was no issues but when we added second windows guest users started to complain that they cannot access network drivers and cannot unzip large zips ( the

Hi, I tried to attach passrough io device to domU, the command (ended successfully in dom0), but when I entered the domU and typed the "lspci" command I didn''t see the new device, although the dom0 removed it from the "pci-list-assignable-devices". When I tried to detach it from the domU, the detach command returned with timeout error. What did I miss? perhaps I

Hi Jasmin, On Sun, Mar 1, 2020 at 11:32 AM Jasmin <jasmin.pm at protonmail.com> wrote: > > Hi, > > for quite some time now I would like to switch from the proprietary driver to nouveau, using a GK107 (Quadro) in a thinkpad. > Unfortunately the monitors connected to the lenovo "ultra dock" are not properly recognized when using nouveau. DP-MST support was first

On Friday 17 November 2017 15:43:33 Ilia Mirkin wrote: > With a new kernel, mind grabbing a dmesg with drm.debug=0x1e > nouveau.debug=debug (or maybe even =trace)? Maybe also see if > fbcon/fbdev have any debug things that can be turned on? Here's diff of the 32MB and 64MB debug logs: --- nouveau-debug-32mb.txt- 2017-11-17 18:12:06.290108330 +0100 +++ nouveau-debug-64mb.txt-

Hi, for quite some time now I would like to switch from the proprietary driver to nouveau, using a GK107 (Quadro) in a thinkpad. Unfortunately the monitors connected to the lenovo "ultra dock" are not properly recognized when using nouveau. The laptop contains a multiplexer: so in the bios it can be selected, whether the docking station's DP/HDMI/VGA-Ports are "directly"

Hi there, I am gettings tons of messages in dmesg output such as: [...] [ 2419.238990] [drm:drm_mode_addfb2 [drm]] [FB:65] [ 2419.243388] 00a0 2 base507c_ntfy_set [ 2419.243391] 00000060 [ 2419.243391] f0000000 [ 2419.243393] 0084 1 base827c_image_set [ 2419.243394] 00000010 [ 2419.243395] 00c0 1 base827c_image_set [ 2419.243395] fb00007a [ 2419.243396] 0110 2 base827c_image_set [ 2419.243397]

Hi Ben, I was looking into some of the LUT-related modesetting issues. I've noticed the following... after I load nouveau, one of my secondary GPUs shows this on first modeset (with drm.debug=4): [ 2368.081307] [drm:drm_helper_probe_single_connector_modes [drm_kms_helper]] [CONNECTOR:44:DVI-I-1] [ 2368.113148] [drm:drm_add_display_info [drm]] non_desktop set to 0 [ 2368.113183]

Dear All, I'm trying to install a Debian Wheezy KVM guest on a CentOS 6.4 Host. The only resolutions supported are 1024x768 or 800x600. I increased the video RAM to 500 MB, but the guest still says: [ 10.321] (II) CIRRUS(0): Not using default mode "1920x1200" (insufficient memory for mode) Only 32 MB are recognized: 00:02.0 VGA compatible controller: Cirrus Logic GD 5446

Hi, I was wondering is it possible to can get my GeForce GTX 980M work with Nouveau. I see that the non "M" version if GTX 980 is supported ( https://nouveau.freedesktop.org/wiki/CodeNames/) but not the "M" version, how different are they? Now it uses Gallium 0.4 on llvmpipe, from my understanding that's fallback using the cpu right? *lshw -C video:* *-display

I have and new motherboard and trying to get X going. it starts at 800x600 and vesa driver... I have tried via (I get not driver found) I have tried S3 I have tried savage None of these work. I tried them all as I was getting conflicting information on the net about which driver it is. below is lspci -v Any suggestions on what to try? THanks, jerry 01:00.0 VGA compatible controller: VIA

And what about IO MMU ? On 10/13/2014 12:02 PM, Weis, Michael (DWIE) wrote: > Hi Pierre, > > thanks for your reply. > > I am using kernel 3.10.0-123.8.1.el7.x86_64. > The kernel modul used after nodedev-detach is vfio-pci > > This is the output of lspci -vv after I did a virsh nodedev-detatch pci_0000_02_00_0 > > 02:00.0 Ethernet controller: PLX Technology, Inc.

Hi, I''m using the xen-3.4-unstable version with Debian Lenny. Next to that I use a HVM Guest. The error message from the Xend.log is: 2009-02-26 14:44:15 2325] INFO (XendDomain:1180) Domain ExampleHVMDomain (35) unpaused. [2009-02-26 14:44:15 2325] INFO (XendDomainInfo:1781) Domain has shutdown: name=ExampleHVMDomain id=35 reason=poweroff. [2009-02-26 14:44:15 2325] DEBUG

Hi Andreas, On Mon, May 18, 2020 at 9:56 AM Andreas Schwab <schwab at linux-m68k.org> wrote: > > On Mai 18 2020, Michael Ellerman wrote: > > > The old drivers may be crufty but they presumably have been tested by > > people and at least somewhat work. > > I can confirm that the nvidia fbdev driver is working perfectly fine. > > > I gave it a quick spin on

Hi, I am working on pass through using Xen-3.4 unstable. I am having trouble in installing HVM domain. Configuration file lokks like below: # Kernel image file. kernel = "/usr/lib/xen/boot/hvmloader" # The domain build function. HVM domain uses ''hvm''. builder=''hvm'' # Initial memory allocation (in megabytes) for the new domain. memory

https://bugs.freedesktop.org/show_bug.cgi?id=36090 aebenjam at opentext.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aebenjam at opentext.com --- Comment #1 from aebenjam at opentext.com 2012-01-30 08:34:15 PST --- Also experienced with: 01:00.0

https://bugs.freedesktop.org/show_bug.cgi?id=70389 --- Comment #1 from Kevin Murphy <kemurphy.cmu at gmail.com> --- Also experiencing this on a Thinkpad T530 running Arch with kernel 3.11.6. 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device 21f5 Control: I/O+ Mem+