Tried this on two different machines with same error. We are using a build of our bits merged with what was in the ON gate Monday night. Our stuff was working with Nevada build 97. Thanks Margot # virt-install -n dom55 \> --nographics -p \ > -f /export/home/dom55.img -s 23 \ > -l /export/home/solarisdvd-x86-b99.iso \ > -r 1280Starting install... Creating storage file... 100% |=========================| 23 GB 00:00 Creating domain... 0 B 00:04 libvir: Xen Daemon error : GET operation failed: libvir: error : invalid argument in virDomainLookupByUUIDString libvir: Xen Daemon error : GET operation failed: Couldn''t find domain "6". Domain installation does not appear to have been successful. If it was, you can restart your domain by running ''virsh start dom55''; otherwise, please restart your installation. # -- This message posted from opensolaris.org
Margot H. Miller wrote:> Tried this on two different machines with same error. We are using > a build of our bits merged with what was in the ON gate Monday night. > Our stuff was working with Nevada build 97.Perhaps it''s 6751828? Try pulling in the fix for that and see if it makes a difference. -Ryan> > Thanks > Margot > > # virt-install -n dom55 \ >> --nographics -p \ >> -f /export/home/dom55.img -s 23 \ >> -l /export/home/solarisdvd-x86-b99.iso \ >> -r 1280 > > Starting install... > Creating storage file... 100% |=========================| 23 GB 00:00 Creating domain... 0 B 00:04 > libvir: Xen Daemon error : GET operation failed: > libvir: error : invalid argument in virDomainLookupByUUIDString > libvir: Xen Daemon error : GET operation failed: > Couldn''t find domain "6". > > Domain installation does not appear to have been > successful. If it was, you can restart your domain > by running ''virsh start dom55''; otherwise, please > restart your installation. > # > -- > This message posted from opensolaris.org > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org
Susan Kamm-Worrell
2008-Sep-25 04:42 UTC
Re: virt-install and virDomainLookupByUUIDString error
Margot, Do you see any errors in the log files in /var/log/xen? Thanks, Susan Margot H. Miller wrote:> Tried this on two different machines with same error. We are using > a build of our bits merged with what was in the ON gate Monday night. > Our stuff was working with Nevada build 97. > > Thanks > Margot > > # virt-install -n dom55 \ >> --nographics -p \ >> -f /export/home/dom55.img -s 23 \ >> -l /export/home/solarisdvd-x86-b99.iso \ >> -r 1280 > > Starting install... > Creating storage file... 100% |=========================| 23 GB 00:00 Creating domain... 0 B 00:04 > libvir: Xen Daemon error : GET operation failed: > libvir: error : invalid argument in virDomainLookupByUUIDString > libvir: Xen Daemon error : GET operation failed: > Couldn''t find domain "6". > > Domain installation does not appear to have been > successful. If it was, you can restart your domain > by running ''virsh start dom55''; otherwise, please > restart your installation. > # > -- > This message posted from opensolaris.org > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org
Margot Miller
2008-Sep-25 06:37 UTC
Re: virt-install and virDomainLookupByUUIDString error
Hey Susan, Doing a xm dmesg, I see the below: (xVM) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) (xVM) Xen is relinquishing VGA console. (xVM) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen). (xVM) Freed 128kB init memory. (xVM) Xen trace buffers: initialized (xVM) Unhandled page fault in domain 1 on VCPU 0 (ec=0000) (xVM) Pagetable walk from 0000000000005e00: (xVM) L4[0x000] = 00000000a69d3027 000000000000b517 (xVM) L3[0x000] = 0000000000000000 ffffffffffffffff (xVM) domain_crash_sync called from entry.S (xVM) Domain 1 (vcpu#0) crashed on cpu#1: (xVM) ----[ Xen-3.1.4-xvm x86_64 debug=n Not tainted ]---- (xVM) CPU: 1 (xVM) RIP: e019:[<00000000f4c12783>] (xVM) RFLAGS: 0000000000000216 CONTEXT: guest (xVM) rax: 0000000000000001 rbx: 00000000408205c0 rcx: 0000000000000000 (xVM) rdx: 000000000000002c rsi: 00000000f4c00000 rdi: 0000000000000000 (xVM) rbp: 000000004080e51c rsp: 000000004080e4e0 r8: 0000000000000000 (xVM) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000 (xVM) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000000 (xVM) r15: 0000000000000000 cr0: 000000008005003b cr4: 00000000000006f0 (xVM) cr3: 00000000eea8a000 cr2: 0000000000005e00 (xVM) ds: e021 es: e021 fs: 0000 gs: 0000 ss: e021 cs: e019 (xVM) Guest stack trace from rbp=000000004080e51c: (xVM) 00000000408205c0 ???????????????? (xVM) Xen stack trace from rsp=000000004080e4e0: (xVM) f4c1278300000000 000100160001e019 f4c0000000000000 (xVM) 4080e51c00000000 0000000000000000 0000000000000000 (xVM) 0000000000000000 4080e52800000000 408205c040800032 (xVM) 0000000000000000 0000000000000000 0000000000000000 (xVM) 0000000000000000 0000000000000000 0000000000000000 (xVM) 0000000000000000 0000000000000000 0000000000000000 (xVM) 0000000000000000 0000000000000000 0000000000000000 (xVM) 0000000000000000 0000000000000000 0000000000000000 (xVM) 0000000000000000 0000000000000000 0000000000000000 (xVM) 0000000000000000 0000000000000000 0000000000000000 (xVM) 0000000000000000 0000000000000000 0000000000000000 (xVM) 0000000000000000 0000000000000000 0000000000000000 (xVM) 0000000000000000 0000000000000000 0000000000000000 (xVM) 0000000000000000 0000000000000000 0000000000000000 (xVM) 0000000000000000 0000000000000000 0000000000000000 (xVM) 0000000000000000 0000000000000000 0000000000000000 (xVM) 0000000000000000 0000000000000000 0000000000000000 (xVM) 0000000000000000 0000000000000000 0000000000000000 (xVM) 0000000000000000 0000000000000000 0000000000000000 (xVM) 0000000000000000 0000000000000000 0000000000000000 (xVM) Xen call trace: (xVM) [<00000000f4c12783>] ??? (xVM) [<00000000408205c0>] ??? (xVM) # Susan Kamm-Worrell wrote:> Margot, > > Do you see any errors in the log files in /var/log/xen? > > Thanks, > Susan > > > Margot H. Miller wrote: > >> Tried this on two different machines with same error. We are using >> a build of our bits merged with what was in the ON gate Monday night. >> Our stuff was working with Nevada build 97. >> >> Thanks >> Margot >> >> # virt-install -n dom55 \ >> >>> --nographics -p \ >>> -f /export/home/dom55.img -s 23 \ >>> -l /export/home/solarisdvd-x86-b99.iso \ >>> -r 1280 >>> >> Starting install... >> Creating storage file... 100% |=========================| 23 GB 00:00 Creating domain... 0 B 00:04 >> libvir: Xen Daemon error : GET operation failed: >> libvir: error : invalid argument in virDomainLookupByUUIDString >> libvir: Xen Daemon error : GET operation failed: >> Couldn''t find domain "6". >> >> Domain installation does not appear to have been >> successful. If it was, you can restart your domain >> by running ''virsh start dom55''; otherwise, please >> restart your installation. >> # >> -- >> This message posted from opensolaris.org >> _______________________________________________ >> xen-discuss mailing list >> xen-discuss@opensolaris.org >> > > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org >
Susan Kamm-Worrell
2008-Sep-25 08:08 UTC
Re: virt-install and virDomainLookupByUUIDString error
Margot, I think you are hitting 6751828 as Ryan suggested. I also noticed that the domain core dump failed, but I''m not sure if that is expected for such an early boot failure. [2008-09-24 23:48:56 102110] WARNING (XendDomainInfo:1200) Domain has crashed: name=dom55 id=1. [2008-09-24 23:48:56 102110] ERROR (XendDomainInfo:1430) XendDomainInfo.dumpCore failed: id = 1 name = dom55 Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1425, in dumpCore Error: (1, ''Internal error'', ''p2m_size < nr_pages -1 (0 < 4ffff'') Susan Margot Miller wrote:> Hey Susan, > > Doing a xm dmesg, I see the below: > > (xVM) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) > (xVM) Xen is relinquishing VGA console. > (xVM) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch > input to Xen). > (xVM) Freed 128kB init memory. > (xVM) Xen trace buffers: initialized > (xVM) Unhandled page fault in domain 1 on VCPU 0 (ec=0000) > (xVM) Pagetable walk from 0000000000005e00: > (xVM) L4[0x000] = 00000000a69d3027 000000000000b517 > (xVM) L3[0x000] = 0000000000000000 ffffffffffffffff > (xVM) domain_crash_sync called from entry.S > (xVM) Domain 1 (vcpu#0) crashed on cpu#1: > (xVM) ----[ Xen-3.1.4-xvm x86_64 debug=n Not tainted ]---- > (xVM) CPU: 1 > (xVM) RIP: e019:[<00000000f4c12783>] > (xVM) RFLAGS: 0000000000000216 CONTEXT: guest > (xVM) rax: 0000000000000001 rbx: 00000000408205c0 rcx: 0000000000000000 > (xVM) rdx: 000000000000002c rsi: 00000000f4c00000 rdi: 0000000000000000 > (xVM) rbp: 000000004080e51c rsp: 000000004080e4e0 r8: 0000000000000000 > (xVM) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000 > (xVM) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000000 > (xVM) r15: 0000000000000000 cr0: 000000008005003b cr4: 00000000000006f0 > (xVM) cr3: 00000000eea8a000 cr2: 0000000000005e00 > (xVM) ds: e021 es: e021 fs: 0000 gs: 0000 ss: e021 cs: e019 > (xVM) Guest stack trace from rbp=000000004080e51c: > (xVM) 00000000408205c0 ???????????????? > (xVM) Xen stack trace from rsp=000000004080e4e0: > (xVM) f4c1278300000000 000100160001e019 f4c0000000000000 > (xVM) 4080e51c00000000 0000000000000000 0000000000000000 > (xVM) 0000000000000000 4080e52800000000 408205c040800032 > (xVM) 0000000000000000 0000000000000000 0000000000000000 > (xVM) 0000000000000000 0000000000000000 0000000000000000 > (xVM) 0000000000000000 0000000000000000 0000000000000000 > (xVM) 0000000000000000 0000000000000000 0000000000000000 > (xVM) 0000000000000000 0000000000000000 0000000000000000 > (xVM) 0000000000000000 0000000000000000 0000000000000000 > (xVM) 0000000000000000 0000000000000000 0000000000000000 > (xVM) 0000000000000000 0000000000000000 0000000000000000 > (xVM) 0000000000000000 0000000000000000 0000000000000000 > (xVM) 0000000000000000 0000000000000000 0000000000000000 > (xVM) 0000000000000000 0000000000000000 0000000000000000 > (xVM) 0000000000000000 0000000000000000 0000000000000000 > (xVM) 0000000000000000 0000000000000000 0000000000000000 > (xVM) 0000000000000000 0000000000000000 0000000000000000 > (xVM) 0000000000000000 0000000000000000 0000000000000000 > (xVM) 0000000000000000 0000000000000000 0000000000000000 > (xVM) 0000000000000000 0000000000000000 0000000000000000 > (xVM) Xen call trace: > (xVM) [<00000000f4c12783>] ??? > (xVM) [<00000000408205c0>] ??? > (xVM) # > > > Susan Kamm-Worrell wrote: >> Margot, >> >> Do you see any errors in the log files in /var/log/xen? >> >> Thanks, >> Susan >> >> >> Margot H. Miller wrote: >> >>> Tried this on two different machines with same error. We are using >>> a build of our bits merged with what was in the ON gate Monday night. >>> Our stuff was working with Nevada build 97. >>> >>> Thanks >>> Margot >>> >>> # virt-install -n dom55 \ >>> >>>> --nographics -p \ >>>> -f /export/home/dom55.img -s 23 \ >>>> -l /export/home/solarisdvd-x86-b99.iso \ >>>> -r 1280 >>>> >>> Starting install... >>> Creating storage file... 100% |=========================| 23 GB >>> 00:00 Creating >>> domain... 0 B 00:04 >>> libvir: Xen Daemon error : GET operation failed: >>> libvir: error : invalid argument in virDomainLookupByUUIDString >>> libvir: Xen Daemon error : GET operation failed: >>> Couldn''t find domain "6". >>> >>> Domain installation does not appear to have been >>> successful. If it was, you can restart your domain >>> by running ''virsh start dom55''; otherwise, please >>> restart your installation. >>> # >>> -- >>> This message posted from opensolaris.org >>> _______________________________________________ >>> xen-discuss mailing list >>> xen-discuss@opensolaris.org >>> >> >> _______________________________________________ >> xen-discuss mailing list >> xen-discuss@opensolaris.org >> >
Margot Miller
2008-Sep-26 03:51 UTC
Re: virt-install and virDomainLookupByUUIDString error
Yes that was it. Got the latest bits with the fix to 6751828 and now it works like a charm. Thanks for your help, Margot Susan Kamm-Worrell wrote:> Margot, > > I think you are hitting 6751828 as Ryan suggested. > > I also noticed that the domain core dump failed, but I''m not sure if that > is expected for such an early boot failure. > > [2008-09-24 23:48:56 102110] WARNING (XendDomainInfo:1200) Domain has crashed: name=dom55 id=1. > [2008-09-24 23:48:56 102110] ERROR (XendDomainInfo:1430) XendDomainInfo.dumpCore failed: id = 1 name = dom55 > Traceback (most recent call last): > File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1425, in dumpCore > Error: (1, ''Internal error'', ''p2m_size < nr_pages -1 (0 < 4ffff'') > > Susan > > > Margot Miller wrote: > >> Hey Susan, >> >> Doing a xm dmesg, I see the below: >> >> (xVM) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) >> (xVM) Xen is relinquishing VGA console. >> (xVM) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch >> input to Xen). >> (xVM) Freed 128kB init memory. >> (xVM) Xen trace buffers: initialized >> (xVM) Unhandled page fault in domain 1 on VCPU 0 (ec=0000) >> (xVM) Pagetable walk from 0000000000005e00: >> (xVM) L4[0x000] = 00000000a69d3027 000000000000b517 >> (xVM) L3[0x000] = 0000000000000000 ffffffffffffffff >> (xVM) domain_crash_sync called from entry.S >> (xVM) Domain 1 (vcpu#0) crashed on cpu#1: >> (xVM) ----[ Xen-3.1.4-xvm x86_64 debug=n Not tainted ]---- >> (xVM) CPU: 1 >> (xVM) RIP: e019:[<00000000f4c12783>] >> (xVM) RFLAGS: 0000000000000216 CONTEXT: guest >> (xVM) rax: 0000000000000001 rbx: 00000000408205c0 rcx: 0000000000000000 >> (xVM) rdx: 000000000000002c rsi: 00000000f4c00000 rdi: 0000000000000000 >> (xVM) rbp: 000000004080e51c rsp: 000000004080e4e0 r8: 0000000000000000 >> (xVM) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000 >> (xVM) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000000 >> (xVM) r15: 0000000000000000 cr0: 000000008005003b cr4: 00000000000006f0 >> (xVM) cr3: 00000000eea8a000 cr2: 0000000000005e00 >> (xVM) ds: e021 es: e021 fs: 0000 gs: 0000 ss: e021 cs: e019 >> (xVM) Guest stack trace from rbp=000000004080e51c: >> (xVM) 00000000408205c0 ???????????????? >> (xVM) Xen stack trace from rsp=000000004080e4e0: >> (xVM) f4c1278300000000 000100160001e019 f4c0000000000000 >> (xVM) 4080e51c00000000 0000000000000000 0000000000000000 >> (xVM) 0000000000000000 4080e52800000000 408205c040800032 >> (xVM) 0000000000000000 0000000000000000 0000000000000000 >> (xVM) 0000000000000000 0000000000000000 0000000000000000 >> (xVM) 0000000000000000 0000000000000000 0000000000000000 >> (xVM) 0000000000000000 0000000000000000 0000000000000000 >> (xVM) 0000000000000000 0000000000000000 0000000000000000 >> (xVM) 0000000000000000 0000000000000000 0000000000000000 >> (xVM) 0000000000000000 0000000000000000 0000000000000000 >> (xVM) 0000000000000000 0000000000000000 0000000000000000 >> (xVM) 0000000000000000 0000000000000000 0000000000000000 >> (xVM) 0000000000000000 0000000000000000 0000000000000000 >> (xVM) 0000000000000000 0000000000000000 0000000000000000 >> (xVM) 0000000000000000 0000000000000000 0000000000000000 >> (xVM) 0000000000000000 0000000000000000 0000000000000000 >> (xVM) 0000000000000000 0000000000000000 0000000000000000 >> (xVM) 0000000000000000 0000000000000000 0000000000000000 >> (xVM) 0000000000000000 0000000000000000 0000000000000000 >> (xVM) 0000000000000000 0000000000000000 0000000000000000 >> (xVM) Xen call trace: >> (xVM) [<00000000f4c12783>] ??? >> (xVM) [<00000000408205c0>] ??? >> (xVM) # >> >> >> Susan Kamm-Worrell wrote: >> >>> Margot, >>> >>> Do you see any errors in the log files in /var/log/xen? >>> >>> Thanks, >>> Susan >>> >>> >>> Margot H. Miller wrote: >>> >>> >>>> Tried this on two different machines with same error. We are using >>>> a build of our bits merged with what was in the ON gate Monday night. >>>> Our stuff was working with Nevada build 97. >>>> >>>> Thanks >>>> Margot >>>> >>>> # virt-install -n dom55 \ >>>> >>>> >>>>> --nographics -p \ >>>>> -f /export/home/dom55.img -s 23 \ >>>>> -l /export/home/solarisdvd-x86-b99.iso \ >>>>> -r 1280 >>>>> >>>>> >>>> Starting install... >>>> Creating storage file... 100% |=========================| 23 GB >>>> 00:00 Creating >>>> domain... 0 B 00:04 >>>> libvir: Xen Daemon error : GET operation failed: >>>> libvir: error : invalid argument in virDomainLookupByUUIDString >>>> libvir: Xen Daemon error : GET operation failed: >>>> Couldn''t find domain "6". >>>> >>>> Domain installation does not appear to have been >>>> successful. If it was, you can restart your domain >>>> by running ''virsh start dom55''; otherwise, please >>>> restart your installation. >>>> # >>>> -- >>>> This message posted from opensolaris.org >>>> _______________________________________________ >>>> xen-discuss mailing list >>>> xen-discuss@opensolaris.org >>>> >>>> >>> _______________________________________________ >>> xen-discuss mailing list >>> xen-discuss@opensolaris.org >>> >>> > > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org >