similar to: Booting from a real cdrom

Dear List-Colleagues: I have been working on installing Xen on Suse 10.3 for some time now. I am green as grass - both a total newbie to Xen and a relative newbie to Linux (as well as a total newbie to SuSE). Currently, I am at the point that when I click on the Xen entry in my grub loader I see Xen starting and running through much of its early setup. Eventually, however, it quits on

Thanks you all guys. I am able to create the RHEL5 PVM on RHEL5 host successfully. Only thing that i need to add is /mnt/etc/fstab in inintrd command and preload to both the fronthend drivers. As blow. # mount /home/disk /mnt # mkinirtd /boot//boot/initrd-2.6.18-8.el5xenU.img 2.6.18-8.el5xen --fstab /mnt/ etc/fstab --with xenblk --with xennet --preload xenblk --preload xennet Thanks a lot,

Hi List, I''d compiled Xen-3.0.3-testing (changeset 11740) on Suse 10.0 Enterprise Server. The compilation succeeded without any errors but the mkinitrd command fails(???) The initrd is being created but when loading the xen kernel, I get the following message repeatedly: "azx_get_reponse() timeout" after pressing ^c the computer continue to run... Then, when I start a gnome

I have a CentOS 5.1 dom0 running on a machine with two cores and 4gb of memory. It runs three 4.6 domUs and one 5.1 domU. Just out of the blue the other night all the 4.6 domUs crashed, but the dom0 stayed up. I ran xm console (domU-name) and got the Oops information below. I didn't get anything from the 5.1 domU. I think it had been rebooted a few days before and hadn't come up

I have a CentOS 5.1 dom0 running on a machine with two cores and 4gb of memory. It runs three 4.6 domUs and one 5.1 domU. Just out of the blue the other night all the 4.6 domUs crashed, but the dom0 stayed up. I ran xm console (domU-name) and got the Oops information below. I didn't get anything from the 5.1 domU. I think it had been rebooted a few days before and hadn't come up

Dear Fellow Xen Users: I am as green as grass and trying to install Xen 3.1.0 on to a brand new machine running SuSE 10.3. I am at the point where Xen starts to boot and quits on a "Waiting for device......./dev/sda5" message. I believe that this may be related to the fact that xennet and xenblk are missing, as far as I can tell, from my

