similar to: Disabling checksum offloading at OSOL DomU via kmdb at intial boot.

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

I''m running a ubuntu 9.04 64 bit dom0 with kernel 2.6.29.6 and xen 3.4.0. My eth0 is bridged to br0 and to my guest VMs. The dom0 is running a dhcp server on br0 which is able to provide leases to physical machines on eth0, and also to a windows xp domU which is bridged to br0. However my open solaris 2009.6 domU is unable to obtain a dhcp lease. On the opensolaris side I can see this:

When trying to boot the OpenSolaris b75a dvd in a pv domU (using the linux phy:/dev/cdrom device as the source for the boot media), running on an Ubuntu 7.10 x86_64 dom0 box with xen 3.1.0 hypervisor, using the following config file... ======================================== # # Hostname # name = ''solaris-install2'' # # Kernel + memory size # kernel =

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

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

I am currently running a Redhat Rel5 Dom0 with a solaris 11-66 xen domU as well as a Redhat REL4 domU. I am experiancing problems similary to those described the the Aug 2006 Release notes regarding ... Solaris domUs on non-Solaris dom0s 32-bit Solaris domUs should run on any 3.0.2-3 or later dom0. The majority of our testing has been on CentOS dom0s. 64-bit solaris dom0 and domU require updates

Following bellow procedure involves Solaris Kernel module debugger to patch OSOL’s (SNV_111b) kernel at booting up to succeed with dhcp lease and to be able proceed with initial install. File /etc/system gets updated via root terminal session before standard reboot to make the patch for kernel permanent

Author: bmc Repository: /hg/zfs-crypto/gate Revision: 213bfe03af413cdf71c523fb076aaa65a6306a7e Log message: 6256581 System got a hang or a panic with dtrace+kmdb 6264573 unanchored dtrace_getpcstack is rather imprecise toward function end 6289517 dtrace doesn''t like fd_intr anymore 6291378 dtrace helpers can interfere with the use of kmdb 6295554 dtrace doesn''t report

Author: meem Repository: /hg/zfs-crypto/gate Revision: 4d618a4110ff44c57939c29a3a8a198be2ec8352 Log message: 6336683 address::queue -v blows up kmdb and mdb 6338969 netstrategy needs to use SIOCGLIFFLAGS and friends to see IFF_VIRTUAL 6339847 ip_rcm incorrectly parses interface names 6340643 ip_rcm is lugging around dead code 6340645 ip_rcm tracks needless phyint state Files: update:

It was rumored that Nevada build 105 would have ZFS encrypted file systems integrated into the main source. In reviewing the Change logs (URL''s below) I did not see anything mentioned that this had come to pass. Its going to be another week before I have a chance to play with b105. Does anyone know specifically if b105 has ZFS encryption? Thanks, Jerry -------- Original Message

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 =

It was rumored that Nevada build 105 would have ZFS encrypted file systems integrated into the main source. In reviewing the Change logs (URL''s below) I did not see anything mentioned that this had come to pass. Its going to be another week before I have a chance to play with b105. Does anyone know specifically if b105 has ZFS encryption? Thanks, Jerry -------- Original Message

As requested by several people, an Overview document has been posted at http://blogs.sun.com/sunay The reference section also contains a pointer to the slides that will be used for tonights presentation. See you all there. Cheers, Sunay -------- Original Message -------- Subject: [osol-discuss] SVOSUG - This Thurs, August 24, Sunay Tripathi presents Crossbow 7:30pm SCA03 Date: Mon, 21 Aug

In usr/src/uts/common/xen/io/xnbu.c, function xnbu_cksum_from_peer() http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/common/xen/io/xnbu.c#110 we have this: if ((flags & NETTXF_csum_blank) != 0) { /* * The checksum is blank. We must fill it in here. */ mp = xnb_process_cksum_flags(xnbp, mp, 0);

Hi, On Fri, Oct 30, 2009 at 8:41 AM, Gopi Desaboyina <gopidesaboyina at yahoo.com> wrote: > I think your system might be over heating. I observed this kind of behaviour in laptops when they get overheated. check if FAN is working or not. How frequent it gets rebooted. you could boot from opensolaris LiveCD and keep it for a day like that. if it reboots that means there could be h/w

Hello Nico, Friday, January 19, 2007, 7:53:06 PM, you wrote: NVdM> Hi, NVdM> Looking if someone already found a solution, or workaround, to change the GUID of a zfs pool. NVdM> Explain me some more in depth, by use of tools like ShadowImage NVdM> on storage Arrays like the Sun Storagetek 99xx (but also for SUN NVdM> related storage Arrays or IBM, EMC and other storage vendors)

On 03/10/10 10:48 AM, Mahesh wrote: > Hi all, > > I need some help in debugging the gldv3 driver performance issue on sparc. The driver has single Tx queue and 4 Rx queues and performs at almost the line rate(10G) on Sun intel boxes but the same driver performs very badly on sparc. The code is identical for sparc and intel except swapping involved since the hardware is little endian .

brtfs could be supported on Opensolaris, too. IMO it could even complement ZFS and spawn some concurrent development between both. ZFS is too high end and works very poorly with less than 2GB while brtfs reportedly works well with 128MB on ARM. Olga On Wed, Apr 14, 2010 at 5:31 PM, <Casper.Dik at sun.com> wrote: > > >>Just a completely different question...is there any plans

UNIX admin wrote: >> Adding crypto to ZFS isn''t that hard once we have >> IEEE 1619 mode >> (AES LRW) implemented in the crypto framework aes >> module(s). >> >> Dealing with the key management is very hard because >> thats the critical >> bit to making it both usable and secure. > > (Scratching head) > If I had to solve this

I''ve set up an opensolaris domU as a NFS server, of which my ubuntu dom0 is a client. However the IP layer somehow keeps failing, causing any application on the dom0 to freeze. If I switch to the console of the opensolaris domU and issue a ping to the dom0, this also fails. After a while (not sure how long), the network resumes operation. I''ve tried ping flooding the solaris