similar to: Question(s) about the new smxgate-66 with fedora 6 DomU

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);

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:

Hi, all I want to get some information of How xVM is integrated with Crossbow project. Do some buddies have those documents or blogs? Thanks --luke

Hi, I found a problem with the DNS resolution in a Solaris 10 DomU. The Test Environment was: I installed the Xen bfu on top of Solaris snv43 and booted the Dom0 with Solaris. Then I installed and booted a Solaris 10 DomU. In the Solaris 10 Dom0 the DNS resolution works; in the Solaris 10 DomU the DNS resolution does not work as expected: Inside the Solaris 10 DomU I can''t use

I''d like to enhance Solaris network configuration slightly to allow guest domain IPv4 details to be passed from the domain building control tools through to the relevant components in Solaris (svc:/network/physical and uts/common/fs/nfs/nfs_dlinet.c). Attached is a proposal, roughly in the form of a fasttrack. Diffs for a prototype are at:

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

This fast-track covers the SMF-related changes for dom0. This is a final draft, so any comments by the end of the week please... Man pages are attached. thanks john SMF services for Xen 1. Introduction This case introduces the SMF services used by a Solaris-based domain 0 when running on Xen, or a Xen-compatible hypervisor. All of these services only run on domain 0 when booted

I am sponsoring this fasttrack for John Levon. It is set to expire on 3/14/2007. Note that this is an externally visible case. liane --- SMF services for Xen 1. Introduction This case introduces the SMF services used by a Solaris-based domain 0 when running on Xen, or a Xen-compatible hypervisor. All of these services only run on domain 0 when booted under Xen virtualisation.

Hi Everyone, Can anyone confirm if a xen based domU can be used for snort setup? It is not for commercial use, rather just SOHO use. Regards, dot.yet _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi Everyone, Can anyone confirm if a xen based domU can be used for snort setup? It is not for commercial use, rather just SOHO use. Regards, dot.yet _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

In testing our implementation of the hypervisor copy based backend- >frontend networking changes, we see what I believe are spurious warning messages during the shutdown of the frontend domain: (XEN) /export/build/schuster/xvm-gate/xen.hg/xen/include/asm/mm.h: 189:d0 Error pfn 30e290: rd=ffff830000fcf100, od=ffff830000fcf100, caf=00000000, taf=0000000000000000 (XEN) Xen call trace:

I created a DomU with a dedicated network connection script path=''/usr/lib/xen/scripts/vif-dedicated'' Having run the virtual machine I now destroy the domain, undefine it, change the script to script path=''/usr/lib/xen/scripts/vif-vnic'' define the domain and try to start it. This fails. If I change the assigned MAC address the newly defined virtual

Hi: I got OpenSolaris 2008.05 running as dom0 under VmWare fusion on my MacBook pro. Using the instructions from Dipleep''s blog http://blogs.sun.com/dkumar/entry/how_to_create_domu_in Everything seems okay except the networking. When booting OpenSolaris (without dom0) the pcn0 interface works just fine but when booting Solaris xVM version them pcn0 does not work (ie) I get failures

How do I create a vnic that represents the factory assigned MAC address of my physical nic? The bge device in my system (x2100) appears to support 4 MAC addresses. The driver reserves the first as the ''primary/default'' address and allows manipulation of the other three via the MAC_CAPAB_MULTIADDRESS interface. I''d like to use vnics on this system, as I have Xen guest

Hi, does anybody have a list of working Linux Live CDs with Xen Support which I can use in a Xen Domain? What I''m looking for is more or less something like Knoppix with Xen Support so that I can use the yet-not-supported hardware of my Ferrari 4005 in the Linux Domain regards Bernd This message posted from opensolaris.org

Disabling checksum offloading at OSOL DomU via kmdb at intial boot :- ( -kd at extra line):- root@ServerJaunty:/home/boris/nevada# xm create -c osol.install Using config file "./osol.install". Started domain osol.install (id=6)                                   Loading kmdb... Welcome to kmdb Loaded modules: [ unix krtld genunix ] [0]> ::bp xnf`_init [0]> :c v3.4.1-rc7 chgset

I''d like reviewers for: 6734731 vif-vnic instances can race against each other 6734123 xpvd-event logging is dismal The webrev is at http://dme.org/solaris/webrev/xvm-script-cleanup.

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

Hi, I am trying to install CentOS on an Opensolaris Dom0. virt-install fails with an error in virDomainCreateLinux(). Is this a known issue? Am I missing some step? manoj@mowgli:~$ uname -a SunOS mowgli 5.11 snv_101b i86pc i386 i86xpv Solaris manoj@mowgli:~$ pfexec virt-install What is the name of your virtual machine? centos How much RAM should be allocated (in megabytes)? 512 What would