similar to: Xen boots to blank screen

Hi, I test pvgrub on xen-3.3.0. After starting pvgrub with "xm cr xmexample.pv-grub", I can see nothing but qemu window. With "xm li" , I can see this domain is running: Name ID Mem VCPUs State Time(s) Domain-0 0 1024 2 r-----

Thank Zhigang Wang for your response. I have test pvgrub with this config file: #pv-config kernel = "/usr/lib/xen/boot/pv-grub-x86_32.gz" extra = "(hd0,5)/boot/grub/menu.lst" memory = 512 name = "ExampleDomain" disk = [ ''file:/var/lib/xen/images/opensuse11-1/disk0,xvda,w'' ] vif = [ "bridge=eth0" ] root = "/dev/sda5 ro" start

hello, just for a success story : After bad experience on fedeora core 6, I have tested a OpenSuse 10.2beta2. I have installed with success a Windows XP SP2. The hardware: A intel DQ965gf Intel Core 2 Duo 6700 USB DVD reader IDE disk (PATA) Set AHCI mode in BIOS and add all-generic-ide in boot option. The opensuse 10.2beta2 does not well configured the xen kernel, you should do a mkinitrd and

Hi all I succed to install xen 4.1.2 on open suse .for as , all gone well. when i boot the xen it succeds . when i type "xm list" arise an error , such this "Error: Unable to connect to xend: No such file or directory. Is xend running?" . I post here the content of menu.lst file. Please help me ........................ # Modified by YaST2. Last modification on Wed Aug 8

Hello all, I''m trying to pass my PCI device through to an HVM. I''m following the steps on the xen pci passthrough wiki. First I check my pci devices #lspci - 03:00.0 VGA compatible controller: ATI Technologies Inc Device 671d 03:00.1 Audio device: ATI Technologies Inc Device aa80 04:00.0 Display controller: ATI Technologies Inc Device 671d 04:00.1 Audio device: ATI

Hello, I''ve recently installed a hvm domU opensuse 11 guest and I cannot set the screen resolution higher then 640x480. This seems very strange to me, because I don''t have any problem to set higher resolution on a windows 7 domU, using the following parameters in the configuration file: stdvga=1 videoram=16 What could the problem be? Is some video driver missing? -- Flavio

Hello, I''ve recently installed a hvm domU opensuse 11 guest and I cannot set the screen resolution higher then 640x480. This seems very strange to me, because I don''t have any problem to set higher resolution on a windows 7 domU, using the following parameters in the configuration file: stdvga=1 videoram=16 What could the problem be? Is some video driver missing? -- Flavio

Dear list, I''m trying to get Xen working on a P3-600E with 320 MB RAM. (256+64) It has suse linux 9.1 installed on it, and I tried to get xen running with both the binary download from the xen pages and the suse xen packages mentioned on this list some days ago. Both ''install packages/kernels'' lead to the same error: (XEN) Not enough memory for DOM0 memory

hi all, i want to install xen3.1 on my system, suse linux enterprise server 10 SP1 (kernel 2.6.16.46-0.12). i download the tarball binary file. it contains only "vmlinuz-2.6.18-xen" and "xen-3.1.gz", no initrd. but see the following code in my grub menu.lst, it seems like i need the initrd file. i tried the installation with this binary Tarball, it didn''t work.

Hello, I am using Xen 3.2.1 and I cannot boot it on my machine unless I use the noacpi option. As far as I know noacpi option is incompatible with SMP, so I must not use it, because my machine is SMP. I am describing the problem in more detail below. If you could point me in the right direction, I''d greatly appreciate it. I downloaded Xen 3.2.1 official source distribution tarball from

Greetings! Trying to to run a xen3 domU on a xen4 dem0 I run into problems. The xen server ''XEN1''(dom0) is openSUSE-11.3 (kernel 2.6.34) and xen-4.0.1. With qemu I created an image ''M08.raw'' from the SUSE-9.3 (kernel 2.6.11) and XEN-3.0 installation CD''s. The XEN modules were included in the installation. In M08.raw/boot I configured grub/menu.lst:

hi, i''ve been successfully running a headless install of OpenSuse 11.0 + Xen 321 as a Xen Dom0 w/ multiple DomUs for quite awhile ... i just built up a new OpenSuse 11.1 + Xen 331 box. short story -- not working, and not clear as to why not .entirely possible i''ve missed some new config req''ts ... what do I need to do to get xen behaving under 11.1? i''m

I''m having trouble actually seeing a PCI device in my VMs. I''ve resolved several of my issues using previous posts and using the VTdHowTo wiki page. I have both VT and VTd BIOS options enabled. I have pciback hiding the devices and xm can list and assign the devices to VMs. I don''t see the PCI devices in my VMs though. I have tried a windows and a Linux vm, without

I''m having problems booting Dom0 on an unbranded server. Server is running SuSE 9.3 x86_64 and has been working fine for a couple of years as a standard boot pc. I installed the 2.0.5c version of Xen which is part of the SuSE repository. I cannot boot into Xen though, booting Dom0 stops after: NET: Registered protocol family 16 I know from a normal boot that the next part is PCI

Hi all This is a strange one. On upgraging to SuSE kernel-2.6.11.4-21.7, I have suddenly found that I loose the video on boot up! The video disappears very early in boot, possibly while Xen hypervisor is starting, printing out the physical memory map. If you are patient and wait for the machine to reach run level 5, the X server starts up and you get a picture back. You can then switch back and

Suse 10.1 AMD64 Xen3 New to Xen. The dom0 is up and running. I am trying to get my first domU working. My approach is to use precompiled images from jailtime.org. After some manual tinkering with the .cfg file the domU proceeds to boot but stalls with the following error. I cannot get past this - any ideas ? Brian Using config file "/etc/xen/vm/vm1". Started domain vm1 Bootdata ok

Hi , I have setup xen on a number of different machines already; however, I couldn''t get xSeries 330 working with Xen. When it boots up, it says "Waiting for device /dev/sda1 .... device not found" and then return a shell prompt. I have looked up this error on the mailing list. I found that the error is potentially caused SCSI driver and it can be resolved this problem by

We have a system that is designed with no VGA port, graphics card, or keyboard, only a serial console. We're trying to boot a Linux via ISOLINUX. The problem is that when ISOLINUX comes up, the screen is usually garbled. Not always; sometimes it's intact, sometimes it's completely blank. When it is garbled, it is NOT the garbled text of a wrong baud rate. Rather, it looks like

Hi all, did somebody successfuly export ISDN Cards to DomU? I want to have 2 ISDN Cards in DomU (for Asterisk with mISDN) lspci -vt -[0000:00]-+-00.0 nVidia Corporation MCP55 Memory Controller +-01.0 nVidia Corporation MCP55 LPC Bridge ... +-05.1 nVidia Corporation MCP55 SATA Controller +-06.0-[0000:01]--+-00.0 Cologne Chip Designs GmbH ISDN

Hi all, In June 2007 Jerry Nelson started a thread on this mailing list about a problem he was seeing. The thread was http://syslinux.zytor.com/archives/2007-June/008673.html After several hours of searching through the list, I am still convinced that his problem was never solved and is very valid. I recently moved from the old syslinux config options model (all labels in 1 default config file)