similar to: centos5 xen domu with X: screens not found [SOLVED]

Hi, I am in a process to virtualize an existing non-virtualized CentOS5 system. Everything else works fine except X: virt-manager's console just hangs after bootup. I can use the text console though and what I see in X server's log is the error message "screens not found". The only graphics related setup I've done is in the domu config this line: vfb = [

flight 5665 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/5665/ Regressions :-( Tests which did not succeed and are blocking: build-amd64-oldkern 4 xen-build fail REGR. vs. 5640 build-amd64 4 xen-build fail REGR. vs. 5640 build-i386-oldkern 4 xen-build fail REGR. vs. 5640

Hi all, the patch "qemu-vnc-wmvi.patch" adds support for the WMVi pseudoencoding in qemu vnc server. If the client implements it, it is supposed to be able to change colour depth when receiving a WMVi message. Since I didn''t know any client that supports it and I wanted to test the implementation before submitting any patch I also modified vncviewer to support WMVi. The

Dear all, In case of someone else is trying to do the same configuration as mine, I stated below the steps to configure HVM and PV''s domains to use FIXED VNC Ports (instead of having Xen automatically assign one unused port based on domain id): For HVM''s: vnc=1 # Enable VNC vncconsole=0 # Don''t start vncviewer after "create" the

Hi, I am not so familiar with Xen. So I need help. I have put Xen (3.2) and XenoLinux (2.6.18.8) into Fedora8. After that I have created a Debian-Etch DomU image using Xen-tools. I used the role scripts to put xdm functionality into it. With only this I tried to boot the domU image, but got some segmentation fault error while booting the domU. So following the direction in

Hello, I''m running 6.26-2-xen-amd64 with xen-hypervisor-3.2-1-amd64. Now I try to pass through a controller card to WHS, at the moment without success because the card isn''t present in DomU. At the first moment I guess it''s a windows problem ;) so I''d tried to boot a Knoppix .iso but same problem there, the passed through device isn''t present in DomU.

After a yum update my two guests that had been shutdown do not start any more. I have two other guests running that seem to work okay but I am now afraid that they won't come up again if I restart them. I am running CentOS5 with kernel 2.6.18-8.1.8.el5xen. Previously I had following xen versions installed: Oct 14 23:45:10 Updated: xen-libs.i386 3.0.3-25.0.4.el5 Oct 14 23:46:05 Updated:

root@boris-P5Q-E:/mnt/usr/tmp# losetup -f ubuntu11.04.iso root@boris-P5Q-E:/mnt/usr/tmp# losetup -a /dev/loop0: [0809]:406494 (/mnt/usr/tmp/ubuntu11.04.iso) root@boris-P5Q-E:~/vms/natty# cat natty.hvm name = "NattyHVM" builder = "hvm" memory = "2048" disk = [''phy:/dev/sda5,hda,w'', ''phy:/dev/loop0,hdc:cdrom,r''] vif = [

root@boris-P5Q-E:/mnt/usr/tmp# losetup -f ubuntu11.04.iso root@boris-P5Q-E:/mnt/usr/tmp# losetup -a /dev/loop0: [0809]:406494 (/mnt/usr/tmp/ubuntu11.04.iso) root@boris-P5Q-E:~/vms/natty# cat natty.hvm name = "NattyHVM" builder = "hvm" memory = "2048" disk = [''phy:/dev/sda5,hda,w'', ''phy:/dev/loop0,hdc:cdrom,r''] vif = [

flight 17860 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17860/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-pvops 4 kernel-build fail REGR. vs. 17854 Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-pcipt-intel 1 xen-build-check(1)

This adds a backend_domname field in libxl devices that contain a backend_domid field, allowing either a domid or a domain name to be specified in the configuration structures. The domain name is resolved into a domain ID in the _setdefault function when adding the device. This change allows the backend of the block devices to be specified (which previously required passing the libxl_ctx down

Surely you hear plenty about what''s not working, so I thought I''d shoot a quick message on something that did work. I got Windows Server 2008 RC2 installed. I have yet to even activate it and prove all internal features/devices work, but installation alone satisfied me! I had to fight a couple issues and I''ll mention them here, i think they''d be pretty

Hi My original message and problem is in http://lists.xenproject.org/archives/html/xen-users/2013-06/msg00422.html, but I couldn''t reply to that, so I''m sending an update in the form of a new message. I have changed the memory parameter in /etc/xen/win.cfg, from 1024 to 4096 and now the domU stays active, or at least on the list before: memory=1024

Dear xen-users. First of all, I''m not a linux-guru and a beginner with xen and completly new in this mailinglist. I''ve installed Xen on debian 6 and I was successful creating two machines: one for tests and "fogserver" (to test speed of writing computer images), both para-virtualisations.

Hello, I set up a Sabayon Linux domU as hvm guest and I completed the installation successfully. The problem is that when KDE is going to start, I see a blank screen. I use vncviewer but I don''t think this problem is related to vnc. Then I''ve read the minimal system requirements and I have seen this: 1) i686 Processor (starting from AMD K6 and Intel Pentium II) 2) 512 MB of RAM

I want to give my clients access to their Xen domU consoles using VNC. This works great using vfb device configured as type=vnc. However I have 2 problems: * I can't figure out how I can add a vfb device to a running domain without restarting it (I have 100+ domU's I want to enable this on, and want to avoid restarting them all if possible) * Related, I can't figure out how I can

flight 8803 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/8803/ Regressions :-( Tests which did not succeed and are blocking: test-amd64-i386-rhel6hvm-intel 4 xen-install fail REGR. vs. 8769 test-amd64-i386-xl 4 xen-install fail REGR. vs. 8769 test-amd64-i386-pair 6 xen-install/dst_host fail REGR. vs. 8769

"Old" tested version had not actually been tested; therefore in this flight we test it, rather than a new candidate. The baseline, if any, is the most recent actually tested revision. flight 20079 qemu-upstream-4.3-testing real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/20079/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking:

"Old" tested version had not actually been tested; therefore in this flight we test it, rather than a new candidate. The baseline, if any, is the most recent actually tested revision. flight 20078 qemu-upstream-4.2-testing real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/20078/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking:

Hi all, I had met with a question about vhd format when i install xen 4.2.0 source code on suse11_x86_64_sp2. execute steps: 1)Install fully suse 11 sp2 to host pc 2)Boot from Xen kernel menu 3)Download xen 4.2.0 source code from http://xen.org/download/index_4.2.0.html 4)Download bin86-0.16.19.tar.gz cmake-2.8.9.tar.gz Dev86src-0.16.19.tar.gz gettext-0.18.1.1.tar.gz