Hello, I''m trying to install Nevada66 as domU under Fedora 8 dom0 (64 bits) but the boot process fails. My config file contains: name = ''solaris'' memory = ''1024'' vcpus = 1 disk = [ ''file:/home/nico/solaris-inst.iso,6:cdrom,r'', ''file:/home/nico/solaris.img,hda,w'' ] vif = [ ''bridge=virbr0'' ] on_shutdown = ''destroy'' on_reboot = ''restart'' on_crash = ''destroy'' kernel = ''/usr/local/xen/unix-66-0624-nd'' ramdisk = ''/usr/local/xen/x86.miniroot-66-0624-nd'' extra = ''/platform/i86xpv/kernel/unix -B install_media=cdrom'' #rootdisk = "/dev/dsk/c0d0s0" extra = ''/platform/i86xpv/kernel/unix -B install_media=cdrom'' but when I startup it I obtain: $ xm create -c solaris.conf Using config file "/etc/xen/solaris.conf". Started domain solaris SunOS Release 5.11 Version xen-nv66-2007-06-24 32-bit Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. WARNING: Found xen v3.1.0-rc7-2942.fc8 but need xen v3.0.4-1-sun WARNING: The kernel may not function correctly panic[cpu0]/thread=d2a44e00: HYPERVISOR_mmu_update() failed d2c31ac0 unix:x86pte_cas+122 (d983a530, 0, 0, 0, ) d2c31b00 unix:link_ptp+6d (d983a530, d983a4e0,) d2c31b68 unix:htable_create+19d (d944ff08, 8047000, ) d2c31ba0 unix:hati_load_common+78 (d944ff08, 8047000, ) d2c31bd4 unix:hat_memload+5f (d944ff08, 8047000, ) d2c31c44 genunix:segvn_faultpage+39b (d944ff08, d2a41f98,) d2c31d34 genunix:segvn_fault+8a4 (d944ff08, d2a41f98,) d2c31dc4 genunix:as_fault+4ae (d944ff08, d2a42f08,) d2c31e1c unix:pagefault+183 (8047ff4, 0, 2, 0) d2c31eb4 unix:trap+1141 (d2c31ec8, 8047ff4, ) d2c31ec8 unix:cmntrap+aa (d2c301b1, f4d10000,) d2c31f20 unix:kcopy+25 (d94502b0, 8047ff4, ) d2c31f6c genunix:exec_init+143 (f506c39c, f506c29c) d2c31f88 genunix:start_init_common+c4 (0, d2c31fa4, f4c3f0) d2c31f94 genunix:start_init+1c (0, 0) d2c31fa4 unix:thread_start+8 () syncing file systems... done skipping system dump - no dump device configured rebooting... P.S. This is the third time that I post this message: all other posts were never delivered to the ML nor bounced back (although I was already subscribed at the time). Thanks, Nico
Nico Sabbi wrote:> Hello, > I''m trying to install Nevada66 as domU under Fedora 8 dom0 (64 bits) > but the boot process fails.can you try a 64-bit domU install? MRJ> My config file contains: > name = ''solaris'' > memory = ''1024'' > vcpus = 1 > disk = > [ ''file:/home/nico/solaris-inst.iso,6:cdrom,r'', ''file:/home/nico/solaris.img,hda,w'' ] > vif = [ ''bridge=virbr0'' ] > on_shutdown = ''destroy'' > on_reboot = ''restart'' > on_crash = ''destroy'' > kernel = ''/usr/local/xen/unix-66-0624-nd'' > ramdisk = ''/usr/local/xen/x86.miniroot-66-0624-nd'' > extra = ''/platform/i86xpv/kernel/unix -B install_media=cdrom'' > #rootdisk = "/dev/dsk/c0d0s0" > extra = ''/platform/i86xpv/kernel/unix -B install_media=cdrom'' > > > but when I startup it I obtain: > > $ xm create -c solaris.conf > Using config file "/etc/xen/solaris.conf". > Started domain solaris > SunOS Release 5.11 Version xen-nv66-2007-06-24 32-bit > Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved. > Use is subject to license terms. > WARNING: Found xen v3.1.0-rc7-2942.fc8 but need xen v3.0.4-1-sun > WARNING: The kernel may not function correctly > > panic[cpu0]/thread=d2a44e00: HYPERVISOR_mmu_update() failed > > d2c31ac0 unix:x86pte_cas+122 (d983a530, 0, 0, 0, ) > d2c31b00 unix:link_ptp+6d (d983a530, d983a4e0,) > d2c31b68 unix:htable_create+19d (d944ff08, 8047000, ) > d2c31ba0 unix:hati_load_common+78 (d944ff08, 8047000, ) > d2c31bd4 unix:hat_memload+5f (d944ff08, 8047000, ) > d2c31c44 genunix:segvn_faultpage+39b (d944ff08, d2a41f98,) > d2c31d34 genunix:segvn_fault+8a4 (d944ff08, d2a41f98,) > d2c31dc4 genunix:as_fault+4ae (d944ff08, d2a42f08,) > d2c31e1c unix:pagefault+183 (8047ff4, 0, 2, 0) > d2c31eb4 unix:trap+1141 (d2c31ec8, 8047ff4, ) > d2c31ec8 unix:cmntrap+aa (d2c301b1, f4d10000,) > d2c31f20 unix:kcopy+25 (d94502b0, 8047ff4, ) > d2c31f6c genunix:exec_init+143 (f506c39c, f506c29c) > d2c31f88 genunix:start_init_common+c4 (0, d2c31fa4, f4c3f0) > d2c31f94 genunix:start_init+1c (0, 0) > d2c31fa4 unix:thread_start+8 () > > syncing file systems... done > skipping system dump - no dump device configured > rebooting... > > > P.S. This is the third time that I post this message: all other posts > were never delivered to the ML nor bounced back (although > I was already subscribed at the time). > > Thanks, > Nico > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org-- Mark Johnson <mark.johnson@sun.com> Sun Microsystems, Inc. (781) 442-0869
Il Friday 28 September 2007 15:48:32 hai scritto:> Nico Sabbi wrote: > > Hello, > > I''m trying to install Nevada66 as domU under Fedora 8 dom0 (64 > > bits) but the boot process fails. > > can you try a 64-bit domU install? >I forgot to say that I tried both the 32bits unix+miniroot and the 64bits one, always with the same result
Nico Sabbi wrote:> Il Friday 28 September 2007 15:48:32 hai scritto: >> Nico Sabbi wrote: >>> Hello, >>> I''m trying to install Nevada66 as domU under Fedora 8 dom0 (64 >>> bits) but the boot process fails. >> can you try a 64-bit domU install? >> > I forgot to say that I tried both the 32bits unix+miniroot and the > 64bits one, always with the same resultHmm, do you have access to the Xen console. There should be some error messages on there. MRJ -- Mark Johnson <mark.johnson@sun.com> Sun Microsystems, Inc. (781) 442-0869
> I''m trying to install Nevada66 as domU under Fedora 8 dom0 (64 bits) > but the boot process fails. > > My config file contains: > name = ''solaris'' > memory = ''1024'' > vcpus = 1 > disk = > [ ''file:/home/nico/solaris-inst.iso,6:cdrom,r'',''file:/home/nico/solaris.img,hda,w'' ]> vif = [ ''bridge=virbr0'' ] > on_shutdown = ''destroy'' > on_reboot = ''restart'' > on_crash = ''destroy'' > kernel = ''/usr/local/xen/unix-66-0624-nd'' > ramdisk = ''/usr/local/xen/x86.miniroot-66-0624-nd'' > extra = ''/platform/i86xpv/kernel/unix -B install_media=cdrom'' > #rootdisk = "/dev/dsk/c0d0s0" > extra = ''/platform/i86xpv/kernel/unix -B install_media=cdrom'' > > > but when I startup it I obtain: > > $ xm create -c solaris.conf > Using config file "/etc/xen/solaris.conf". > Started domain solaris > SunOS Release 5.11 Version xen-nv66-2007-06-24 32-bit > Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved. > Use is subject to license terms. > WARNING: Found xen v3.1.0-rc7-2942.fc8 but need xen v3.0.4-1-sun > WARNING: The kernel may not function correctlyHmm, I''m not sure if it is possible to mix a v3.1 hypervisor and a Solaris xVM domU kernel that needs v3.0.4. Doesn''t the Solaris xVM dom0 (and domU?) kernel use some hypervisor sysctl calls; which are failing because the Solaris kernel uses XEN_SYSCTL_INTERFACE_VERSION == 2, but xen v3.1 only implements XEN_SYSCTL_INTERFACE_VERSION == 3 ? Ok, maybe this is only a problem with a v3.1 hypervisor and a Solaris dom0 kernel...> panic[cpu0]/thread=d2a44e00: HYPERVISOR_mmu_update() failed > > d2c31ac0 unix:x86pte_cas+122 (d983a530, 0, 0, 0, ) > d2c31b00 unix:link_ptp+6d (d983a530, d983a4e0,) > d2c31b68 unix:htable_create+19d (d944ff08, 8047000, ) > d2c31ba0 unix:hati_load_common+78 (d944ff08, 8047000, ) > d2c31bd4 unix:hat_memload+5f (d944ff08, 8047000, ) > d2c31c44 genunix:segvn_faultpage+39b (d944ff08, d2a41f98,) > d2c31d34 genunix:segvn_fault+8a4 (d944ff08, d2a41f98,) > d2c31dc4 genunix:as_fault+4ae (d944ff08, d2a42f08,) > d2c31e1c unix:pagefault+183 (8047ff4, 0, 2, 0) > d2c31eb4 unix:trap+1141 (d2c31ec8, 8047ff4, ) > d2c31ec8 unix:cmntrap+aa (d2c301b1, f4d10000,) > d2c31f20 unix:kcopy+25 (d94502b0, 8047ff4, ) > d2c31f6c genunix:exec_init+143 (f506c39c, f506c29c) > d2c31f88 genunix:start_init_common+c4 (0, d2c31fa4, f4c3f0) > d2c31f94 genunix:start_init+1c (0, 0) > d2c31fa4 unix:thread_start+8 () > > syncing file systems... done > skipping system dump - no dump device configured > rebooting...Are there any error messages returned by "xm dmesg" ?
Il Friday 28 September 2007 16:16:49 Juergen Keil ha scritto:> > Hmm, I''m not sure if it is possible to mix a v3.1 hypervisor and > a Solaris xVM domU kernel that needs v3.0.4. > > Doesn''t the Solaris xVM dom0 (and domU?) kernel use some > hypervisor sysctl calls; which are failing because the Solaris > kernel uses XEN_SYSCTL_INTERFACE_VERSION == 2, but xen v3.1 only > implements XEN_SYSCTL_INTERFACE_VERSION == 3 ? > > > Ok, maybe this is only a problem with a v3.1 hypervisor and > a Solaris dom0 kernel... >:(> > Are there any error messages returned by "xm dmesg" ?I have the machines at home. tonight I''ll send the logs
Juergen Keil wrote:> >> I''m trying to install Nevada66 as domU under Fedora 8 dom0 (64 bits) >> but the boot process fails. >> >> My config file contains: >> name = ''solaris'' >> memory = ''1024'' >> vcpus = 1 >> disk = >> [ ''file:/home/nico/solaris-inst.iso,6:cdrom,r'', > ''file:/home/nico/solaris.img,hda,w'' ] >> vif = [ ''bridge=virbr0'' ] >> on_shutdown = ''destroy'' >> on_reboot = ''restart'' >> on_crash = ''destroy'' >> kernel = ''/usr/local/xen/unix-66-0624-nd'' >> ramdisk = ''/usr/local/xen/x86.miniroot-66-0624-nd'' >> extra = ''/platform/i86xpv/kernel/unix -B install_media=cdrom'' >> #rootdisk = "/dev/dsk/c0d0s0" >> extra = ''/platform/i86xpv/kernel/unix -B install_media=cdrom'' >> >> >> but when I startup it I obtain: >> >> $ xm create -c solaris.conf >> Using config file "/etc/xen/solaris.conf". >> Started domain solaris >> SunOS Release 5.11 Version xen-nv66-2007-06-24 32-bit >> Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved. >> Use is subject to license terms. >> WARNING: Found xen v3.1.0-rc7-2942.fc8 but need xen v3.0.4-1-sun >> WARNING: The kernel may not function correctly > > Hmm, I''m not sure if it is possible to mix a v3.1 hypervisor and > a Solaris xVM domU kernel that needs v3.0.4. > > Doesn''t the Solaris xVM dom0 (and domU?) kernel use some > hypervisor sysctl calls; which are failing because the Solaris > kernel uses XEN_SYSCTL_INTERFACE_VERSION == 2, but xen v3.1 only > implements XEN_SYSCTL_INTERFACE_VERSION == 3 ?The hypervisor & dom0 are supposed to support older domUs.> > Ok, maybe this is only a problem with a v3.1 hypervisor and > a Solaris dom0 kernel...I have a solaris domU running on a 32-bit Fedora7 dom0 which is based off of 3.1. But I agree, that this looks like a problem between solaris and the latest Xen bits... MRJ> >> panic[cpu0]/thread=d2a44e00: HYPERVISOR_mmu_update() failed >> >> d2c31ac0 unix:x86pte_cas+122 (d983a530, 0, 0, 0, ) >> d2c31b00 unix:link_ptp+6d (d983a530, d983a4e0,) >> d2c31b68 unix:htable_create+19d (d944ff08, 8047000, ) >> d2c31ba0 unix:hati_load_common+78 (d944ff08, 8047000, ) >> d2c31bd4 unix:hat_memload+5f (d944ff08, 8047000, ) >> d2c31c44 genunix:segvn_faultpage+39b (d944ff08, d2a41f98,) >> d2c31d34 genunix:segvn_fault+8a4 (d944ff08, d2a41f98,) >> d2c31dc4 genunix:as_fault+4ae (d944ff08, d2a42f08,) >> d2c31e1c unix:pagefault+183 (8047ff4, 0, 2, 0) >> d2c31eb4 unix:trap+1141 (d2c31ec8, 8047ff4, ) >> d2c31ec8 unix:cmntrap+aa (d2c301b1, f4d10000,) >> d2c31f20 unix:kcopy+25 (d94502b0, 8047ff4, ) >> d2c31f6c genunix:exec_init+143 (f506c39c, f506c29c) >> d2c31f88 genunix:start_init_common+c4 (0, d2c31fa4, f4c3f0) >> d2c31f94 genunix:start_init+1c (0, 0) >> d2c31fa4 unix:thread_start+8 () >> >> syncing file systems... done >> skipping system dump - no dump device configured >> rebooting... > > > Are there any error messages returned by "xm dmesg" ? > > > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org-- Mark Johnson <mark.johnson@sun.com> Sun Microsystems, Inc. (781) 442-0869
Mark Johnson wrote:> Juergen Keil wrote: > > > >> I''m trying to install Nevada66 as domU under Fedora 8 dom0 (64 bits) > >> but the boot process fails.> >> $ xm create -c solaris.conf > >> Using config file "/etc/xen/solaris.conf". > >> Started domain solaris > >> SunOS Release 5.11 Version xen-nv66-2007-06-24 32-bit > >> Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved. > >> Use is subject to license terms. > >> WARNING: Found xen v3.1.0-rc7-2942.fc8 but need xen v3.0.4-1-sun > >> WARNING: The kernel may not function correctly > > > > Hmm, I''m not sure if it is possible to mix a v3.1 hypervisor and > > a Solaris xVM domU kernel that needs v3.0.4. > > > > Doesn''t the Solaris xVM dom0 (and domU?) kernel use some > > hypervisor sysctl calls; which are failing because the Solaris > > kernel uses XEN_SYSCTL_INTERFACE_VERSION == 2, but xen v3.1 only > > implements XEN_SYSCTL_INTERFACE_VERSION == 3 ? > > The hypervisor & dom0 are supposed to support older domUs. > > > > > > Ok, maybe this is only a problem with a v3.1 hypervisor and > > a Solaris dom0 kernel... > > I have a solaris domU running on a 32-bit Fedora7 dom0 which > is based off of 3.1. But I agree, that this looks like a problem > between solaris and the latest Xen bits...I don''t remeber the exact details, but I was trying to boot an opensolaris snv_75 dom0 kernel under a v3.1 hypervisor that I compiled from sources, and (IIRC) I got a panic like this one ("physinfo op refused"): http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/i86pc/os/machdep.c#1091 1091 #if defined(__xpv) 1092 if (DOMAIN_IS_INITDOMAIN(xen_info)) { 1093 xen_sysctl_t op; 1094 1095 op.cmd = XEN_SYSCTL_physinfo; 1096 op.interface_version = XEN_SYSCTL_INTERFACE_VERSION; 1097 if (HYPERVISOR_sysctl(&op) != 0) 1098 panic("physinfo op refused"); 1099 1100 return ((pgcnt_t)op.u.physinfo.total_pages); 1101 } 1102 #endif /* __xpv */ Or maybe this one: http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/i86pc/os/mp_machdep.c#1014 1014 #if defined(__xpv) 1015 vcpu_time_info_t *vti = &CPU->cpu_m.mcpu_vcpu_info->time; 1016 uint64_t cpu_hz; 1017 1018 /* 1019 * During dom0 bringup, it was noted that on at least one older 1020 * Intel HT machine, the hypervisor initially gives a tsc_to_system_mul 1021 * value that is quite wrong (the 3.06GHz clock was reported 1022 * as 4.77GHz) 1023 * 1024 * The curious thing is, that if you stop the kernel at entry, 1025 * breakpoint here and inspect the value with kmdb, the value 1026 * is correct - but if you don''t stop and simply enable the 1027 * printf statement (below), you can see the bad value printed 1028 * here. Almost as if something kmdb did caused the hypervisor to 1029 * figure it out correctly. And, note that the hypervisor 1030 * eventually -does- figure it out correctly ... if you look at 1031 * the field later in the life of dom0, it is correct. 1032 * 1033 * For now, on dom0, we employ a slightly cheesy workaround of 1034 * using the DOM0_PHYSINFO hypercall. 1035 */ 1036 if (DOMAIN_IS_INITDOMAIN(xen_info) && xpv_cpufreq_workaround) { 1037 xen_sysctl_t op0, *op = &op0; 1038 1039 op->cmd = XEN_SYSCTL_physinfo; 1040 op->interface_version = XEN_SYSCTL_INTERFACE_VERSION; 1041 if (HYPERVISOR_sysctl(op) != 0) 1042 panic("physinfo op refused"); 1043 1044 cpu_hz = 1000 * (uint64_t)op->u.physinfo.cpu_khz; 1045 } else { Ok, so these HYPERVISOR_sysctl() calls are only used when running in a dom0, so Nico''s attempts to run a Solaris domU under a v3.1 hypervisor may not be affected by these Xen ABI changes ...
Juergen Keil wrote:> Mark Johnson wrote: > >> Juergen Keil wrote: >>>> I''m trying to install Nevada66 as domU under Fedora 8 dom0 (64 bits) >>>> but the boot process fails. > >>>> $ xm create -c solaris.conf >>>> Using config file "/etc/xen/solaris.conf". >>>> Started domain solaris >>>> SunOS Release 5.11 Version xen-nv66-2007-06-24 32-bit >>>> Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved. >>>> Use is subject to license terms. >>>> WARNING: Found xen v3.1.0-rc7-2942.fc8 but need xen v3.0.4-1-sun >>>> WARNING: The kernel may not function correctly >>> Hmm, I''m not sure if it is possible to mix a v3.1 hypervisor and >>> a Solaris xVM domU kernel that needs v3.0.4. >>> >>> Doesn''t the Solaris xVM dom0 (and domU?) kernel use some >>> hypervisor sysctl calls; which are failing because the Solaris >>> kernel uses XEN_SYSCTL_INTERFACE_VERSION == 2, but xen v3.1 only >>> implements XEN_SYSCTL_INTERFACE_VERSION == 3 ? >> The hypervisor & dom0 are supposed to support older domUs. >> >> >>> Ok, maybe this is only a problem with a v3.1 hypervisor and >>> a Solaris dom0 kernel... >> I have a solaris domU running on a 32-bit Fedora7 dom0 which >> is based off of 3.1. But I agree, that this looks like a problem >> between solaris and the latest Xen bits... > > > I don''t remeber the exact details, but I was trying to boot > an opensolaris snv_75 dom0 kernel under a v3.1 hypervisor that I > compiled from sources, and (IIRC) I got a panic like this one > ("physinfo op refused"):I just updated both my fedora7 dom0 and solaris domU to the latest bits.. Still boots fine on my system. This is 3.1 based, but not the latest and greatest Xen code. [root@fedora ~]# virsh start solaris virsh Domain solaris started [root@fedora ~]# virsh console solaris Loading kmdb... SunOS Release 5.11 Version matrix-devel-build 32-bit Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. WARNING: Found xen v3.1.0-rc7-2934.fc7 but need xen v3.0.4-1-xvm WARNING: The kernel may not function correctly Hostname: unknown Reading ZFS config: done. unknown console login:> http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/i86pc/os/machdep.c#1091 > > 1091 #if defined(__xpv) > 1092 if (DOMAIN_IS_INITDOMAIN(xen_info)) { > 1093 xen_sysctl_t op; > 1094 > 1095 op.cmd = XEN_SYSCTL_physinfo; > 1096 op.interface_version = XEN_SYSCTL_INTERFACE_VERSION; > 1097 if (HYPERVISOR_sysctl(&op) != 0) > 1098 panic("physinfo op refused"); > 1099 > 1100 return ((pgcnt_t)op.u.physinfo.total_pages); > 1101 } > 1102 #endif /* __xpv */ > > > Or maybe this one: > > http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/i86pc/os/mp_machdep.c#1014 > > 1014 #if defined(__xpv) > 1015 vcpu_time_info_t *vti = &CPU->cpu_m.mcpu_vcpu_info->time; > 1016 uint64_t cpu_hz; > 1017 > 1018 /* > 1019 * During dom0 bringup, it was noted that on at least one older > 1020 * Intel HT machine, the hypervisor initially gives a tsc_to_system_mul > 1021 * value that is quite wrong (the 3.06GHz clock was reported > 1022 * as 4.77GHz) > 1023 * > 1024 * The curious thing is, that if you stop the kernel at entry, > 1025 * breakpoint here and inspect the value with kmdb, the value > 1026 * is correct - but if you don''t stop and simply enable the > 1027 * printf statement (below), you can see the bad value printed > 1028 * here. Almost as if something kmdb did caused the hypervisor to > 1029 * figure it out correctly. And, note that the hypervisor > 1030 * eventually -does- figure it out correctly ... if you look at > 1031 * the field later in the life of dom0, it is correct. > 1032 * > 1033 * For now, on dom0, we employ a slightly cheesy workaround of > 1034 * using the DOM0_PHYSINFO hypercall. > 1035 */ > 1036 if (DOMAIN_IS_INITDOMAIN(xen_info) && xpv_cpufreq_workaround) { > 1037 xen_sysctl_t op0, *op = &op0; > 1038 > 1039 op->cmd = XEN_SYSCTL_physinfo; > 1040 op->interface_version = XEN_SYSCTL_INTERFACE_VERSION; > 1041 if (HYPERVISOR_sysctl(op) != 0) > 1042 panic("physinfo op refused"); > 1043 > 1044 cpu_hz = 1000 * (uint64_t)op->u.physinfo.cpu_khz; > 1045 } else { > > > > Ok, so these HYPERVISOR_sysctl() calls are only used when > running in a dom0, so Nico''s attempts to run a Solaris domU > under a v3.1 hypervisor may not be affected by these Xen ABI > changes ...I''m still worried that the latest Xen bits break Solaris domU. It wouldn''t be the first time.. MRJ -- Mark Johnson <mark.johnson@sun.com> Sun Microsystems, Inc. (781) 442-0869
Il Friday 28 September 2007 17:43:37 Mark Johnson ha scritto:> I just updated both my fedora7 dom0 and solaris domU to the > latest bits.. Still boots fine on my system. This is 3.1 > based, but not the latest and greatest Xen code. >doesn''t fedora 7 use xen 3.0? P.S. this list lacks a reply-to header, thus replies go off-list by default: very annoying. It would be nice to have that header set
Nico Sabbi wrote:> Il Friday 28 September 2007 17:43:37 Mark Johnson ha scritto: > >> I just updated both my fedora7 dom0 and solaris domU to the >> latest bits.. Still boots fine on my system. This is 3.1 >> based, but not the latest and greatest Xen code. >> > > doesn''t fedora 7 use xen 3.0?No, fedora 6 did... The version is set to v3.1.0-rc7-2934.fc7 MRJ> P.S. this list lacks a reply-to header, thus replies go off-list by > default: very annoying. > It would be nice to have that header set > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org-- Mark Johnson <mark.johnson@sun.com> Sun Microsystems, Inc. (781) 442-0869
premise: hand-edited :)>> Are there any error messages returned by "xm dmesg" ? > >I have the machines at home. tonight I''ll send the logs$ xm dmesg -c (XEN) mm.c:681:d7 Bad L3 flags 6 (XEN) mm.c:681:d8 Bad L3 flags 6 $ xen log [2007-09-29 01:33:51 2467] DEBUG (XendDomainInfo:78) XendDomainInfo.create([\047vm\047, [\047name\047, \047solaris\047], [\047memory\047, \0471024\047], [\047on_reboot\047, \047restart\047], [\047on_crash\047, \047destroy\047], [\047vcpus\047, 1], [\047on_xend_start\047, \047ignore\047], [\047on_xend_stop\047, \047ignore\047], [\047image\047, [\047linux\047, [\047kernel\047, \047/usr/local/xen/unix-66-0624-nd\047], [\047ramdisk\047, \047/usr/local/xen/x86.miniroot-66-0624-nd\047], [\047args\047, \047/platform/i86xpv/kernel/unix -B install_media=cdrom\047]]], [\047device\047, [\047vbd\047, [\047uname\047, \047file:/home/nico/solaris-inst.iso\047], [\047dev\047, \0476:cdrom\047], [\047mode\047, \047r\047]]], [\047device\047, [\047vbd\047, [\047uname\047, \047file:/home/nico/solaris.img\047], [\047dev\047, \047hda\047], [\047mode\047, \047w\047]]], [\047device\047, [\047vif\047, [\047bridge\047, \047virbr0\047]]]]) [2007-09-29 01:33:51 2467] DEBUG (XendDomainInfo:1465) XendDomainInfo.constructDomain [2007-09-29 01:33:51 2467] DEBUG (balloon:113) Balloon: 1049216 KiB free; need 2048; done. [2007-09-29 01:33:51 2467] DEBUG (XendDomain:443) Adding Domain: 9 [2007-09-29 01:33:51 2467] DEBUG (XendDomainInfo:1519) XendDomainInfo.initDomain: 9 256 [2007-09-29 01:33:51 2467] DEBUG (XendDomainInfo:1551) _initDomain:shadow_memory=0x0, memory_static_max=0x40000000, memory_static_min=0x0. [2007-09-29 01:33:51 2467] DEBUG (balloon:113) Balloon: 1049208 KiB free; need 1048576; done. [2007-09-29 01:33:51 2467] INFO (image:130) buildDomain os=linux dom=9 vcpus=1 [2007-09-29 01:33:51 2467] DEBUG (image:199) domid = 9 [2007-09-29 01:33:51 2467] DEBUG (image:200) memsize = 1024 [2007-09-29 01:33:51 2467] DEBUG (image:201) image = /usr/local/xen/unix-66-0624-nd [2007-09-29 01:33:51 2467] DEBUG (image:202) store_evtchn = 1 [2007-09-29 01:33:51 2467] DEBUG (image:203) console_evtchn = 2 [2007-09-29 01:33:51 2467] DEBUG (image:204) cmdline = /platform/i86xpv/kernel/unix -B install_media=cdrom [2007-09-29 01:33:51 2467] DEBUG (image:205) ramdisk = /usr/local/xen/x86.miniroot-66-0624-nd [2007-09-29 01:33:51 2467] DEBUG (image:206) vcpus = 1 [2007-09-29 01:33:51 2467] DEBUG (image:207) features [2007-09-29 01:33:53 2467] INFO (XendDomainInfo:1367) createDevice: vbd : {\047uuid\047: \0471c2d29e0-c9f2-02dd-bfe1-ce4d5f52069e\047, \047bootable\047: 1, \047driver\047: \047paravirtualised\047, \047dev\047: \0476:cdrom\047, \047uname\047: \047file:/home/nico/solaris-inst.iso\047, \047mode\047: \047r\047} [2007-09-29 01:33:53 2467] DEBUG (DevController:115) DevController: writing {\047virtual-device\047: \0476\047, \047device-type\047: \047cdrom\047, \047protocol\047: \047x86_32-abi\047, \047backend-id\047: \0470\047, \047state\047: \0471\047, \047backend\047: \047/local/domain/0/backend/vbd/9/6\047} to /local/domain/9/device/vbd/6. [2007-09-29 01:33:53 2467] DEBUG (DevController:117) DevController: writing {\047domain\047: \047solaris\047, \047frontend\047: \047/local/domain/9/device/vbd/6\047, \047uuid\047: \0471c2d29e0-c9f2-02dd-bfe1-ce4d5f52069e\047, \047dev\047: \0476\047, \047state\047: \0471\047, \047params\047: \047/home/nico/solaris-inst.iso\047, \047mode\047: \047r\047, \047online\047: \0471\047, \047frontend-id\047: \0479\047, \047type\047: \047file\047} to /local/domain/0/backend/vbd/9/6. [2007-09-29 01:33:53 2467] INFO (XendDomainInfo:1367) createDevice: vbd : {\047uuid\047: \0476778a01f-d73b-08d4-6e31-28cc68893231\047, \047bootable\047: 0, \047driver\047: \047paravirtualised\047, \047dev\047: \047hda\047, \047uname\047: \047file:/home/nico/solaris.img\047, \047mode\047: \047w\047} [2007-09-29 01:33:53 2467] DEBUG (DevController:115) DevController: writing {\047virtual-device\047: \047768\047, \047device-type\047: \047disk\047, \047protocol\047: \047x86_32-abi\047, \047backend-id\047: \0470\047, \047state\047: \0471\047, \047backend\047: \047/local/domain/0/backend/vbd/9/768\047} to /local/domain/9/device/vbd/768. [2007-09-29 01:33:53 2467] DEBUG (DevController:117) DevController: writing {\047domain\047: \047solaris\047, \047frontend\047: \047/local/domain/9/device/vbd/768\047, \047uuid\047: \0476778a01f-d73b-08d4-6e31-28cc68893231\047, \047dev\047: \047hda\047, \047state\047: \0471\047, \047params\047: \047/home/nico/solaris.img\047, \047mode\047: \047w\047, \047online\047: \0471\047, \047frontend-id\047: \0479\047, \047type\047: \047file\047} to /local/domain/0/backend/vbd/9/768. [2007-09-29 01:33:53 2467] INFO (XendDomainInfo:1367) createDevice: vif : {\047bridge\047: \047virbr0\047, \047uuid\047: \047ba0e75f5-be2b-4525-8f19-ab19b0e7b037\047} [2007-09-29 01:33:53 2467] DEBUG (DevController:115) DevController: writing {\047mac\047: \04700:16:3e:0a:18:bb\047, \047handle\047: \0470\047, \047protocol\047: \047x86_32-abi\047, \047backend-id\047: \0470\047, \047state\047: \0471\047, \047backend\047: \047/local/domain/0/backend/vif/9/0\047} to /local/domain/9/device/vif/0. [2007-09-29 01:33:53 2467] DEBUG (DevController:117) DevController: writing {\047bridge\047: \047virbr0\047, \047domain\047: \047solaris\047, \047handle\047: \0470\047, \047uuid\047: \047ba0e75f5-be2b-4525-8f19-ab19b0e7b037\047, \047script\047: \047/etc/xen/scripts/vif-bridge\047, \047state\047: \0471\047, \047frontend\047: \047/local/domain/9/device/vif/0\047, \047mac\047: \04700:16:3e:0a:18:bb\047, \047online\047: \0471\047, \047frontend-id\047: \0479\047} to /local/domain/0/backend/vif/9/0. [2007-09-29 01:33:53 2467] DEBUG (XendDomainInfo:2026) Storing VM details: {\047on_xend_stop\047: \047ignore\047, \047shadow_memory\047: \0470\047, \047uuid\047: \047af506412-c7f8-c81f-0a45-f348b9f00dff\047, \047on_reboot\047: \047restart\047, \047start_time\047: \0471191022433.58\047, \047on_poweroff\047: \047destroy\047, \047on_xend_start\047: \047ignore\047, \047on_crash\047: \047destroy\047, \047xend/restart_count\047: \0470\047, \047vcpus\047: \0471\047, \047vcpu_avail\047: \0471\047, \047image\047: "(linux (kernel /usr/local/xen/unix-66-0624-nd) (ramdisk /usr/local/xen/x86.miniroot-66-0624-nd) (args \047/platform/i86xpv/kernel/unix -B install_media=cdrom\047) (notes (VIRT_BASE 1073741824) (PADDR_OFFSET 1073741824) (GUEST_OS Solaris) (LOADER generic) (PAE_MODE \047yes,bimodal\047) (XEN_VERSION xen-3.0)))", \047name\047: \047solaris\047} [2007-09-29 01:33:53 2467] DEBUG (XendDomainInfo:875) Storing domain details: {\047console/ring-ref\047: \047316952\047, \047image/pae-mode\047: \047yes,bimodal\047, \047console/port\047: \0472\047, \047name\047: \047solaris\047, \047console/limit\047: \0471048576\047, \047image/paddr-offset\047: \0471073741824\047, \047image/virt-base\047: \0471073741824\047, \047image/guest-os\047: \047Solaris\047, \047vm\047: \047/vm/af506412-c7f8-c81f-0a45-f348b9f00dff\047, \047domid\047: \0479\047, \047store/port\047: \0471\047, \047image/xen-version\047: \047xen-3.0\047, \047memory/target\047: \0471048576\047, \047control/platform-feature-multiprocessor-suspend\047: \0471\047, \047image/loader\047: \047generic\047, \047store/ring-ref\047: \047316953\047, \047cpu/0/availability\047: \047online\047} [2007-09-29 01:33:53 2467] DEBUG (XendDomainInfo:875) Storing domain details: {\047console/ring-ref\047: \047316952\047, \047image/pae-mode\047: \047yes,bimodal\047, \047name\047: \047solaris\047, \047console/limit\047: \0471048576\047, \047image/paddr-offset\047: \0471073741824\047, \047image/virt-base\047: \0471073741824\047, \047image/guest-os\047: \047Solaris\047, \047vm\047: \047/vm/af506412-c7f8-c81f-0a45-f348b9f00dff\047, \047domid\047: \0479\047, \047store/port\047: \0471\047, \047image/xen-version\047: \047xen-3.0\047, \047memory/target\047: \0471048576\047, \047control/platform-feature-multiprocessor-suspend\047: \0471\047, \047image/loader\047: \047generic\047, \047store/ring-ref\047: \047316953\047, \047cpu/0/availability\047: \047online\047} [2007-09-29 01:33:53 2467] DEBUG (XendDomainInfo:959) XendDomainInfo.handleShutdownWatch [2007-09-29 01:33:53 2467] DEBUG (DevController:148) Waiting for devices vif. [2007-09-29 01:33:53 2467] DEBUG (DevController:153) Waiting for 0. [2007-09-29 01:33:53 2467] DEBUG (DevController:558) hotplugStatusCallback /local/domain/0/backend/vif/9/0/hotplug-status. [2007-09-29 01:33:53 2467] DEBUG (DevController:558) hotplugStatusCallback /local/domain/0/backend/vif/9/0/hotplug-status. [2007-09-29 01:33:53 2467] DEBUG (DevController:572) hotplugStatusCallback 1. [2007-09-29 01:33:53 2467] DEBUG (DevController:148) Waiting for devices usb. [2007-09-29 01:33:53 2467] DEBUG (DevController:148) Waiting for devices vbd. [2007-09-29 01:33:53 2467] DEBUG (DevController:153) Waiting for 6. [2007-09-29 01:33:53 2467] DEBUG (DevController:558) hotplugStatusCallback /local/domain/0/backend/vbd/9/6/hotplug-status. [2007-09-29 01:33:53 2467] DEBUG (DevController:572) hotplugStatusCallback 1. [2007-09-29 01:33:53 2467] DEBUG (DevController:153) Waiting for 768. [2007-09-29 01:33:53 2467] DEBUG (DevController:558) hotplugStatusCallback /local/domain/0/backend/vbd/9/768/hotplug-status. [2007-09-29 01:33:53 2467] DEBUG (DevController:558) hotplugStatusCallback /local/domain/0/backend/vbd/9/768/hotplug-status. [2007-09-29 01:33:53 2467] DEBUG (DevController:572) hotplugStatusCallback 1. [2007-09-29 01:33:53 2467] DEBUG (DevController:148) Waiting for devices irq. [2007-09-29 01:33:53 2467] DEBUG (DevController:148) Waiting for devices vkbd. [2007-09-29 01:33:53 2467] DEBUG (DevController:148) Waiting for devices vfb. [2007-09-29 01:33:53 2467] DEBUG (DevController:148) Waiting for devices console. [2007-09-29 01:33:53 2467] DEBUG (DevController:148) Waiting for devices pci. [2007-09-29 01:33:53 2467] DEBUG (DevController:148) Waiting for devices ioports. [2007-09-29 01:33:53 2467] DEBUG (DevController:148) Waiting for devices tap. [2007-09-29 01:33:53 2467] DEBUG (DevController:148) Waiting for devices vtpm. [2007-09-29 01:33:53 2467] INFO (XendDomain:1123) Domain solaris (9) unpaused. [2007-09-29 01:33:55 2467] INFO (XendDomainInfo:1141) Domain has shutdown: name=solaris id=9 reason=reboot. [2007-09-29 01:33:55 2467] DEBUG (XendDomainInfo:875) Storing domain details: {\047console/ring-ref\047: \047316952\047, \047image/pae-mode\047: \047yes,bimodal\047, \047name\047: \047solaris\047, \047console/limit\047: \0471048576\047, \047image/paddr-offset\047: \0471073741824\047, \047image/virt-base\047: \0471073741824\047, \047image/guest-os\047: \047Solaris\047, \047vm\047: \047/vm/af506412-c7f8-c81f-0a45-f348b9f00dff\047, \047domid\047: \0479\047, \047store/port\047: \0471\047, \047image/xen-version\047: \047xen-3.0\047, \047memory/target\047: \0471048576\047, \047control/platform-feature-multiprocessor-suspend\047: \0471\047, \047image/loader\047: \047generic\047, \047store/ring-ref\047: \047316953\047, \047cpu/0/availability\047: \047online\047} [2007-09-29 01:33:55 2467] DEBUG (XendDomainInfo:1730) XendDomainInfo.destroyDomain(9) [2007-09-29 01:33:55 2467] DEBUG (XendDomainInfo:100) XendDomainInfo.create_from_dict({\047vcpus_params\047: {}, \047PV_args\047: \047/platform/i86xpv/kernel/unix -B install_media=cdrom\047, \047features\047: \047\047, \047cpus\047: [], \047paused\047: 0, \047domid\047: 9, \047shutdown\047: 0, \047VCPUs_live\047: 1, \047PV_bootloader\047: \047\047, \047actions_after_crash\047: \047destroy\047, \047vbd_refs\047: [\0471c2d29e0-c9f2-02dd-bfe1-ce4d5f52069e\047, \0476778a01f-d73b-08d4-6e31-28cc68893231\047], \047PV_ramdisk\047: \047/usr/local/xen/x86.miniroot-66-0624-nd\047, \047is_control_domain\047: False, \047name_label\047: \047solaris\047, \047VCPUs_at_startup\047: 1, \047HVM_boot_params\047: {}, \047platform\047: {\047rtc_timeoffset\047: \0470\047}, \047cpu_weight\047: 256, \047console_refs\047: [], \047online_vcpus\047: 1, \047cpu_cap\047: 0, \047blocked\047: 0, \047on_xend_stop\047: \047ignore\047, \047memory_static_min\047: 0, \047HVM_boot_policy\047: \047\047, \047shutdown_reason\047: 1, \047VCPUs_max\047: 1, \047start_time\047: 1191022433.580929, \047memory_static_max\047: 1073741824, \047actions_after_shutdown\047: \047destroy\047, \047on_xend_start\047: \047ignore\047, \047crashed\047: 0, \047memory_dynamic_max\047: 1073741824, \047actions_after_suspend\047: \047\047, \047is_a_template\047: False, \047PV_bootloader_args\047: \047\047, \047memory_dynamic_min\047: 1073741824, \047uuid\047: \047af506412-c7f8-c81f-0a45-f348b9f00dff\047, \047PV_kernel\047: \047/usr/local/xen/unix-66-0624-nd\047, \047cpu_time\047: 1.717119286, \047shadow_memory\047: 0, \047dying\047: 0, \047vcpu_avail\047: 1, \047notes\047: {\047VIRT_BASE\047: \0471073741824\047, \047PADDR_OFFSET\047: \0471073741824\047, \047GUEST_OS\047: \047Solaris\047, \047LOADER\047: \047generic\047, \047PAE_MODE\047: \047yes,bimodal\047, \047XEN_VERSION\047: \047xen-3.0\047}, \047other_config\047: {}, \047running\047: 0, \047actions_after_reboot\047: \047restart\047, \047vif_refs\047: [\047ba0e75f5-be2b-4525-8f19-ab19b0e7b037\047], \047vtpm_refs\047: [], \047security\047: None, \047devices\047: {\0471c2d29e0-c9f2-02dd-bfe1-ce4d5f52069e\047: (\047vbd\047, {\047uuid\047: \0471c2d29e0-c9f2-02dd-bfe1-ce4d5f52069e\047, \047bootable\047: 1, \047devid\047: 6, \047driver\047: \047paravirtualised\047, \047dev\047: \0476:cdrom\047, \047uname\047: \047file:/home/nico/solaris-inst.iso\047, \047mode\047: \047r\047}), \0476778a01f-d73b-08d4-6e31-28cc68893231\047: (\047vbd\047, {\047uuid\047: \0476778a01f-d73b-08d4-6e31-28cc68893231\047, \047bootable\047: 0, \047devid\047: 768, \047driver\047: \047paravirtualised\047, \047dev\047: \047hda\047, \047uname\047: \047file:/home/nico/solaris.img\047, \047mode\047: \047w\047}), \047ba0e75f5-be2b-4525-8f19-ab19b0e7b037\047: (\047vif\047, {\047bridge\047: \047virbr0\047, \047devid\047: 0, \047uuid\047: \047ba0e75f5-be2b-4525-8f19-ab19b0e7b037\047})}}) [2007-09-29 01:33:55 2467] DEBUG (XendDomainInfo:1465) XendDomainInfo.constructDomain [2007-09-29 01:33:55 2467] DEBUG (balloon:113) Balloon: 308884 KiB free; need 2048; done. [2007-09-29 01:33:55 2467] DEBUG (XendDomain:443) Adding Domain: 10 [2007-09-29 01:33:55 2467] DEBUG (XendDomainInfo:1519) XendDomainInfo.initDomain: 10 256 [2007-09-29 01:33:55 2467] DEBUG (XendDomainInfo:1551) _initDomain:shadow_memory=0x0, memory_static_max=0x40000000, memory_static_min=0x0. [2007-09-29 01:33:55 2467] DEBUG (balloon:119) Balloon: 326012 KiB free; 723196 to scrub; need 1048576; retries: 20. [2007-09-29 01:33:55 2467] DEBUG (balloon:127) Balloon: waiting on scrubbing [2007-09-29 01:33:56 2467] DEBUG (balloon:113) Balloon: 1049208 KiB free; need 1048576; done. [2007-09-29 01:33:56 2467] INFO (image:130) buildDomain os=linux dom=10 vcpus=1 [2007-09-29 01:33:56 2467] DEBUG (image:199) domid = 10 [2007-09-29 01:33:56 2467] DEBUG (image:200) memsize = 1024 [2007-09-29 01:33:56 2467] DEBUG (image:201) image = /usr/local/xen/unix-66-0624-nd [2007-09-29 01:33:56 2467] DEBUG (image:202) store_evtchn = 1 [2007-09-29 01:33:56 2467] DEBUG (image:203) console_evtchn = 2 [2007-09-29 01:33:56 2467] DEBUG (image:204) cmdline = /platform/i86xpv/kernel/unix -B install_media=cdrom [2007-09-29 01:33:56 2467] DEBUG (image:205) ramdisk = /usr/local/xen/x86.miniroot-66-0624-nd [2007-09-29 01:33:56 2467] DEBUG (image:206) vcpus = 1 [2007-09-29 01:33:56 2467] DEBUG (image:207) features [2007-09-29 01:33:58 2467] INFO (XendDomainInfo:1367) createDevice: vbd : {\047uuid\047: \0471c2d29e0-c9f2-02dd-bfe1-ce4d5f52069e\047, \047bootable\047: 1, \047devid\047: 6, \047driver\047: \047paravirtualised\047, \047dev\047: \0476:cdrom\047, \047uname\047: \047file:/home/nico/solaris-inst.iso\047, \047mode\047: \047r\047} [2007-09-29 01:33:58 2467] DEBUG (DevController:115) DevController: writing {\047virtual-device\047: \0476\047, \047device-type\047: \047cdrom\047, \047protocol\047: \047x86_32-abi\047, \047backend-id\047: \0470\047, \047state\047: \0471\047, \047backend\047: \047/local/domain/0/backend/vbd/10/6\047} to /local/domain/10/device/vbd/6. [2007-09-29 01:33:58 2467] DEBUG (DevController:117) DevController: writing {\047domain\047: \047solaris\047, \047frontend\047: \047/local/domain/10/device/vbd/6\047, \047uuid\047: \0471c2d29e0-c9f2-02dd-bfe1-ce4d5f52069e\047, \047dev\047: \0476\047, \047state\047: \0471\047, \047params\047: \047/home/nico/solaris-inst.iso\047, \047mode\047: \047r\047, \047online\047: \0471\047, \047frontend-id\047: \04710\047, \047type\047: \047file\047} to /local/domain/0/backend/vbd/10/6. [2007-09-29 01:33:58 2467] INFO (XendDomainInfo:1367) createDevice: vbd : {\047uuid\047: \0476778a01f-d73b-08d4-6e31-28cc68893231\047, \047bootable\047: 0, \047devid\047: 768, \047driver\047: \047paravirtualised\047, \047dev\047: \047hda\047, \047uname\047: \047file:/home/nico/solaris.img\047, \047mode\047: \047w\047} [2007-09-29 01:33:58 2467] DEBUG (DevController:115) DevController: writing {\047virtual-device\047: \047768\047, \047device-type\047: \047disk\047, \047protocol\047: \047x86_32-abi\047, \047backend-id\047: \0470\047, \047state\047: \0471\047, \047backend\047: \047/local/domain/0/backend/vbd/10/768\047} to /local/domain/10/device/vbd/768. [2007-09-29 01:33:58 2467] DEBUG (DevController:117) DevController: writing {\047domain\047: \047solaris\047, \047frontend\047: \047/local/domain/10/device/vbd/768\047, \047uuid\047: \0476778a01f-d73b-08d4-6e31-28cc68893231\047, \047dev\047: \047hda\047, \047state\047: \0471\047, \047params\047: \047/home/nico/solaris.img\047, \047mode\047: \047w\047, \047online\047: \0471\047, \047frontend-id\047: \04710\047, \047type\047: \047file\047} to /local/domain/0/backend/vbd/10/768. [2007-09-29 01:33:58 2467] INFO (XendDomainInfo:1367) createDevice: vif : {\047bridge\047: \047virbr0\047, \047devid\047: 0, \047uuid\047: \047ba0e75f5-be2b-4525-8f19-ab19b0e7b037\047} [2007-09-29 01:33:58 2467] DEBUG (DevController:115) DevController: writing {\047mac\047: \04700:16:3e:2f:92:b3\047, \047handle\047: \0470\047, \047protocol\047: \047x86_32-abi\047, \047backend-id\047: \0470\047, \047state\047: \0471\047, \047backend\047: \047/local/domain/0/backend/vif/10/0\047} to /local/domain/10/device/vif/0. [2007-09-29 01:33:58 2467] DEBUG (DevController:117) DevController: writing {\047bridge\047: \047virbr0\047, \047domain\047: \047solaris\047, \047handle\047: \0470\047, \047uuid\047: \047ba0e75f5-be2b-4525-8f19-ab19b0e7b037\047, \047script\047: \047/etc/xen/scripts/vif-bridge\047, \047state\047: \0471\047, \047frontend\047: \047/local/domain/10/device/vif/0\047, \047mac\047: \04700:16:3e:2f:92:b3\047, \047online\047: \0471\047, \047frontend-id\047: \04710\047} to /local/domain/0/backend/vif/10/0. [2007-09-29 01:33:58 2467] DEBUG (XendDomainInfo:2026) Storing VM details: {\047on_xend_stop\047: \047ignore\047, \047shadow_memory\047: \0470\047, \047uuid\047: \047af506412-c7f8-c81f-0a45-f348b9f00dff\047, \047on_reboot\047: \047restart\047, \047start_time\047: \0471191022438.19\047, \047on_poweroff\047: \047destroy\047, \047on_xend_start\047: \047ignore\047, \047on_crash\047: \047destroy\047, \047vcpus\047: \0471\047, \047vcpu_avail\047: \0471\047, \047image\047: "(linux (kernel /usr/local/xen/unix-66-0624-nd) (ramdisk /usr/local/xen/x86.miniroot-66-0624-nd) (args \047/platform/i86xpv/kernel/unix -B install_media=cdrom\047) (rtc_timeoffset 0) (notes (VIRT_BASE 1073741824) (PADDR_OFFSET 1073741824) (GUEST_OS Solaris) (LOADER generic) (PAE_MODE \047yes,bimodal\047) (XEN_VERSION xen-3.0)))", \047name\047: \047solaris\047} [2007-09-29 01:33:58 2467] DEBUG (XendDomainInfo:875) Storing domain details: {\047console/ring-ref\047: \047488868\047, \047image/pae-mode\047: \047yes,bimodal\047, \047console/port\047: \0472\047, \047name\047: \047solaris\047, \047console/limit\047: \0471048576\047, \047image/paddr-offset\047: \0471073741824\047, \047image/virt-base\047: \0471073741824\047, \047image/guest-os\047: \047Solaris\047, \047vm\047: \047/vm/af506412-c7f8-c81f-0a45-f348b9f00dff\047, \047domid\047: \04710\047, \047store/port\047: \0471\047, \047image/xen-version\047: \047xen-3.0\047, \047memory/target\047: \0471048576\047, \047control/platform-feature-multiprocessor-suspend\047: \0471\047, \047image/loader\047: \047generic\047, \047store/ring-ref\047: \047488869\047, \047cpu/0/availability\047: \047online\047} [2007-09-29 01:33:58 2467] DEBUG (XendDomainInfo:959) XendDomainInfo.handleShutdownWatch [2007-09-29 01:33:59 2467] INFO (XendDomainInfo:1141) Domain has shutdown: name=solaris id=10 reason=reboot. [2007-09-29 01:33:59 2467] ERROR (XendDomainInfo:1246) VM solaris restarting too fast (4.377662 seconds since the last restart). Refusing to restart to avoid loops. [2007-09-29 01:33:59 2467] DEBUG (XendDomainInfo:1713) XendDomainInfo.destroy: domid=10 [2007-09-29 01:33:59 2467] DEBUG (XendDomainInfo:1730) XendDomainInfo.destroyDomain(10)
> premise: hand-edited :) > > >> Are there any error messages returned by "xm dmesg" ? > > > >I have the machines at home. tonight I''ll send the logs > > $ xm dmesg -c > (XEN) mm.c:681:d7 Bad L3 flags 6 > (XEN) mm.c:681:d8 Bad L3 flags 6It seems the only way "Bad L3 flags 6" can be reported by xen-3.1 is when the xen hypervisor is compiled with "CONFIG_COMPAT" and the condition "is_pv_32on64_domain(d)" is true. That is, it occurs only when running a 32-bit PV (non-HVM) guest on a 64-bit xen hypervisor (and 64-bit dom0)? Mark already suggested to try a 64-bit domU install. I''m not sure if that''s possible at all, given that the Solaris x86 installation optical media only contains the 32-bit environment (but the SunOS on the installed HDD would include both 32-bit and 64-bit environments). Maybe you could try it the other way: boot a 32-bit xen 3.1 Linux dom0, and try to install Nevada build66 as 32-bit domU ? This message posted from opensolaris.org
Il Friday 28 September 2007 15:54:52 Mark Johnson ha scritto:> Nico Sabbi wrote: > > Il Friday 28 September 2007 15:48:32 hai scritto: > >> Nico Sabbi wrote: > >>> Hello, > >>> I''m trying to install Nevada66 as domU under Fedora 8 dom0 (64 > >>> bits) but the boot process fails. > >> > >> can you try a 64-bit domU install? > > > > I forgot to say that I tried both the 32bits unix+miniroot and > > the 64bits one, always with the same result > > Hmm, do you have access to the Xen console. There > should be some error messages on there. > > > > MRJnot needed: I mounted and used the 64bit version from the boot/ directory in the install cd. After having fixed extra = ''/platform/i86xpv/kernel/unix -B install_media=cdrom'' to extra = ''/platform/i86xpv/kernel/amd64/unix -B install_media=cdrom'' there were no more errors and the setup started correctly. The final file is (at least for the moment): [root@nico2 ~]# cat /etc/xen/solaris.conf name = ''solaris'' memory = ''512'' vcpus = 1 disk = [ ''file:/home/nico/solaris-inst.iso,6:cdrom,r'', ''file:/home/nico/solaris.img,hda,w'' ] vif = [ ''bridge=virbr0'' ] on_shutdown = ''destroy'' on_reboot = ''restart'' on_crash = ''destroy'' kernel = ''/home/nico/Solaris/unix'' ramdisk = ''/home/nico/Solaris/x86.miniroot'' extra = ''/platform/i86xpv/kernel/amd64/unix -B install_media=cdrom''
I was able to start Solaris DomU (64 bit) install on top F7 Dom0 (64 bit) Xen 3.1 has been installed allong with F7 from distribution CD, but got problems later , trying to reproduce:- http://bderzhavets.blogspot.com/2007/09/install-solaris-domu-64-bit-under-xen-3.html Xen 3.1 (64 bit) Binary install had been done previously under CentOS 5 and Debian Etch (x86_64). However, in case of F7 installed along with it''s own Xen I was unable to "scp" /a/platform/i86pc/amd64/boot_archive to F7 Dom0 Next fresh F7 install : after packages installation phase I again dropped to shell and tried just to ping F7 dom0 (192.168.122.25 assigned by me) and virbr0 (192.168.122.1 assigned by system). No respond. It worked fine for both CentOS 5 & Debian Etch Dom0 on top of original Xen 3.1 (64 bit) (2.6.18 linux based kernel). I don''t know how important is match between Linux kernels 2.6.18 (CentOS 5 & Debian Etch 4.0) and Xen''s kernel version for successfull Solaris DomU (64) installation. I also compared Xen 3.1 on CentOS 5 and F7''s( built in) network reports. On F7:- 1. ifconfig shows virbr0 as active 192.168.122.1 on F7 dom0 immediately after F7 install 2."brctl show" doesn''t show any interfaces connected to bridge "virbr0" On CentOS 5 & Debian Etch:- 1.ifcconfig shows xenbr0 without any assigned IP. 2."brctl show" shows two interfaces assigned to bridge xenbr0:- peth0,vif1.0 It is usual xen bridge behavior versus F7 one''s at least for myself # /etc/xen/scripts/network-bridge start/stop bridge=xenbr1 netdev=eth1 also didn''t work on F7 when I brought up eth1 for second ethernet adapter. Looks like F7''s Xen 3.1 behaves in it''s own (new ?) way. This message posted from opensolaris.org