On Thursday, 6 April 2017 12:04:20 CEST Richard W.M. Jones wrote: > Our previous test was wrong. It tested whether the xennet.ko module > exists. This module was renamed in more recent kernels (to > xen-netfront.ko), so it happened to not detect modern kernels as > PV-only, but this was by chance. Just stumbled upon this bit in v2v/convert_linux.ml: if family = `SUSE_family

Hello, we have a bug on any xen kernel > 3.4 like this: kernel BUG at /home/abuild/rpmbuild/BUILD/kernel- xen-3.7.9/linux-3.7/fs/buffer.c:2952! [ 628.054552] invalid opcode: 0000 [#1] SMP [ 628.054557] Modules linked in: bridge stp llc iptable_filter ip_tables x_tables nbd blktap2 pciback usbbk xen_scsibk openvswitch blkbk blkback_pagemap netbk xenbus_be gntdev evtchn ocfs2_dlmfs

Hi Shimizu --- Shimizu Miki <> schrieb: > Hello, > > Doesn''t the vircual nic work at all? After the hint of Timo (http://lists.xensource.com/archives/html/xen-users/2006-05/msg00091.html) I got the virtual xen network card show up in yast. However, when I configured it, yast came up with an error message that''no driver module for the device found''

I followed the book called "Professional Xen Virtualization" written by William von Hagen,and published by Wiley Publishing,Inc. Here are some configuration files: #cat /xen/ubuntu/ubuntu.xen3.cfg kernel = "/boot/vmlinuz-2.6.18-128.1.16.el5xen" ramdisk = "/boot/initrd-2.6.18-128.1.16.el5xen-no-scsi.img" memory = "512" name = "Ubuntu804" vif =

Hi all, This is my first post in the list. Nowadays I am starting with xen due a work task, for some of you my problem should be something very basic but for me it is taking long hours doing research on the issue and trying different things. What I have is a Xen image already built and what I want to do is just play it and make it accessible by the network. I can play it, that is not a problem at

I''m having an issue forwarding through an Intel on-board graphics adapter. This is on a Dell Optiplex 780 with 8GB of RAM. The pass-through works perfectly fine if I have 2GB of RAM assigned to the HVM domU. If I try to assign 3GB or 4GB of RAM, I get the following on the console: [ 41.222073] br0: port 2(vif1.0) entering forwarding state [ 41.269854] (cdrom_add_media_watch()

I''m having an issue forwarding through an Intel on-board graphics adapter. This is on a Dell Optiplex 780 with 8GB of RAM. The pass-through works perfectly fine if I have 2GB of RAM assigned to the HVM domU. If I try to assign 3GB or 4GB of RAM, I get the following on the console: [ 41.222073] br0: port 2(vif1.0) entering forwarding state [ 41.269854] (cdrom_add_media_watch()

Related: change the name of the function the comment describes to be more accurate. --- perl/lib/Sys/Guestfs/Lib.pm | 18 ++++++++---------- 1 files changed, 8 insertions(+), 10 deletions(-) diff --git a/perl/lib/Sys/Guestfs/Lib.pm b/perl/lib/Sys/Guestfs/Lib.pm index be17a30..bbc583f 100644 --- a/perl/lib/Sys/Guestfs/Lib.pm +++ b/perl/lib/Sys/Guestfs/Lib.pm @@ -1342,7 +1342,7 @@ sub

Ok So I''ve been able to successfully create a CentOS5 virt-install on xen using LVM created partitions. But have many problems trying to install 4.4 (It does not work with virt-install hence you have to try another method). I Created a name, name-tmp, name-swap, name-root paritions. I did mke2fs and mkswap no problem everything is good. I went on further to mount the name-tmp and

Hi everyone After configuring bonding eth0 and eth1 in domU, "cat /proc/net/bonding/bond0" showed it was configured correctly. ----------------------------------------------------------------------------------------- Bonding Mode: fault-tolerance (active-backup) Primary Slave: eth1 Currently Active Slave: eth1 MII Status: up MII Polling Interval (ms): 0 Up Delay (ms): 0 Down Delay (ms):

I am having an issue getting a DomU to boot properly. There is never any indication of a stop error or kernel panic, it simply hangs after "Starting crond [ OK ]" and never continues. I''ve included my mkinitrd and output from xm create... please help! ##### XENBUS errors ##### XENBUS: Device with no driver: device/vbd/2049 XENBUS: Device with no driver: device/vbd/2050

I have an F7 host that''s running the 2.6.20-2925.11.fc7xen 64-bit kernel on a Dell 2950 using the latest 64-bit Xen packages in F7, 3.1.0-2.f7. I''m trying to install RHEL 5 386 as a guest which I hear is possible. 64-bit RHEL5 isn''t available to use anyway. When I try to paravirtualize the install and only utilize 1 CPU, I always get a kernel oops right before the

Hi there, After updating a server from CentOS 5.3 to 5.4 my Xen pci-passthru setup has some troubles. The server has two NICs, one used by dom0 and the other assigned to a domU and one SCSI controler assigned to another domU. It has been working fine since CentOS 5.1, when I did the initial setup. After upgrading to 5.4, I get this error when starting the domU with one of the NICs assigned:

Hello, i will describe my approach 1) I have downloaded Centos5-64bit xen image from jailtime.org 2) I have created own swap image with 512MB file size 3) I have used same as dom0 kernel 2.6.18-53.1.19.el5xen 4) I have mounted my image file and copied /lib/modules/2.6.18-53.1.19.el5xen 5) I have created custom ramdisk for domU with mkinitrd --with=xennet --preload=xenblk