similar to: Creating a Fedora 11 DomU

Fasiha Ashraf --- On Sat, 22/8/09, Fasiha Ashraf <feehapk@yahoo.co.in> wrote: From: Fasiha Ashraf <feehapk@yahoo.co.in> Subject: Re: [Xen-users] my bootlog To: "Boris Derzhavets" <bderzhavets@yahoo.com> Date: Saturday, 22 August, 2009, 11:12 AM Please check what wrong here grub.conf        title Fedora (2.6.30-rc6-tip)         root (hd0,6)         kernel

I was able to get login prompt ( commit 7c62209cde5b13b81685e79b2f9e3757e293aef1 ) first time via serial console:- title Xen 3.4.1  Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1)   root (hd1,0)   kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1   module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=hvc0 earlyprintk=xen   module

Hi, These are my make menuconfig screen shots. I haven''t found any xen option in v2.6.30-rc. Why is that so? this happens with most of the version. What should I do? should I just let it as it is an run the make command to build the kernel? Regards, Fasiha Ashraf See the Web''s breaking stories, chosen by people like you. Check out Yahoo! Buzz. Love Cricket?

Hi, I''ve seen this asked a few times, but I just can''t work out whether I am misinterpreting how this is supposed to work, or if it is just broken in my setup. What I want is to be able to see the character cell console of DomU''s via VNC. As far as I understand, when I create/startup the DomU, then a vnc server should start listening on my Dom0. I have tried every

Previous 2.6.31-rc8 kernel was built on F11 and installed with modules on F12. Current kernel has been built on F12 (2.6.31-0.204.rc9.fc12.x86_64) and installed on F12 before loading under Xen 3.4.1. Dmesg log looks similar to Michael Yuong''s ''rc7.git4''  kernel for F12. Boris. --- On Tue, 9/8/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: From: Boris

Hi all, I am trying to install OpenSUSE 11.1 as a para-virtualized DomU on an opensolaris2009.06 guest using the xvm packages provided via IPS. I followed the instructions available here: http://www.opensolaris.org/os/community/xen/docs/virtinstall/ but I get the following error when trying to install from a NFS share where I mounted the iso (as far as I understand the only way to get a Linux

Thanks all for the advice. It seems there is an issue with Dracut booting from these hosts when LVM is used. dracut: Scanning devices sda2 for LVM logical volumes VolGroup/lv_swap VolGroup/lv_root dracut: inactive '/dev/VolGroup/lv_swap' [1.94 GiB] inherit dracut: inactive '/dev/VolGroup/lv_root' [230.69 GiB] inherit dracut: PARTIAL MODE. Incomplete logical volumes will be

Are you expecting improvement after  09/15/2009 new-swiotlb commits ? 4097,6144, "No_dom0_mem_specified" don''t look to me to have any. Boris.   _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

As mentioned yesterday, Xen 4.6 packages are now available for testing. These also include an update to libvirt 1.3.0, in line with what's available for CentOS 7. Please test, particularly the upgrade if you can, and report any problems here. To upgrade: yum update --enablerepo=centos-virt-xen-testing To install from scratch: * Install centos-release-xen from centos-extras yum install

Hi- Is it safe to use the zerofree utility on an ext4 partition inside an LVM with guestfish? I know zerofree works on ext4, but I am unsure about LVM. The info page uses the syntax "zerofree <device>", so using the info page example, could I (safely) do something like the following? $ guestfish Welcome to guestfish, the libguestfs filesystem interactive shell for

On 04/13/2016 12:02 AM, ???? wrote: > In /etc/rc.d/rc.sysinit, > there's "mount -a -n -t nonfs,nfs4,smbfs,ncpfs,cifs,gfs,gfs2i,glusterfs -O > no_netdev". > > > I have other same type servers. And on other servers with same /etc/fstsb, > file system is correct. > There's no difference between normal server's rc.sysinit and this problem > server's

