similar to: Increasegraphical screen size of vm

I have a CentOS 4.3 workstation I use for experimentation on my desk at work. It was plugged into an old LG 14" monitor, and I switched the video cable to a Samsung 17" LCD without rebooting. The screen resolution was set to 800x600 on the 14" monitor, and the display worked fine at 800x600 after switching to the Samsung 17". When I changed the resolution to 1024x764, the

I originally set up this monitor with an analogue lead. Everything seemed fine, so I didn't check xorg.conf at all. Then I bought a digital lead, and since then the monitor blinks. Running system-config-display identifies it as a 1280 x 1084 CRT monitor. It is an LCD monitor. That model is not on the drop-down list, so assuming that a specific driver wasn't available for it, I

Hi all, Up until today everything has been fine with CentOS on my Toshiba laptop. I booted into CentOS 4.3 today and Kudzu detected my video card for some reason. I let it configure it (wish I hadn't now). I can still get in. X and Gnome work. But the video resolution is 800x640. The LCD is capable of 1024x768. I cannot change it using Gnome tools or direct editing of

My OQO has a VIA chipset. From the hwconf: class: VIDEO bus: PCI detached: 0 desc: "VIA Technologies, Inc. CX700M2 UniChrome PRO II Graphics" vendorId: 1106 deviceId: 3157 subVendorId: 1106 subDeviceId: 3157 pciType: 1 pcidom: 0 pcibus: 1 pcidev: 0 pcifn: 0 When I install Centos, I default to the vesa driver, and it operates at the monitor's native 800x480. Of course I

I''ve been looking at anti-virus software for Xen use on Linux systems, on both Dom0 and DomU, in industrial environments. Reviewing documentation on various packages seems to show that all the commercial ones insist on sticking kernel modules into a limited set of standard known kernels. This of course creates some serious risks until the anti-virus packages are developed in and

Ryan wrote: > I did, 1024x768. > Sorry, analog Matthew Miller wrote: > Maybe the problem is just in that adjustment, then. Yes. You need to have your signaling _exact_ when dealing with LCDs. Some are very good at taking the timings of VESA standards. But some support some eccentric Windows timings that are _not_ the exact same as VESA. Or maybe you have configured your monitor for

I''m not seeing the problem that Fan Zhao is reporting, instead I get this one. Not sure if ti''s the same one or a different problem... This happens with my simple-guest [i.e. not using hvmloader, as I described before]. This worked fine yesterday. (XEN) event_channel.c:178:d0 EVTCHNOP failure: domain 0, error -22, line 178 (XEN) bad shared page: 0 (XEN) domain_crash_sync called

Hi developers, I met some domU issues and the log suggests missing interrupt. Details from here: http://www.gossamer-threads.com/lists/xen/users/263938#263938 In summary, this is the suspicious log: (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3 I''ve checked the code in question and found that mode 3 is an ''reserved_1'' mode. I want to trace down the source of this

I just put a 1680x1050 LCD monitor on my home system, and I went into system-config-display to configure it as such, and it just won't take. I had to tweak some of the settings by hand, but when I log out, I get the wide screen for both the Nvidia driver splash screen and the login screen. But, when I log in, It jumps back to 1280x1024 and refuses to run in wide screen mode. Here's the

I have had my "nv" driver lock up a number of times. I downloaded the "nvidia" drivers and they did not work at 1920x1080 resolution. I am looking for an updated driver for just "nv". I found some once for a different driver that you just update commonXXX and yourdriverXXX not the whole X recompile. Where can I find those drivers? THanks, Jerry --------------

Hi: we have following setup: 1. 2.6.16-33-based Xen 3.0.3/Xen-3.0.4 DOM-0 kernels. 2. Using LILO-mbootpack from USB we boot Xen-->DOM-0 setup 3. We mount harddisk and try to install xp.hvm While,we are successful with FCs as DOM-U, for XP we get, VBD (768) could not be connected. We do have max_loop count to 64 and enough loop devices. Note that above error is consistent on both 3.0.3

> Hmmm... wouldn''t it be nice if we didn''t have a bespoke, > buggy & incomplete emulator for hvm mmio. ;-) In the process of solving this one, I''ve got to (another) of the blocking points... At the moment, we translate the virtual address from the guest in the page-fault-handler to guest physical address via the gva_to_gpa() function in svm.c/vmx.c:

I can boot a 64-bit HVM image on my SVM-system, and it goes quite a long way before it crashes (due to not finding the hard-disk image and thus no root FS - which I think may well be the configuration file). But if I set debug=y in the Rules.mk, I don''t get very far at all - it crashes well before it gets to any user-mode (Ring3) - in fact, I think it''s crashing pretty much as

In the vein of the "Can't get resolution higher than 1280x1024" and "Another CentOS 5 oddity..." threads, I just installed CentOS5 w/Xen kernel on a Sony VAIO desktop with an nVidia NV5M64 (RIVA TNT2 64 Pro) card, using an old Samsung SyncMaster 700NF monitor. system-config-display chose the highest possible resolution for the monitor and Xorg did its best to drive it, but

Hi all, I manage to create a VM (slackware image) and hide the PCI device (qlogic HBA) from Dom0 to DomainU. Now the Dom0 cant see this HBA and the ''xm list -l'' shows this pci device under the DomainU. But how can I do some scsi inquiry or check if this PCI device is visible to the DomainU from the DomainU''s console. Any help? Thanks and regards Ashit

What are methods to debug domU when it hangs? Using xen 3.1 compiled from sources I could not manage to launch no domU. Fot instance, I run something like this: =====8<===================== disk = [ ''file:/oradata-act/sles.disk,hda1,w'', '',hdc:cdrom,r'' ] kernel = "/boot/vmlinuz-2.6.18-xen" ramdisk = "/boot/initrd-2.6.18-xen" cpus =

Hello, it''s not the first time but ... Who know? Well, I use xen in HVM. All works fine, my keyboard in Dom0 is AZERTY, but this keyboard become QWERTY when i enter in VM, it''s not useful to type password. How can i keep my keyboard AZERTY in my VM and in Dom0? -- Benjamin HENRION Elève de 4eme année de l'' EXIA (Nancy) Ecole supérieure d''informatique Spé

Good morning, I installed on xen a windows XP and a Windows 2003 domU. Windows operating system does not know the real network card but it setup up an AMD pcnet card 10mbps. Is it possible to setup a full virtualized domU with a real network card ? I installed also windows on a trial xen enterprise and real network card seeems to work fine. What differences between xen and xen entrprise as far

I sometimes see this with a clean build and most often it is 'Attributes.inc' that is missing. I usually have to 'touch Attributes.td' for this. But I don't know CMake well enough to know how to fix these issue properly. MartinO -----Original Message----- From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Jonathan Roelofs via llvm-dev Sent: 16 November

+cbieneman Mr. CMake might know how to fix it ;) Jon On 11/16/16 1:52 PM, mats petersson wrote: > Thanks, at least I know I'm not imagining or doing something really > daft! ;) > > My cmake skills are near 0%, so not sure I can fix, but perhaps I can > at least raise a bug? ;) > > -- > Mats > > On 16 November 2016 at 20:28, Martin J. O'Riordan >