We are running 4 Solaris10u7 DomUs on a b113 Dom0
I''d like to upgrade the Dom0 to b122 but not rebuild the DomUs. Below
is a typical DomU xml dump. Is there anything obvious that will bite
me in upgrading from 113 to 122?
Thanks
John
virsh # dumpxml achilles2
<domain type=''xen'' id=''1''>
<name>achilles2</name>
<uuid>3dc86feb-d343-43a8-060f-8cd2b3fe5e6d</uuid>
<os>
<type>hvm</type>
<loader>/usr/lib/xen/boot/hvmloader</loader>
<boot dev=''hd''/>
</os>
<memory>2097152</memory>
<vcpu>2</vcpu>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<distro name=''solaris10''/>
<features>
<acpi/>
<apic/>
<pae/>
</features>
<clock offset=''localtime''/>
<devices>
<emulator>/usr/lib/xen/bin/qemu-dm</emulator>
<interface type=''bridge''>
<source bridge=''e1000g3''/>
<target dev=''vif1.0''/>
<mac address=''52:54:00:11:47:c9''/>
<script path=''vif-vnic''/>
</interface>
<disk type=''block'' device=''disk''>
<driver name=''phy''/>
<source
dev=''/dev/zvol/dsk/vdisk1/achilles2.zvol''/>
<target dev=''hda''/>
</disk>
<disk device=''cdrom''>
<target dev=''hdc''/>
<readonly/>
</disk>
<disk type=''block'' device=''disk''>
<driver name=''phy''/>
<source
dev=''/dev/zvol/dsk/vdisk1/achilles2_shome.zvol''/>
<target dev=''hdb''/>
</disk>
<input type=''mouse'' bus=''ps2''/>
<graphics type=''vnc'' port=''5900''/>
<input type=''tablet'' bus=''usb''/>
<console tty=''/dev/pts/2''/>
</devices>
</domain>
--
John Landamore
Department of Computer Science
University of Leicester
University Road, LEICESTER, LE1 7RH
J.Landamore@mcs.le.ac.uk
Phone: +44 (0)116 2523410 Fax: +44 (0)116 2523604
On Mon, Sep 07, 2009 at 01:46:53PM +0100, J. Landamore wrote:> We are running 4 Solaris10u7 DomUs on a b113 Dom0 > I''d like to upgrade the Dom0 to b122 but not rebuild the DomUs. Below > is a typical DomU xml dump. Is there anything obvious that will bite > me in upgrading from 113 to 122? > > Thanks >There shouldn''t be any problems (I know of one compatibility problem, but it''s obscure and won''t affect you) regards john
On Mon, Sep 07, 2009 at 02:01:13PM +0100, John Levon wrote:> On Mon, Sep 07, 2009 at 01:46:53PM +0100, J. Landamore wrote:...> > I''d like to upgrade the Dom0 to b122 but not rebuild the DomUs. Below > > is a typical DomU xml dump. Is there anything obvious that will bite > > me in upgrading from 113 to 122?...> There shouldn''t be any problems (I know of one compatibility problem, > but it''s obscure and won''t affect you)1) Can you eleborate a little bit on this (my current plan is to LU Dom0 from snv_b98 to snv_b124 in november, DomUs: Win SBS 2003 32bit, Win STD Server 2008 32bit) ? 2) Is it possible, that the PV driver gets loaded very late, i.e. after Win 2008 Std Server has done its filecheck? If so, is it possible to force it to load earlier? Background: Had a prod server, which was not accessible via RDP. virsh list and xentop reported that this DomU is running for ~20s, after that ''no state'' for ~2-3s and than running again. During the ''running'' phases CPU usage was between 25-120% (I guess, it used only a single core - 4 are assigned to it). So connected via vnc and it showed, something like: 3 Prozent abgeschlossen. (35850 von 95360 Datensaetzen verarbeitet) in english - I guess it would be 3 Percent finished. (35850 of 95360 datasets processed) At this time each dataset check took about ~1.67s !!! Since I was wondering, what comes next, I let it ran further 27 !!! hours. Than it startet to check ~ 150K indexes at the same speed (saying 11% finished). And this was the time, when I decided to rollback to the previous snapshot (more than a day without a redundant server for more or less mission critical stuff is a little bit too hot IMHO ;-)). So actually it seemed to be very odd. The server uses about 20 of 24GB zvol. Since it happend a 2nd time within 3 month, I guess, beside Windows the PV driver could be a problem as well ... So any hints? Regards, jel. -- Otto-von-Guericke University http://www.cs.uni-magdeburg.de/ Department of Computer Science Geb. 29 R 027, Universitaetsplatz 2 39106 Magdeburg, Germany Tel: +49 391 67 12768
On Wed, Sep 09, 2009 at 12:57:33AM +0200, Jens Elkner wrote:> > There shouldn''t be any problems (I know of one compatibility problem, > > but it''s obscure and won''t affect you) > > Can you eleborate a little bit on this (my current plan is to LU Dom0 > from snv_b98 to snv_b124 in november, DomUs: Win SBS 2003 32bit, > Win STD Server 2008 32bit) ?http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6844714 ''e1000g0 '' causes problems with VNIC script> Is it possible, that the PV driver gets loaded very late, i.e. after > Win 2008 Std Server has done its filecheck? If so, is it possible to > force it to load earlier?I don''t know anything about Windows PV drivers. regards john
On Wed, Sep 09, 2009 at 12:18:47AM +0100, John Levon wrote:> On Wed, Sep 09, 2009 at 12:57:33AM +0200, Jens Elkner wrote: > > > > There shouldn''t be any problems (I know of one compatibility problem, > > > but it''s obscure and won''t affect you) > > > > Can you eleborate a little bit on this (my current plan is to LU Dom0 > > from snv_b98 to snv_b124 in november, DomUs: Win SBS 2003 32bit, > > Win STD Server 2008 32bit) ? > > http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6844714 > ''e1000g0 '' causes problems with VNIC scriptAhh - good to know: have <source bridge=''e1000g0''/> as well...> > Is it possible, that the PV driver gets loaded very late, i.e. after > > Win 2008 Std Server has done its filecheck? If so, is it possible to > > force it to load earlier? > > I don''t know anything about Windows PV drivers.Hmmm, wondering whether anyone else has seen this problem ... Thanx, jel. -- Otto-von-Guericke University http://www.cs.uni-magdeburg.de/ Department of Computer Science Geb. 29 R 027, Universitaetsplatz 2 39106 Magdeburg, Germany Tel: +49 391 67 12768