HI, I am trying to install xen through yum. Here is what I did. [root@localhost Kishore]# yum install kernel-xen xen Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package kernel.x86_64 0:2.6.31.9-174.fc12 set to be installed --> Processing Dependency: kernel-firmware >= 2.6.31.9-174.fc12 for package: kernel-2.6.31.9-174.fc12.x86_64

hi, The problem: for kvm/qemu disks are /dev/vdx devices when using the virtio driver. For vmware, drives are /dev/sdx devices. For hp servers, /dev/ccisss/whatever (sorry, no proliant with an array controller handy to check it). in order to just have one kickstart script to maintain I am trying to use the %pre section but getting a bit stuck. This is what I have: %pre if [ -b /dev/sda ] then

> -----Original Message----- > From: Johnny Hughes > On 12/01/2014 04:48 AM, Bob Ball wrote: > > > > [<ffffffff81575480>] panic+0xc4/0x1e1 > > [<ffffffff81054836>] find_new_reaper+0x176/0x180 > > [<ffffffff81055345>] forget_original_parent+0x45/0x2c0 > > [<ffffffff81107214>] ? task_function_call+0x44/0x50 > >

Has anyone managed to create an encrypted disk partition with CentOS 8 kickstart? 1 reqpart --add-boot 2 part /boot --fstype ext3 --size=1024 --ondrive=sda 3 part pv.1 --size=1 --grow --ondrive=sda --encrypted --pashphrase="bla" 4 volgroup vol0 pv.100000 5 logvol / --vgname=vg_00 --name=lv_root --size=102400 --fstype=ext4 ... No matter what I specify in line 3, the installer bombs out.

Andy, OSOL 2009.06 been installed in stub domain (hvm domain) at mentioned Dom0 with 2.6.30 xenified kernel via xen-patches-2.6.30-2.tar.bz2 refuse to activate PV drivers. When same Dom0 starts with 2.6.29.4 xenified kernel (xen-patches-2.6.29-6.tar.bz2) kernel OSOL 2009.06 in stub (hvm) domain does activate PV drivers for xdf, xnf . Boris

On 04/13/2016 08:44 PM, ???? wrote: > # mount > /dev/mapper/VolGroup-lv_root on / type ext4 (rw,usrquota,grpquota) > proc on /proc type proc (rw) > sysfs on /sys type sysfs (rw) > devpts on /dev/pts type devpts (rw,gid=5,mode=620) > tmpfs on /dev/shm type tmpfs (rw) > /dev/vda1 on /boot type ext4 (rw) > /dev/vdb on /mnt/extradiskA type ext4 (rw,usrquota,grpquota) >

Next question:- eth0            8000.001c2596e32b       no              peth0 pan0            8000.000000000000       no virbr0          8000.000000000000       yes Presence virbr0 in report seems strange. Direct port  Xen 3.4.2  to F11 doesn''t install daemon libvirtd ( bridge virbr0 ) , unless you wrote xen-3.4.2-(x).fc12.src.rpm  yourself. So , from where bridge virbr0 comes 

Yes, build issue has been resolved perfectly by Changeset 19594. However, NO  hotplug logs again. root@ServerJaunty:/var/log/xen# ls -l total 788 -rw-r--r-- 1 root root 184025 2009-05-15 11:12 domain-builder-ng.log -rw-r--r-- 1 root root 157480 2009-05-15 11:09 xend-debug.log -rw-r--r-- 1 root root 446867 2009-05-15 11:14 xend.log I''ve also made same test on F11 preview ( obviously not

Are these the current functional procedures for dropping a dom0 on a jaunty 64 bit server? xen-tools: http://bderzhavets.wordpress.com/2009/08/14/attempt-of-prevu-xen-3-4-1-hypervisor-on-ubuntu-jaunty-server-64-bit/ kernel: http://bderzhavets.wordpress.com/2009/07/07/building-xenified-2-6-30-1-kernel-via-xen-patches-2-6-30-2-tar-bz2/ Regarding the patches used in the above procedure from here: