[EMAIL PROTECTED] writes: > Send xen-discuss mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://mail.opensolaris.org/mailman/listinfo/xen-discuss > or, via email, send a message with subject or body 'help' to > [EMAIL PROTECTED] > > You can reach the person managing the list at > [EMAIL PROTECTED] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of xen-discuss digest..." > > > Today's Topics: > > 1. Problem installing Linux as an hvm guest on Solaris Dom0 (Nirmal) > 2. Unable to boot Dom0 from external hard disk in snv_b81 > (Sreedhar G S) > 3. Attempt to configure SNV81 DomU with DHCP at F8 (32 bit) Dom0 > (Boris Derzhavets) > 4. Re: Attempt to configure SNV81 DomU with DHCP at F8 (32 bit) > Dom0 (Mark Johnson) > 5. Re: Problem installing Linux as an hvm guest on Solaris Dom0 > (Boris Derzhavets) > 6. Re: Attempt to configure SNV81 DomU with DHCP at F8 (32 > bit) > Dom0 (Boris Derzhavets) > 7. Q. xm migrate [--live] vs virsh (Neil Garthwaite) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 12 Feb 2008 06:40:45 +0000 > From: Nirmal <[EMAIL PROTECTED]> > Subject: [xen-discuss] Problem installing Linux as an hvm guest on > Solaris Dom0 > To: "Xen discuss" <[email protected]> > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi all > > I am trying to install linux(fedora/kubuntu) as hvm guest on Solaris > Neavada dom 0 build 79a.It gets stuck at boot menu in case of fedora 8 > and I am not able to press enter into the vncviewer.In case of kubuntu > it doesn't go ahead from the loading screen. > I also tried after booting the solaris in 32bit mode and using 32 bit > linux iso.But again faced the same problem.At the same time I am able > to install Solaris as an hvm guest and it works fine. > Has anybody encountered the same situation ?? > Any possible workarounds ?? > > Regards > Nirmal Agarwal > > > ------------------------------ > > Message: 2 > Date: Tue, 12 Feb 2008 20:36:23 +0530 > From: "Sreedhar G S" <[EMAIL PROTECTED]> > Subject: [xen-discuss] Unable to boot Dom0 from external hard disk in > snv_b81 > To: [email protected] > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="iso-8859-1" > > Hi All, > I installed snv_b81 in my portable hard disk(capacity 160gb with 2 > partitions, one for solaris and other for windows). When I tried to boot > into dom0 from grub, I got the following errors and the system gets hanged. > > Warning : No SOF interrupts have been received, this USB EHCI host > controller is unusable > panic[cpu0]/thread=f502ae20:cannot mount root path /[EMAIL PROTECTED], > 0/pci8086, > [EMAIL PROTECTED], 7/[EMAIL PROTECTED]/[EMAIL PROTECTED],0:a > f505570c genuix:rootconf +fc (0,1,f502a590,0, ) > f5055730 genuix : vfs_mountroot +54 (f46c00010,f5051548, ) > f5055740 genuix: main +b4() > skipping system dump - no dump device configured > rebooting... > > and the system hangs. I made my first hard disk as the portable one and the > second harddisk as the internal hard disk in (which contains fc8 and winxp) > in BIOS. The i86pc version boots fine and I am able to work without any > problems. > The same system(i86xpv) worked for me in my lab when I installed in an > internal hard disk. > Could some one help me fix the problem? > Regards > Sreedhar GS > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://mail.opensolaris.org/pipermail/xen-discuss/attachments/20080212/8733f240/attachment-0001.html > > > ------------------------------ > > Message: 3 > Date: Tue, 12 Feb 2008 07:30:26 PST > From: Boris Derzhavets <[EMAIL PROTECTED]> > Subject: [xen-discuss] Attempt to configure SNV81 DomU with DHCP at F8 > (32 bit) Dom0 > To: [email protected] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=UTF-8 > > I?ve placed F8 Dom0 box on DHCP bridge. Service ?dnsmasq? > behaves exactly the same way as on F8 Dom0 box with static IP :- > It serves dhcp requests from RH DomUs and refuse to serve dhcp request > from SNV76,78,81 DomUs . Any dhcp request from SNV DomU > gets timed out. > Regarding CentOS 5.1 Dom0 boxes, everything works just fine and doesn?t > depend on network config for Dom0:- > ?dnsmasq? serves dhcp request from SNV76,78,81 with no delays > > I guess, if eth0 is configured as DHCP at Linux Dom0, to create SNV DomU > with xnf0 configured as DHCP i need an entry into xend-config.sxp. > > (network-script 'network-bridge bridge=xenbr0 netdev=eth0') > > been read by xend daemon at boot up so that:- > > [EMAIL PROTECTED]:~# brctl show > > bridge name bridge id STP enabled interfaces > xenbr0 8000.feffffffffff no vif0.0 > > > peth0 > > It seems , that libvirtd daemon built in behavior at F8 Dom0 > doesn't allow to do that and does allow to do that at CentOS 5.1 Dom0:- > # chkconfig libvirtd off > I cannot disable libvirtd on F8 to turn off virbr0 and work with old fashioned > xen-bridge. External DHCP Server appears to be useless for me on Fedoras > However, due to multiple MRJ's feedbacks i understand , that someting > has been done incorrect. > > > This message posted from opensolaris.org > > > ------------------------------ > > Message: 4 > Date: Tue, 12 Feb 2008 10:50:00 -0500 > From: Mark Johnson <[EMAIL PROTECTED]> > Subject: Re: [xen-discuss] Attempt to configure SNV81 DomU with DHCP > at F8 (32 bit) Dom0 > To: Boris Derzhavets <[EMAIL PROTECTED]> > Cc: [email protected] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; format=flowed; charset=UTF-8 > > > > Boris Derzhavets wrote: > > I?ve placed F8 Dom0 box on DHCP bridge. Service ?dnsmasq? > > behaves exactly the same way as on F8 Dom0 box with static IP :- > > It serves dhcp requests from RH DomUs and refuse to serve dhcp request > > from SNV76,78,81 DomUs . Any dhcp request from SNV DomU > > gets timed out. > > Regarding CentOS 5.1 Dom0 boxes, everything works just fine and doesn?t > > depend on network config for Dom0:- > > ?dnsmasq? serves dhcp request from SNV76,78,81 with no delays > > > > I guess, if eth0 is configured as DHCP at Linux Dom0, to create SNV DomU > > with xnf0 configured as DHCP i need an entry into xend-config.sxp. > > > > (network-script 'network-bridge bridge=xenbr0 netdev=eth0') > > > > been read by xend daemon at boot up so that:- > > > > [EMAIL PROTECTED]:~# brctl show > > > > bridge name bridge id STP enabled interfaces > > xenbr0 8000.feffffffffff no vif0.0 > > > > > > peth0 > > > > It seems , that libvirtd daemon built in behavior at F8 Dom0 > > doesn't allow to do that and does allow to do that at CentOS 5.1 Dom0:- > > # chkconfig libvirtd off > > I cannot disable libvirtd on F8 to turn off virbr0 and work with old > > fashioned > > xen-bridge. External DHCP Server appears to be useless for me on Fedoras > > However, due to multiple MRJ's feedbacks i understand , that someting > > has been done incorrect. > > It could be that they recently change something in FC8? I haven't sync'd > up recently. > > > > MRJ > > > > > ------------------------------ > > Message: 5 > Date: Tue, 12 Feb 2008 07:51:16 PST > From: Boris Derzhavets <[EMAIL PROTECTED]> > Subject: Re: [xen-discuss] Problem installing Linux as an hvm guest on > Solaris Dom0 > To: [email protected] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=UTF-8 > > > Hi all > > > > I am trying to install linux(fedora/kubuntu) as hvm > > guest on Solaris > > Neavada dom 0 build 79a.It gets stuck at boot menu in > > case of fedora 8 > > and I am not able to press enter into the > > vncviewer.In case of kubuntu > > it doesn't go ahead from the loading screen. > View:- > http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6637632 > > > I also tried after booting the solaris in 32bit mode > > and using 32 bit > > linux iso.But again faced the same problem.At the > > same time I am able > > to install Solaris as an hvm guest and it works fine. > > Has anybody encountered the same situation ?? > > Any possible workarounds ?? > > > > Regards > > Nirmal Agarwal > > _______________________________________________ > > xen-discuss mailing list > > [email protected] > > > This message posted from opensolaris.org > > > ------------------------------ > > Message: 6 > Date: Tue, 12 Feb 2008 07:56:42 PST > From: Boris Derzhavets <[EMAIL PROTECTED]> > Subject: Re: [xen-discuss] Attempt to configure SNV81 DomU with DHCP > at F8 (32 bit) Dom0 > To: [email protected] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=UTF-8 > > > It could be that they recently change something in > > FC8? I haven't sync'd > > up recently. > Does your statement mean, that you just turned into old fashioned > xen-bridging , having libvirtd daemon (as well as virbr0 ) disabled on F8 ? > > > > > > > > MRJ > > > > > > _______________________________________________ > > xen-discuss mailing list > > [email protected] > > > This message posted from opensolaris.org > > > ------------------------------ > > Message: 7 > Date: Tue, 12 Feb 2008 18:18:29 +0000 > From: Neil Garthwaite <[EMAIL PROTECTED]> > Subject: [xen-discuss] Q. xm migrate [--live] vs virsh > To: [email protected] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="us-ascii" > > Hi, > > I'm just playing with xm migrate and xm migrate --live and just have a > few questions, > > 1. Is there an equivalent virsh command to xm migrate/live migrate. > > 2. It appears that via xm migrate it is possible to have the same domU > name, albeit with a different domain id on the same xVM node. Please > consider the following > > bash-3.2# virsh list --all > Id Name State > ---------------------------------- > 0 Domain-0 running > - elko-1 shut off > - elko-2 shut off > > bash-3.2# virsh start elko-2 > Domain elko-2 started > > bash-3.2# virsh list --all > Id Name State > ---------------------------------- > 0 Domain-0 running > 47 elko-2 running > - elko-1 shut off > > bash-3.2# > bash-3.2# virsh start elko-2 > error: Domain is already active > > bash-3.2# virsh list --all > Id Name State > ---------------------------------- > 0 Domain-0 running > 47 elko-2 blocked > - elko-1 shut off > > bash-3.2# > > For me at least, I like the above behavior. > > However, I could end up with this if I start elko-2 on another node > and then xm migrate --live to the node above, i.e. > > bash-3.2# virsh list --all > Id Name State > ---------------------------------- > 0 Domain-0 running > 47 elko-2 blocked > 48 elko-2 blocked > - elko-1 shut off > > If we consider multiple xVM nodes that will participate in live > migration, i.e. assuming an NFS mounted filesystem on these xVM nodes > for the boot image, then I could start the same domU on another or all > xVM nodes that could potentially participate in live migration. > > While I accept that doing so will likely corrupt the backend data > store and confuse everyone where the domu is running if it is running, > it nevertheless is currently possible to do. If we consider that for > live migration to work we need to follow these steps, > > Listen on all addresses (or you can specify a particular interface IP) > # svccfg -s xend setprop config/xend-relocation-address = \"\" > Create list of hosts from which to accept migrations: > # svccfg -s xend setprop config/xend-relocation-hosts-allow = \"^flax$ > ^localhost$\" > Update the config: > # svcadm refresh xend && svcadm restart xend > > Then my question #1 comes back into play albeit somewhat expanded. > > 1. Is there a [planned] virsh start/migrate command that would check > the "config/xend-relocation-hosts-allow" hostlist to determine if the > "Domain is already active" somewhere on this relocation hostlist, and > if it is then not allow the domain to be started and instead push out > the message "Domain is already active on node X". > > Regards > Neil > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://mail.opensolaris.org/pipermail/xen-discuss/attachments/20080212/43be5a2d/attachment.html > > > ------------------------------ > > _______________________________________________ > xen-discuss mailing list > [email protected] > > End of xen-discuss Digest, Vol 29, Issue 20 > ******************************************* _______________________________________________ xen-discuss mailing list [email protected]
