similar to: Failure to install SNV85 DomU at Xen 3.2 CentOS 5.1 Dom0 (64-bit)

System config:- bash-3.2# ifconfig -a lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 rge0: flags=201004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4,CoS> mtu 1500 index 2 inet 192.168.1.53 netmask ffffff00 broadcast 192.168.1.255 ether 0:1e:8c:25:cc:a5 lo0:

While attempting to install snv_85 as a domU, Debian etch as the dom0, the kernel panics before the rest of the system starts to boot. Currently I''m using the sid releases of xen 3.2 found in Debian sid. I stopped using 3.0.3, as it appears I''m unable to use a ramdisk setting. # dmesg | grep -i mem ... Memory: 1903728k/1949252k available (1623k kernel code, 36208k reserved,

Hi There is a problem when creating a domU. I intend to install Solaris N90 on RedHat RHEL5 in paravirtualized(I''ve tried fully virtualized method, that''s no problem). #xm info release : 2.6.18-53.el5xen machine : i686 xen_caps : xen-3.0-x86_32p My steps are as follow(install via NFS): 1 mkdir disk and mkdir Solaris 2 mount /dev/cdrom /disk/Solaris, it tell me that disk

Adding -kd to extra line drops me to kmdb :- root@ServerJaunty:/home/boris/nevada# xm create -c osol.install Using config file "./osol.install". Started domain osol.install (id=4) Loading kmdb... Welcome to kmdb Loaded modules: [ unix krtld genunix ] [0]> I want patch kernel like it happens when adding to /etc/system:- set xnf:xnf_cksum_offload = 0

Hi all Opensolaris works perfectly, but I am not able to boot the xvm kernel on this hardware. I added the -k option in grub, but the system hangs before the hostname line without any debug info. I''ve tried snv from b94 to b99, with the same results. If I install Debian with xen kernel I am able to use pvm and hvm guests. What can I do ? thanks Giacomo -- This message posted from

Hi, I have installed b_78 on a Dell 2950 and booting to bare metal works fine but when I try to boot using the grub entry Solaris xVM it will boot to the point where it displays the uname info and then just stays there. It will not boot past that point. I have enabled VT technology in the BIOS (but only after the installation). Where/what can I look at to trouble shoot this? I am new to xen and

Hi all, I have a Toshiba Tecra M9 and have not been able to boot it dom0. This is running SXDE 01/08, snv79b. After booting under kmdb and setting moddebug=80000000 before booting the Solaris kernel (with help from Dan Mick), I was able to see mac_ether as the last thing loading, right after loading the e1000g driver. I cannot drop into kmdb via F1-A after it hangs. I''ve also

Hello: I successfully installed Solaris10 nv77 x86 on my Compaq NX6325 laptop with the following specs: - Mobile AMD Turion 64 X2 TL-52 (dual core 64bit). - 4GB RAM. The installation destination was an external 120GB USB 2.0 drive. I was able to successfully boot into regular Solaris, but not into xVM Solaris. Meaning, after highlighting the xVM menu item and pressing enter, the screen turns

Hello, I''m using the latest b75 ISO to try and get a solaris dom0 running on my laptop, a Sony SZ-330P. The Xen LiveCD works just fine, so I know that theoretically it should work. Build 75 also works just fine on my Sony, including sound and video, etc. But when I try and boot the Xen kernel, the system hangs. There''s no panic printed to console. If I pass a -v option at

http://bderzhavets.blogspot.com/2008/05/install-solaris-nevada-build-87-domu-at.html This message posted from opensolaris.org

So I realize this is somewhat stupid, and I''ve actually gotten myself out of kmdb to kill my dtrace script but this has happened in the past and I''m wondering if there''s any better way around it than hitting :c a bunch of times. Say you set a breakpoint() to fire in a common function. This will drop you into kmdb where you can do some debugging, you take a look around

I am trying to build Xen from on-src-b79. According to opensolaris website, all xVM sources should be in the on-src-b79 tree, and no additional sources are required. I followed the procedure for doing the nightly build, and I expected that, as a result I will build, along with the Solaris kernel, the xen.gz image. I was hoping to copy that xen.gz image to my test machine, so I can boot with my own

After BFU-ing my system to b75 I ended up with a panicing system when booting into Xen: grub> #---------- ADDED BY BOOTADM - DO NOT EDIT ---------- grub> title Solaris on Xen grub> kernel$ /boot/$ISADIR/xen.gz grub> module$ /platform/i86xpv/kernel/$ISADIR/unix /platform/i86xpv/kernel/$ISADIR/unix -B console=ttyb grub> module$ /platform/i86pc/$ISADIR/boot_archive grub>

Folks: I am unable to get my opensolaris sn-b85 domU to start up in an opensolaris sn-b85 dom0. I am booted to xvm. Other systems, such as Fedora 8, WinXP Pro, W2k3 server, W2k8 server and Windows Vista startup normally. I have used the following to build the domU: # mkfile -n 25g /solhvm/solhvm.img # ls -l /solhvm total 269 -rw------T 1 root root 26843545600 Jul 7 10:37 solhvm.img

I''ve been testing ZFS since it came out on b27 and this week I BFUed to b30. I''ve seen two problems, one I''ll call minor and the other major. The hardware is a Dell PowerEdge 2600 with 2 3.2GHz Xeons, 2GB memory and a perc3 controller. I have created a filesystem for over 1000 users on it and take hourly snapshots, which destroy the one from 24 hours ago, except the

Remote box SNV93 (xVM kernel) 192.168.1.54 (NIC RTL8169) Attempts of ssh connection from CentOS 5.1 DomU 192.168.1.37 at SNV93 Dom0 (NIC RTL8110SC) # ssh user1@192.168.1.54 hangs .. TCPDUMP running on remote box (192.168.1.54) # tcdump -s 1600 -vv One entry generates for each ssh connection attempt. First:- 17:12:43.058821 IP (tos 0x0, ttl 64, id 19771, offset 0, flags [DF], proto TCP (6),

Copied ramdisk and kernel to Dom0 root@ServerXen331:/mnt/home/boris/isos# cat copy.sh mount -o loop,ro os200906.iso /mnt cp /mnt/boot/x86.microroot /home/boris/solaris cp /mnt/platform/i86xpv/kernel/amd64/unix /home/boris/solaris Created profile like for osol 2008.11 root@ServerXen331:/mnt/home/boris/solaris# cat osol200906.install name = "sol0906" vcpus = 1 memory =

I have a Sony lib-162 tape library hooked up to an adaptec 39160 scsi controller. I''m running OpenSolaris / Indiana snv_98 with the CADP160 driver installed from a SXCE dvd (snv_99). When I boot without xvm, I can run "mt config" and see the configuration information for the first drive in the library. Under xvm, some scsi operations still work - I can access the changer, move

Hi, I have setup an old Compaq Proliant DL580 with 2 xeon @700MHz 2Gb RAM two SmartArray 5300 controllers and 12 drives in an array enclosure. I am running the latest opensolaris update bfu''ed from binaries since I could not build from source. I am controlling the drives with the cpqary3 driver (Solaris 10) from HP. Initially the array had 7 drives and I created a raidz zfs pool

Hi -- I''m getting this error even though I have correct DVD ISO image for snv_92. bash-3.2# uname -a SunOS stoakly2 5.11 snv_92 i86pc i386 i86xpv bash-3.2# xm create snv.py Using config file "./snv.py". Error: (2, ''Invalid kernel'', ''elf_xen_note_check: ERROR: Will only load images built for the generic loader or Linux images'') bash-3.2#