similar to: Problem with virtual network bridge

Hi all, I''ve just upgraded my OpenSolaris 2008.05 workstation to snv_90 after unsucessfully trying to get virt-install.sh to run on snv_86 and now have (I think) a more serious problem. In the xend-debug.log file I keep getting the following error repeated many times : Failed allocation for dom 8: 1 extents of order 9 ERROR Internal error: Cannot allocate more 2M pages for HVM guest.

Hi ! In snv_127 I suddenly face a problem I never had before. Xvm can''t attach a vif to my primary physical nic any longer: $ pfexec xm start ulrac1 Error: Device 0 (vif) could not be connected. error: Failed to create vnic over yukonx1 with MAC address 00:16:36:3c:bf:70 This worked fine in all previous snv_12x releases I tested, including snv_126. I think there is a privilege

Hi all, I installed 2009.06, xVM and happily installed a domU with no issues. I just did this through the virt-manager GUI, and kept it as simple as possible. Later I installed and booted a zone with very simple and standard configuration. My existing xVM virtual machine did not immediately stop working, or have any interruption at all. But, I can no longer create new virtual machines, or even

Hi All, I have a machine with three network cards, and the third card(named e1000g2) is in use now. I want to use e1000g2 as default NIC when I create Guest. How can I change the default NIC? I can override the default value of config/default-nic property of svc:/system/xvm/xend. But xend still use e1000g0 when creating Guest. BTW, I can explicitly set "bridge=e1000g2" when creating

Using OpenSolaris 2008.11 build 110. Created vnic''s and etherstub''s and they are displayed using dladm show-links but when the server is rebooted a ''dladm show-link'' is empty although the vnic and etherstub devices are still there and function properly. That is a real inconvenience, so why do the no longer show after a reboot or shutdown/start? Is there a

Hi all! I am running SXCE 121 on a dual quad-core X2200M2 (64 bit of course). During an installation of a NetBSD 5.0.1 PVM domU, the entire machine crashed with a kernel panic. Here''s what I managed to salvage from the LOM console of the machine: Sep 2 18:55:19 glaurung genunix: /xpvd/xdb@41,51712 (xdb5) offline Sep 2 18:55:19 glaurung genunix: /xpvd/xdb@41,51728 (xdb6) offline

I recently updated to snv_125 and now bridged networks for my VirtualBox guests can''t move any network traffic. I''ve tried both VirtualBox 3.0.4 and 3.0.8 with no success. Any ideas? Thanks, Gordon -- This message posted from opensolaris.org

Is dovecot *really* that picky about grep, or did it just happen to pick up an autoconf that's being overly pedantic? I saw this message a couple of times when googling, but no particularly good solution presents itself. I'll probably give it a new GNU grep just to get it to shut up, but I'm a bit surprised. I tried to compile dovecot in an OpenSolaris 2008.5 system in a zone

hi list, initial situation: SunOS alusol 5.11 snv_86 i86pc i386 i86pc SunOS Release 5.11 Version snv_86 64-bit 3 USB HDDs on 1 USB hub: zpool status: state: ONLINE NAME STATE READ WRITE CKSUM usbpool ONLINE 0 0 0 mirror ONLINE 0 0 0 c7t0d0p0 ONLINE 0 0 0 c8t0d0p0

After googling around and reading the material on the opensolaris.org xvm community site, I still do not understanding the configuration of networking and would appreciate some assistance. Problem: I have successfully installed an hvm domU running Windows XP on opensolaris 2005.11 (build 94), and when the laptop (lenovo t61, core2 9300) is connected via the e1000g0 interface networking works

[ Redirecting to xen-discuss@opensolaris.org ] xiao liu wrote: > I installed Nevada b84 on my laptop then built latest onnv-gate > on it. > > After I installed it using Install and try to boot, > it panic for don''t know "/xpvd" (hvmboot_rootconf failed) > > Seems b84 don''t support xpvd/xpv, What should I do now, > should I use BFU instead?

Howdy, I just installed the crossbow snapshot from opensolaris.org, and bumped into an issue when attempting to create a virtual nic: $ dladm create-vnic -i 192.168.1.101 -d ni0 2 dladm: VNIC creation failed: No such file or directory (unknown diagnostic) When I truss the process, it looks like it''s failing when attempting to open the vnic pseudo-device: 100878/1:

Basically what I am trying to attempt here is to have multiple vm''s in a private network that is seperate from any of the physical networking devices. So far all I have really been able to do is connect the vm''s to an etherstub, but cannot get them to communicate with eachother. I have been using this (http://blogs.sun.com/droux/entry/private_virtual_networks_for_solaris) as a

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.

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

On OpenSolaris 2009.06 I created a flow, half a dozen VNICs, and I set some properties, and everything was working, then I rebooted my system and everything disappeared from show-vnic, show-flow, and show-prop. When I tried to re-create the objects, dladm said they already existed. While I could not see the objects, I could delete them. Example: # dladm show-vnic # dladm create-vnic -l bge0

I have NexentaCP2 (Opensolaris b104+). Parameters for the kernel: ''zfs-bootfs=syspool/rootfs-nmu-000,bootpath=/xpvd/xdf@0:a'' Pygrub returns: ''zfs-bootfs=syspool/30,bootpath=/xpvd/xdf@0:a'' Result: Boot with pygrub don''t work. What is "30" in syspool/30 ? _______________________________________________ Xen-users mailing list

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:

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#

Hi, I''m using opensolaris 2008.05, updated to snv_94. On dom0, I have : - bnx1 connected to switch as trunk - bnx128001, vlan 128 on bnx1, allocated an IP address and serve as dom0''s primary network interface. I created a RHEL5 domU with this vif config vif = [ ''mac=00:16:XX:XX:XX:XX, bridge=bnx128001'' ] but domU startup failed with Error: Device 0 (vif)