* RE: blktap2: need more than 3 values to unpack [not found] <Pine.GSO.4.60.0906020756360.23746@cascade.cs.ubc.ca> @ 2009-06-02 17:33 ` Dan Magenheimer 2009-06-02 22:44 ` Keir Fraser 0 siblings, 1 reply; 20+ messages in thread From: Dan Magenheimer @ 2009-06-02 17:33 UTC (permalink / raw) To: Dutch Meyer, Xen-Devel (E-mail) Thanks. Looks like a partial configuration patch got checked in for blktap2 (cs 886)? CONFIG_XEN_BLKDEV_TAP2 must be configured but afaict is not turned on by default (yet?). So a fresh xen-unstable tip doesn't build the blktap2 driver. See: http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/3e01555dd227 (I'm guessing since this was submitted by Isaku that blktap2 shouldn't be the default on ia64?) Should CONFIG_XEN_BLKDEV_TAP2 be turned on by default, instead of CONFIG_XEN_BLKDEV_TAP, at least on x86? I tried modifying linux-2.6.18-xen.hg/buildconfigs/linux-defconfig_xen0_x86_32 (and also linux-2.6.18-xen.hg/buildconfigs/linux-defconfig_xen_x86_32) followed by: KERNELS=linux-2.6-xen0 make linux-2.6-xen-config CONFIGMODE=oldconfig (I don't need or want to go through a manual config process) but BLKDEV_TAP is always selected, not BLKDEV_TAP2. Finally, I resorted to manually changing linux-2.6.18-xen.hg/drivers/xen/Kconfig and this succeeds in turning it on, but it just reverses the above checked-in patch, so I suspect that's not the right answer either. > -----Original Message----- > From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] > Sent: Tuesday, June 02, 2009 9:05 AM > To: Dan Magenheimer > Subject: RE: [Xen-devel] blktap2: need more than 3 values to unpack > > > I think that you don't have the blktap2 driver loaded in > dom0. A clean > build/install of the dom0 kernel image should sort you out. If > drivers/xen/blktap2 is compiled in it should be setting up > these paths. > > Let me know if that fixes things and I'll make python spit out more > meaningful errors, otherwise we can try to figure out the > blktap2 kernel > code isn't working. > > --Dutch > > On Tue, 2 Jun 2009, Dan Magenheimer wrote: > > > It replies with "didn't find blktap-control in /proc/misc" > > > > If that fails, perhaps the path doesn't exist, but I looked > > and /sys/class/blktap2 doesn't exist. > > > >> -----Original Message----- > >> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] > >> Sent: Monday, June 01, 2009 10:37 PM > >> To: Dan Magenheimer > >> Subject: RE: [Xen-devel] blktap2: need more than 3 values to unpack > >> > >> > >> Can you try this from the command line: > >> > >> tapdisk2 -n aio:/pathto/file.img > >> > >> If successful, this will create your aio device and print a > >> /dev device > >> associated with it. > >> > >> In that case you'll then be able to remove it with: > >> > >> echo 1 > /sys/class/blktap2/<disk>/remove > >> > >> Where <disk> will be obvious from the output of the > tapdisk2 command. > >> > >> However, I expect that this will fail. > >> > >> --Dutch > >> > >> On Mon, 1 Jun 2009, Dan Magenheimer wrote: > >> > >>>> Then I might be able to help, but I'm not sure how to > >>>> reproduce it. If > >>>> you send a log file and config for this latter error I'll > >>>> take a look. > >>> > >>> Here ya go. > >>> > >>> Thanks, > >>> Dan > >>> > >>>> -----Original Message----- > >>>> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] > >>>> Sent: Monday, June 01, 2009 8:32 PM > >>>> To: Dan Magenheimer > >>>> Cc: Xen-Devel (E-mail) > >>>> Subject: Re: [Xen-devel] blktap2: need more than 3 > values to unpack > >>>> > >>>> > >>>> The tap:aio:/pathto/file.img syntax that you're using in your > >>>> config was > >>>> changed before blktap2 was introduced. > >>>> tap:tapdisk:aio:/pathto/file.img is > >>>> apparently the correct syntax now, though the README didn't > >>>> get updated to > >>>> reflect this. Our blktap2 documentation is no better - > I'll try to > >>>> remedy that this week. > >>>> > >>>> > >>>> If you're still seeing this error: > >>>> "Error: 'file' object has no attribute 'find'" > >>>> > >>>> Then I might be able to help, but I'm not sure how to > >>>> reproduce it. If > >>>> you send a log file and config for this latter error I'll > >>>> take a look. > >>>> Yang seems to be reporting the same thing in another thread. > >>>> > >>>> --Dutch > >>>> > >>>> On Mon, 1 Jun 2009, Dan Magenheimer wrote: > >>>> > >>>>> Hmmm... trying blktap2 for the first time, using 19682. > >>>>> I had thought that the syntax hadn't changed, but I am > >>>>> getting what appears to be a parsing error on my vbd line. > >>>>> > >>>>> "ValueError: need more than 3 values to unpack" > >>>>> > >>>>> Thinking maybe that "w!" was the culprit, I changed > >>>>> it to "w" with no change in result. > >>>>> > >>>>> Looking at the python code that generated the error, > >>>>> I tried to figure out the syntax by experimentation > >>>>> but without luck. I tried: > >>>>> > >>>>> tap:tapdisk:aio:/pathto/file.img > >>>>> > >>>>> but got "Error: 'file' object has no attribute 'find'" > >>>>> > >>>>> To see if I could use the old blktap, I tried > >>>>> > >>>>> tap:tapdisk:ioemu:/pathto/file.img > >>>>> > >>>>> but got the dreaded "Error: Device 768 (tap) could not be > >>>>> connected. Hotplug scripts not working" > >>>>> > >>>>> Am I missing something in the syntax for blktap2? > >>>>> Is there a how-to or readme I didn't find? Or > >>>>> is there some required dependency I don't know about > >>>>> that is missing? > >>>>> > >>>>> I thought maybe I had a bad install, so rebuilt and > >>>>> reinstalled with the same result. > >>>>> > >>>>> xend.log and config file attached. > >>>>> > >>>>> Thanks, > >>>>> Dan > >>>>> > >>>>> P.S. I am trying blktap2 because both blktap and > >>>>> file-backed fail. Blktap sometimes reads garbage > >>>>> from the file and > >>>> > >>>> _______________________________________________ > >>>> Xen-devel mailing list > >>>> Xen-devel@lists.xensource.com > >>>> http://lists.xensource.com/xen-devel > >>>> > >> > > > ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: blktap2: need more than 3 values to unpack 2009-06-02 17:33 ` blktap2: need more than 3 values to unpack Dan Magenheimer @ 2009-06-02 22:44 ` Keir Fraser 2009-06-02 23:49 ` Dan Magenheimer 0 siblings, 1 reply; 20+ messages in thread From: Keir Fraser @ 2009-06-02 22:44 UTC (permalink / raw) To: Dan Magenheimer, Dutch Meyer, Xen-Devel (E-mail) Probably you had an old .config hanging around in your build tree somewhere. c/s 889 should fix this for a fresh build. -- Keir On 02/06/2009 18:33, "Dan Magenheimer" <dan.magenheimer@oracle.com> wrote: > Thanks. Looks like a partial configuration patch got checked > in for blktap2 (cs 886)? CONFIG_XEN_BLKDEV_TAP2 must be configured > but afaict is not turned on by default (yet?). So a fresh > xen-unstable tip doesn't build the blktap2 driver. See: > > http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/3e01555dd227 > > (I'm guessing since this was submitted by Isaku that blktap2 > shouldn't be the default on ia64?) > > Should CONFIG_XEN_BLKDEV_TAP2 be turned on by default, instead > of CONFIG_XEN_BLKDEV_TAP, at least on x86? > > I tried modifying > > linux-2.6.18-xen.hg/buildconfigs/linux-defconfig_xen0_x86_32 > > (and also > > linux-2.6.18-xen.hg/buildconfigs/linux-defconfig_xen_x86_32) > > followed by: > > KERNELS=linux-2.6-xen0 make linux-2.6-xen-config CONFIGMODE=oldconfig > > (I don't need or want to go through a manual config process) > > but BLKDEV_TAP is always selected, not BLKDEV_TAP2. > > Finally, I resorted to manually changing > > linux-2.6.18-xen.hg/drivers/xen/Kconfig > > and this succeeds in turning it on, but it just reverses the > above checked-in patch, so I suspect that's not the right > answer either. > >> -----Original Message----- >> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] >> Sent: Tuesday, June 02, 2009 9:05 AM >> To: Dan Magenheimer >> Subject: RE: [Xen-devel] blktap2: need more than 3 values to unpack >> >> >> I think that you don't have the blktap2 driver loaded in >> dom0. A clean >> build/install of the dom0 kernel image should sort you out. If >> drivers/xen/blktap2 is compiled in it should be setting up >> these paths. >> >> Let me know if that fixes things and I'll make python spit out more >> meaningful errors, otherwise we can try to figure out the >> blktap2 kernel >> code isn't working. >> >> --Dutch >> >> On Tue, 2 Jun 2009, Dan Magenheimer wrote: >> >>> It replies with "didn't find blktap-control in /proc/misc" >>> >>> If that fails, perhaps the path doesn't exist, but I looked >>> and /sys/class/blktap2 doesn't exist. >>> >>>> -----Original Message----- >>>> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] >>>> Sent: Monday, June 01, 2009 10:37 PM >>>> To: Dan Magenheimer >>>> Subject: RE: [Xen-devel] blktap2: need more than 3 values to unpack >>>> >>>> >>>> Can you try this from the command line: >>>> >>>> tapdisk2 -n aio:/pathto/file.img >>>> >>>> If successful, this will create your aio device and print a >>>> /dev device >>>> associated with it. >>>> >>>> In that case you'll then be able to remove it with: >>>> >>>> echo 1 > /sys/class/blktap2/<disk>/remove >>>> >>>> Where <disk> will be obvious from the output of the >> tapdisk2 command. >>>> >>>> However, I expect that this will fail. >>>> >>>> --Dutch >>>> >>>> On Mon, 1 Jun 2009, Dan Magenheimer wrote: >>>> >>>>>> Then I might be able to help, but I'm not sure how to >>>>>> reproduce it. If >>>>>> you send a log file and config for this latter error I'll >>>>>> take a look. >>>>> >>>>> Here ya go. >>>>> >>>>> Thanks, >>>>> Dan >>>>> >>>>>> -----Original Message----- >>>>>> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] >>>>>> Sent: Monday, June 01, 2009 8:32 PM >>>>>> To: Dan Magenheimer >>>>>> Cc: Xen-Devel (E-mail) >>>>>> Subject: Re: [Xen-devel] blktap2: need more than 3 >> values to unpack >>>>>> >>>>>> >>>>>> The tap:aio:/pathto/file.img syntax that you're using in your >>>>>> config was >>>>>> changed before blktap2 was introduced. >>>>>> tap:tapdisk:aio:/pathto/file.img is >>>>>> apparently the correct syntax now, though the README didn't >>>>>> get updated to >>>>>> reflect this. Our blktap2 documentation is no better - >> I'll try to >>>>>> remedy that this week. >>>>>> >>>>>> >>>>>> If you're still seeing this error: >>>>>> "Error: 'file' object has no attribute 'find'" >>>>>> >>>>>> Then I might be able to help, but I'm not sure how to >>>>>> reproduce it. If >>>>>> you send a log file and config for this latter error I'll >>>>>> take a look. >>>>>> Yang seems to be reporting the same thing in another thread. >>>>>> >>>>>> --Dutch >>>>>> >>>>>> On Mon, 1 Jun 2009, Dan Magenheimer wrote: >>>>>> >>>>>>> Hmmm... trying blktap2 for the first time, using 19682. >>>>>>> I had thought that the syntax hadn't changed, but I am >>>>>>> getting what appears to be a parsing error on my vbd line. >>>>>>> >>>>>>> "ValueError: need more than 3 values to unpack" >>>>>>> >>>>>>> Thinking maybe that "w!" was the culprit, I changed >>>>>>> it to "w" with no change in result. >>>>>>> >>>>>>> Looking at the python code that generated the error, >>>>>>> I tried to figure out the syntax by experimentation >>>>>>> but without luck. I tried: >>>>>>> >>>>>>> tap:tapdisk:aio:/pathto/file.img >>>>>>> >>>>>>> but got "Error: 'file' object has no attribute 'find'" >>>>>>> >>>>>>> To see if I could use the old blktap, I tried >>>>>>> >>>>>>> tap:tapdisk:ioemu:/pathto/file.img >>>>>>> >>>>>>> but got the dreaded "Error: Device 768 (tap) could not be >>>>>>> connected. Hotplug scripts not working" >>>>>>> >>>>>>> Am I missing something in the syntax for blktap2? >>>>>>> Is there a how-to or readme I didn't find? Or >>>>>>> is there some required dependency I don't know about >>>>>>> that is missing? >>>>>>> >>>>>>> I thought maybe I had a bad install, so rebuilt and >>>>>>> reinstalled with the same result. >>>>>>> >>>>>>> xend.log and config file attached. >>>>>>> >>>>>>> Thanks, >>>>>>> Dan >>>>>>> >>>>>>> P.S. I am trying blktap2 because both blktap and >>>>>>> file-backed fail. Blktap sometimes reads garbage >>>>>>> from the file and >>>>>> >>>>>> _______________________________________________ >>>>>> Xen-devel mailing list >>>>>> Xen-devel@lists.xensource.com >>>>>> http://lists.xensource.com/xen-devel >>>>>> >>>> >>> >> > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 20+ messages in thread
* RE: blktap2: need more than 3 values to unpack 2009-06-02 22:44 ` Keir Fraser @ 2009-06-02 23:49 ` Dan Magenheimer 2009-06-03 4:45 ` Dan Magenheimer 0 siblings, 1 reply; 20+ messages in thread From: Dan Magenheimer @ 2009-06-02 23:49 UTC (permalink / raw) To: Keir Fraser, Dutch Meyer, Xen-Devel (E-mail) Thanks. It is indeed a pilot error on my part but a bit more bizarre. I apparently have a linux-2.6-xen.hg directory as both a sister and a child to xen-unstable.hg. In this case the build apparently chooses the child. I was looking at and modifying the un-updated child so blktap2 wasn't even present yet. Removing the child causes the sibling to build. BUT! Now dom0 is crashing early on during boot. (This is an Intel Weybridge box.) I'll look into this further tomorrow. ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ATAPI, max UDMA/100 ata2.00: configured for UDMA/100 scsi2 : ahci ata3: SATA link down (SStatus 0 SControl 300) scsi3 : ahci ata4: SATA link down (SStatus 0 SControl 300) Vendor: ATA Model: ST3320620AS Rev: 3.AA Type: Direct-Access ANSI SCSI revision: 05 ata1: EH pending after completion, repeating EH (cnt=4) Vendor: LITE-ON Model: DVDRW LH-20A1S Rev: 9L03 Type: CD-ROM ANSI SCSI revision: 05 (XEN) PCI add device 00:1f.5 ata_piix 0000:00:1f.5: MAP [ P0 P2 P1 P3 ] ACPI: PCI Interrupt 0000:00:1f.5[B] -> GSI 19 (level, low) -> IRQ 16 ata5: SATA max UDMA/133 cmd 0x0 ctl 0x2 bmdma 0x0 irq 16 ata6: SATA max UDMA/133 cmd 0x0 ctl 0x2 bmdma 0x0 irq 16 scsi4 : ata_piix scsi5 : ata_piix device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@redhat.com Kernel panic - not syncing: Attempted to kill init! (XEN) Domain 0 crashed: rebooting machine in 5 seconds. > -----Original Message----- > From: Keir Fraser [mailto:keir.fraser@eu.citrix.com] > Sent: Tuesday, June 02, 2009 4:45 PM > To: Dan Magenheimer; Dutch Meyer; Xen-Devel (E-mail) > Subject: Re: [Xen-devel] blktap2: need more than 3 values to unpack > > > Probably you had an old .config hanging around in your build > tree somewhere. > c/s 889 should fix this for a fresh build. > > -- Keir > > On 02/06/2009 18:33, "Dan Magenheimer" > <dan.magenheimer@oracle.com> wrote: > > > Thanks. Looks like a partial configuration patch got checked > > in for blktap2 (cs 886)? CONFIG_XEN_BLKDEV_TAP2 must be configured > > but afaict is not turned on by default (yet?). So a fresh > > xen-unstable tip doesn't build the blktap2 driver. See: > > > > http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/3e01555dd227 > > > > (I'm guessing since this was submitted by Isaku that blktap2 > > shouldn't be the default on ia64?) > > > > Should CONFIG_XEN_BLKDEV_TAP2 be turned on by default, instead > > of CONFIG_XEN_BLKDEV_TAP, at least on x86? > > > > I tried modifying > > > > linux-2.6.18-xen.hg/buildconfigs/linux-defconfig_xen0_x86_32 > > > > (and also > > > > linux-2.6.18-xen.hg/buildconfigs/linux-defconfig_xen_x86_32) > > > > followed by: > > > > KERNELS=linux-2.6-xen0 make linux-2.6-xen-config > CONFIGMODE=oldconfig > > > > (I don't need or want to go through a manual config process) > > > > but BLKDEV_TAP is always selected, not BLKDEV_TAP2. > > > > Finally, I resorted to manually changing > > > > linux-2.6.18-xen.hg/drivers/xen/Kconfig > > > > and this succeeds in turning it on, but it just reverses the > > above checked-in patch, so I suspect that's not the right > > answer either. > > > >> -----Original Message----- > >> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] > >> Sent: Tuesday, June 02, 2009 9:05 AM > >> To: Dan Magenheimer > >> Subject: RE: [Xen-devel] blktap2: need more than 3 values to unpack > >> > >> > >> I think that you don't have the blktap2 driver loaded in > >> dom0. A clean > >> build/install of the dom0 kernel image should sort you out. If > >> drivers/xen/blktap2 is compiled in it should be setting up > >> these paths. > >> > >> Let me know if that fixes things and I'll make python spit out more > >> meaningful errors, otherwise we can try to figure out the > >> blktap2 kernel > >> code isn't working. > >> > >> --Dutch > >> > >> On Tue, 2 Jun 2009, Dan Magenheimer wrote: > >> > >>> It replies with "didn't find blktap-control in /proc/misc" > >>> > >>> If that fails, perhaps the path doesn't exist, but I looked > >>> and /sys/class/blktap2 doesn't exist. > >>> > >>>> -----Original Message----- > >>>> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] > >>>> Sent: Monday, June 01, 2009 10:37 PM > >>>> To: Dan Magenheimer > >>>> Subject: RE: [Xen-devel] blktap2: need more than 3 > values to unpack > >>>> > >>>> > >>>> Can you try this from the command line: > >>>> > >>>> tapdisk2 -n aio:/pathto/file.img > >>>> > >>>> If successful, this will create your aio device and print a > >>>> /dev device > >>>> associated with it. > >>>> > >>>> In that case you'll then be able to remove it with: > >>>> > >>>> echo 1 > /sys/class/blktap2/<disk>/remove > >>>> > >>>> Where <disk> will be obvious from the output of the > >> tapdisk2 command. > >>>> > >>>> However, I expect that this will fail. > >>>> > >>>> --Dutch > >>>> > >>>> On Mon, 1 Jun 2009, Dan Magenheimer wrote: > >>>> > >>>>>> Then I might be able to help, but I'm not sure how to > >>>>>> reproduce it. If > >>>>>> you send a log file and config for this latter error I'll > >>>>>> take a look. > >>>>> > >>>>> Here ya go. > >>>>> > >>>>> Thanks, > >>>>> Dan > >>>>> > >>>>>> -----Original Message----- > >>>>>> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] > >>>>>> Sent: Monday, June 01, 2009 8:32 PM > >>>>>> To: Dan Magenheimer > >>>>>> Cc: Xen-Devel (E-mail) > >>>>>> Subject: Re: [Xen-devel] blktap2: need more than 3 > >> values to unpack > >>>>>> > >>>>>> > >>>>>> The tap:aio:/pathto/file.img syntax that you're using in your > >>>>>> config was > >>>>>> changed before blktap2 was introduced. > >>>>>> tap:tapdisk:aio:/pathto/file.img is > >>>>>> apparently the correct syntax now, though the README didn't > >>>>>> get updated to > >>>>>> reflect this. Our blktap2 documentation is no better - > >> I'll try to > >>>>>> remedy that this week. > >>>>>> > >>>>>> > >>>>>> If you're still seeing this error: > >>>>>> "Error: 'file' object has no attribute 'find'" > >>>>>> > >>>>>> Then I might be able to help, but I'm not sure how to > >>>>>> reproduce it. If > >>>>>> you send a log file and config for this latter error I'll > >>>>>> take a look. > >>>>>> Yang seems to be reporting the same thing in another thread. > >>>>>> > >>>>>> --Dutch > >>>>>> > >>>>>> On Mon, 1 Jun 2009, Dan Magenheimer wrote: > >>>>>> > >>>>>>> Hmmm... trying blktap2 for the first time, using 19682. > >>>>>>> I had thought that the syntax hadn't changed, but I am > >>>>>>> getting what appears to be a parsing error on my vbd line. > >>>>>>> > >>>>>>> "ValueError: need more than 3 values to unpack" > >>>>>>> > >>>>>>> Thinking maybe that "w!" was the culprit, I changed > >>>>>>> it to "w" with no change in result. > >>>>>>> > >>>>>>> Looking at the python code that generated the error, > >>>>>>> I tried to figure out the syntax by experimentation > >>>>>>> but without luck. I tried: > >>>>>>> > >>>>>>> tap:tapdisk:aio:/pathto/file.img > >>>>>>> > >>>>>>> but got "Error: 'file' object has no attribute 'find'" > >>>>>>> > >>>>>>> To see if I could use the old blktap, I tried > >>>>>>> > >>>>>>> tap:tapdisk:ioemu:/pathto/file.img > >>>>>>> > >>>>>>> but got the dreaded "Error: Device 768 (tap) could not be > >>>>>>> connected. Hotplug scripts not working" > >>>>>>> > >>>>>>> Am I missing something in the syntax for blktap2? > >>>>>>> Is there a how-to or readme I didn't find? Or > >>>>>>> is there some required dependency I don't know about > >>>>>>> that is missing? > >>>>>>> > >>>>>>> I thought maybe I had a bad install, so rebuilt and > >>>>>>> reinstalled with the same result. > >>>>>>> > >>>>>>> xend.log and config file attached. > >>>>>>> > >>>>>>> Thanks, > >>>>>>> Dan > >>>>>>> > >>>>>>> P.S. I am trying blktap2 because both blktap and > >>>>>>> file-backed fail. Blktap sometimes reads garbage > >>>>>>> from the file and > >>>>>> > >>>>>> _______________________________________________ > >>>>>> Xen-devel mailing list > >>>>>> Xen-devel@lists.xensource.com > >>>>>> http://lists.xensource.com/xen-devel > >>>>>> > >>>> > >>> > >> > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel > > > ^ permalink raw reply [flat|nested] 20+ messages in thread
* RE: blktap2: need more than 3 values to unpack 2009-06-02 23:49 ` Dan Magenheimer @ 2009-06-03 4:45 ` Dan Magenheimer 2009-06-03 17:35 ` Dom0 crashing when built with c/s 881 (Was: blktap2: need more than 3 values to unpack) Dan Magenheimer 0 siblings, 1 reply; 20+ messages in thread From: Dan Magenheimer @ 2009-06-03 4:45 UTC (permalink / raw) To: dan.magenheimer, Keir Fraser, Dutch Meyer, Xen-Devel (E-mail) Followup: my dom0 boots failed with 888, boots fine with 876, then to ensure no pilot error, I rebuilt 888 again and it failed again. > -----Original Message----- > From: Dan Magenheimer > Sent: Tuesday, June 02, 2009 5:50 PM > To: Keir Fraser; Dutch Meyer; Xen-Devel (E-mail) > Subject: RE: [Xen-devel] blktap2: need more than 3 values to unpack > > > Thanks. It is indeed a pilot error on my part but a bit > more bizarre. I apparently have a linux-2.6-xen.hg directory > as both a sister and a child to xen-unstable.hg. In this > case the build apparently chooses the child. I was > looking at and modifying the un-updated child so > blktap2 wasn't even present yet. Removing the child > causes the sibling to build. BUT! Now dom0 is > crashing early on during boot. (This is an Intel > Weybridge box.) I'll look into this further tomorrow. > > ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > ata2.00: ATAPI, max UDMA/100 > ata2.00: configured for UDMA/100 > scsi2 : ahci > ata3: SATA link down (SStatus 0 SControl 300) > scsi3 : ahci > ata4: SATA link down (SStatus 0 SControl 300) > Vendor: ATA Model: ST3320620AS Rev: 3.AA > Type: Direct-Access ANSI SCSI revision: 05 > ata1: EH pending after completion, repeating EH (cnt=4) > Vendor: LITE-ON Model: DVDRW LH-20A1S Rev: 9L03 > Type: CD-ROM ANSI SCSI revision: 05 > (XEN) PCI add device 00:1f.5 > ata_piix 0000:00:1f.5: MAP [ P0 P2 P1 P3 ] > ACPI: PCI Interrupt 0000:00:1f.5[B] -> GSI 19 (level, low) -> IRQ 16 > ata5: SATA max UDMA/133 cmd 0x0 ctl 0x2 bmdma 0x0 irq 16 > ata6: SATA max UDMA/133 cmd 0x0 ctl 0x2 bmdma 0x0 irq 16 > scsi4 : ata_piix > scsi5 : ata_piix > device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: > dm-devel@redhat.com > Kernel panic - not syncing: Attempted to kill init! > (XEN) Domain 0 crashed: rebooting machine in 5 seconds. > > > -----Original Message----- > > From: Keir Fraser [mailto:keir.fraser@eu.citrix.com] > > Sent: Tuesday, June 02, 2009 4:45 PM > > To: Dan Magenheimer; Dutch Meyer; Xen-Devel (E-mail) > > Subject: Re: [Xen-devel] blktap2: need more than 3 values to unpack > > > > > > Probably you had an old .config hanging around in your build > > tree somewhere. > > c/s 889 should fix this for a fresh build. > > > > -- Keir > > > > On 02/06/2009 18:33, "Dan Magenheimer" > > <dan.magenheimer@oracle.com> wrote: > > > > > Thanks. Looks like a partial configuration patch got checked > > > in for blktap2 (cs 886)? CONFIG_XEN_BLKDEV_TAP2 must be > configured > > > but afaict is not turned on by default (yet?). So a fresh > > > xen-unstable tip doesn't build the blktap2 driver. See: > > > > > > http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/3e01555dd227 > > > > > > (I'm guessing since this was submitted by Isaku that blktap2 > > > shouldn't be the default on ia64?) > > > > > > Should CONFIG_XEN_BLKDEV_TAP2 be turned on by default, instead > > > of CONFIG_XEN_BLKDEV_TAP, at least on x86? > > > > > > I tried modifying > > > > > > linux-2.6.18-xen.hg/buildconfigs/linux-defconfig_xen0_x86_32 > > > > > > (and also > > > > > > linux-2.6.18-xen.hg/buildconfigs/linux-defconfig_xen_x86_32) > > > > > > followed by: > > > > > > KERNELS=linux-2.6-xen0 make linux-2.6-xen-config > > CONFIGMODE=oldconfig > > > > > > (I don't need or want to go through a manual config process) > > > > > > but BLKDEV_TAP is always selected, not BLKDEV_TAP2. > > > > > > Finally, I resorted to manually changing > > > > > > linux-2.6.18-xen.hg/drivers/xen/Kconfig > > > > > > and this succeeds in turning it on, but it just reverses the > > > above checked-in patch, so I suspect that's not the right > > > answer either. > > > > > >> -----Original Message----- > > >> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] > > >> Sent: Tuesday, June 02, 2009 9:05 AM > > >> To: Dan Magenheimer > > >> Subject: RE: [Xen-devel] blktap2: need more than 3 > values to unpack > > >> > > >> > > >> I think that you don't have the blktap2 driver loaded in > > >> dom0. A clean > > >> build/install of the dom0 kernel image should sort you out. If > > >> drivers/xen/blktap2 is compiled in it should be setting up > > >> these paths. > > >> > > >> Let me know if that fixes things and I'll make python > spit out more > > >> meaningful errors, otherwise we can try to figure out the > > >> blktap2 kernel > > >> code isn't working. > > >> > > >> --Dutch > > >> > > >> On Tue, 2 Jun 2009, Dan Magenheimer wrote: > > >> > > >>> It replies with "didn't find blktap-control in /proc/misc" > > >>> > > >>> If that fails, perhaps the path doesn't exist, but I looked > > >>> and /sys/class/blktap2 doesn't exist. > > >>> > > >>>> -----Original Message----- > > >>>> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] > > >>>> Sent: Monday, June 01, 2009 10:37 PM > > >>>> To: Dan Magenheimer > > >>>> Subject: RE: [Xen-devel] blktap2: need more than 3 > > values to unpack > > >>>> > > >>>> > > >>>> Can you try this from the command line: > > >>>> > > >>>> tapdisk2 -n aio:/pathto/file.img > > >>>> > > >>>> If successful, this will create your aio device and print a > > >>>> /dev device > > >>>> associated with it. > > >>>> > > >>>> In that case you'll then be able to remove it with: > > >>>> > > >>>> echo 1 > /sys/class/blktap2/<disk>/remove > > >>>> > > >>>> Where <disk> will be obvious from the output of the > > >> tapdisk2 command. > > >>>> > > >>>> However, I expect that this will fail. > > >>>> > > >>>> --Dutch > > >>>> > > >>>> On Mon, 1 Jun 2009, Dan Magenheimer wrote: > > >>>> > > >>>>>> Then I might be able to help, but I'm not sure how to > > >>>>>> reproduce it. If > > >>>>>> you send a log file and config for this latter error I'll > > >>>>>> take a look. > > >>>>> > > >>>>> Here ya go. > > >>>>> > > >>>>> Thanks, > > >>>>> Dan > > >>>>> > > >>>>>> -----Original Message----- > > >>>>>> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] > > >>>>>> Sent: Monday, June 01, 2009 8:32 PM > > >>>>>> To: Dan Magenheimer > > >>>>>> Cc: Xen-Devel (E-mail) > > >>>>>> Subject: Re: [Xen-devel] blktap2: need more than 3 > > >> values to unpack > > >>>>>> > > >>>>>> > > >>>>>> The tap:aio:/pathto/file.img syntax that you're using in your > > >>>>>> config was > > >>>>>> changed before blktap2 was introduced. > > >>>>>> tap:tapdisk:aio:/pathto/file.img is > > >>>>>> apparently the correct syntax now, though the README didn't > > >>>>>> get updated to > > >>>>>> reflect this. Our blktap2 documentation is no better - > > >> I'll try to > > >>>>>> remedy that this week. > > >>>>>> > > >>>>>> > > >>>>>> If you're still seeing this error: > > >>>>>> "Error: 'file' object has no attribute 'find'" > > >>>>>> > > >>>>>> Then I might be able to help, but I'm not sure how to > > >>>>>> reproduce it. If > > >>>>>> you send a log file and config for this latter error I'll > > >>>>>> take a look. > > >>>>>> Yang seems to be reporting the same thing in another thread. > > >>>>>> > > >>>>>> --Dutch > > >>>>>> > > >>>>>> On Mon, 1 Jun 2009, Dan Magenheimer wrote: > > >>>>>> > > >>>>>>> Hmmm... trying blktap2 for the first time, using 19682. > > >>>>>>> I had thought that the syntax hadn't changed, but I am > > >>>>>>> getting what appears to be a parsing error on my vbd line. > > >>>>>>> > > >>>>>>> "ValueError: need more than 3 values to unpack" > > >>>>>>> > > >>>>>>> Thinking maybe that "w!" was the culprit, I changed > > >>>>>>> it to "w" with no change in result. > > >>>>>>> > > >>>>>>> Looking at the python code that generated the error, > > >>>>>>> I tried to figure out the syntax by experimentation > > >>>>>>> but without luck. I tried: > > >>>>>>> > > >>>>>>> tap:tapdisk:aio:/pathto/file.img > > >>>>>>> > > >>>>>>> but got "Error: 'file' object has no attribute 'find'" > > >>>>>>> > > >>>>>>> To see if I could use the old blktap, I tried > > >>>>>>> > > >>>>>>> tap:tapdisk:ioemu:/pathto/file.img > > >>>>>>> > > >>>>>>> but got the dreaded "Error: Device 768 (tap) could not be > > >>>>>>> connected. Hotplug scripts not working" > > >>>>>>> > > >>>>>>> Am I missing something in the syntax for blktap2? > > >>>>>>> Is there a how-to or readme I didn't find? Or > > >>>>>>> is there some required dependency I don't know about > > >>>>>>> that is missing? > > >>>>>>> > > >>>>>>> I thought maybe I had a bad install, so rebuilt and > > >>>>>>> reinstalled with the same result. > > >>>>>>> > > >>>>>>> xend.log and config file attached. > > >>>>>>> > > >>>>>>> Thanks, > > >>>>>>> Dan > > >>>>>>> > > >>>>>>> P.S. I am trying blktap2 because both blktap and > > >>>>>>> file-backed fail. Blktap sometimes reads garbage > > >>>>>>> from the file and > > >>>>>> > > >>>>>> _______________________________________________ > > >>>>>> Xen-devel mailing list > > >>>>>> Xen-devel@lists.xensource.com > > >>>>>> http://lists.xensource.com/xen-devel > > >>>>>> > > >>>> > > >>> > > >> > > > > > > _______________________________________________ > > > Xen-devel mailing list > > > Xen-devel@lists.xensource.com > > > http://lists.xensource.com/xen-devel > > > > > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > ^ permalink raw reply [flat|nested] 20+ messages in thread
* Dom0 crashing when built with c/s 881 (Was: blktap2: need more than 3 values to unpack) 2009-06-03 4:45 ` Dan Magenheimer @ 2009-06-03 17:35 ` Dan Magenheimer 2009-06-03 17:48 ` Keir Fraser 0 siblings, 1 reply; 20+ messages in thread From: Dan Magenheimer @ 2009-06-03 17:35 UTC (permalink / raw) To: dan.magenheimer, Keir Fraser, Xen-Devel (E-mail) OK, it appears that linux-2.6.18-xen.hg c/s 881 is causing my dom0 to crash. Dom0 boots successfully at 880 and fails with 881 or anything after. Any ideas? > -----Original Message----- > From: Dan Magenheimer > Sent: Tuesday, June 02, 2009 10:45 PM > To: Dan Magenheimer; Keir Fraser; Dutch Meyer; Xen-Devel (E-mail) > Subject: RE: [Xen-devel] blktap2: need more than 3 values to unpack > > > Followup: my dom0 boots failed with 888, boots fine with 876, > then to ensure no pilot error, I rebuilt 888 again and it > failed again. > > > -----Original Message----- > > From: Dan Magenheimer > > Sent: Tuesday, June 02, 2009 5:50 PM > > To: Keir Fraser; Dutch Meyer; Xen-Devel (E-mail) > > Subject: RE: [Xen-devel] blktap2: need more than 3 values to unpack > > > > > > Thanks. It is indeed a pilot error on my part but a bit > > more bizarre. I apparently have a linux-2.6-xen.hg directory > > as both a sister and a child to xen-unstable.hg. In this > > case the build apparently chooses the child. I was > > looking at and modifying the un-updated child so > > blktap2 wasn't even present yet. Removing the child > > causes the sibling to build. BUT! Now dom0 is > > crashing early on during boot. (This is an Intel > > Weybridge box.) I'll look into this further tomorrow. > > > > ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > > ata2.00: ATAPI, max UDMA/100 > > ata2.00: configured for UDMA/100 > > scsi2 : ahci > > ata3: SATA link down (SStatus 0 SControl 300) > > scsi3 : ahci > > ata4: SATA link down (SStatus 0 SControl 300) > > Vendor: ATA Model: ST3320620AS Rev: 3.AA > > Type: Direct-Access ANSI SCSI revision: 05 > > ata1: EH pending after completion, repeating EH (cnt=4) > > Vendor: LITE-ON Model: DVDRW LH-20A1S Rev: 9L03 > > Type: CD-ROM ANSI SCSI revision: 05 > > (XEN) PCI add device 00:1f.5 > > ata_piix 0000:00:1f.5: MAP [ P0 P2 P1 P3 ] > > ACPI: PCI Interrupt 0000:00:1f.5[B] -> GSI 19 (level, low) -> IRQ 16 > > ata5: SATA max UDMA/133 cmd 0x0 ctl 0x2 bmdma 0x0 irq 16 > > ata6: SATA max UDMA/133 cmd 0x0 ctl 0x2 bmdma 0x0 irq 16 > > scsi4 : ata_piix > > scsi5 : ata_piix > > device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: > > dm-devel@redhat.com > > Kernel panic - not syncing: Attempted to kill init! > > (XEN) Domain 0 crashed: rebooting machine in 5 seconds. > > > > > -----Original Message----- > > > From: Keir Fraser [mailto:keir.fraser@eu.citrix.com] > > > Sent: Tuesday, June 02, 2009 4:45 PM > > > To: Dan Magenheimer; Dutch Meyer; Xen-Devel (E-mail) > > > Subject: Re: [Xen-devel] blktap2: need more than 3 values > to unpack > > > > > > > > > Probably you had an old .config hanging around in your build > > > tree somewhere. > > > c/s 889 should fix this for a fresh build. > > > > > > -- Keir > > > > > > On 02/06/2009 18:33, "Dan Magenheimer" > > > <dan.magenheimer@oracle.com> wrote: > > > > > > > Thanks. Looks like a partial configuration patch got checked > > > > in for blktap2 (cs 886)? CONFIG_XEN_BLKDEV_TAP2 must be > > configured > > > > but afaict is not turned on by default (yet?). So a fresh > > > > xen-unstable tip doesn't build the blktap2 driver. See: > > > > > > > > > http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/3e01555dd227 > > > > > > > > (I'm guessing since this was submitted by Isaku that blktap2 > > > > shouldn't be the default on ia64?) > > > > > > > > Should CONFIG_XEN_BLKDEV_TAP2 be turned on by default, instead > > > > of CONFIG_XEN_BLKDEV_TAP, at least on x86? > > > > > > > > I tried modifying > > > > > > > > linux-2.6.18-xen.hg/buildconfigs/linux-defconfig_xen0_x86_32 > > > > > > > > (and also > > > > > > > > linux-2.6.18-xen.hg/buildconfigs/linux-defconfig_xen_x86_32) > > > > > > > > followed by: > > > > > > > > KERNELS=linux-2.6-xen0 make linux-2.6-xen-config > > > CONFIGMODE=oldconfig > > > > > > > > (I don't need or want to go through a manual config process) > > > > > > > > but BLKDEV_TAP is always selected, not BLKDEV_TAP2. > > > > > > > > Finally, I resorted to manually changing > > > > > > > > linux-2.6.18-xen.hg/drivers/xen/Kconfig > > > > > > > > and this succeeds in turning it on, but it just reverses the > > > > above checked-in patch, so I suspect that's not the right > > > > answer either. > > > > > > > >> -----Original Message----- > > > >> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] > > > >> Sent: Tuesday, June 02, 2009 9:05 AM > > > >> To: Dan Magenheimer > > > >> Subject: RE: [Xen-devel] blktap2: need more than 3 > > values to unpack > > > >> > > > >> > > > >> I think that you don't have the blktap2 driver loaded in > > > >> dom0. A clean > > > >> build/install of the dom0 kernel image should sort you out. If > > > >> drivers/xen/blktap2 is compiled in it should be setting up > > > >> these paths. > > > >> > > > >> Let me know if that fixes things and I'll make python > > spit out more > > > >> meaningful errors, otherwise we can try to figure out the > > > >> blktap2 kernel > > > >> code isn't working. > > > >> > > > >> --Dutch > > > >> > > > >> On Tue, 2 Jun 2009, Dan Magenheimer wrote: > > > >> > > > >>> It replies with "didn't find blktap-control in /proc/misc" > > > >>> > > > >>> If that fails, perhaps the path doesn't exist, but I looked > > > >>> and /sys/class/blktap2 doesn't exist. > > > >>> > > > >>>> -----Original Message----- > > > >>>> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] > > > >>>> Sent: Monday, June 01, 2009 10:37 PM > > > >>>> To: Dan Magenheimer > > > >>>> Subject: RE: [Xen-devel] blktap2: need more than 3 > > > values to unpack > > > >>>> > > > >>>> > > > >>>> Can you try this from the command line: > > > >>>> > > > >>>> tapdisk2 -n aio:/pathto/file.img > > > >>>> > > > >>>> If successful, this will create your aio device and print a > > > >>>> /dev device > > > >>>> associated with it. > > > >>>> > > > >>>> In that case you'll then be able to remove it with: > > > >>>> > > > >>>> echo 1 > /sys/class/blktap2/<disk>/remove > > > >>>> > > > >>>> Where <disk> will be obvious from the output of the > > > >> tapdisk2 command. > > > >>>> > > > >>>> However, I expect that this will fail. > > > >>>> > > > >>>> --Dutch > > > >>>> > > > >>>> On Mon, 1 Jun 2009, Dan Magenheimer wrote: > > > >>>> > > > >>>>>> Then I might be able to help, but I'm not sure how to > > > >>>>>> reproduce it. If > > > >>>>>> you send a log file and config for this latter error I'll > > > >>>>>> take a look. > > > >>>>> > > > >>>>> Here ya go. > > > >>>>> > > > >>>>> Thanks, > > > >>>>> Dan > > > >>>>> > > > >>>>>> -----Original Message----- > > > >>>>>> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] > > > >>>>>> Sent: Monday, June 01, 2009 8:32 PM > > > >>>>>> To: Dan Magenheimer > > > >>>>>> Cc: Xen-Devel (E-mail) > > > >>>>>> Subject: Re: [Xen-devel] blktap2: need more than 3 > > > >> values to unpack > > > >>>>>> > > > >>>>>> > > > >>>>>> The tap:aio:/pathto/file.img syntax that you're > using in your > > > >>>>>> config was > > > >>>>>> changed before blktap2 was introduced. > > > >>>>>> tap:tapdisk:aio:/pathto/file.img is > > > >>>>>> apparently the correct syntax now, though the README didn't > > > >>>>>> get updated to > > > >>>>>> reflect this. Our blktap2 documentation is no better - > > > >> I'll try to > > > >>>>>> remedy that this week. > > > >>>>>> > > > >>>>>> > > > >>>>>> If you're still seeing this error: > > > >>>>>> "Error: 'file' object has no attribute 'find'" > > > >>>>>> > > > >>>>>> Then I might be able to help, but I'm not sure how to > > > >>>>>> reproduce it. If > > > >>>>>> you send a log file and config for this latter error I'll > > > >>>>>> take a look. > > > >>>>>> Yang seems to be reporting the same thing in > another thread. > > > >>>>>> > > > >>>>>> --Dutch > > > >>>>>> > > > >>>>>> On Mon, 1 Jun 2009, Dan Magenheimer wrote: > > > >>>>>> > > > >>>>>>> Hmmm... trying blktap2 for the first time, using 19682. > > > >>>>>>> I had thought that the syntax hadn't changed, but I am > > > >>>>>>> getting what appears to be a parsing error on my vbd line. > > > >>>>>>> > > > >>>>>>> "ValueError: need more than 3 values to unpack" > > > >>>>>>> > > > >>>>>>> Thinking maybe that "w!" was the culprit, I changed > > > >>>>>>> it to "w" with no change in result. > > > >>>>>>> > > > >>>>>>> Looking at the python code that generated the error, > > > >>>>>>> I tried to figure out the syntax by experimentation > > > >>>>>>> but without luck. I tried: > > > >>>>>>> > > > >>>>>>> tap:tapdisk:aio:/pathto/file.img > > > >>>>>>> > > > >>>>>>> but got "Error: 'file' object has no attribute 'find'" > > > >>>>>>> > > > >>>>>>> To see if I could use the old blktap, I tried > > > >>>>>>> > > > >>>>>>> tap:tapdisk:ioemu:/pathto/file.img > > > >>>>>>> > > > >>>>>>> but got the dreaded "Error: Device 768 (tap) could not be > > > >>>>>>> connected. Hotplug scripts not working" > > > >>>>>>> > > > >>>>>>> Am I missing something in the syntax for blktap2? > > > >>>>>>> Is there a how-to or readme I didn't find? Or > > > >>>>>>> is there some required dependency I don't know about > > > >>>>>>> that is missing? > > > >>>>>>> > > > >>>>>>> I thought maybe I had a bad install, so rebuilt and > > > >>>>>>> reinstalled with the same result. > > > >>>>>>> > > > >>>>>>> xend.log and config file attached. > > > >>>>>>> > > > >>>>>>> Thanks, > > > >>>>>>> Dan > > > >>>>>>> > > > >>>>>>> P.S. I am trying blktap2 because both blktap and > > > >>>>>>> file-backed fail. Blktap sometimes reads garbage > > > >>>>>>> from the file and > > > >>>>>> > > > >>>>>> _______________________________________________ > > > >>>>>> Xen-devel mailing list > > > >>>>>> Xen-devel@lists.xensource.com > > > >>>>>> http://lists.xensource.com/xen-devel > > > >>>>>> > > > >>>> > > > >>> > > > >> > > > > > > > > _______________________________________________ > > > > Xen-devel mailing list > > > > Xen-devel@lists.xensource.com > > > > http://lists.xensource.com/xen-devel > > > > > > > > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel > > ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Dom0 crashing when built with c/s 881 (Was: blktap2: need more than 3 values to unpack) 2009-06-03 17:35 ` Dom0 crashing when built with c/s 881 (Was: blktap2: need more than 3 values to unpack) Dan Magenheimer @ 2009-06-03 17:48 ` Keir Fraser 2009-06-03 17:57 ` Dulloor 0 siblings, 1 reply; 20+ messages in thread From: Keir Fraser @ 2009-06-03 17:48 UTC (permalink / raw) To: Dan Magenheimer, Xen-Devel (E-mail); +Cc: Isaku Yamahata Perhaps post a diff of boot output with c/s 880 vs c/s 881. I've cc'ed Isaku, who submitted the patch that's causing your problem. -- Keir On 03/06/2009 18:35, "Dan Magenheimer" <dan.magenheimer@oracle.com> wrote: > OK, it appears that linux-2.6.18-xen.hg c/s 881 is causing > my dom0 to crash. Dom0 boots successfully at 880 and fails > with 881 or anything after. > > Any ideas? > >> -----Original Message----- >> From: Dan Magenheimer >> Sent: Tuesday, June 02, 2009 10:45 PM >> To: Dan Magenheimer; Keir Fraser; Dutch Meyer; Xen-Devel (E-mail) >> Subject: RE: [Xen-devel] blktap2: need more than 3 values to unpack >> >> >> Followup: my dom0 boots failed with 888, boots fine with 876, >> then to ensure no pilot error, I rebuilt 888 again and it >> failed again. >> >>> -----Original Message----- >>> From: Dan Magenheimer >>> Sent: Tuesday, June 02, 2009 5:50 PM >>> To: Keir Fraser; Dutch Meyer; Xen-Devel (E-mail) >>> Subject: RE: [Xen-devel] blktap2: need more than 3 values to unpack >>> >>> >>> Thanks. It is indeed a pilot error on my part but a bit >>> more bizarre. I apparently have a linux-2.6-xen.hg directory >>> as both a sister and a child to xen-unstable.hg. In this >>> case the build apparently chooses the child. I was >>> looking at and modifying the un-updated child so >>> blktap2 wasn't even present yet. Removing the child >>> causes the sibling to build. BUT! Now dom0 is >>> crashing early on during boot. (This is an Intel >>> Weybridge box.) I'll look into this further tomorrow. >>> >>> ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) >>> ata2.00: ATAPI, max UDMA/100 >>> ata2.00: configured for UDMA/100 >>> scsi2 : ahci >>> ata3: SATA link down (SStatus 0 SControl 300) >>> scsi3 : ahci >>> ata4: SATA link down (SStatus 0 SControl 300) >>> Vendor: ATA Model: ST3320620AS Rev: 3.AA >>> Type: Direct-Access ANSI SCSI revision: 05 >>> ata1: EH pending after completion, repeating EH (cnt=4) >>> Vendor: LITE-ON Model: DVDRW LH-20A1S Rev: 9L03 >>> Type: CD-ROM ANSI SCSI revision: 05 >>> (XEN) PCI add device 00:1f.5 >>> ata_piix 0000:00:1f.5: MAP [ P0 P2 P1 P3 ] >>> ACPI: PCI Interrupt 0000:00:1f.5[B] -> GSI 19 (level, low) -> IRQ 16 >>> ata5: SATA max UDMA/133 cmd 0x0 ctl 0x2 bmdma 0x0 irq 16 >>> ata6: SATA max UDMA/133 cmd 0x0 ctl 0x2 bmdma 0x0 irq 16 >>> scsi4 : ata_piix >>> scsi5 : ata_piix >>> device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: >>> dm-devel@redhat.com >>> Kernel panic - not syncing: Attempted to kill init! >>> (XEN) Domain 0 crashed: rebooting machine in 5 seconds. >>> >>>> -----Original Message----- >>>> From: Keir Fraser [mailto:keir.fraser@eu.citrix.com] >>>> Sent: Tuesday, June 02, 2009 4:45 PM >>>> To: Dan Magenheimer; Dutch Meyer; Xen-Devel (E-mail) >>>> Subject: Re: [Xen-devel] blktap2: need more than 3 values >> to unpack >>>> >>>> >>>> Probably you had an old .config hanging around in your build >>>> tree somewhere. >>>> c/s 889 should fix this for a fresh build. >>>> >>>> -- Keir >>>> >>>> On 02/06/2009 18:33, "Dan Magenheimer" >>>> <dan.magenheimer@oracle.com> wrote: >>>> >>>>> Thanks. Looks like a partial configuration patch got checked >>>>> in for blktap2 (cs 886)? CONFIG_XEN_BLKDEV_TAP2 must be >>> configured >>>>> but afaict is not turned on by default (yet?). So a fresh >>>>> xen-unstable tip doesn't build the blktap2 driver. See: >>>>> >>>>> >> http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/3e01555dd227 >>>>> >>>>> (I'm guessing since this was submitted by Isaku that blktap2 >>>>> shouldn't be the default on ia64?) >>>>> >>>>> Should CONFIG_XEN_BLKDEV_TAP2 be turned on by default, instead >>>>> of CONFIG_XEN_BLKDEV_TAP, at least on x86? >>>>> >>>>> I tried modifying >>>>> >>>>> linux-2.6.18-xen.hg/buildconfigs/linux-defconfig_xen0_x86_32 >>>>> >>>>> (and also >>>>> >>>>> linux-2.6.18-xen.hg/buildconfigs/linux-defconfig_xen_x86_32) >>>>> >>>>> followed by: >>>>> >>>>> KERNELS=linux-2.6-xen0 make linux-2.6-xen-config >>>> CONFIGMODE=oldconfig >>>>> >>>>> (I don't need or want to go through a manual config process) >>>>> >>>>> but BLKDEV_TAP is always selected, not BLKDEV_TAP2. >>>>> >>>>> Finally, I resorted to manually changing >>>>> >>>>> linux-2.6.18-xen.hg/drivers/xen/Kconfig >>>>> >>>>> and this succeeds in turning it on, but it just reverses the >>>>> above checked-in patch, so I suspect that's not the right >>>>> answer either. >>>>> >>>>>> -----Original Message----- >>>>>> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] >>>>>> Sent: Tuesday, June 02, 2009 9:05 AM >>>>>> To: Dan Magenheimer >>>>>> Subject: RE: [Xen-devel] blktap2: need more than 3 >>> values to unpack >>>>>> >>>>>> >>>>>> I think that you don't have the blktap2 driver loaded in >>>>>> dom0. A clean >>>>>> build/install of the dom0 kernel image should sort you out. If >>>>>> drivers/xen/blktap2 is compiled in it should be setting up >>>>>> these paths. >>>>>> >>>>>> Let me know if that fixes things and I'll make python >>> spit out more >>>>>> meaningful errors, otherwise we can try to figure out the >>>>>> blktap2 kernel >>>>>> code isn't working. >>>>>> >>>>>> --Dutch >>>>>> >>>>>> On Tue, 2 Jun 2009, Dan Magenheimer wrote: >>>>>> >>>>>>> It replies with "didn't find blktap-control in /proc/misc" >>>>>>> >>>>>>> If that fails, perhaps the path doesn't exist, but I looked >>>>>>> and /sys/class/blktap2 doesn't exist. >>>>>>> >>>>>>>> -----Original Message----- >>>>>>>> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] >>>>>>>> Sent: Monday, June 01, 2009 10:37 PM >>>>>>>> To: Dan Magenheimer >>>>>>>> Subject: RE: [Xen-devel] blktap2: need more than 3 >>>> values to unpack >>>>>>>> >>>>>>>> >>>>>>>> Can you try this from the command line: >>>>>>>> >>>>>>>> tapdisk2 -n aio:/pathto/file.img >>>>>>>> >>>>>>>> If successful, this will create your aio device and print a >>>>>>>> /dev device >>>>>>>> associated with it. >>>>>>>> >>>>>>>> In that case you'll then be able to remove it with: >>>>>>>> >>>>>>>> echo 1 > /sys/class/blktap2/<disk>/remove >>>>>>>> >>>>>>>> Where <disk> will be obvious from the output of the >>>>>> tapdisk2 command. >>>>>>>> >>>>>>>> However, I expect that this will fail. >>>>>>>> >>>>>>>> --Dutch >>>>>>>> >>>>>>>> On Mon, 1 Jun 2009, Dan Magenheimer wrote: >>>>>>>> >>>>>>>>>> Then I might be able to help, but I'm not sure how to >>>>>>>>>> reproduce it. If >>>>>>>>>> you send a log file and config for this latter error I'll >>>>>>>>>> take a look. >>>>>>>>> >>>>>>>>> Here ya go. >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> Dan >>>>>>>>> >>>>>>>>>> -----Original Message----- >>>>>>>>>> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] >>>>>>>>>> Sent: Monday, June 01, 2009 8:32 PM >>>>>>>>>> To: Dan Magenheimer >>>>>>>>>> Cc: Xen-Devel (E-mail) >>>>>>>>>> Subject: Re: [Xen-devel] blktap2: need more than 3 >>>>>> values to unpack >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> The tap:aio:/pathto/file.img syntax that you're >> using in your >>>>>>>>>> config was >>>>>>>>>> changed before blktap2 was introduced. >>>>>>>>>> tap:tapdisk:aio:/pathto/file.img is >>>>>>>>>> apparently the correct syntax now, though the README didn't >>>>>>>>>> get updated to >>>>>>>>>> reflect this. Our blktap2 documentation is no better - >>>>>> I'll try to >>>>>>>>>> remedy that this week. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> If you're still seeing this error: >>>>>>>>>> "Error: 'file' object has no attribute 'find'" >>>>>>>>>> >>>>>>>>>> Then I might be able to help, but I'm not sure how to >>>>>>>>>> reproduce it. If >>>>>>>>>> you send a log file and config for this latter error I'll >>>>>>>>>> take a look. >>>>>>>>>> Yang seems to be reporting the same thing in >> another thread. >>>>>>>>>> >>>>>>>>>> --Dutch >>>>>>>>>> >>>>>>>>>> On Mon, 1 Jun 2009, Dan Magenheimer wrote: >>>>>>>>>> >>>>>>>>>>> Hmmm... trying blktap2 for the first time, using 19682. >>>>>>>>>>> I had thought that the syntax hadn't changed, but I am >>>>>>>>>>> getting what appears to be a parsing error on my vbd line. >>>>>>>>>>> >>>>>>>>>>> "ValueError: need more than 3 values to unpack" >>>>>>>>>>> >>>>>>>>>>> Thinking maybe that "w!" was the culprit, I changed >>>>>>>>>>> it to "w" with no change in result. >>>>>>>>>>> >>>>>>>>>>> Looking at the python code that generated the error, >>>>>>>>>>> I tried to figure out the syntax by experimentation >>>>>>>>>>> but without luck. I tried: >>>>>>>>>>> >>>>>>>>>>> tap:tapdisk:aio:/pathto/file.img >>>>>>>>>>> >>>>>>>>>>> but got "Error: 'file' object has no attribute 'find'" >>>>>>>>>>> >>>>>>>>>>> To see if I could use the old blktap, I tried >>>>>>>>>>> >>>>>>>>>>> tap:tapdisk:ioemu:/pathto/file.img >>>>>>>>>>> >>>>>>>>>>> but got the dreaded "Error: Device 768 (tap) could not be >>>>>>>>>>> connected. Hotplug scripts not working" >>>>>>>>>>> >>>>>>>>>>> Am I missing something in the syntax for blktap2? >>>>>>>>>>> Is there a how-to or readme I didn't find? Or >>>>>>>>>>> is there some required dependency I don't know about >>>>>>>>>>> that is missing? >>>>>>>>>>> >>>>>>>>>>> I thought maybe I had a bad install, so rebuilt and >>>>>>>>>>> reinstalled with the same result. >>>>>>>>>>> >>>>>>>>>>> xend.log and config file attached. >>>>>>>>>>> >>>>>>>>>>> Thanks, >>>>>>>>>>> Dan >>>>>>>>>>> >>>>>>>>>>> P.S. I am trying blktap2 because both blktap and >>>>>>>>>>> file-backed fail. Blktap sometimes reads garbage >>>>>>>>>>> from the file and >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Xen-devel mailing list >>>>>>>>>> Xen-devel@lists.xensource.com >>>>>>>>>> http://lists.xensource.com/xen-devel >>>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Xen-devel mailing list >>>>> Xen-devel@lists.xensource.com >>>>> http://lists.xensource.com/xen-devel >>>> >>>> >>>> >>> >>> _______________________________________________ >>> Xen-devel mailing list >>> Xen-devel@lists.xensource.com >>> http://lists.xensource.com/xen-devel >>> ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Dom0 crashing when built with c/s 881 (Was: blktap2: need more than 3 values to unpack) 2009-06-03 17:48 ` Keir Fraser @ 2009-06-03 17:57 ` Dulloor 2009-06-03 18:45 ` Keir Fraser 0 siblings, 1 reply; 20+ messages in thread From: Dulloor @ 2009-06-03 17:57 UTC (permalink / raw) To: Keir Fraser; +Cc: Isaku Yamahata, Dan Magenheimer, Xen-Devel (E-mail) [-- Attachment #1.1: Type: text/plain, Size: 10911 bytes --] Is it better to have the new option added by c/s(CONFIG_PCI_IOMULTI) default 'n' ? -dulloor On Wed, Jun 3, 2009 at 1:48 PM, Keir Fraser <keir.fraser@eu.citrix.com>wrote: > Perhaps post a diff of boot output with c/s 880 vs c/s 881. I've cc'ed > Isaku, who submitted the patch that's causing your problem. > > -- Keir > > On 03/06/2009 18:35, "Dan Magenheimer" <dan.magenheimer@oracle.com> wrote: > > > OK, it appears that linux-2.6.18-xen.hg c/s 881 is causing > > my dom0 to crash. Dom0 boots successfully at 880 and fails > > with 881 or anything after. > > > > Any ideas? > > > >> -----Original Message----- > >> From: Dan Magenheimer > >> Sent: Tuesday, June 02, 2009 10:45 PM > >> To: Dan Magenheimer; Keir Fraser; Dutch Meyer; Xen-Devel (E-mail) > >> Subject: RE: [Xen-devel] blktap2: need more than 3 values to unpack > >> > >> > >> Followup: my dom0 boots failed with 888, boots fine with 876, > >> then to ensure no pilot error, I rebuilt 888 again and it > >> failed again. > >> > >>> -----Original Message----- > >>> From: Dan Magenheimer > >>> Sent: Tuesday, June 02, 2009 5:50 PM > >>> To: Keir Fraser; Dutch Meyer; Xen-Devel (E-mail) > >>> Subject: RE: [Xen-devel] blktap2: need more than 3 values to unpack > >>> > >>> > >>> Thanks. It is indeed a pilot error on my part but a bit > >>> more bizarre. I apparently have a linux-2.6-xen.hg directory > >>> as both a sister and a child to xen-unstable.hg. In this > >>> case the build apparently chooses the child. I was > >>> looking at and modifying the un-updated child so > >>> blktap2 wasn't even present yet. Removing the child > >>> causes the sibling to build. BUT! Now dom0 is > >>> crashing early on during boot. (This is an Intel > >>> Weybridge box.) I'll look into this further tomorrow. > >>> > >>> ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > >>> ata2.00: ATAPI, max UDMA/100 > >>> ata2.00: configured for UDMA/100 > >>> scsi2 : ahci > >>> ata3: SATA link down (SStatus 0 SControl 300) > >>> scsi3 : ahci > >>> ata4: SATA link down (SStatus 0 SControl 300) > >>> Vendor: ATA Model: ST3320620AS Rev: 3.AA > >>> Type: Direct-Access ANSI SCSI revision: 05 > >>> ata1: EH pending after completion, repeating EH (cnt=4) > >>> Vendor: LITE-ON Model: DVDRW LH-20A1S Rev: 9L03 > >>> Type: CD-ROM ANSI SCSI revision: 05 > >>> (XEN) PCI add device 00:1f.5 > >>> ata_piix 0000:00:1f.5: MAP [ P0 P2 P1 P3 ] > >>> ACPI: PCI Interrupt 0000:00:1f.5[B] -> GSI 19 (level, low) -> IRQ 16 > >>> ata5: SATA max UDMA/133 cmd 0x0 ctl 0x2 bmdma 0x0 irq 16 > >>> ata6: SATA max UDMA/133 cmd 0x0 ctl 0x2 bmdma 0x0 irq 16 > >>> scsi4 : ata_piix > >>> scsi5 : ata_piix > >>> device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: > >>> dm-devel@redhat.com > >>> Kernel panic - not syncing: Attempted to kill init! > >>> (XEN) Domain 0 crashed: rebooting machine in 5 seconds. > >>> > >>>> -----Original Message----- > >>>> From: Keir Fraser [mailto:keir.fraser@eu.citrix.com] > >>>> Sent: Tuesday, June 02, 2009 4:45 PM > >>>> To: Dan Magenheimer; Dutch Meyer; Xen-Devel (E-mail) > >>>> Subject: Re: [Xen-devel] blktap2: need more than 3 values > >> to unpack > >>>> > >>>> > >>>> Probably you had an old .config hanging around in your build > >>>> tree somewhere. > >>>> c/s 889 should fix this for a fresh build. > >>>> > >>>> -- Keir > >>>> > >>>> On 02/06/2009 18:33, "Dan Magenheimer" > >>>> <dan.magenheimer@oracle.com> wrote: > >>>> > >>>>> Thanks. Looks like a partial configuration patch got checked > >>>>> in for blktap2 (cs 886)? CONFIG_XEN_BLKDEV_TAP2 must be > >>> configured > >>>>> but afaict is not turned on by default (yet?). So a fresh > >>>>> xen-unstable tip doesn't build the blktap2 driver. See: > >>>>> > >>>>> > >> http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/3e01555dd227 > >>>>> > >>>>> (I'm guessing since this was submitted by Isaku that blktap2 > >>>>> shouldn't be the default on ia64?) > >>>>> > >>>>> Should CONFIG_XEN_BLKDEV_TAP2 be turned on by default, instead > >>>>> of CONFIG_XEN_BLKDEV_TAP, at least on x86? > >>>>> > >>>>> I tried modifying > >>>>> > >>>>> linux-2.6.18-xen.hg/buildconfigs/linux-defconfig_xen0_x86_32 > >>>>> > >>>>> (and also > >>>>> > >>>>> linux-2.6.18-xen.hg/buildconfigs/linux-defconfig_xen_x86_32) > >>>>> > >>>>> followed by: > >>>>> > >>>>> KERNELS=linux-2.6-xen0 make linux-2.6-xen-config > >>>> CONFIGMODE=oldconfig > >>>>> > >>>>> (I don't need or want to go through a manual config process) > >>>>> > >>>>> but BLKDEV_TAP is always selected, not BLKDEV_TAP2. > >>>>> > >>>>> Finally, I resorted to manually changing > >>>>> > >>>>> linux-2.6.18-xen.hg/drivers/xen/Kconfig > >>>>> > >>>>> and this succeeds in turning it on, but it just reverses the > >>>>> above checked-in patch, so I suspect that's not the right > >>>>> answer either. > >>>>> > >>>>>> -----Original Message----- > >>>>>> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] > >>>>>> Sent: Tuesday, June 02, 2009 9:05 AM > >>>>>> To: Dan Magenheimer > >>>>>> Subject: RE: [Xen-devel] blktap2: need more than 3 > >>> values to unpack > >>>>>> > >>>>>> > >>>>>> I think that you don't have the blktap2 driver loaded in > >>>>>> dom0. A clean > >>>>>> build/install of the dom0 kernel image should sort you out. If > >>>>>> drivers/xen/blktap2 is compiled in it should be setting up > >>>>>> these paths. > >>>>>> > >>>>>> Let me know if that fixes things and I'll make python > >>> spit out more > >>>>>> meaningful errors, otherwise we can try to figure out the > >>>>>> blktap2 kernel > >>>>>> code isn't working. > >>>>>> > >>>>>> --Dutch > >>>>>> > >>>>>> On Tue, 2 Jun 2009, Dan Magenheimer wrote: > >>>>>> > >>>>>>> It replies with "didn't find blktap-control in /proc/misc" > >>>>>>> > >>>>>>> If that fails, perhaps the path doesn't exist, but I looked > >>>>>>> and /sys/class/blktap2 doesn't exist. > >>>>>>> > >>>>>>>> -----Original Message----- > >>>>>>>> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] > >>>>>>>> Sent: Monday, June 01, 2009 10:37 PM > >>>>>>>> To: Dan Magenheimer > >>>>>>>> Subject: RE: [Xen-devel] blktap2: need more than 3 > >>>> values to unpack > >>>>>>>> > >>>>>>>> > >>>>>>>> Can you try this from the command line: > >>>>>>>> > >>>>>>>> tapdisk2 -n aio:/pathto/file.img > >>>>>>>> > >>>>>>>> If successful, this will create your aio device and print a > >>>>>>>> /dev device > >>>>>>>> associated with it. > >>>>>>>> > >>>>>>>> In that case you'll then be able to remove it with: > >>>>>>>> > >>>>>>>> echo 1 > /sys/class/blktap2/<disk>/remove > >>>>>>>> > >>>>>>>> Where <disk> will be obvious from the output of the > >>>>>> tapdisk2 command. > >>>>>>>> > >>>>>>>> However, I expect that this will fail. > >>>>>>>> > >>>>>>>> --Dutch > >>>>>>>> > >>>>>>>> On Mon, 1 Jun 2009, Dan Magenheimer wrote: > >>>>>>>> > >>>>>>>>>> Then I might be able to help, but I'm not sure how to > >>>>>>>>>> reproduce it. If > >>>>>>>>>> you send a log file and config for this latter error I'll > >>>>>>>>>> take a look. > >>>>>>>>> > >>>>>>>>> Here ya go. > >>>>>>>>> > >>>>>>>>> Thanks, > >>>>>>>>> Dan > >>>>>>>>> > >>>>>>>>>> -----Original Message----- > >>>>>>>>>> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] > >>>>>>>>>> Sent: Monday, June 01, 2009 8:32 PM > >>>>>>>>>> To: Dan Magenheimer > >>>>>>>>>> Cc: Xen-Devel (E-mail) > >>>>>>>>>> Subject: Re: [Xen-devel] blktap2: need more than 3 > >>>>>> values to unpack > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> The tap:aio:/pathto/file.img syntax that you're > >> using in your > >>>>>>>>>> config was > >>>>>>>>>> changed before blktap2 was introduced. > >>>>>>>>>> tap:tapdisk:aio:/pathto/file.img is > >>>>>>>>>> apparently the correct syntax now, though the README didn't > >>>>>>>>>> get updated to > >>>>>>>>>> reflect this. Our blktap2 documentation is no better - > >>>>>> I'll try to > >>>>>>>>>> remedy that this week. > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> If you're still seeing this error: > >>>>>>>>>> "Error: 'file' object has no attribute 'find'" > >>>>>>>>>> > >>>>>>>>>> Then I might be able to help, but I'm not sure how to > >>>>>>>>>> reproduce it. If > >>>>>>>>>> you send a log file and config for this latter error I'll > >>>>>>>>>> take a look. > >>>>>>>>>> Yang seems to be reporting the same thing in > >> another thread. > >>>>>>>>>> > >>>>>>>>>> --Dutch > >>>>>>>>>> > >>>>>>>>>> On Mon, 1 Jun 2009, Dan Magenheimer wrote: > >>>>>>>>>> > >>>>>>>>>>> Hmmm... trying blktap2 for the first time, using 19682. > >>>>>>>>>>> I had thought that the syntax hadn't changed, but I am > >>>>>>>>>>> getting what appears to be a parsing error on my vbd line. > >>>>>>>>>>> > >>>>>>>>>>> "ValueError: need more than 3 values to unpack" > >>>>>>>>>>> > >>>>>>>>>>> Thinking maybe that "w!" was the culprit, I changed > >>>>>>>>>>> it to "w" with no change in result. > >>>>>>>>>>> > >>>>>>>>>>> Looking at the python code that generated the error, > >>>>>>>>>>> I tried to figure out the syntax by experimentation > >>>>>>>>>>> but without luck. I tried: > >>>>>>>>>>> > >>>>>>>>>>> tap:tapdisk:aio:/pathto/file.img > >>>>>>>>>>> > >>>>>>>>>>> but got "Error: 'file' object has no attribute 'find'" > >>>>>>>>>>> > >>>>>>>>>>> To see if I could use the old blktap, I tried > >>>>>>>>>>> > >>>>>>>>>>> tap:tapdisk:ioemu:/pathto/file.img > >>>>>>>>>>> > >>>>>>>>>>> but got the dreaded "Error: Device 768 (tap) could not be > >>>>>>>>>>> connected. Hotplug scripts not working" > >>>>>>>>>>> > >>>>>>>>>>> Am I missing something in the syntax for blktap2? > >>>>>>>>>>> Is there a how-to or readme I didn't find? Or > >>>>>>>>>>> is there some required dependency I don't know about > >>>>>>>>>>> that is missing? > >>>>>>>>>>> > >>>>>>>>>>> I thought maybe I had a bad install, so rebuilt and > >>>>>>>>>>> reinstalled with the same result. > >>>>>>>>>>> > >>>>>>>>>>> xend.log and config file attached. > >>>>>>>>>>> > >>>>>>>>>>> Thanks, > >>>>>>>>>>> Dan > >>>>>>>>>>> > >>>>>>>>>>> P.S. I am trying blktap2 because both blktap and > >>>>>>>>>>> file-backed fail. Blktap sometimes reads garbage > >>>>>>>>>>> from the file and > >>>>>>>>>> > >>>>>>>>>> _______________________________________________ > >>>>>>>>>> Xen-devel mailing list > >>>>>>>>>> Xen-devel@lists.xensource.com > >>>>>>>>>> http://lists.xensource.com/xen-devel > >>>>>>>>>> > >>>>>>>> > >>>>>>> > >>>>>> > >>>>> > >>>>> _______________________________________________ > >>>>> Xen-devel mailing list > >>>>> Xen-devel@lists.xensource.com > >>>>> http://lists.xensource.com/xen-devel > >>>> > >>>> > >>>> > >>> > >>> _______________________________________________ > >>> Xen-devel mailing list > >>> Xen-devel@lists.xensource.com > >>> http://lists.xensource.com/xen-devel > >>> > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > [-- Attachment #1.2: Type: text/html, Size: 18704 bytes --] [-- Attachment #2: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Dom0 crashing when built with c/s 881 (Was: blktap2: need more than 3 values to unpack) 2009-06-03 17:57 ` Dulloor @ 2009-06-03 18:45 ` Keir Fraser 2009-06-03 20:15 ` Dan Magenheimer 2009-06-04 4:13 ` Isaku Yamahata 0 siblings, 2 replies; 20+ messages in thread From: Keir Fraser @ 2009-06-03 18:45 UTC (permalink / raw) To: Dulloor; +Cc: Isaku Yamahata, Dan Magenheimer, Xen-Devel (E-mail) Depends on the feature's impact when unused. -- Keir On 03/06/2009 18:57, "Dulloor" <dulloor@gmail.com> wrote: > Is it better to have the new option added by c/s(CONFIG_PCI_IOMULTI) default > 'n' ? > > -dulloor > > On Wed, Jun 3, 2009 at 1:48 PM, Keir Fraser <keir.fraser@eu.citrix.com> wrote: >> Perhaps post a diff of boot output with c/s 880 vs c/s 881. I've cc'ed >> Isaku, who submitted the patch that's causing your problem. >> >> -- Keir >> >> On 03/06/2009 18:35, "Dan Magenheimer" <dan.magenheimer@oracle.com> wrote: >> >>> OK, it appears that linux-2.6.18-xen.hg c/s 881 is causing >>> my dom0 to crash. Dom0 boots successfully at 880 and fails >>> with 881 or anything after. >>> >>> Any ideas? >>> >>>> -----Original Message----- >>>> From: Dan Magenheimer >>>> Sent: Tuesday, June 02, 2009 10:45 PM >>>> To: Dan Magenheimer; Keir Fraser; Dutch Meyer; Xen-Devel (E-mail) >>>> Subject: RE: [Xen-devel] blktap2: need more than 3 values to unpack >>>> >>>> >>>> Followup: my dom0 boots failed with 888, boots fine with 876, >>>> then to ensure no pilot error, I rebuilt 888 again and it >>>> failed again. >>>> >>>>> -----Original Message----- >>>>> From: Dan Magenheimer >>>>> Sent: Tuesday, June 02, 2009 5:50 PM >>>>> To: Keir Fraser; Dutch Meyer; Xen-Devel (E-mail) >>>>> Subject: RE: [Xen-devel] blktap2: need more than 3 values to unpack >>>>> >>>>> >>>>> Thanks. It is indeed a pilot error on my part but a bit >>>>> more bizarre. I apparently have a linux-2.6-xen.hg directory >>>>> as both a sister and a child to xen-unstable.hg. In this >>>>> case the build apparently chooses the child. I was >>>>> looking at and modifying the un-updated child so >>>>> blktap2 wasn't even present yet. Removing the child >>>>> causes the sibling to build. BUT! Now dom0 is >>>>> crashing early on during boot. (This is an Intel >>>>> Weybridge box.) I'll look into this further tomorrow. >>>>> >>>>> ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) >>>>> ata2.00: ATAPI, max UDMA/100 >>>>> ata2.00: configured for UDMA/100 >>>>> scsi2 : ahci >>>>> ata3: SATA link down (SStatus 0 SControl 300) >>>>> scsi3 : ahci >>>>> ata4: SATA link down (SStatus 0 SControl 300) >>>>> Vendor: ATA Model: ST3320620AS Rev: 3.AA >>>>> Type: Direct-Access ANSI SCSI revision: 05 >>>>> ata1: EH pending after completion, repeating EH (cnt=4) >>>>> Vendor: LITE-ON Model: DVDRW LH-20A1S Rev: 9L03 >>>>> Type: CD-ROM ANSI SCSI revision: 05 >>>>> (XEN) PCI add device 00:1f.5 >>>>> ata_piix 0000:00:1f.5: MAP [ P0 P2 P1 P3 ] >>>>> ACPI: PCI Interrupt 0000:00:1f.5[B] -> GSI 19 (level, low) -> IRQ 16 >>>>> ata5: SATA max UDMA/133 cmd 0x0 ctl 0x2 bmdma 0x0 irq 16 >>>>> ata6: SATA max UDMA/133 cmd 0x0 ctl 0x2 bmdma 0x0 irq 16 >>>>> scsi4 : ata_piix >>>>> scsi5 : ata_piix >>>>> device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: >>>>> dm-devel@redhat.com >>>>> Kernel panic - not syncing: Attempted to kill init! >>>>> (XEN) Domain 0 crashed: rebooting machine in 5 seconds. >>>>> >>>>>> -----Original Message----- >>>>>> From: Keir Fraser [mailto:keir.fraser@eu.citrix.com] >>>>>> Sent: Tuesday, June 02, 2009 4:45 PM >>>>>> To: Dan Magenheimer; Dutch Meyer; Xen-Devel (E-mail) >>>>>> Subject: Re: [Xen-devel] blktap2: need more than 3 values >>>> to unpack >>>>>> >>>>>> >>>>>> Probably you had an old .config hanging around in your build >>>>>> tree somewhere. >>>>>> c/s 889 should fix this for a fresh build. >>>>>> >>>>>> -- Keir >>>>>> >>>>>> On 02/06/2009 18:33, "Dan Magenheimer" >>>>>> <dan.magenheimer@oracle.com> wrote: >>>>>> >>>>>>> Thanks. Looks like a partial configuration patch got checked >>>>>>> in for blktap2 (cs 886)? CONFIG_XEN_BLKDEV_TAP2 must be >>>>> configured >>>>>>> but afaict is not turned on by default (yet?). So a fresh >>>>>>> xen-unstable tip doesn't build the blktap2 driver. See: >>>>>>> >>>>>>> >>>> http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/3e01555dd227 >>>>>>> >>>>>>> (I'm guessing since this was submitted by Isaku that blktap2 >>>>>>> shouldn't be the default on ia64?) >>>>>>> >>>>>>> Should CONFIG_XEN_BLKDEV_TAP2 be turned on by default, instead >>>>>>> of CONFIG_XEN_BLKDEV_TAP, at least on x86? >>>>>>> >>>>>>> I tried modifying >>>>>>> >>>>>>> linux-2.6.18-xen.hg/buildconfigs/linux-defconfig_xen0_x86_32 >>>>>>> >>>>>>> (and also >>>>>>> >>>>>>> linux-2.6.18-xen.hg/buildconfigs/linux-defconfig_xen_x86_32) >>>>>>> >>>>>>> followed by: >>>>>>> >>>>>>> KERNELS=linux-2.6-xen0 make linux-2.6-xen-config >>>>>> CONFIGMODE=oldconfig >>>>>>> >>>>>>> (I don't need or want to go through a manual config process) >>>>>>> >>>>>>> but BLKDEV_TAP is always selected, not BLKDEV_TAP2. >>>>>>> >>>>>>> Finally, I resorted to manually changing >>>>>>> >>>>>>> linux-2.6.18-xen.hg/drivers/xen/Kconfig >>>>>>> >>>>>>> and this succeeds in turning it on, but it just reverses the >>>>>>> above checked-in patch, so I suspect that's not the right >>>>>>> answer either. >>>>>>> >>>>>>>> -----Original Message----- >>>>>>>> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] >>>>>>>> Sent: Tuesday, June 02, 2009 9:05 AM >>>>>>>> To: Dan Magenheimer >>>>>>>> Subject: RE: [Xen-devel] blktap2: need more than 3 >>>>> values to unpack >>>>>>>> >>>>>>>> >>>>>>>> I think that you don't have the blktap2 driver loaded in >>>>>>>> dom0. A clean >>>>>>>> build/install of the dom0 kernel image should sort you out. If >>>>>>>> drivers/xen/blktap2 is compiled in it should be setting up >>>>>>>> these paths. >>>>>>>> >>>>>>>> Let me know if that fixes things and I'll make python >>>>> spit out more >>>>>>>> meaningful errors, otherwise we can try to figure out the >>>>>>>> blktap2 kernel >>>>>>>> code isn't working. >>>>>>>> >>>>>>>> --Dutch >>>>>>>> >>>>>>>> On Tue, 2 Jun 2009, Dan Magenheimer wrote: >>>>>>>> >>>>>>>>> It replies with "didn't find blktap-control in /proc/misc" >>>>>>>>> >>>>>>>>> If that fails, perhaps the path doesn't exist, but I looked >>>>>>>>> and /sys/class/blktap2 doesn't exist. >>>>>>>>> >>>>>>>>>> -----Original Message----- >>>>>>>>>> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] >>>>>>>>>> Sent: Monday, June 01, 2009 10:37 PM >>>>>>>>>> To: Dan Magenheimer >>>>>>>>>> Subject: RE: [Xen-devel] blktap2: need more than 3 >>>>>> values to unpack >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Can you try this from the command line: >>>>>>>>>> >>>>>>>>>> tapdisk2 -n aio:/pathto/file.img >>>>>>>>>> >>>>>>>>>> If successful, this will create your aio device and print a >>>>>>>>>> /dev device >>>>>>>>>> associated with it. >>>>>>>>>> >>>>>>>>>> In that case you'll then be able to remove it with: >>>>>>>>>> >>>>>>>>>> echo 1 > /sys/class/blktap2/<disk>/remove >>>>>>>>>> >>>>>>>>>> Where <disk> will be obvious from the output of the >>>>>>>> tapdisk2 command. >>>>>>>>>> >>>>>>>>>> However, I expect that this will fail. >>>>>>>>>> >>>>>>>>>> --Dutch >>>>>>>>>> >>>>>>>>>> On Mon, 1 Jun 2009, Dan Magenheimer wrote: >>>>>>>>>> >>>>>>>>>>>> Then I might be able to help, but I'm not sure how to >>>>>>>>>>>> reproduce it. If >>>>>>>>>>>> you send a log file and config for this latter error I'll >>>>>>>>>>>> take a look. >>>>>>>>>>> >>>>>>>>>>> Here ya go. >>>>>>>>>>> >>>>>>>>>>> Thanks, >>>>>>>>>>> Dan >>>>>>>>>>> >>>>>>>>>>>> -----Original Message----- >>>>>>>>>>>> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] >>>>>>>>>>>> Sent: Monday, June 01, 2009 8:32 PM >>>>>>>>>>>> To: Dan Magenheimer >>>>>>>>>>>> Cc: Xen-Devel (E-mail) >>>>>>>>>>>> Subject: Re: [Xen-devel] blktap2: need more than 3 >>>>>>>> values to unpack >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> The tap:aio:/pathto/file.img syntax that you're >>>> using in your >>>>>>>>>>>> config was >>>>>>>>>>>> changed before blktap2 was introduced. >>>>>>>>>>>> tap:tapdisk:aio:/pathto/file.img is >>>>>>>>>>>> apparently the correct syntax now, though the README didn't >>>>>>>>>>>> get updated to >>>>>>>>>>>> reflect this. Our blktap2 documentation is no better - >>>>>>>> I'll try to >>>>>>>>>>>> remedy that this week. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> If you're still seeing this error: >>>>>>>>>>>> "Error: 'file' object has no attribute 'find'" >>>>>>>>>>>> >>>>>>>>>>>> Then I might be able to help, but I'm not sure how to >>>>>>>>>>>> reproduce it. If >>>>>>>>>>>> you send a log file and config for this latter error I'll >>>>>>>>>>>> take a look. >>>>>>>>>>>> Yang seems to be reporting the same thing in >>>> another thread. >>>>>>>>>>>> >>>>>>>>>>>> --Dutch >>>>>>>>>>>> >>>>>>>>>>>> On Mon, 1 Jun 2009, Dan Magenheimer wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hmmm... trying blktap2 for the first time, using 19682. >>>>>>>>>>>>> I had thought that the syntax hadn't changed, but I am >>>>>>>>>>>>> getting what appears to be a parsing error on my vbd line. >>>>>>>>>>>>> >>>>>>>>>>>>> "ValueError: need more than 3 values to unpack" >>>>>>>>>>>>> >>>>>>>>>>>>> Thinking maybe that "w!" was the culprit, I changed >>>>>>>>>>>>> it to "w" with no change in result. >>>>>>>>>>>>> >>>>>>>>>>>>> Looking at the python code that generated the error, >>>>>>>>>>>>> I tried to figure out the syntax by experimentation >>>>>>>>>>>>> but without luck. I tried: >>>>>>>>>>>>> >>>>>>>>>>>>> tap:tapdisk:aio:/pathto/file.img >>>>>>>>>>>>> >>>>>>>>>>>>> but got "Error: 'file' object has no attribute 'find'" >>>>>>>>>>>>> >>>>>>>>>>>>> To see if I could use the old blktap, I tried >>>>>>>>>>>>> >>>>>>>>>>>>> tap:tapdisk:ioemu:/pathto/file.img >>>>>>>>>>>>> >>>>>>>>>>>>> but got the dreaded "Error: Device 768 (tap) could not be >>>>>>>>>>>>> connected. Hotplug scripts not working" >>>>>>>>>>>>> >>>>>>>>>>>>> Am I missing something in the syntax for blktap2? >>>>>>>>>>>>> Is there a how-to or readme I didn't find? Or >>>>>>>>>>>>> is there some required dependency I don't know about >>>>>>>>>>>>> that is missing? >>>>>>>>>>>>> >>>>>>>>>>>>> I thought maybe I had a bad install, so rebuilt and >>>>>>>>>>>>> reinstalled with the same result. >>>>>>>>>>>>> >>>>>>>>>>>>> xend.log and config file attached. >>>>>>>>>>>>> >>>>>>>>>>>>> Thanks, >>>>>>>>>>>>> Dan >>>>>>>>>>>>> >>>>>>>>>>>>> P.S. I am trying blktap2 because both blktap and >>>>>>>>>>>>> file-backed fail. Blktap sometimes reads garbage >>>>>>>>>>>>> from the file and >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Xen-devel mailing list >>>>>>>>>>>> Xen-devel@lists.xensource.com >>>>>>>>>>>> http://lists.xensource.com/xen-devel >>>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Xen-devel mailing list >>>>>>> Xen-devel@lists.xensource.com >>>>>>> http://lists.xensource.com/xen-devel >>>>>> >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Xen-devel mailing list >>>>> Xen-devel@lists.xensource.com >>>>> http://lists.xensource.com/xen-devel >>>>> >> >> >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel > > ^ permalink raw reply [flat|nested] 20+ messages in thread
* RE: Dom0 crashing when built with c/s 881 (Was: blktap2: need more than 3 values to unpack) 2009-06-03 18:45 ` Keir Fraser @ 2009-06-03 20:15 ` Dan Magenheimer 2009-06-03 20:46 ` Keir Fraser 2009-06-04 4:13 ` Isaku Yamahata 1 sibling, 1 reply; 20+ messages in thread From: Dan Magenheimer @ 2009-06-03 20:15 UTC (permalink / raw) To: Keir Fraser, Dulloor, Isaku Yamahata; +Cc: Xen-Devel (E-mail) [-- Attachment #1: Type: text/plain, Size: 13220 bytes --] > > Is it better to have the new option added by > > c/s(CONFIG_PCI_IOMULTI) default 'n' ? Turning off that option doesn't stop my dom0 from crashing. Reverting 881 DOES stop my dom0 from crashing. Attached are the boot output for fail and success (the only difference between the two dom0's is the success has 881 reverted). Of note, the fail log has three lines of the type: "Driver 'xxx' needs updating - please use bus_type methods" (xxx = usbfs, hub, usb) and the success log has a line that says: "PCI IO multiplexer device installed" which is missing in the fail log. > -----Original Message----- > From: Keir Fraser [mailto:keir.fraser@eu.citrix.com] > Sent: Wednesday, June 03, 2009 12:45 PM > To: Dulloor > Cc: Isaku Yamahata; Dan Magenheimer; Xen-Devel (E-mail) > Subject: Re: Dom0 crashing when built with c/s 881 (Was: [Xen-devel] > blktap2: need more than 3 values to unpack) > > > Depends on the feature's impact when unused. > > -- Keir > > On 03/06/2009 18:57, "Dulloor" <dulloor@gmail.com> wrote: > > > Is it better to have the new option added by > c/s(CONFIG_PCI_IOMULTI) default > > 'n' ? > > > > -dulloor > > > > On Wed, Jun 3, 2009 at 1:48 PM, Keir Fraser > <keir.fraser@eu.citrix.com> wrote: > >> Perhaps post a diff of boot output with c/s 880 vs c/s > 881. I've cc'ed > >> Isaku, who submitted the patch that's causing your problem. > >> > >> -- Keir > >> > >> On 03/06/2009 18:35, "Dan Magenheimer" > <dan.magenheimer@oracle.com> wrote: > >> > >>> OK, it appears that linux-2.6.18-xen.hg c/s 881 is causing > >>> my dom0 to crash. Dom0 boots successfully at 880 and fails > >>> with 881 or anything after. > >>> > >>> Any ideas? > >>> > >>>> -----Original Message----- > >>>> From: Dan Magenheimer > >>>> Sent: Tuesday, June 02, 2009 10:45 PM > >>>> To: Dan Magenheimer; Keir Fraser; Dutch Meyer; Xen-Devel (E-mail) > >>>> Subject: RE: [Xen-devel] blktap2: need more than 3 > values to unpack > >>>> > >>>> > >>>> Followup: my dom0 boots failed with 888, boots fine with 876, > >>>> then to ensure no pilot error, I rebuilt 888 again and it > >>>> failed again. > >>>> > >>>>> -----Original Message----- > >>>>> From: Dan Magenheimer > >>>>> Sent: Tuesday, June 02, 2009 5:50 PM > >>>>> To: Keir Fraser; Dutch Meyer; Xen-Devel (E-mail) > >>>>> Subject: RE: [Xen-devel] blktap2: need more than 3 > values to unpack > >>>>> > >>>>> > >>>>> Thanks. It is indeed a pilot error on my part but a bit > >>>>> more bizarre. I apparently have a linux-2.6-xen.hg directory > >>>>> as both a sister and a child to xen-unstable.hg. In this > >>>>> case the build apparently chooses the child. I was > >>>>> looking at and modifying the un-updated child so > >>>>> blktap2 wasn't even present yet. Removing the child > >>>>> causes the sibling to build. BUT! Now dom0 is > >>>>> crashing early on during boot. (This is an Intel > >>>>> Weybridge box.) I'll look into this further tomorrow. > >>>>> > >>>>> ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > >>>>> ata2.00: ATAPI, max UDMA/100 > >>>>> ata2.00: configured for UDMA/100 > >>>>> scsi2 : ahci > >>>>> ata3: SATA link down (SStatus 0 SControl 300) > >>>>> scsi3 : ahci > >>>>> ata4: SATA link down (SStatus 0 SControl 300) > >>>>> Vendor: ATA Model: ST3320620AS Rev: 3.AA > >>>>> Type: Direct-Access ANSI SCSI > revision: 05 > >>>>> ata1: EH pending after completion, repeating EH (cnt=4) > >>>>> Vendor: LITE-ON Model: DVDRW LH-20A1S Rev: 9L03 > >>>>> Type: CD-ROM ANSI SCSI > revision: 05 > >>>>> (XEN) PCI add device 00:1f.5 > >>>>> ata_piix 0000:00:1f.5: MAP [ P0 P2 P1 P3 ] > >>>>> ACPI: PCI Interrupt 0000:00:1f.5[B] -> GSI 19 (level, > low) -> IRQ 16 > >>>>> ata5: SATA max UDMA/133 cmd 0x0 ctl 0x2 bmdma 0x0 irq 16 > >>>>> ata6: SATA max UDMA/133 cmd 0x0 ctl 0x2 bmdma 0x0 irq 16 > >>>>> scsi4 : ata_piix > >>>>> scsi5 : ata_piix > >>>>> device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: > >>>>> dm-devel@redhat.com > >>>>> Kernel panic - not syncing: Attempted to kill init! > >>>>> (XEN) Domain 0 crashed: rebooting machine in 5 seconds. > >>>>> > >>>>>> -----Original Message----- > >>>>>> From: Keir Fraser [mailto:keir.fraser@eu.citrix.com] > >>>>>> Sent: Tuesday, June 02, 2009 4:45 PM > >>>>>> To: Dan Magenheimer; Dutch Meyer; Xen-Devel (E-mail) > >>>>>> Subject: Re: [Xen-devel] blktap2: need more than 3 values > >>>> to unpack > >>>>>> > >>>>>> > >>>>>> Probably you had an old .config hanging around in your build > >>>>>> tree somewhere. > >>>>>> c/s 889 should fix this for a fresh build. > >>>>>> > >>>>>> -- Keir > >>>>>> > >>>>>> On 02/06/2009 18:33, "Dan Magenheimer" > >>>>>> <dan.magenheimer@oracle.com> wrote: > >>>>>> > >>>>>>> Thanks. Looks like a partial configuration patch got checked > >>>>>>> in for blktap2 (cs 886)? CONFIG_XEN_BLKDEV_TAP2 must be > >>>>> configured > >>>>>>> but afaict is not turned on by default (yet?). So a fresh > >>>>>>> xen-unstable tip doesn't build the blktap2 driver. See: > >>>>>>> > >>>>>>> > >>>> http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/3e01555dd227 > >>>>>>> > >>>>>>> (I'm guessing since this was submitted by Isaku that blktap2 > >>>>>>> shouldn't be the default on ia64?) > >>>>>>> > >>>>>>> Should CONFIG_XEN_BLKDEV_TAP2 be turned on by default, instead > >>>>>>> of CONFIG_XEN_BLKDEV_TAP, at least on x86? > >>>>>>> > >>>>>>> I tried modifying > >>>>>>> > >>>>>>> linux-2.6.18-xen.hg/buildconfigs/linux-defconfig_xen0_x86_32 > >>>>>>> > >>>>>>> (and also > >>>>>>> > >>>>>>> linux-2.6.18-xen.hg/buildconfigs/linux-defconfig_xen_x86_32) > >>>>>>> > >>>>>>> followed by: > >>>>>>> > >>>>>>> KERNELS=linux-2.6-xen0 make linux-2.6-xen-config > >>>>>> CONFIGMODE=oldconfig > >>>>>>> > >>>>>>> (I don't need or want to go through a manual config process) > >>>>>>> > >>>>>>> but BLKDEV_TAP is always selected, not BLKDEV_TAP2. > >>>>>>> > >>>>>>> Finally, I resorted to manually changing > >>>>>>> > >>>>>>> linux-2.6.18-xen.hg/drivers/xen/Kconfig > >>>>>>> > >>>>>>> and this succeeds in turning it on, but it just reverses the > >>>>>>> above checked-in patch, so I suspect that's not the right > >>>>>>> answer either. > >>>>>>> > >>>>>>>> -----Original Message----- > >>>>>>>> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] > >>>>>>>> Sent: Tuesday, June 02, 2009 9:05 AM > >>>>>>>> To: Dan Magenheimer > >>>>>>>> Subject: RE: [Xen-devel] blktap2: need more than 3 > >>>>> values to unpack > >>>>>>>> > >>>>>>>> > >>>>>>>> I think that you don't have the blktap2 driver loaded in > >>>>>>>> dom0. A clean > >>>>>>>> build/install of the dom0 kernel image should sort > you out. If > >>>>>>>> drivers/xen/blktap2 is compiled in it should be setting up > >>>>>>>> these paths. > >>>>>>>> > >>>>>>>> Let me know if that fixes things and I'll make python > >>>>> spit out more > >>>>>>>> meaningful errors, otherwise we can try to figure out the > >>>>>>>> blktap2 kernel > >>>>>>>> code isn't working. > >>>>>>>> > >>>>>>>> --Dutch > >>>>>>>> > >>>>>>>> On Tue, 2 Jun 2009, Dan Magenheimer wrote: > >>>>>>>> > >>>>>>>>> It replies with "didn't find blktap-control in /proc/misc" > >>>>>>>>> > >>>>>>>>> If that fails, perhaps the path doesn't exist, but I looked > >>>>>>>>> and /sys/class/blktap2 doesn't exist. > >>>>>>>>> > >>>>>>>>>> -----Original Message----- > >>>>>>>>>> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] > >>>>>>>>>> Sent: Monday, June 01, 2009 10:37 PM > >>>>>>>>>> To: Dan Magenheimer > >>>>>>>>>> Subject: RE: [Xen-devel] blktap2: need more than 3 > >>>>>> values to unpack > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> Can you try this from the command line: > >>>>>>>>>> > >>>>>>>>>> tapdisk2 -n aio:/pathto/file.img > >>>>>>>>>> > >>>>>>>>>> If successful, this will create your aio device and print a > >>>>>>>>>> /dev device > >>>>>>>>>> associated with it. > >>>>>>>>>> > >>>>>>>>>> In that case you'll then be able to remove it with: > >>>>>>>>>> > >>>>>>>>>> echo 1 > /sys/class/blktap2/<disk>/remove > >>>>>>>>>> > >>>>>>>>>> Where <disk> will be obvious from the output of the > >>>>>>>> tapdisk2 command. > >>>>>>>>>> > >>>>>>>>>> However, I expect that this will fail. > >>>>>>>>>> > >>>>>>>>>> --Dutch > >>>>>>>>>> > >>>>>>>>>> On Mon, 1 Jun 2009, Dan Magenheimer wrote: > >>>>>>>>>> > >>>>>>>>>>>> Then I might be able to help, but I'm not sure how to > >>>>>>>>>>>> reproduce it. If > >>>>>>>>>>>> you send a log file and config for this latter error I'll > >>>>>>>>>>>> take a look. > >>>>>>>>>>> > >>>>>>>>>>> Here ya go. > >>>>>>>>>>> > >>>>>>>>>>> Thanks, > >>>>>>>>>>> Dan > >>>>>>>>>>> > >>>>>>>>>>>> -----Original Message----- > >>>>>>>>>>>> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] > >>>>>>>>>>>> Sent: Monday, June 01, 2009 8:32 PM > >>>>>>>>>>>> To: Dan Magenheimer > >>>>>>>>>>>> Cc: Xen-Devel (E-mail) > >>>>>>>>>>>> Subject: Re: [Xen-devel] blktap2: need more than 3 > >>>>>>>> values to unpack > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> The tap:aio:/pathto/file.img syntax that you're > >>>> using in your > >>>>>>>>>>>> config was > >>>>>>>>>>>> changed before blktap2 was introduced. > >>>>>>>>>>>> tap:tapdisk:aio:/pathto/file.img is > >>>>>>>>>>>> apparently the correct syntax now, though the > README didn't > >>>>>>>>>>>> get updated to > >>>>>>>>>>>> reflect this. Our blktap2 documentation is no better - > >>>>>>>> I'll try to > >>>>>>>>>>>> remedy that this week. > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> If you're still seeing this error: > >>>>>>>>>>>> "Error: 'file' object has no attribute 'find'" > >>>>>>>>>>>> > >>>>>>>>>>>> Then I might be able to help, but I'm not sure how to > >>>>>>>>>>>> reproduce it. If > >>>>>>>>>>>> you send a log file and config for this latter error I'll > >>>>>>>>>>>> take a look. > >>>>>>>>>>>> Yang seems to be reporting the same thing in > >>>> another thread. > >>>>>>>>>>>> > >>>>>>>>>>>> --Dutch > >>>>>>>>>>>> > >>>>>>>>>>>> On Mon, 1 Jun 2009, Dan Magenheimer wrote: > >>>>>>>>>>>> > >>>>>>>>>>>>> Hmmm... trying blktap2 for the first time, using 19682. > >>>>>>>>>>>>> I had thought that the syntax hadn't changed, but I am > >>>>>>>>>>>>> getting what appears to be a parsing error on > my vbd line. > >>>>>>>>>>>>> > >>>>>>>>>>>>> "ValueError: need more than 3 values to unpack" > >>>>>>>>>>>>> > >>>>>>>>>>>>> Thinking maybe that "w!" was the culprit, I changed > >>>>>>>>>>>>> it to "w" with no change in result. > >>>>>>>>>>>>> > >>>>>>>>>>>>> Looking at the python code that generated the error, > >>>>>>>>>>>>> I tried to figure out the syntax by experimentation > >>>>>>>>>>>>> but without luck. I tried: > >>>>>>>>>>>>> > >>>>>>>>>>>>> tap:tapdisk:aio:/pathto/file.img > >>>>>>>>>>>>> > >>>>>>>>>>>>> but got "Error: 'file' object has no attribute 'find'" > >>>>>>>>>>>>> > >>>>>>>>>>>>> To see if I could use the old blktap, I tried > >>>>>>>>>>>>> > >>>>>>>>>>>>> tap:tapdisk:ioemu:/pathto/file.img > >>>>>>>>>>>>> > >>>>>>>>>>>>> but got the dreaded "Error: Device 768 (tap) > could not be > >>>>>>>>>>>>> connected. Hotplug scripts not working" > >>>>>>>>>>>>> > >>>>>>>>>>>>> Am I missing something in the syntax for blktap2? > >>>>>>>>>>>>> Is there a how-to or readme I didn't find? Or > >>>>>>>>>>>>> is there some required dependency I don't know about > >>>>>>>>>>>>> that is missing? > >>>>>>>>>>>>> > >>>>>>>>>>>>> I thought maybe I had a bad install, so rebuilt and > >>>>>>>>>>>>> reinstalled with the same result. > >>>>>>>>>>>>> > >>>>>>>>>>>>> xend.log and config file attached. > >>>>>>>>>>>>> > >>>>>>>>>>>>> Thanks, > >>>>>>>>>>>>> Dan > >>>>>>>>>>>>> > >>>>>>>>>>>>> P.S. I am trying blktap2 because both blktap and > >>>>>>>>>>>>> file-backed fail. Blktap sometimes reads garbage > >>>>>>>>>>>>> from the file and > >>>>>>>>>>>> > >>>>>>>>>>>> _______________________________________________ > >>>>>>>>>>>> Xen-devel mailing list > >>>>>>>>>>>> Xen-devel@lists.xensource.com > >>>>>>>>>>>> http://lists.xensource.com/xen-devel > >>>>>>>>>>>> > >>>>>>>>>> > >>>>>>>>> > >>>>>>>> > >>>>>>> > >>>>>>> _______________________________________________ > >>>>>>> Xen-devel mailing list > >>>>>>> Xen-devel@lists.xensource.com > >>>>>>> http://lists.xensource.com/xen-devel > >>>>>> > >>>>>> > >>>>>> > >>>>> > >>>>> _______________________________________________ > >>>>> Xen-devel mailing list > >>>>> Xen-devel@lists.xensource.com > >>>>> http://lists.xensource.com/xen-devel > >>>>> > >> > >> > >> > >> _______________________________________________ > >> Xen-devel mailing list > >> Xen-devel@lists.xensource.com > >> http://lists.xensource.com/xen-devel > > > > > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > [-- Attachment #2: fail.out --] [-- Type: application/octet-stream, Size: 16604 bytes --] (XEN) Resetting with ACPI MEMORY or I/O RESET_REG. __ __ _____ ____ _ _ _ \ \/ /___ _ __ |___ / | ___| _ _ _ __ ___| |_ __ _| |__ | | ___ \ // _ \ '_ \ |_ \ |___ \ __| | | | '_ \/ __| __/ _` | '_ \| |/ _ \ / \ __/ | | | ___) | ___) |__| |_| | | | \__ \ || (_| | |_) | | __/ /_/\_\___|_| |_| |____(_)____/ \__,_|_| |_|___/\__\__,_|_.__/|_|\___| (XEN) Xen version 3.5-unstable (root@(none)) (gcc version 4.1.2 20071124 (Red Ha t 4.1.2-42)) Tue Jun 2 17:16:27 MDT 2009 (XEN) Latest ChangeSet: Tue Jun 02 11:50:16 2009 +0100 19698:f72d26c00002 (XEN) Command line: com1=115200,8n1 dom0_mem=256M console=com1,vga tmem tmem_com press loglvl=all (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds (XEN) EDID info not retrieved because no DDC retrieval method detected (XEN) Disc information: (XEN) Found 1 MBR signatures (XEN) Found 1 EDD information structures (XEN) Xen-e820 RAM map: (XEN) 0000000000000000 - 000000000009cc00 (usable) (XEN) 000000000009cc00 - 00000000000a0000 (reserved) (XEN) 00000000000e0000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 000000007d6b0000 (usable) (XEN) 000000007d6b0000 - 000000007d6be000 (ACPI data) (XEN) 000000007d6be000 - 000000007d6f0000 (ACPI NVS) (XEN) 000000007d6f0000 - 000000007d700000 (reserved) (XEN) 00000000fee00000 - 00000000fee01000 (reserved) (XEN) 00000000ffa6f000 - 00000000ffa70000 (reserved) (XEN) 00000000ffb00000 - 0000000100000000 (reserved) (XEN) System RAM: 2006MB (2054448kB) (XEN) ACPI: RSDP 000F9990, 0014 (r0 ACPIAM) (XEN) ACPI: RSDT 7D6B0000, 0048 (r1 A M I OEMRSDT 5000708 MSFT 97) (XEN) ACPI: FACP 7D6B0200, 0084 (r2 A M I OEMFACP 5000708 MSFT 97) (XEN) ACPI: DSDT 7D6B0490, 6643 (r1 SDBLI9 SDBLI944 44 INTL 20051117) (XEN) ACPI: FACS 7D6BE000, 0040 (XEN) ACPI: APIC 7D6B0390, 006C (r1 A M I OEMAPIC 5000708 MSFT 97) (XEN) ACPI: MCFG 7D6B0450, 003C (r1 A M I OEMMCFG 5000708 MSFT 97) (XEN) ACPI: OEMB 7D6BE040, 0079 (r1 A M I AMI_OEM 5000708 MSFT 97) (XEN) ACPI: HPET 7D6B6AE0, 0038 (r1 A M I OEMHPET 5000708 MSFT 97) (XEN) ACPI: ASF! 7D6B6B18, 0099 (r32 LEGEND I865PASF 1 INTL 20051117) (XEN) ACPI: GSCI 7D6BE0C0, 2024 (r1 A M I GMCHSCI 5000708 MSFT 97) (XEN) ACPI: iEIT 7D6C00F0, 00B0 (r1 A M I EITTABLE 5000708 MSFT 97) (XEN) ACPI: SSDT 7D6C0BC0, 0877 (r1 DpgPmm CpuPm 12 INTL 20051117) (XEN) NUMA turned off (XEN) Faking a node at 0000000000000000-000000007d6b0000 (XEN) Xen heap: 9MB (9640kB) (XEN) Domain heap initialised (XEN) found SMP MP-table at 000ff780 (XEN) DMI present. (XEN) Using APIC driver default (XEN) ACPI: PM-Timer IO Port: 0x808 (XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[804,0], pm1x_evt[800,0] (XEN) ACPI: wakeup_vec[7d6be00c], vec_size[20] (XEN) ACPI: Local APIC address 0xfee00000 (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) (XEN) Processor #0 6:15 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) (XEN) Processor #1 6:15 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled) (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled) (XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) (XEN) ACPI: IRQ0 used by override. (XEN) ACPI: IRQ2 used by override. (XEN) ACPI: IRQ9 used by override. (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) ACPI: HPET id: 0x8086a301 base: 0xfed00000 (XEN) Using ACPI (MADT) for SMP configuration information (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Initializing CPU#0 (XEN) Detected 2992.587 MHz processor. (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K (XEN) CPU: L2 cache: 4096K (XEN) CPU: Physical Processor ID: 0 (XEN) CPU: Processor Core ID: 0 (XEN) VMX: Supported advanced features: (XEN) - APIC MMIO access virtualisation (XEN) - APIC TPR shadow (XEN) - Virtual NMI (XEN) - MSR direct-access bitmap (XEN) HVM: VMX enabled (XEN) Intel machine check reporting enabled on CPU#0. (XEN) CPU0: Thermal monitoring enabled (TM2) (XEN) CMCI: CPU0 has no CMCI support (XEN) CPU0: Intel(R) Core(TM)2 Duo CPU E6850 @ 3.00GHz stepping 0b (XEN) Booting processor 1/1 eip 8c000 (XEN) Initializing CPU#1 (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K (XEN) CPU: L2 cache: 4096K (XEN) CPU: Physical Processor ID: 0 (XEN) CPU: Processor Core ID: 1 (XEN) Intel machine check reporting enabled on CPU#1. (XEN) CPU1: Thermal monitoring enabled (TM2) (XEN) CMCI: CPU1 has no CMCI support (XEN) CPU1: Intel(R) Core(TM)2 Duo CPU E6850 @ 3.00GHz stepping 0b (XEN) Total of 2 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 (XEN) checking TSC synchronization across 2 CPUs: passed. (XEN) Platform timer is 14.318MHz HPET (XEN) Brought up 2 CPUs (XEN) I/O virtualisation disabled (XEN) HPET: 4 timers in total, 0 timers will be used for broadcast (XEN) ACPI sleep modes: S3 (XEN) mcheck_poll: Machine check polling timer started. (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 32-bit, PAE, lsb (XEN) Dom0 kernel: 32-bit, PAE, lsb, paddr 0xc0100000 -> 0xc048837c (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 000000003e000000->000000003f000000 (61440 pages to be allo cated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: c0100000->c048837c (XEN) Init. ramdisk: c0489000->c0b57200 (XEN) Phys-Mach map: c0b58000->c0b98000 (XEN) Start info: c0b98000->c0b9847c (XEN) Page tables: c0b99000->c0ba6000 (XEN) Boot stack: c0ba6000->c0ba7000 (XEN) TOTAL: c0000000->c1000000 (XEN) ENTRY ADDRESS: c0100000 (XEN) Dom0 has maximum 2 VCPUs (XEN) Scrubbing Free RAM: ................done. (XEN) Xen trace buffers: disabled (XEN) tmem: initialized comp=1 global-lock=0 (XEN) Std. Loglevel: All (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) (XEN) Xen is relinquishing VGA console. (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen ) (XEN) Freed 116kB init memory. Linux version 2.6.18.8-xen (root@djm-weyb2) (gcc version 4.1.2 20071124 (Red Hat 4.1.2-42)) #10 SMP Wed Jun 3 12:55:05 MDT 2009 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000010800000 (usable) 0MB HIGHMEM available. 264MB LOWMEM available. NX (Execute Disable) protection: active found SMP MP-table at 000ff780 DMI present. ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) Enabling APIC mode: Flat. Using 1 I/O APICs Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 80000000 (gap: 7d700000:81700000) Detected 2992.559 MHz processor. Built 1 zonelists. Total pages: 67584 Kernel command line: ro root=/dev/VolGroup00/LogVol00 max_loop=255 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 PID hash table entries: 2048 (order: 11, 8192 bytes) Xen reported: 2992.586 MHz processor. Console: colour VGA+ 80x25 Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Software IO TLB enabled: Aperture: 2 megabytes Kernel range: c1289000 - c1489000 Address size: 24 bits vmalloc area: d1000000-f51fe000, maxmem 2d7fe000 Memory: 245972k/270336k available (2096k kernel code, 16124k reserved, 857k data , 196k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 5986.54 BogoMIPS (lpj=29932715) Security Framework v1.0.0 initialized Capability LSM initialized Mount-cache hash table entries: 512 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 4096K Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code ACPI: Core revision 20060707 ENABLING IO-APIC IRQs SMP alternatives: switching to SMP code Brought up 2 CPUs Initializing CPU#1 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 4096K migration_cost=11 checking if image is initramfs... it is Freeing initrd memory: 6968k freed NET: Registered protocol family 16 ACPI: bus type pci registered PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved PCI: Not using MMCONFIG. PCI: Using configuration type 1 Setting up standard PCI resources ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing Error attaching device data Error attaching device data Error attaching device data Error attaching device data ACPI: PCI Root Bridge [PCI0] (0000:00) PCI: Transparent bridge - 0000:00:1e.0 ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *10 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 12 14 *15) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 12 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 7 10 12 14 15) ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 12 *14 15) ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 *10 12 14 15) ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 *5 6 7 10 12 14 15) ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 12 14 *15) Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init (XEN) io_apic.c:2130: (XEN) ioapic_guest_write: apic=0, pin=4, old_irq=4, new_irq=4 (XEN) ioapic_guest_write: old_entry=000009f1, new_entry=000109f1 (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! pnp: PnP ACPI: found 24 devices xen_mem: Initialising balloon driver. PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report pnp: 00:0a: ioport range 0xa20-0xa3f has been reserved pnp: 00:0a: ioport range 0xa00-0xa0f has been reserved pnp: 00:0a: ioport range 0xa10-0xa1f has been reserved pnp: 00:0a: ioport range 0xa40-0xa5f has been reserved PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.0 PCI: Bridge: 0000:00:1e.0 IO window: disabled. MEM window: disabled. PREFETCH window: disabled. NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 2, 16384 bytes) TCP established hash table entries: 16384 (order: 5, 131072 bytes) TCP bind hash table entries: 8192 (order: 4, 65536 bytes) TCP: Hash tables configured (established 16384 bind 8192) TCP reno registered IA-32 Microcode Update Driver: v1.14a-xen <tigran@veritas.com> audit: initializing netlink socket (disabled) audit(1244056465.718:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Initializing Cryptographic API io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) Floppy drive(s): fd0 is 1.44M floppy0: Unable to grab DMA2 for the floppy driver FDC 0 is a National Semiconductor PC87306 RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize loop: loaded (max 255 devices) Xen virtual console successfully installed as xvc0 Event-channel device installed. blktap_device_init: blktap device major 254 blktap_ring_init: blktap ring major: 253 netfront: Initialising virtual ethernet driver. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx (XEN) PCI add device 00:03.2 (XEN) PCI add device 00:1f.5 PNP: No PS/2 controller found. Probing ports directly. serio: i8042 AUX port at 0x60,0x64 irq 12 serio: i8042 KBD port at 0x60,0x64 irq 1 mice: PS/2 mouse device common for all mice md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: bitmap version 4.39 NET: Registered protocol family 1 NET: Registered protocol family 17 (XEN) platform_hypercall.c:183: Domain 0 says that IO-APIC REGSEL is good Using IPI No-Shortcut mode ACPI: (supports S0 S1 S3 S4 S5) BIOS EDD facility v0.16 2004-Jun-25, 1 devices found Freeing unused kernel memory: 196k freed usbcore: no version for "struct_module" found: kernel tainted. Driver 'usbfs' needs updating - please use bus_type methods usbcore: registered new driver usbfs Driver 'hub' needs updating - please use bus_type methods usbcore: registered new driver hub Driver 'usb' needs updating - please use bus_type methods (XEN) PCI add device 00:1a.7 ACPI: PCI Interrupt 0000:00:1a.7[D] -> GSI 19 (level, low) -> IRQ 16 ACPI: PCI interrupt for device 0000:00:1a.7 disabled ehci_hcd 0000:00:1a.7: init 0000:00:1a.7 fail, -16 ehci_hcd: probe of 0000:00:1a.7 failed with error -16 (XEN) PCI add device 00:1d.7 ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 23 (level, low) -> IRQ 17 ACPI: PCI interrupt for device 0000:00:1d.7 disabled ehci_hcd 0000:00:1d.7: init 0000:00:1d.7 fail, -16 ehci_hcd: probe of 0000:00:1d.7 failed with error -16 USB Universal Host Controller Interface driver v3.0 (XEN) PCI add device 00:1a.0 ACPI: PCI Interrupt 0000:00:1a.0[A] -> GSI 16 (level, low) -> IRQ 18 ACPI: PCI interrupt for device 0000:00:1a.0 disabled uhci_hcd 0000:00:1a.0: init 0000:00:1a.0 fail, -16 uhci_hcd: probe of 0000:00:1a.0 failed with error -16 (XEN) PCI add device 00:1a.1 ACPI: PCI Interrupt 0000:00:1a.1[B] -> GSI 21 (level, low) -> IRQ 19 ACPI: PCI interrupt for device 0000:00:1a.1 disabled uhci_hcd 0000:00:1a.1: init 0000:00:1a.1 fail, -16 uhci_hcd: probe of 0000:00:1a.1 failed with error -16 (XEN) PCI add device 00:1a.2 ACPI: PCI Interrupt 0000:00:1a.2[C] -> GSI 18 (level, low) -> IRQ 20 ACPI: PCI interrupt for device 0000:00:1a.2 disabled uhci_hcd 0000:00:1a.2: init 0000:00:1a.2 fail, -16 uhci_hcd: probe of 0000:00:1a.2 failed with error -16 (XEN) PCI add device 00:1d.0 ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 23 (level, low) -> IRQ 17 ACPI: PCI interrupt for device 0000:00:1d.0 disabled uhci_hcd 0000:00:1d.0: init 0000:00:1d.0 fail, -16 uhci_hcd: probe of 0000:00:1d.0 failed with error -16 (XEN) PCI add device 00:1d.1 ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 16 ACPI: PCI interrupt for device 0000:00:1d.1 disabled uhci_hcd 0000:00:1d.1: init 0000:00:1d.1 fail, -16 uhci_hcd: probe of 0000:00:1d.1 failed with error -16 (XEN) PCI add device 00:1d.2 ACPI: PCI Interrupt 0000:00:1d.2[D] -> GSI 16 (level, low) -> IRQ 18 ACPI: PCI interrupt for device 0000:00:1d.2 disabled uhci_hcd 0000:00:1d.2: init 0000:00:1d.2 fail, -16 uhci_hcd: probe of 0000:00:1d.2 failed with error -16 SCSI subsystem initialized (XEN) PCI add device 00:1f.2 ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 16 ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 4 ports ? Gbps 0xf impl SATA mode ahci 0000:00:1f.2: flags: 64bit ncq stag led clo pmp pio slum part ata1: SATA max UDMA/133 cmd 0xD1014900 ctl 0x0 bmdma 0x0 irq 1279 ata2: SATA max UDMA/133 cmd 0xD1014980 ctl 0x0 bmdma 0x0 irq 1279 ata3: SATA max UDMA/133 cmd 0xD1014A00 ctl 0x0 bmdma 0x0 irq 1279 ata4: SATA max UDMA/133 cmd 0xD1014A80 ctl 0x0 bmdma 0x0 irq 1279 scsi0 : ahci ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: ATA-7, max UDMA/133, 625142448 sectors: LBA48 NCQ (depth 31/32) ata1.00: configured for UDMA/133 scsi1 : ahci ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ATAPI, max UDMA/100 ata2.00: configured for UDMA/100 scsi2 : ahci ata3: SATA link down (SStatus 0 SControl 300) scsi3 : ahci ata4: SATA link down (SStatus 0 SControl 300) Vendor: ATA Model: ST3320620AS Rev: 3.AA Type: Direct-Access ANSI SCSI revision: 05 ata1: EH pending after completion, repeating EH (cnt=4) Vendor: LITE-ON Model: DVDRW LH-20A1S Rev: 9L03 Type: CD-ROM ANSI SCSI revision: 05 (XEN) PCI add device 00:1f.5 ata_piix 0000:00:1f.5: MAP [ P0 P2 P1 P3 ] ACPI: PCI Interrupt 0000:00:1f.5[B] -> GSI 19 (level, low) -> IRQ 16 ata5: SATA max UDMA/133 cmd 0x0 ctl 0x2 bmdma 0x0 irq 16 ata6: SATA max UDMA/133 cmd 0x0 ctl 0x2 bmdma 0x0 irq 16 scsi4 : ata_piix scsi5 : ata_piix device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@redhat.com Kernel panic - not syncing: Attempted to kill init! (XEN) Domain 0 crashed: rebooting machine in 5 seconds. (XEN) Resetting with ACPI MEMORY or I/O RESET_REG. [-- Attachment #3: success.out --] [-- Type: application/octet-stream, Size: 19586 bytes --] (XEN) Resetting with ACPI MEMORY or I/O RESET_REG. ÿ __ __ _____ ____ _ _ _ \ \/ /___ _ __ |___ / | ___| _ _ _ __ ___| |_ __ _| |__ | | ___ \ // _ \ '_ \ |_ \ |___ \ __| | | | '_ \/ __| __/ _` | '_ \| |/ _ \ / \ __/ | | | ___) | ___) |__| |_| | | | \__ \ || (_| | |_) | | __/ /_/\_\___|_| |_| |____(_)____/ \__,_|_| |_|___/\__\__,_|_.__/|_|\___| (XEN) Xen version 3.5-unstable (root@(none)) (gcc version 4.1.2 20071124 (Red Ha t 4.1.2-42)) Tue Jun 2 17:16:27 MDT 2009 (XEN) Latest ChangeSet: Tue Jun 02 11:50:16 2009 +0100 19698:f72d26c00002 (XEN) Command line: com1=115200,8n1 dom0_mem=256M console=com1,vga tmem tmem_com press loglvl=all (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds (XEN) EDID info not retrieved because no DDC retrieval method detected (XEN) Disc information: (XEN) Found 1 MBR signatures (XEN) Found 1 EDD information structures (XEN) Xen-e820 RAM map: (XEN) 0000000000000000 - 000000000009cc00 (usable) (XEN) 000000000009cc00 - 00000000000a0000 (reserved) (XEN) 00000000000e0000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 000000007d6b0000 (usable) (XEN) 000000007d6b0000 - 000000007d6be000 (ACPI data) (XEN) 000000007d6be000 - 000000007d6f0000 (ACPI NVS) (XEN) 000000007d6f0000 - 000000007d700000 (reserved) (XEN) 00000000fee00000 - 00000000fee01000 (reserved) (XEN) 00000000ffa6f000 - 00000000ffa70000 (reserved) (XEN) 00000000ffb00000 - 0000000100000000 (reserved) (XEN) System RAM: 2006MB (2054448kB) (XEN) ACPI: RSDP 000F9990, 0014 (r0 ACPIAM) (XEN) ACPI: RSDT 7D6B0000, 0048 (r1 A M I OEMRSDT 5000708 MSFT 97) (XEN) ACPI: FACP 7D6B0200, 0084 (r2 A M I OEMFACP 5000708 MSFT 97) (XEN) ACPI: DSDT 7D6B0490, 6643 (r1 SDBLI9 SDBLI944 44 INTL 20051117) (XEN) ACPI: FACS 7D6BE000, 0040 (XEN) ACPI: APIC 7D6B0390, 006C (r1 A M I OEMAPIC 5000708 MSFT 97) (XEN) ACPI: MCFG 7D6B0450, 003C (r1 A M I OEMMCFG 5000708 MSFT 97) (XEN) ACPI: OEMB 7D6BE040, 0079 (r1 A M I AMI_OEM 5000708 MSFT 97) (XEN) ACPI: HPET 7D6B6AE0, 0038 (r1 A M I OEMHPET 5000708 MSFT 97) (XEN) ACPI: ASF! 7D6B6B18, 0099 (r32 LEGEND I865PASF 1 INTL 20051117) (XEN) ACPI: GSCI 7D6BE0C0, 2024 (r1 A M I GMCHSCI 5000708 MSFT 97) (XEN) ACPI: iEIT 7D6C00F0, 00B0 (r1 A M I EITTABLE 5000708 MSFT 97) (XEN) ACPI: SSDT 7D6C0BC0, 0877 (r1 DpgPmm CpuPm 12 INTL 20051117) (XEN) NUMA turned off (XEN) Faking a node at 0000000000000000-000000007d6b0000 (XEN) Xen heap: 9MB (9640kB) (XEN) Domain heap initialised (XEN) found SMP MP-table at 000ff780 (XEN) DMI present. (XEN) Using APIC driver default (XEN) ACPI: PM-Timer IO Port: 0x808 (XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[804,0], pm1x_evt[800,0] (XEN) ACPI: wakeup_vec[7d6be00c], vec_size[20] (XEN) ACPI: Local APIC address 0xfee00000 (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) (XEN) Processor #0 6:15 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) (XEN) Processor #1 6:15 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled) (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled) (XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) (XEN) ACPI: IRQ0 used by override. (XEN) ACPI: IRQ2 used by override. (XEN) ACPI: IRQ9 used by override. (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) ACPI: HPET id: 0x8086a301 base: 0xfed00000 (XEN) Using ACPI (MADT) for SMP configuration information (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Initializing CPU#0 (XEN) Detected 2992.564 MHz processor. (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K (XEN) CPU: L2 cache: 4096K (XEN) CPU: Physical Processor ID: 0 (XEN) CPU: Processor Core ID: 0 (XEN) VMX: Supported advanced features: (XEN) - APIC MMIO access virtualisation (XEN) - APIC TPR shadow (XEN) - Virtual NMI (XEN) - MSR direct-access bitmap (XEN) HVM: VMX enabled (XEN) Intel machine check reporting enabled on CPU#0. (XEN) CPU0: Thermal monitoring enabled (TM2) (XEN) CMCI: CPU0 has no CMCI support (XEN) CPU0: Intel(R) Core(TM)2 Duo CPU E6850 @ 3.00GHz stepping 0b (XEN) Booting processor 1/1 eip 8c000 (XEN) Initializing CPU#1 (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K (XEN) CPU: L2 cache: 4096K (XEN) CPU: Physical Processor ID: 0 (XEN) CPU: Processor Core ID: 1 (XEN) Intel machine check reporting enabled on CPU#1. (XEN) CPU1: Thermal monitoring enabled (TM2) (XEN) CMCI: CPU1 has no CMCI support (XEN) CPU1: Intel(R) Core(TM)2 Duo CPU E6850 @ 3.00GHz stepping 0b (XEN) Total of 2 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 (XEN) checking TSC synchronization across 2 CPUs: passed. (XEN) Platform timer is 14.318MHz HPET (XEN) Brought up 2 CPUs (XEN) I/O virtualisation disabled (XEN) HPET: 4 timers in total, 0 timers will be used for broadcast (XEN) ACPI sleep modes: S3 (XEN) mcheck_poll: Machine check polling timer started. (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 32-bit, PAE, lsb (XEN) Dom0 kernel: 32-bit, PAE, lsb, paddr 0xc0100000 -> 0xc048847c (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 000000003e000000->000000003f000000 (61440 pages to be allo cated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: c0100000->c048847c (XEN) Init. ramdisk: c0489000->c0b57200 (XEN) Phys-Mach map: c0b58000->c0b98000 (XEN) Start info: c0b98000->c0b9847c (XEN) Page tables: c0b99000->c0ba6000 (XEN) Boot stack: c0ba6000->c0ba7000 (XEN) TOTAL: c0000000->c1000000 (XEN) ENTRY ADDRESS: c0100000 (XEN) Dom0 has maximum 2 VCPUs (XEN) Scrubbing Free RAM: ................done. (XEN) Xen trace buffers: disabled (XEN) tmem: initialized comp=1 global-lock=0 (XEN) Std. Loglevel: All (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) (XEN) Xen is relinquishing VGA console. (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen ) (XEN) Freed 116kB init memory. Linux version 2.6.18.8-xen (root@djm-weyb2) (gcc version 4.1.2 20071124 (Red Hat 4.1.2-42)) #11 SMP Wed Jun 3 13:45:12 MDT 2009 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000010800000 (usable) 0MB HIGHMEM available. 264MB LOWMEM available. NX (Execute Disable) protection: active found SMP MP-table at 000ff780 DMI present. ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) Enabling APIC mode: Flat. Using 1 I/O APICs Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 80000000 (gap: 7d700000:81700000) Detected 2992.917 MHz processor. Built 1 zonelists. Total pages: 67584 Kernel command line: ro root=/dev/VolGroup00/LogVol00 max_loop=255 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 PID hash table entries: 2048 (order: 11, 8192 bytes) Xen reported: 2992.564 MHz processor. Console: colour VGA+ 80x25 Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Software IO TLB enabled: Aperture: 2 megabytes Kernel range: c1289000 - c1489000 Address size: 24 bits vmalloc area: d1000000-f51fe000, maxmem 2d7fe000 Memory: 245972k/270336k available (2103k kernel code, 16124k reserved, 855k data , 196k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 5986.45 BogoMIPS (lpj=29932256) Security Framework v1.0.0 initialized Capability LSM initialized Mount-cache hash table entries: 512 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 4096K Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code ACPI: Core revision 20060707 ENABLING IO-APIC IRQs SMP alternatives: switching to SMP code Brought up 2 CPUs Initializing CPU#1 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 4096K migration_cost=57 checking if image is initramfs... it is Freeing initrd memory: 6968k freed NET: Registered protocol family 16 ACPI: bus type pci registered PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved PCI: Not using MMCONFIG. PCI: Using configuration type 1 Setting up standard PCI resources ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing Error attaching device data Error attaching device data Error attaching device data Error attaching device data ACPI: PCI Root Bridge [PCI0] (0000:00) PCI: Transparent bridge - 0000:00:1e.0 ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *10 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 12 14 *15) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 12 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 7 10 12 14 15) ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 12 *14 15) ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 *10 12 14 15) ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 *5 6 7 10 12 14 15) ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 12 14 *15) Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init (XEN) io_apic.c:2130: (XEN) ioapic_guest_write: apic=0, pin=4, old_irq=4, new_irq=4 (XEN) ioapic_guest_write: old_entry=000009f1, new_entry=000109f1 (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! pnp: PnP ACPI: found 24 devices xen_mem: Initialising balloon driver. PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report pnp: 00:0a: ioport range 0xa20-0xa3f has been reserved pnp: 00:0a: ioport range 0xa00-0xa0f has been reserved pnp: 00:0a: ioport range 0xa10-0xa1f has been reserved pnp: 00:0a: ioport range 0xa40-0xa5f has been reserved PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.0 PCI: Bridge: 0000:00:1e.0 IO window: disabled. MEM window: disabled. PREFETCH window: disabled. NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 2, 16384 bytes) TCP established hash table entries: 16384 (order: 5, 131072 bytes) TCP bind hash table entries: 8192 (order: 4, 65536 bytes) TCP: Hash tables configured (established 16384 bind 8192) TCP reno registered IA-32 Microcode Update Driver: v1.14a-xen <tigran@veritas.com> audit: initializing netlink socket (disabled) audit(1244058908.711:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Initializing Cryptographic API io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) Floppy drive(s): fd0 is 1.44M floppy0: Unable to grab DMA2 for the floppy driver FDC 0 is a National Semiconductor PC87306 RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize loop: loaded (max 255 devices) Xen virtual console successfully installed as xvc0 Event-channel device installed. blktap_device_init: blktap device major 254 blktap_ring_init: blktap ring major: 253 netfront: Initialising virtual ethernet driver. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx (XEN) PCI add device 00:03.2 (XEN) PCI add device 00:1f.5 PNP: No PS/2 controller found. Probing ports directly. serio: i8042 AUX port at 0x60,0x64 irq 12 serio: i8042 KBD port at 0x60,0x64 irq 1 mice: PS/2 mouse device common for all mice md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: bitmap version 4.39 NET: Registered protocol family 1 NET: Registered protocol family 17 (XEN) platform_hypercall.c:183: Domain 0 says that IO-APIC REGSEL is good Using IPI No-Shortcut mode PCI IO multiplexer device installed. ACPI: (supports S0 S1 S3 S4 S5) BIOS EDD facility v0.16 2004-Jun-25, 1 devices found Freeing unused kernel memory: 196k freed usbcore: no version for "struct_module" found: kernel tainted. usbcore: registered new driver usbfs usbcore: registered new driver hub (XEN) PCI add device 00:1a.7 ACPI: PCI Interrupt 0000:00:1a.7[D] -> GSI 19 (level, low) -> IRQ 16 ACPI: PCI interrupt for device 0000:00:1a.7 disabled ehci_hcd 0000:00:1a.7: init 0000:00:1a.7 fail, -16 ehci_hcd: probe of 0000:00:1a.7 failed with error -16 (XEN) PCI add device 00:1d.7 ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 23 (level, low) -> IRQ 17 ACPI: PCI interrupt for device 0000:00:1d.7 disabled ehci_hcd 0000:00:1d.7: init 0000:00:1d.7 fail, -16 ehci_hcd: probe of 0000:00:1d.7 failed with error -16 USB Universal Host Controller Interface driver v3.0 (XEN) PCI add device 00:1a.0 ACPI: PCI Interrupt 0000:00:1a.0[A] -> GSI 16 (level, low) -> IRQ 18 ACPI: PCI interrupt for device 0000:00:1a.0 disabled uhci_hcd 0000:00:1a.0: init 0000:00:1a.0 fail, -16 uhci_hcd: probe of 0000:00:1a.0 failed with error -16 (XEN) PCI add device 00:1a.1 ACPI: PCI Interrupt 0000:00:1a.1[B] -> GSI 21 (level, low) -> IRQ 19 ACPI: PCI interrupt for device 0000:00:1a.1 disabled uhci_hcd 0000:00:1a.1: init 0000:00:1a.1 fail, -16 uhci_hcd: probe of 0000:00:1a.1 failed with error -16 (XEN) PCI add device 00:1a.2 ACPI: PCI Interrupt 0000:00:1a.2[C] -> GSI 18 (level, low) -> IRQ 20 ACPI: PCI interrupt for device 0000:00:1a.2 disabled uhci_hcd 0000:00:1a.2: init 0000:00:1a.2 fail, -16 uhci_hcd: probe of 0000:00:1a.2 failed with error -16 (XEN) PCI add device 00:1d.0 ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 23 (level, low) -> IRQ 17 ACPI: PCI interrupt for device 0000:00:1d.0 disabled uhci_hcd 0000:00:1d.0: init 0000:00:1d.0 fail, -16 uhci_hcd: probe of 0000:00:1d.0 failed with error -16 (XEN) PCI add device 00:1d.1 ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 16 ACPI: PCI interrupt for device 0000:00:1d.1 disabled uhci_hcd 0000:00:1d.1: init 0000:00:1d.1 fail, -16 uhci_hcd: probe of 0000:00:1d.1 failed with error -16 (XEN) PCI add device 00:1d.2 ACPI: PCI Interrupt 0000:00:1d.2[D] -> GSI 16 (level, low) -> IRQ 18 ACPI: PCI interrupt for device 0000:00:1d.2 disabled uhci_hcd 0000:00:1d.2: init 0000:00:1d.2 fail, -16 uhci_hcd: probe of 0000:00:1d.2 failed with error -16 SCSI subsystem initialized (XEN) PCI add device 00:1f.2 ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 16 ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 4 ports ? Gbps 0xf impl SATA mode ahci 0000:00:1f.2: flags: 64bit ncq stag led clo pmp pio slum part ata1: SATA max UDMA/133 cmd 0xD1014900 ctl 0x0 bmdma 0x0 irq 1279 ata2: SATA max UDMA/133 cmd 0xD1014980 ctl 0x0 bmdma 0x0 irq 1279 ata3: SATA max UDMA/133 cmd 0xD1014A00 ctl 0x0 bmdma 0x0 irq 1279 ata4: SATA max UDMA/133 cmd 0xD1014A80 ctl 0x0 bmdma 0x0 irq 1279 scsi0 : ahci ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: ATA-7, max UDMA/133, 625142448 sectors: LBA48 NCQ (depth 31/32) ata1.00: configured for UDMA/133 scsi1 : ahci ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ATAPI, max UDMA/100 ata2.00: configured for UDMA/100 scsi2 : ahci ata3: SATA link down (SStatus 0 SControl 300) scsi3 : ahci ata4: SATA link down (SStatus 0 SControl 300) Vendor: ATA Model: ST3320620AS Rev: 3.AA Type: Direct-Access ANSI SCSI revision: 05 SCSI device sda: 625142448 512-byte hdwr sectors (320073 MB) sda: Write Protect is off SCSI device sda: drive cache: write back SCSI device sda: 625142448 512-byte hdwr sectors (320073 MB) sda: Write Protect is off SCSI device sda: drive cache: write back sda: sda1 sda2 sd 0:0:0:0: Attached scsi disk sda Vendor: LITE-ON Model: DVDRW LH-20A1S Rev: 9L03 Type: CD-ROM ANSI SCSI revision: 05 (XEN) PCI add device 00:1f.5 ata_piix 0000:00:1f.5: MAP [ P0 P2 P1 P3 ] ACPI: PCI Interrupt 0000:00:1f.5[B] -> GSI 19 (level, low) -> IRQ 16 ata5: SATA max UDMA/133 cmd 0x0 ctl 0x2 bmdma 0x0 irq 16 ata6: SATA max UDMA/133 cmd 0x0 ctl 0x2 bmdma 0x0 irq 16 scsi4 : ata_piix scsi5 : ata_piix device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@redhat.com kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. *************************************************************** *************************************************************** ** WARNING: Currently emulating unsupported memory accesses ** ** in /lib/tls glibc libraries. The emulation is ** ** slow. To ensure full performance you should ** ** install a 'xen-friendly' (nosegneg) version of ** ** the library, or disable tls support by executing ** ** the following as root: ** ** mv /lib/tls /lib/tls.disabled ** ** Offending process: modprobe (pid=1165) ** *************************************************************** *************************************************************** Continuing... Real Time Clock Driver v1.12ac (XEN) PCI add device 00:1f.3 (XEN) PCI add device 00:03.3 (XEN) PCI add device 00:1b.0 (XEN) Set CPU acpi_id(1) cpuid(0) Px State info: (XEN) _PPC: 0 (XEN) cpuid.MWAIT[.eax=40, .ebx=40, .ecx=3, .edx=220] (XEN) Monitor-Mwait will be used to enter C-1 state (XEN) Set CPU acpi_id(1) cpuid(0) Px State info: (XEN) _PCT: descriptor=130, length=12, space_id=127, bit_width=0, bit_offset=0 , reserved=0, address=0 (XEN) _PCT: descriptor=130, length=12, space_id=127, bit_width=0, bit_offset=0 , reserved=0, address=0 (XEN) _PSS: state_count=4 (XEN) State0: 3000MHz 89000mW 10us 10us 0x92a 0x92a (XEN) State1: 2667MHz 76000mW 10us 10us 0x825 0x825 (XEN) State2: 2333MHz 64000mW 10us 10us 0x720 0x720 (XEN) State3: 2000MHz 53000mW 10us 10us 0x61a 0x61a (XEN) _PSD: num_entries=5 rev=0 domain=0 coord_type=252 num_processors=2 (XEN) _PPC: 0 (XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space (XEN) CPU 0 initialization completed (XEN) Set CPU acpi_id(2) cpuid(1) Px State info: (XEN) _PPC: 0 (XEN) cpuid.MWAIT[.eax=40, .ebx=40, .ecx=3, .edx=220] (XEN) Monitor-Mwait will be used to enter C-1 state (XEN) Set CPU acpi_id(2) cpuid(1) Px State info: (XEN) _PCT: descriptor=130, length=12, space_id=127, bit_width=0, bit_offset=0 , reserved=0, address=0 (XEN) _PCT: descriptor=130, length=12, space_id=127, bit_width=0, bit_offset=0 , reserved=0, address=0 (XEN) _PSS: state_count=4 (XEN) State0: 3000MHz 89000mW 10us 10us 0x92a 0x92a (XEN) State1: 2667MHz 76000mW 10us 10us 0x825 0x825 (XEN) State2: 2333MHz 64000mW 10us 10us 0x720 0x720 (XEN) State3: 2000MHz 53000mW 10us 10us 0x61a 0x61a (XEN) _PSD: num_entries=5 rev=0 domain=0 coord_type=252 num_processors=2 (XEN) _PPC: 0 (XEN) adding CPU 1 (XEN) no cpu_id for acpi_id 3 (XEN) no cpu_id for acpi_id 4 (XEN) microcode: CPU0 updated from revision 0xb3 to 0xb6, date = 2007-07-13 (XEN) microcode: CPU1 updated from revision 0xb3 to 0xb6, date = 2007-07-13 Bridge firewalling registered Enterprise Linux Enterprise Linux Server release 5.2 (Carthage) Kernel 2.6.18.8-xen on an i686 djm-weyb2 login: [-- Attachment #4: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Dom0 crashing when built with c/s 881 (Was: blktap2: need more than 3 values to unpack) 2009-06-03 20:15 ` Dan Magenheimer @ 2009-06-03 20:46 ` Keir Fraser 2009-06-03 21:17 ` Dan Magenheimer 0 siblings, 1 reply; 20+ messages in thread From: Keir Fraser @ 2009-06-03 20:46 UTC (permalink / raw) To: Dan Magenheimer, Dulloor, Isaku Yamahata; +Cc: Xen-Devel (E-mail) Changeset 881 is "pcie io space multiplex: backport of bus event notification patch", right? I don't believe that you are reverting just that patch, for two reasons: 1. It only adds extra functionality which by default would not do anything. Just reading the patch I can see it's harmless by itself as it merely introduces a new notifier chain which noone registers on. 2. Changeset 882 depends on 881. If you revert just 881 then the tree will not build. -- Keir On 03/06/2009 21:15, "Dan Magenheimer" <dan.magenheimer@oracle.com> wrote: >>> Is it better to have the new option added by >>> c/s(CONFIG_PCI_IOMULTI) default 'n' ? > > Turning off that option doesn't stop my dom0 from crashing. > Reverting 881 DOES stop my dom0 from crashing. Attached are > the boot output for fail and success (the only difference > between the two dom0's is the success has 881 reverted). > > Of note, the fail log has three lines of the type: > > "Driver 'xxx' needs updating - please use bus_type methods" > > (xxx = usbfs, hub, usb) and the success log has a line that says: > > "PCI IO multiplexer device installed" > > which is missing in the fail log. > >> -----Original Message----- >> From: Keir Fraser [mailto:keir.fraser@eu.citrix.com] >> Sent: Wednesday, June 03, 2009 12:45 PM >> To: Dulloor >> Cc: Isaku Yamahata; Dan Magenheimer; Xen-Devel (E-mail) >> Subject: Re: Dom0 crashing when built with c/s 881 (Was: [Xen-devel] >> blktap2: need more than 3 values to unpack) >> >> >> Depends on the feature's impact when unused. >> >> -- Keir >> >> On 03/06/2009 18:57, "Dulloor" <dulloor@gmail.com> wrote: >> >>> Is it better to have the new option added by >> c/s(CONFIG_PCI_IOMULTI) default >>> 'n' ? >>> >>> -dulloor >>> >>> On Wed, Jun 3, 2009 at 1:48 PM, Keir Fraser >> <keir.fraser@eu.citrix.com> wrote: >>>> Perhaps post a diff of boot output with c/s 880 vs c/s >> 881. I've cc'ed >>>> Isaku, who submitted the patch that's causing your problem. >>>> >>>> -- Keir >>>> >>>> On 03/06/2009 18:35, "Dan Magenheimer" >> <dan.magenheimer@oracle.com> wrote: >>>> >>>>> OK, it appears that linux-2.6.18-xen.hg c/s 881 is causing >>>>> my dom0 to crash. Dom0 boots successfully at 880 and fails >>>>> with 881 or anything after. >>>>> >>>>> Any ideas? >>>>> >>>>>> -----Original Message----- >>>>>> From: Dan Magenheimer >>>>>> Sent: Tuesday, June 02, 2009 10:45 PM >>>>>> To: Dan Magenheimer; Keir Fraser; Dutch Meyer; Xen-Devel (E-mail) >>>>>> Subject: RE: [Xen-devel] blktap2: need more than 3 >> values to unpack >>>>>> >>>>>> >>>>>> Followup: my dom0 boots failed with 888, boots fine with 876, >>>>>> then to ensure no pilot error, I rebuilt 888 again and it >>>>>> failed again. >>>>>> >>>>>>> -----Original Message----- >>>>>>> From: Dan Magenheimer >>>>>>> Sent: Tuesday, June 02, 2009 5:50 PM >>>>>>> To: Keir Fraser; Dutch Meyer; Xen-Devel (E-mail) >>>>>>> Subject: RE: [Xen-devel] blktap2: need more than 3 >> values to unpack >>>>>>> >>>>>>> >>>>>>> Thanks. It is indeed a pilot error on my part but a bit >>>>>>> more bizarre. I apparently have a linux-2.6-xen.hg directory >>>>>>> as both a sister and a child to xen-unstable.hg. In this >>>>>>> case the build apparently chooses the child. I was >>>>>>> looking at and modifying the un-updated child so >>>>>>> blktap2 wasn't even present yet. Removing the child >>>>>>> causes the sibling to build. BUT! Now dom0 is >>>>>>> crashing early on during boot. (This is an Intel >>>>>>> Weybridge box.) I'll look into this further tomorrow. >>>>>>> >>>>>>> ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) >>>>>>> ata2.00: ATAPI, max UDMA/100 >>>>>>> ata2.00: configured for UDMA/100 >>>>>>> scsi2 : ahci >>>>>>> ata3: SATA link down (SStatus 0 SControl 300) >>>>>>> scsi3 : ahci >>>>>>> ata4: SATA link down (SStatus 0 SControl 300) >>>>>>> Vendor: ATA Model: ST3320620AS Rev: 3.AA >>>>>>> Type: Direct-Access ANSI SCSI >> revision: 05 >>>>>>> ata1: EH pending after completion, repeating EH (cnt=4) >>>>>>> Vendor: LITE-ON Model: DVDRW LH-20A1S Rev: 9L03 >>>>>>> Type: CD-ROM ANSI SCSI >> revision: 05 >>>>>>> (XEN) PCI add device 00:1f.5 >>>>>>> ata_piix 0000:00:1f.5: MAP [ P0 P2 P1 P3 ] >>>>>>> ACPI: PCI Interrupt 0000:00:1f.5[B] -> GSI 19 (level, >> low) -> IRQ 16 >>>>>>> ata5: SATA max UDMA/133 cmd 0x0 ctl 0x2 bmdma 0x0 irq 16 >>>>>>> ata6: SATA max UDMA/133 cmd 0x0 ctl 0x2 bmdma 0x0 irq 16 >>>>>>> scsi4 : ata_piix >>>>>>> scsi5 : ata_piix >>>>>>> device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: >>>>>>> dm-devel@redhat.com >>>>>>> Kernel panic - not syncing: Attempted to kill init! >>>>>>> (XEN) Domain 0 crashed: rebooting machine in 5 seconds. >>>>>>> >>>>>>>> -----Original Message----- >>>>>>>> From: Keir Fraser [mailto:keir.fraser@eu.citrix.com] >>>>>>>> Sent: Tuesday, June 02, 2009 4:45 PM >>>>>>>> To: Dan Magenheimer; Dutch Meyer; Xen-Devel (E-mail) >>>>>>>> Subject: Re: [Xen-devel] blktap2: need more than 3 values >>>>>> to unpack >>>>>>>> >>>>>>>> >>>>>>>> Probably you had an old .config hanging around in your build >>>>>>>> tree somewhere. >>>>>>>> c/s 889 should fix this for a fresh build. >>>>>>>> >>>>>>>> -- Keir >>>>>>>> >>>>>>>> On 02/06/2009 18:33, "Dan Magenheimer" >>>>>>>> <dan.magenheimer@oracle.com> wrote: >>>>>>>> >>>>>>>>> Thanks. Looks like a partial configuration patch got checked >>>>>>>>> in for blktap2 (cs 886)? CONFIG_XEN_BLKDEV_TAP2 must be >>>>>>> configured >>>>>>>>> but afaict is not turned on by default (yet?). So a fresh >>>>>>>>> xen-unstable tip doesn't build the blktap2 driver. See: >>>>>>>>> >>>>>>>>> >>>>>> http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/3e01555dd227 >>>>>>>>> >>>>>>>>> (I'm guessing since this was submitted by Isaku that blktap2 >>>>>>>>> shouldn't be the default on ia64?) >>>>>>>>> >>>>>>>>> Should CONFIG_XEN_BLKDEV_TAP2 be turned on by default, instead >>>>>>>>> of CONFIG_XEN_BLKDEV_TAP, at least on x86? >>>>>>>>> >>>>>>>>> I tried modifying >>>>>>>>> >>>>>>>>> linux-2.6.18-xen.hg/buildconfigs/linux-defconfig_xen0_x86_32 >>>>>>>>> >>>>>>>>> (and also >>>>>>>>> >>>>>>>>> linux-2.6.18-xen.hg/buildconfigs/linux-defconfig_xen_x86_32) >>>>>>>>> >>>>>>>>> followed by: >>>>>>>>> >>>>>>>>> KERNELS=linux-2.6-xen0 make linux-2.6-xen-config >>>>>>>> CONFIGMODE=oldconfig >>>>>>>>> >>>>>>>>> (I don't need or want to go through a manual config process) >>>>>>>>> >>>>>>>>> but BLKDEV_TAP is always selected, not BLKDEV_TAP2. >>>>>>>>> >>>>>>>>> Finally, I resorted to manually changing >>>>>>>>> >>>>>>>>> linux-2.6.18-xen.hg/drivers/xen/Kconfig >>>>>>>>> >>>>>>>>> and this succeeds in turning it on, but it just reverses the >>>>>>>>> above checked-in patch, so I suspect that's not the right >>>>>>>>> answer either. >>>>>>>>> >>>>>>>>>> -----Original Message----- >>>>>>>>>> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] >>>>>>>>>> Sent: Tuesday, June 02, 2009 9:05 AM >>>>>>>>>> To: Dan Magenheimer >>>>>>>>>> Subject: RE: [Xen-devel] blktap2: need more than 3 >>>>>>> values to unpack >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> I think that you don't have the blktap2 driver loaded in >>>>>>>>>> dom0. A clean >>>>>>>>>> build/install of the dom0 kernel image should sort >> you out. If >>>>>>>>>> drivers/xen/blktap2 is compiled in it should be setting up >>>>>>>>>> these paths. >>>>>>>>>> >>>>>>>>>> Let me know if that fixes things and I'll make python >>>>>>> spit out more >>>>>>>>>> meaningful errors, otherwise we can try to figure out the >>>>>>>>>> blktap2 kernel >>>>>>>>>> code isn't working. >>>>>>>>>> >>>>>>>>>> --Dutch >>>>>>>>>> >>>>>>>>>> On Tue, 2 Jun 2009, Dan Magenheimer wrote: >>>>>>>>>> >>>>>>>>>>> It replies with "didn't find blktap-control in /proc/misc" >>>>>>>>>>> >>>>>>>>>>> If that fails, perhaps the path doesn't exist, but I looked >>>>>>>>>>> and /sys/class/blktap2 doesn't exist. >>>>>>>>>>> >>>>>>>>>>>> -----Original Message----- >>>>>>>>>>>> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] >>>>>>>>>>>> Sent: Monday, June 01, 2009 10:37 PM >>>>>>>>>>>> To: Dan Magenheimer >>>>>>>>>>>> Subject: RE: [Xen-devel] blktap2: need more than 3 >>>>>>>> values to unpack >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Can you try this from the command line: >>>>>>>>>>>> >>>>>>>>>>>> tapdisk2 -n aio:/pathto/file.img >>>>>>>>>>>> >>>>>>>>>>>> If successful, this will create your aio device and print a >>>>>>>>>>>> /dev device >>>>>>>>>>>> associated with it. >>>>>>>>>>>> >>>>>>>>>>>> In that case you'll then be able to remove it with: >>>>>>>>>>>> >>>>>>>>>>>> echo 1 > /sys/class/blktap2/<disk>/remove >>>>>>>>>>>> >>>>>>>>>>>> Where <disk> will be obvious from the output of the >>>>>>>>>> tapdisk2 command. >>>>>>>>>>>> >>>>>>>>>>>> However, I expect that this will fail. >>>>>>>>>>>> >>>>>>>>>>>> --Dutch >>>>>>>>>>>> >>>>>>>>>>>> On Mon, 1 Jun 2009, Dan Magenheimer wrote: >>>>>>>>>>>> >>>>>>>>>>>> Then I might be able to help, but I'm not sure how to >>>>>>>>>>>> reproduce it. If >>>>>>>>>>>> you send a log file and config for this latter error I'll >>>>>>>>>>>> take a look. >>>>>>>>>>>> >>>>>>>>>>>> Here ya go. >>>>>>>>>>>> >>>>>>>>>>>> Thanks, >>>>>>>>>>>> Dan >>>>>>>>>>>> >>>>>>>>>>>> -----Original Message----- >>>>>>>>>>>> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] >>>>>>>>>>>> Sent: Monday, June 01, 2009 8:32 PM >>>>>>>>>>>> To: Dan Magenheimer >>>>>>>>>>>> Cc: Xen-Devel (E-mail) >>>>>>>>>>>> Subject: Re: [Xen-devel] blktap2: need more than 3 >>>>>>>>>> values to unpack >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> The tap:aio:/pathto/file.img syntax that you're >>>>>> using in your >>>>>>>>>>>> config was >>>>>>>>>>>> changed before blktap2 was introduced. >>>>>>>>>>>> tap:tapdisk:aio:/pathto/file.img is >>>>>>>>>>>> apparently the correct syntax now, though the >> README didn't >>>>>>>>>>>> get updated to >>>>>>>>>>>> reflect this. Our blktap2 documentation is no better - >>>>>>>>>> I'll try to >>>>>>>>>>>> remedy that this week. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> If you're still seeing this error: >>>>>>>>>>>> "Error: 'file' object has no attribute 'find'" >>>>>>>>>>>> >>>>>>>>>>>> Then I might be able to help, but I'm not sure how to >>>>>>>>>>>> reproduce it. If >>>>>>>>>>>> you send a log file and config for this latter error I'll >>>>>>>>>>>> take a look. >>>>>>>>>>>> Yang seems to be reporting the same thing in >>>>>> another thread. >>>>>>>>>>>> >>>>>>>>>>>> --Dutch >>>>>>>>>>>> >>>>>>>>>>>> On Mon, 1 Jun 2009, Dan Magenheimer wrote: >>>>>>>>>>>> >>>>>>>>>>>> Hmmm... trying blktap2 for the first time, using 19682. >>>>>>>>>>>> I had thought that the syntax hadn't changed, but I am >>>>>>>>>>>> getting what appears to be a parsing error on >> my vbd line. >>>>>>>>>>>> >>>>>>>>>>>> "ValueError: need more than 3 values to unpack" >>>>>>>>>>>> >>>>>>>>>>>> Thinking maybe that "w!" was the culprit, I changed >>>>>>>>>>>> it to "w" with no change in result. >>>>>>>>>>>> >>>>>>>>>>>> Looking at the python code that generated the error, >>>>>>>>>>>> I tried to figure out the syntax by experimentation >>>>>>>>>>>> but without luck. I tried: >>>>>>>>>>>> >>>>>>>>>>>> tap:tapdisk:aio:/pathto/file.img >>>>>>>>>>>> >>>>>>>>>>>> but got "Error: 'file' object has no attribute 'find'" >>>>>>>>>>>> >>>>>>>>>>>> To see if I could use the old blktap, I tried >>>>>>>>>>>> >>>>>>>>>>>> tap:tapdisk:ioemu:/pathto/file.img >>>>>>>>>>>> >>>>>>>>>>>> but got the dreaded "Error: Device 768 (tap) >> could not be >>>>>>>>>>>> connected. Hotplug scripts not working" >>>>>>>>>>>> >>>>>>>>>>>> Am I missing something in the syntax for blktap2? >>>>>>>>>>>> Is there a how-to or readme I didn't find? Or >>>>>>>>>>>> is there some required dependency I don't know about >>>>>>>>>>>> that is missing? >>>>>>>>>>>> >>>>>>>>>>>> I thought maybe I had a bad install, so rebuilt and >>>>>>>>>>>> reinstalled with the same result. >>>>>>>>>>>> >>>>>>>>>>>> xend.log and config file attached. >>>>>>>>>>>> >>>>>>>>>>>> Thanks, >>>>>>>>>>>> Dan >>>>>>>>>>>> >>>>>>>>>>>> P.S. I am trying blktap2 because both blktap and >>>>>>>>>>>> file-backed fail. Blktap sometimes reads garbage >>>>>>>>>>>> from the file and >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Xen-devel mailing list >>>>>>>>>>>> Xen-devel@lists.xensource.com >>>>>>>>>>>> http://lists.xensource.com/xen-devel >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Xen-devel mailing list >>>>>>>>> Xen-devel@lists.xensource.com >>>>>>>>> http://lists.xensource.com/xen-devel >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Xen-devel mailing list >>>>>>> Xen-devel@lists.xensource.com >>>>>>> http://lists.xensource.com/xen-devel >>>>>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Xen-devel mailing list >>>> Xen-devel@lists.xensource.com >>>> http://lists.xensource.com/xen-devel >>> >>> >> >> >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel >> ^ permalink raw reply [flat|nested] 20+ messages in thread
* RE: Dom0 crashing when built with c/s 881 (Was: blktap2: need more than 3 values to unpack) 2009-06-03 20:46 ` Keir Fraser @ 2009-06-03 21:17 ` Dan Magenheimer 2009-06-03 21:27 ` Keir Fraser 0 siblings, 1 reply; 20+ messages in thread From: Dan Magenheimer @ 2009-06-03 21:17 UTC (permalink / raw) To: Keir Fraser, Dulloor, Isaku Yamahata; +Cc: Xen-Devel (E-mail) Well, hmmm. > 1. It only adds extra functionality which by default would > not do anything. > Just reading the patch I can see it's harmless by itself as it merely > introduces a new notifier chain which noone registers on. I won't pretend to understand the code, but I did reproduce the problem with 881 by itself and with 889 with 881 reverted. > 2. Changeset 882 depends on 881. If you revert just 881 then > the tree will not build. This doesn't appear to be the case for me, though I'm certainly willing to believe there's something wrong with my process: 1) I build* 889 successfully. (It fails to run and I reboot to Linux.) 2) I revert 881 with # cd .../xen-unstable.hg # cd linux-2.6.18-xen.hg # hg diff -r880 -r881 | patch -p1 -R # # the patch output shows the same four files as 881 # cd .. 3) I insert a syntax error in include/linux/device.h and build* again. Build fails (as expected). 4) I remove the syntax error and build* again, build succeeds, installs and reboots fine. * My build process is: # cd .../xen-unstable.hg # KERNELS=linux-2.6-xen0 make linux-2.6-xen-clean # yes "" | KERNELS=linux-2.6-xen0 make \ linux-2.6-xen-config CONFIGMODE=oldconfig # KERNELS=linux-2.6-xen0 make linux-2.6-xen-build # KERNELS=linux-2.6-xen0 make linux-2.6-xen-install and I always check /boot/vmlinux-2.6.18.8-xen to ensure the install succeeded. > -----Original Message----- > From: Keir Fraser [mailto:keir.fraser@eu.citrix.com] > Sent: Wednesday, June 03, 2009 2:47 PM > To: Dan Magenheimer; Dulloor; Isaku Yamahata > Cc: Xen-Devel (E-mail) > Subject: Re: Dom0 crashing when built with c/s 881 (Was: [Xen-devel] > blktap2: need more than 3 values to unpack) > > > Changeset 881 is "pcie io space multiplex: backport of bus event > notification patch", right? I don't believe that you are > reverting just that > patch, for two reasons: > 1. It only adds extra functionality which by default would > not do anything. > Just reading the patch I can see it's harmless by itself as it merely > introduces a new notifier chain which noone registers on. > 2. Changeset 882 depends on 881. If you revert just 881 then > the tree will > not build. > > -- Keir > > On 03/06/2009 21:15, "Dan Magenheimer" > <dan.magenheimer@oracle.com> wrote: > > >>> Is it better to have the new option added by > >>> c/s(CONFIG_PCI_IOMULTI) default 'n' ? > > > > Turning off that option doesn't stop my dom0 from crashing. > > Reverting 881 DOES stop my dom0 from crashing. Attached are > > the boot output for fail and success (the only difference > > between the two dom0's is the success has 881 reverted). > > > > Of note, the fail log has three lines of the type: > > > > "Driver 'xxx' needs updating - please use bus_type methods" > > > > (xxx = usbfs, hub, usb) and the success log has a line that says: > > > > "PCI IO multiplexer device installed" > > > > which is missing in the fail log. > > > >> -----Original Message----- > >> From: Keir Fraser [mailto:keir.fraser@eu.citrix.com] > >> Sent: Wednesday, June 03, 2009 12:45 PM > >> To: Dulloor > >> Cc: Isaku Yamahata; Dan Magenheimer; Xen-Devel (E-mail) > >> Subject: Re: Dom0 crashing when built with c/s 881 (Was: > [Xen-devel] > >> blktap2: need more than 3 values to unpack) > >> > >> > >> Depends on the feature's impact when unused. > >> > >> -- Keir > >> > >> On 03/06/2009 18:57, "Dulloor" <dulloor@gmail.com> wrote: > >> > >>> Is it better to have the new option added by > >> c/s(CONFIG_PCI_IOMULTI) default > >>> 'n' ? > >>> > >>> -dulloor > >>> > >>> On Wed, Jun 3, 2009 at 1:48 PM, Keir Fraser > >> <keir.fraser@eu.citrix.com> wrote: > >>>> Perhaps post a diff of boot output with c/s 880 vs c/s > >> 881. I've cc'ed > >>>> Isaku, who submitted the patch that's causing your problem. > >>>> > >>>> -- Keir > >>>> > >>>> On 03/06/2009 18:35, "Dan Magenheimer" > >> <dan.magenheimer@oracle.com> wrote: > >>>> > >>>>> OK, it appears that linux-2.6.18-xen.hg c/s 881 is causing > >>>>> my dom0 to crash. Dom0 boots successfully at 880 and fails > >>>>> with 881 or anything after. > >>>>> > >>>>> Any ideas? > >>>>> > >>>>>> -----Original Message----- > >>>>>> From: Dan Magenheimer > >>>>>> Sent: Tuesday, June 02, 2009 10:45 PM > >>>>>> To: Dan Magenheimer; Keir Fraser; Dutch Meyer; > Xen-Devel (E-mail) > >>>>>> Subject: RE: [Xen-devel] blktap2: need more than 3 > >> values to unpack > >>>>>> > >>>>>> > >>>>>> Followup: my dom0 boots failed with 888, boots fine with 876, > >>>>>> then to ensure no pilot error, I rebuilt 888 again and it > >>>>>> failed again. > >>>>>> > >>>>>>> -----Original Message----- > >>>>>>> From: Dan Magenheimer > >>>>>>> Sent: Tuesday, June 02, 2009 5:50 PM > >>>>>>> To: Keir Fraser; Dutch Meyer; Xen-Devel (E-mail) > >>>>>>> Subject: RE: [Xen-devel] blktap2: need more than 3 > >> values to unpack > >>>>>>> > >>>>>>> > >>>>>>> Thanks. It is indeed a pilot error on my part but a bit > >>>>>>> more bizarre. I apparently have a linux-2.6-xen.hg directory > >>>>>>> as both a sister and a child to xen-unstable.hg. In this > >>>>>>> case the build apparently chooses the child. I was > >>>>>>> looking at and modifying the un-updated child so > >>>>>>> blktap2 wasn't even present yet. Removing the child > >>>>>>> causes the sibling to build. BUT! Now dom0 is > >>>>>>> crashing early on during boot. (This is an Intel > >>>>>>> Weybridge box.) I'll look into this further tomorrow. > >>>>>>> > >>>>>>> ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > >>>>>>> ata2.00: ATAPI, max UDMA/100 > >>>>>>> ata2.00: configured for UDMA/100 > >>>>>>> scsi2 : ahci > >>>>>>> ata3: SATA link down (SStatus 0 SControl 300) > >>>>>>> scsi3 : ahci > >>>>>>> ata4: SATA link down (SStatus 0 SControl 300) > >>>>>>> Vendor: ATA Model: ST3320620AS Rev: 3.AA > >>>>>>> Type: Direct-Access ANSI SCSI > >> revision: 05 > >>>>>>> ata1: EH pending after completion, repeating EH (cnt=4) > >>>>>>> Vendor: LITE-ON Model: DVDRW LH-20A1S Rev: 9L03 > >>>>>>> Type: CD-ROM ANSI SCSI > >> revision: 05 > >>>>>>> (XEN) PCI add device 00:1f.5 > >>>>>>> ata_piix 0000:00:1f.5: MAP [ P0 P2 P1 P3 ] > >>>>>>> ACPI: PCI Interrupt 0000:00:1f.5[B] -> GSI 19 (level, > >> low) -> IRQ 16 > >>>>>>> ata5: SATA max UDMA/133 cmd 0x0 ctl 0x2 bmdma 0x0 irq 16 > >>>>>>> ata6: SATA max UDMA/133 cmd 0x0 ctl 0x2 bmdma 0x0 irq 16 > >>>>>>> scsi4 : ata_piix > >>>>>>> scsi5 : ata_piix > >>>>>>> device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: > >>>>>>> dm-devel@redhat.com > >>>>>>> Kernel panic - not syncing: Attempted to kill init! > >>>>>>> (XEN) Domain 0 crashed: rebooting machine in 5 seconds. > >>>>>>> > >>>>>>>> -----Original Message----- > >>>>>>>> From: Keir Fraser [mailto:keir.fraser@eu.citrix.com] > >>>>>>>> Sent: Tuesday, June 02, 2009 4:45 PM > >>>>>>>> To: Dan Magenheimer; Dutch Meyer; Xen-Devel (E-mail) > >>>>>>>> Subject: Re: [Xen-devel] blktap2: need more than 3 values > >>>>>> to unpack > >>>>>>>> > >>>>>>>> > >>>>>>>> Probably you had an old .config hanging around in your build > >>>>>>>> tree somewhere. > >>>>>>>> c/s 889 should fix this for a fresh build. > >>>>>>>> > >>>>>>>> -- Keir > >>>>>>>> > >>>>>>>> On 02/06/2009 18:33, "Dan Magenheimer" > >>>>>>>> <dan.magenheimer@oracle.com> wrote: > >>>>>>>> > >>>>>>>>> Thanks. Looks like a partial configuration patch > got checked > >>>>>>>>> in for blktap2 (cs 886)? CONFIG_XEN_BLKDEV_TAP2 must be > >>>>>>> configured > >>>>>>>>> but afaict is not turned on by default (yet?). So a fresh > >>>>>>>>> xen-unstable tip doesn't build the blktap2 driver. See: > >>>>>>>>> > >>>>>>>>> > >>>>>> > http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/3e01555dd227 > >>>>>>>>> > >>>>>>>>> (I'm guessing since this was submitted by Isaku that blktap2 > >>>>>>>>> shouldn't be the default on ia64?) > >>>>>>>>> > >>>>>>>>> Should CONFIG_XEN_BLKDEV_TAP2 be turned on by > default, instead > >>>>>>>>> of CONFIG_XEN_BLKDEV_TAP, at least on x86? > >>>>>>>>> > >>>>>>>>> I tried modifying > >>>>>>>>> > >>>>>>>>> linux-2.6.18-xen.hg/buildconfigs/linux-defconfig_xen0_x86_32 > >>>>>>>>> > >>>>>>>>> (and also > >>>>>>>>> > >>>>>>>>> linux-2.6.18-xen.hg/buildconfigs/linux-defconfig_xen_x86_32) > >>>>>>>>> > >>>>>>>>> followed by: > >>>>>>>>> > >>>>>>>>> KERNELS=linux-2.6-xen0 make linux-2.6-xen-config > >>>>>>>> CONFIGMODE=oldconfig > >>>>>>>>> > >>>>>>>>> (I don't need or want to go through a manual config process) > >>>>>>>>> > >>>>>>>>> but BLKDEV_TAP is always selected, not BLKDEV_TAP2. > >>>>>>>>> > >>>>>>>>> Finally, I resorted to manually changing > >>>>>>>>> > >>>>>>>>> linux-2.6.18-xen.hg/drivers/xen/Kconfig > >>>>>>>>> > >>>>>>>>> and this succeeds in turning it on, but it just reverses the > >>>>>>>>> above checked-in patch, so I suspect that's not the right > >>>>>>>>> answer either. > >>>>>>>>> > >>>>>>>>>> -----Original Message----- > >>>>>>>>>> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] > >>>>>>>>>> Sent: Tuesday, June 02, 2009 9:05 AM > >>>>>>>>>> To: Dan Magenheimer > >>>>>>>>>> Subject: RE: [Xen-devel] blktap2: need more than 3 > >>>>>>> values to unpack > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> I think that you don't have the blktap2 driver loaded in > >>>>>>>>>> dom0. A clean > >>>>>>>>>> build/install of the dom0 kernel image should sort > >> you out. If > >>>>>>>>>> drivers/xen/blktap2 is compiled in it should be setting up > >>>>>>>>>> these paths. > >>>>>>>>>> > >>>>>>>>>> Let me know if that fixes things and I'll make python > >>>>>>> spit out more > >>>>>>>>>> meaningful errors, otherwise we can try to figure out the > >>>>>>>>>> blktap2 kernel > >>>>>>>>>> code isn't working. > >>>>>>>>>> > >>>>>>>>>> --Dutch > >>>>>>>>>> > >>>>>>>>>> On Tue, 2 Jun 2009, Dan Magenheimer wrote: > >>>>>>>>>> > >>>>>>>>>>> It replies with "didn't find blktap-control in /proc/misc" > >>>>>>>>>>> > >>>>>>>>>>> If that fails, perhaps the path doesn't exist, > but I looked > >>>>>>>>>>> and /sys/class/blktap2 doesn't exist. > >>>>>>>>>>> > >>>>>>>>>>>> -----Original Message----- > >>>>>>>>>>>> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] > >>>>>>>>>>>> Sent: Monday, June 01, 2009 10:37 PM > >>>>>>>>>>>> To: Dan Magenheimer > >>>>>>>>>>>> Subject: RE: [Xen-devel] blktap2: need more than 3 > >>>>>>>> values to unpack > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> Can you try this from the command line: > >>>>>>>>>>>> > >>>>>>>>>>>> tapdisk2 -n aio:/pathto/file.img > >>>>>>>>>>>> > >>>>>>>>>>>> If successful, this will create your aio device > and print a > >>>>>>>>>>>> /dev device > >>>>>>>>>>>> associated with it. > >>>>>>>>>>>> > >>>>>>>>>>>> In that case you'll then be able to remove it with: > >>>>>>>>>>>> > >>>>>>>>>>>> echo 1 > /sys/class/blktap2/<disk>/remove > >>>>>>>>>>>> > >>>>>>>>>>>> Where <disk> will be obvious from the output of the > >>>>>>>>>> tapdisk2 command. > >>>>>>>>>>>> > >>>>>>>>>>>> However, I expect that this will fail. > >>>>>>>>>>>> > >>>>>>>>>>>> --Dutch > >>>>>>>>>>>> > >>>>>>>>>>>> On Mon, 1 Jun 2009, Dan Magenheimer wrote: > >>>>>>>>>>>> > >>>>>>>>>>>> Then I might be able to help, but I'm not sure how to > >>>>>>>>>>>> reproduce it. If > >>>>>>>>>>>> you send a log file and config for this latter error I'll > >>>>>>>>>>>> take a look. > >>>>>>>>>>>> > >>>>>>>>>>>> Here ya go. > >>>>>>>>>>>> > >>>>>>>>>>>> Thanks, > >>>>>>>>>>>> Dan > >>>>>>>>>>>> > >>>>>>>>>>>> -----Original Message----- > >>>>>>>>>>>> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] > >>>>>>>>>>>> Sent: Monday, June 01, 2009 8:32 PM > >>>>>>>>>>>> To: Dan Magenheimer > >>>>>>>>>>>> Cc: Xen-Devel (E-mail) > >>>>>>>>>>>> Subject: Re: [Xen-devel] blktap2: need more than 3 > >>>>>>>>>> values to unpack > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> The tap:aio:/pathto/file.img syntax that you're > >>>>>> using in your > >>>>>>>>>>>> config was > >>>>>>>>>>>> changed before blktap2 was introduced. > >>>>>>>>>>>> tap:tapdisk:aio:/pathto/file.img is > >>>>>>>>>>>> apparently the correct syntax now, though the > >> README didn't > >>>>>>>>>>>> get updated to > >>>>>>>>>>>> reflect this. Our blktap2 documentation is no better - > >>>>>>>>>> I'll try to > >>>>>>>>>>>> remedy that this week. > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> If you're still seeing this error: > >>>>>>>>>>>> "Error: 'file' object has no attribute 'find'" > >>>>>>>>>>>> > >>>>>>>>>>>> Then I might be able to help, but I'm not sure how to > >>>>>>>>>>>> reproduce it. If > >>>>>>>>>>>> you send a log file and config for this latter error I'll > >>>>>>>>>>>> take a look. > >>>>>>>>>>>> Yang seems to be reporting the same thing in > >>>>>> another thread. > >>>>>>>>>>>> > >>>>>>>>>>>> --Dutch > >>>>>>>>>>>> > >>>>>>>>>>>> On Mon, 1 Jun 2009, Dan Magenheimer wrote: > >>>>>>>>>>>> > >>>>>>>>>>>> Hmmm... trying blktap2 for the first time, using 19682. > >>>>>>>>>>>> I had thought that the syntax hadn't changed, but I am > >>>>>>>>>>>> getting what appears to be a parsing error on > >> my vbd line. > >>>>>>>>>>>> > >>>>>>>>>>>> "ValueError: need more than 3 values to unpack" > >>>>>>>>>>>> > >>>>>>>>>>>> Thinking maybe that "w!" was the culprit, I changed > >>>>>>>>>>>> it to "w" with no change in result. > >>>>>>>>>>>> > >>>>>>>>>>>> Looking at the python code that generated the error, > >>>>>>>>>>>> I tried to figure out the syntax by experimentation > >>>>>>>>>>>> but without luck. I tried: > >>>>>>>>>>>> > >>>>>>>>>>>> tap:tapdisk:aio:/pathto/file.img > >>>>>>>>>>>> > >>>>>>>>>>>> but got "Error: 'file' object has no attribute 'find'" > >>>>>>>>>>>> > >>>>>>>>>>>> To see if I could use the old blktap, I tried > >>>>>>>>>>>> > >>>>>>>>>>>> tap:tapdisk:ioemu:/pathto/file.img > >>>>>>>>>>>> > >>>>>>>>>>>> but got the dreaded "Error: Device 768 (tap) > >> could not be > >>>>>>>>>>>> connected. Hotplug scripts not working" > >>>>>>>>>>>> > >>>>>>>>>>>> Am I missing something in the syntax for blktap2? > >>>>>>>>>>>> Is there a how-to or readme I didn't find? Or > >>>>>>>>>>>> is there some required dependency I don't know about > >>>>>>>>>>>> that is missing? > >>>>>>>>>>>> > >>>>>>>>>>>> I thought maybe I had a bad install, so rebuilt and > >>>>>>>>>>>> reinstalled with the same result. > >>>>>>>>>>>> > >>>>>>>>>>>> xend.log and config file attached. > >>>>>>>>>>>> > >>>>>>>>>>>> Thanks, > >>>>>>>>>>>> Dan > >>>>>>>>>>>> > >>>>>>>>>>>> P.S. I am trying blktap2 because both blktap and > >>>>>>>>>>>> file-backed fail. Blktap sometimes reads garbage > >>>>>>>>>>>> from the file and > >>>>>>>>>>>> > >>>>>>>>>>>> _______________________________________________ > >>>>>>>>>>>> Xen-devel mailing list > >>>>>>>>>>>> Xen-devel@lists.xensource.com > >>>>>>>>>>>> http://lists.xensource.com/xen-devel > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>> > >>>>>>>>> > >>>>>>>>> _______________________________________________ > >>>>>>>>> Xen-devel mailing list > >>>>>>>>> Xen-devel@lists.xensource.com > >>>>>>>>> http://lists.xensource.com/xen-devel > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>> > >>>>>>> _______________________________________________ > >>>>>>> Xen-devel mailing list > >>>>>>> Xen-devel@lists.xensource.com > >>>>>>> http://lists.xensource.com/xen-devel > >>>>>>> > >>>> > >>>> > >>>> > >>>> _______________________________________________ > >>>> Xen-devel mailing list > >>>> Xen-devel@lists.xensource.com > >>>> http://lists.xensource.com/xen-devel > >>> > >>> > >> > >> > >> > >> _______________________________________________ > >> Xen-devel mailing list > >> Xen-devel@lists.xensource.com > >> http://lists.xensource.com/xen-devel > >> > > > ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Dom0 crashing when built with c/s 881 (Was: blktap2: need more than 3 values to unpack) 2009-06-03 21:17 ` Dan Magenheimer @ 2009-06-03 21:27 ` Keir Fraser 2009-06-03 22:12 ` Dan Magenheimer 0 siblings, 1 reply; 20+ messages in thread From: Keir Fraser @ 2009-06-03 21:27 UTC (permalink / raw) To: Dan Magenheimer, Isaku Yamahata; +Cc: Xen-Devel (E-mail) On 03/06/2009 22:17, "Dan Magenheimer" <dan.magenheimer@oracle.com> wrote: >> 1. It only adds extra functionality which by default would >> not do anything. >> Just reading the patch I can see it's harmless by itself as it merely >> introduces a new notifier chain which noone registers on. > > I won't pretend to understand the code, but I did > reproduce the problem with 881 by itself and with > 889 with 881 reverted. I can't explain that from reading the code. It looks like a no-op to me unless the new function bus_register_notifier() is called. >> 2. Changeset 882 depends on 881. If you revert just 881 then >> the tree will not build. > > This doesn't appear to be the case for me, though > I'm certainly willing to believe there's something > wrong with my process: Actually I missed that the dependent code is only built if CONFIG_PCI_IOMULTI && CONFIG_HOTPLUG_PCI. You've probably got one or both disabled and hence 882 doesn't break without 881 in your case. -- Keir ^ permalink raw reply [flat|nested] 20+ messages in thread
* RE: Dom0 crashing when built with c/s 881 (Was: blktap2: need more than 3 values to unpack) 2009-06-03 21:27 ` Keir Fraser @ 2009-06-03 22:12 ` Dan Magenheimer 2009-06-04 1:09 ` Dan Magenheimer 2009-06-04 4:18 ` Isaku Yamahata 0 siblings, 2 replies; 20+ messages in thread From: Dan Magenheimer @ 2009-06-03 22:12 UTC (permalink / raw) To: Keir Fraser, Isaku Yamahata; +Cc: Xen-Devel (E-mail) > Actually I missed that the dependent code is only built if > CONFIG_PCI_IOMULTI && CONFIG_HOTPLUG_PCI. You've probably got > one or both > disabled and hence 882 doesn't break without 881 in your case. In case it helps, with 889 and 881 reverted, I am using the default config which results in CONFIG_PCI_IOMULTI=y and CONFIG_HOTPLUG_PCI=m. > I can't explain that from reading the code. It looks like a > no-op to me > unless the new function bus_register_notifier() is called. Looking at my boot output on failure, there are those lines: "Driver 'xxx' needs updating - please use bus_type methods" which is printed in linux/drivers/base/driver.c:driver_register() if a complex set of circumstances are true. So clearly something is different. If that doesn't help, I can go add some printk's where that output is happening and see exactly what forces the failure. Dan > -----Original Message----- > From: Keir Fraser [mailto:keir.fraser@eu.citrix.com] > Sent: Wednesday, June 03, 2009 3:28 PM > To: Dan Magenheimer; Isaku Yamahata > Cc: Xen-Devel (E-mail) > Subject: Re: Dom0 crashing when built with c/s 881 (Was: [Xen-devel] > blktap2: need more than 3 values to unpack) > > > On 03/06/2009 22:17, "Dan Magenheimer" > <dan.magenheimer@oracle.com> wrote: > > >> 1. It only adds extra functionality which by default would > >> not do anything. > >> Just reading the patch I can see it's harmless by itself > as it merely > >> introduces a new notifier chain which noone registers on. > > > > I won't pretend to understand the code, but I did > > reproduce the problem with 881 by itself and with > > 889 with 881 reverted. > > I can't explain that from reading the code. It looks like a > no-op to me > unless the new function bus_register_notifier() is called. > > >> 2. Changeset 882 depends on 881. If you revert just 881 then > >> the tree will not build. > > > > This doesn't appear to be the case for me, though > > I'm certainly willing to believe there's something > > wrong with my process: > > Actually I missed that the dependent code is only built if > CONFIG_PCI_IOMULTI && CONFIG_HOTPLUG_PCI. You've probably got > one or both > disabled and hence 882 doesn't break without 881 in your case. > > -- Keir > > > ^ permalink raw reply [flat|nested] 20+ messages in thread
* RE: Dom0 crashing when built with c/s 881 (Was: blktap2: need more than 3 values to unpack) 2009-06-03 22:12 ` Dan Magenheimer @ 2009-06-04 1:09 ` Dan Magenheimer 2009-06-04 4:49 ` Dan Magenheimer 2009-06-04 4:18 ` Isaku Yamahata 1 sibling, 1 reply; 20+ messages in thread From: Dan Magenheimer @ 2009-06-04 1:09 UTC (permalink / raw) To: Keir Fraser, Isaku Yamahata; +Cc: Xen-Devel (E-mail) > If that doesn't help, I can go add some printk's where that > output is happening and see exactly what forces the failure. Here's what I am seeing. Looks like the drv->bus structure is getting overwritten with ASCII. Driver 'usbfs' needs updating - please use bus_type methods drv->bus->probe = 73756f6e (THAT's "nous" I think) drv->probe = d1069ab0 drv->bus->remove = 00000062 drv->remove = d1069960 drv->bus->shutdown = 00000000 drv->shutdown = 00000000 usbcore: registered new driver usbfs Driver 'hub' needs updating - please use bus_type methods drv->bus->probe = 73756f6e drv->probe = d1069ab0 drv->bus->remove = 00000062 drv->remove = d1069960 drv->bus->shutdown = 00000000 drv->shutdown = 00000000 usbcore: registered new driver hub Driver 'usb' needs updating - please use bus_type methods drv->bus->probe = 73756f6e drv->probe = d1069570 > -----Original Message----- > From: Dan Magenheimer > Sent: Wednesday, June 03, 2009 4:12 PM > To: Keir Fraser; Isaku Yamahata > Cc: Xen-Devel (E-mail) > Subject: RE: Dom0 crashing when built with c/s 881 (Was: [Xen-devel] > blktap2: need more than 3 values to unpack) > > > > Actually I missed that the dependent code is only built if > > CONFIG_PCI_IOMULTI && CONFIG_HOTPLUG_PCI. You've probably got > > one or both > > disabled and hence 882 doesn't break without 881 in your case. > > In case it helps, with 889 and 881 reverted, I am using the > default config which results in CONFIG_PCI_IOMULTI=y and > CONFIG_HOTPLUG_PCI=m. > > > I can't explain that from reading the code. It looks like a > > no-op to me > > unless the new function bus_register_notifier() is called. > > Looking at my boot output on failure, there are those lines: > > "Driver 'xxx' needs updating - please use bus_type methods" > > which is printed in linux/drivers/base/driver.c:driver_register() > if a complex set of circumstances are true. So clearly > something is different. > > If that doesn't help, I can go add some printk's where that > output is happening and see exactly what forces the failure. > > Dan > > > > -----Original Message----- > > From: Keir Fraser [mailto:keir.fraser@eu.citrix.com] > > Sent: Wednesday, June 03, 2009 3:28 PM > > To: Dan Magenheimer; Isaku Yamahata > > Cc: Xen-Devel (E-mail) > > Subject: Re: Dom0 crashing when built with c/s 881 (Was: [Xen-devel] > > blktap2: need more than 3 values to unpack) > > > > > > On 03/06/2009 22:17, "Dan Magenheimer" > > <dan.magenheimer@oracle.com> wrote: > > > > >> 1. It only adds extra functionality which by default would > > >> not do anything. > > >> Just reading the patch I can see it's harmless by itself > > as it merely > > >> introduces a new notifier chain which noone registers on. > > > > > > I won't pretend to understand the code, but I did > > > reproduce the problem with 881 by itself and with > > > 889 with 881 reverted. > > > > I can't explain that from reading the code. It looks like a > > no-op to me > > unless the new function bus_register_notifier() is called. > > > > >> 2. Changeset 882 depends on 881. If you revert just 881 then > > >> the tree will not build. > > > > > > This doesn't appear to be the case for me, though > > > I'm certainly willing to believe there's something > > > wrong with my process: > > > > Actually I missed that the dependent code is only built if > > CONFIG_PCI_IOMULTI && CONFIG_HOTPLUG_PCI. You've probably got > > one or both > > disabled and hence 882 doesn't break without 881 in your case. > > > > -- Keir > > > > > > ^ permalink raw reply [flat|nested] 20+ messages in thread
* RE: Dom0 crashing when built with c/s 881 (Was: blktap2: need more than 3 values to unpack) 2009-06-04 1:09 ` Dan Magenheimer @ 2009-06-04 4:49 ` Dan Magenheimer 2009-06-04 7:34 ` Keir Fraser 0 siblings, 1 reply; 20+ messages in thread From: Dan Magenheimer @ 2009-06-04 4:49 UTC (permalink / raw) To: dan.magenheimer, Keir Fraser, Isaku Yamahata; +Cc: Xen-Devel (E-mail) I'm quitting for the night now, but I see that the string "nous" is followed by a "b" in the immediately following word. Put this together and you have "nousb" (read as turn off USB). Given that the "Driver 'xxx' needs updating" are for 'usbfs', 'hub', and 'usb', and given that usb is very related to hotplug, the string "nousb" where a pair of function pointers should be is suspicious (though it may also be a complete coincidence). I'll try turning off CONFIG_HOTPLUG_PCI tomorrow. Dan > -----Original Message----- > From: Dan Magenheimer > Sent: Wednesday, June 03, 2009 7:09 PM > To: Keir Fraser; Isaku Yamahata > Cc: Xen-Devel (E-mail) > Subject: RE: Dom0 crashing when built with c/s 881 (Was: [Xen-devel] > blktap2: need more than 3 values to unpack) > > > > If that doesn't help, I can go add some printk's where that > > output is happening and see exactly what forces the failure. > > Here's what I am seeing. Looks like the drv->bus structure > is getting overwritten with ASCII. > > Driver 'usbfs' needs updating - please use bus_type methods > drv->bus->probe = 73756f6e (THAT's "nous" I think) > drv->probe = d1069ab0 > drv->bus->remove = 00000062 > drv->remove = d1069960 > drv->bus->shutdown = 00000000 > drv->shutdown = 00000000 > usbcore: registered new driver usbfs > Driver 'hub' needs updating - please use bus_type methods > drv->bus->probe = 73756f6e > drv->probe = d1069ab0 > drv->bus->remove = 00000062 > drv->remove = d1069960 > drv->bus->shutdown = 00000000 > drv->shutdown = 00000000 > usbcore: registered new driver hub > Driver 'usb' needs updating - please use bus_type methods > drv->bus->probe = 73756f6e > drv->probe = d1069570 > > > -----Original Message----- > > From: Dan Magenheimer > > Sent: Wednesday, June 03, 2009 4:12 PM > > To: Keir Fraser; Isaku Yamahata > > Cc: Xen-Devel (E-mail) > > Subject: RE: Dom0 crashing when built with c/s 881 (Was: [Xen-devel] > > blktap2: need more than 3 values to unpack) > > > > > > > Actually I missed that the dependent code is only built if > > > CONFIG_PCI_IOMULTI && CONFIG_HOTPLUG_PCI. You've probably got > > > one or both > > > disabled and hence 882 doesn't break without 881 in your case. > > > > In case it helps, with 889 and 881 reverted, I am using the > > default config which results in CONFIG_PCI_IOMULTI=y and > > CONFIG_HOTPLUG_PCI=m. > > > > > I can't explain that from reading the code. It looks like a > > > no-op to me > > > unless the new function bus_register_notifier() is called. > > > > Looking at my boot output on failure, there are those lines: > > > > "Driver 'xxx' needs updating - please use bus_type methods" > > > > which is printed in linux/drivers/base/driver.c:driver_register() > > if a complex set of circumstances are true. So clearly > > something is different. > > > > If that doesn't help, I can go add some printk's where that > > output is happening and see exactly what forces the failure. > > > > Dan > > > > > > > -----Original Message----- > > > From: Keir Fraser [mailto:keir.fraser@eu.citrix.com] > > > Sent: Wednesday, June 03, 2009 3:28 PM > > > To: Dan Magenheimer; Isaku Yamahata > > > Cc: Xen-Devel (E-mail) > > > Subject: Re: Dom0 crashing when built with c/s 881 (Was: > [Xen-devel] > > > blktap2: need more than 3 values to unpack) > > > > > > > > > On 03/06/2009 22:17, "Dan Magenheimer" > > > <dan.magenheimer@oracle.com> wrote: > > > > > > >> 1. It only adds extra functionality which by default would > > > >> not do anything. > > > >> Just reading the patch I can see it's harmless by itself > > > as it merely > > > >> introduces a new notifier chain which noone registers on. > > > > > > > > I won't pretend to understand the code, but I did > > > > reproduce the problem with 881 by itself and with > > > > 889 with 881 reverted. > > > > > > I can't explain that from reading the code. It looks like a > > > no-op to me > > > unless the new function bus_register_notifier() is called. > > > > > > >> 2. Changeset 882 depends on 881. If you revert just 881 then > > > >> the tree will not build. > > > > > > > > This doesn't appear to be the case for me, though > > > > I'm certainly willing to believe there's something > > > > wrong with my process: > > > > > > Actually I missed that the dependent code is only built if > > > CONFIG_PCI_IOMULTI && CONFIG_HOTPLUG_PCI. You've probably got > > > one or both > > > disabled and hence 882 doesn't break without 881 in your case. > > > > > > -- Keir > > > > > > > > > ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Dom0 crashing when built with c/s 881 (Was: blktap2: need more than 3 values to unpack) 2009-06-04 4:49 ` Dan Magenheimer @ 2009-06-04 7:34 ` Keir Fraser 2009-06-04 16:11 ` Dan Magenheimer 0 siblings, 1 reply; 20+ messages in thread From: Keir Fraser @ 2009-06-04 7:34 UTC (permalink / raw) To: Dan Magenheimer, Isaku Yamahata; +Cc: Xen-Devel (E-mail) If memory corruption is the issue, c/s 881 could be innocently triggering a latent bug. -- Keir On 04/06/2009 05:49, "Dan Magenheimer" <dan.magenheimer@oracle.com> wrote: > I'm quitting for the night now, but I see that > the string "nous" is followed by a "b" in the > immediately following word. Put this together > and you have "nousb" (read as turn off USB). > > Given that the "Driver 'xxx' needs updating" > are for 'usbfs', 'hub', and 'usb', and given > that usb is very related to hotplug, the string > "nousb" where a pair of function pointers should > be is suspicious (though it may also be a complete > coincidence). > > I'll try turning off CONFIG_HOTPLUG_PCI tomorrow. > > Dan > >> -----Original Message----- >> From: Dan Magenheimer >> Sent: Wednesday, June 03, 2009 7:09 PM >> To: Keir Fraser; Isaku Yamahata >> Cc: Xen-Devel (E-mail) >> Subject: RE: Dom0 crashing when built with c/s 881 (Was: [Xen-devel] >> blktap2: need more than 3 values to unpack) >> >> >>> If that doesn't help, I can go add some printk's where that >>> output is happening and see exactly what forces the failure. >> >> Here's what I am seeing. Looks like the drv->bus structure >> is getting overwritten with ASCII. >> >> Driver 'usbfs' needs updating - please use bus_type methods >> drv->bus->probe = 73756f6e (THAT's "nous" I think) >> drv->probe = d1069ab0 >> drv->bus->remove = 00000062 >> drv->remove = d1069960 >> drv->bus->shutdown = 00000000 >> drv->shutdown = 00000000 >> usbcore: registered new driver usbfs >> Driver 'hub' needs updating - please use bus_type methods >> drv->bus->probe = 73756f6e >> drv->probe = d1069ab0 >> drv->bus->remove = 00000062 >> drv->remove = d1069960 >> drv->bus->shutdown = 00000000 >> drv->shutdown = 00000000 >> usbcore: registered new driver hub >> Driver 'usb' needs updating - please use bus_type methods >> drv->bus->probe = 73756f6e >> drv->probe = d1069570 >> >>> -----Original Message----- >>> From: Dan Magenheimer >>> Sent: Wednesday, June 03, 2009 4:12 PM >>> To: Keir Fraser; Isaku Yamahata >>> Cc: Xen-Devel (E-mail) >>> Subject: RE: Dom0 crashing when built with c/s 881 (Was: [Xen-devel] >>> blktap2: need more than 3 values to unpack) >>> >>> >>>> Actually I missed that the dependent code is only built if >>>> CONFIG_PCI_IOMULTI && CONFIG_HOTPLUG_PCI. You've probably got >>>> one or both >>>> disabled and hence 882 doesn't break without 881 in your case. >>> >>> In case it helps, with 889 and 881 reverted, I am using the >>> default config which results in CONFIG_PCI_IOMULTI=y and >>> CONFIG_HOTPLUG_PCI=m. >>> >>>> I can't explain that from reading the code. It looks like a >>>> no-op to me >>>> unless the new function bus_register_notifier() is called. >>> >>> Looking at my boot output on failure, there are those lines: >>> >>> "Driver 'xxx' needs updating - please use bus_type methods" >>> >>> which is printed in linux/drivers/base/driver.c:driver_register() >>> if a complex set of circumstances are true. So clearly >>> something is different. >>> >>> If that doesn't help, I can go add some printk's where that >>> output is happening and see exactly what forces the failure. >>> >>> Dan >>> >>> >>>> -----Original Message----- >>>> From: Keir Fraser [mailto:keir.fraser@eu.citrix.com] >>>> Sent: Wednesday, June 03, 2009 3:28 PM >>>> To: Dan Magenheimer; Isaku Yamahata >>>> Cc: Xen-Devel (E-mail) >>>> Subject: Re: Dom0 crashing when built with c/s 881 (Was: >> [Xen-devel] >>>> blktap2: need more than 3 values to unpack) >>>> >>>> >>>> On 03/06/2009 22:17, "Dan Magenheimer" >>>> <dan.magenheimer@oracle.com> wrote: >>>> >>>>>> 1. It only adds extra functionality which by default would >>>>>> not do anything. >>>>>> Just reading the patch I can see it's harmless by itself >>>> as it merely >>>>>> introduces a new notifier chain which noone registers on. >>>>> >>>>> I won't pretend to understand the code, but I did >>>>> reproduce the problem with 881 by itself and with >>>>> 889 with 881 reverted. >>>> >>>> I can't explain that from reading the code. It looks like a >>>> no-op to me >>>> unless the new function bus_register_notifier() is called. >>>> >>>>>> 2. Changeset 882 depends on 881. If you revert just 881 then >>>>>> the tree will not build. >>>>> >>>>> This doesn't appear to be the case for me, though >>>>> I'm certainly willing to believe there's something >>>>> wrong with my process: >>>> >>>> Actually I missed that the dependent code is only built if >>>> CONFIG_PCI_IOMULTI && CONFIG_HOTPLUG_PCI. You've probably got >>>> one or both >>>> disabled and hence 882 doesn't break without 881 in your case. >>>> >>>> -- Keir >>>> >>>> >>>> ^ permalink raw reply [flat|nested] 20+ messages in thread
* RE: Dom0 crashing when built with c/s 881 (Was: blktap2: need more than 3 values to unpack) 2009-06-04 7:34 ` Keir Fraser @ 2009-06-04 16:11 ` Dan Magenheimer 0 siblings, 0 replies; 20+ messages in thread From: Dan Magenheimer @ 2009-06-04 16:11 UTC (permalink / raw) To: Keir Fraser, Isaku Yamahata; +Cc: Xen-Devel (E-mail) Yes indeed. I added some code to reset the fields incorrectly containing "nousb" to their expected value of 0, and the dom0 kernel still fails to boot. So this is likely just a symptom of broader memory corruption. > -----Original Message----- > From: Keir Fraser [mailto:keir.fraser@eu.citrix.com] > Sent: Thursday, June 04, 2009 1:34 AM > To: Dan Magenheimer; Isaku Yamahata > Cc: Xen-Devel (E-mail) > Subject: Re: Dom0 crashing when built with c/s 881 (Was: [Xen-devel] > blktap2: need more than 3 values to unpack) > > > If memory corruption is the issue, c/s 881 could be > innocently triggering a > latent bug. > > -- Keir > > On 04/06/2009 05:49, "Dan Magenheimer" > <dan.magenheimer@oracle.com> wrote: > > > I'm quitting for the night now, but I see that > > the string "nous" is followed by a "b" in the > > immediately following word. Put this together > > and you have "nousb" (read as turn off USB). > > > > Given that the "Driver 'xxx' needs updating" > > are for 'usbfs', 'hub', and 'usb', and given > > that usb is very related to hotplug, the string > > "nousb" where a pair of function pointers should > > be is suspicious (though it may also be a complete > > coincidence). > > > > I'll try turning off CONFIG_HOTPLUG_PCI tomorrow. > > > > Dan > > > >> -----Original Message----- > >> From: Dan Magenheimer > >> Sent: Wednesday, June 03, 2009 7:09 PM > >> To: Keir Fraser; Isaku Yamahata > >> Cc: Xen-Devel (E-mail) > >> Subject: RE: Dom0 crashing when built with c/s 881 (Was: > [Xen-devel] > >> blktap2: need more than 3 values to unpack) > >> > >> > >>> If that doesn't help, I can go add some printk's where that > >>> output is happening and see exactly what forces the failure. > >> > >> Here's what I am seeing. Looks like the drv->bus structure > >> is getting overwritten with ASCII. > >> > >> Driver 'usbfs' needs updating - please use bus_type methods > >> drv->bus->probe = 73756f6e (THAT's "nous" I think) > >> drv->probe = d1069ab0 > >> drv->bus->remove = 00000062 > >> drv->remove = d1069960 > >> drv->bus->shutdown = 00000000 > >> drv->shutdown = 00000000 > >> usbcore: registered new driver usbfs > >> Driver 'hub' needs updating - please use bus_type methods > >> drv->bus->probe = 73756f6e > >> drv->probe = d1069ab0 > >> drv->bus->remove = 00000062 > >> drv->remove = d1069960 > >> drv->bus->shutdown = 00000000 > >> drv->shutdown = 00000000 > >> usbcore: registered new driver hub > >> Driver 'usb' needs updating - please use bus_type methods > >> drv->bus->probe = 73756f6e > >> drv->probe = d1069570 > >> > >>> -----Original Message----- > >>> From: Dan Magenheimer > >>> Sent: Wednesday, June 03, 2009 4:12 PM > >>> To: Keir Fraser; Isaku Yamahata > >>> Cc: Xen-Devel (E-mail) > >>> Subject: RE: Dom0 crashing when built with c/s 881 (Was: > [Xen-devel] > >>> blktap2: need more than 3 values to unpack) > >>> > >>> > >>>> Actually I missed that the dependent code is only built if > >>>> CONFIG_PCI_IOMULTI && CONFIG_HOTPLUG_PCI. You've probably got > >>>> one or both > >>>> disabled and hence 882 doesn't break without 881 in your case. > >>> > >>> In case it helps, with 889 and 881 reverted, I am using the > >>> default config which results in CONFIG_PCI_IOMULTI=y and > >>> CONFIG_HOTPLUG_PCI=m. > >>> > >>>> I can't explain that from reading the code. It looks like a > >>>> no-op to me > >>>> unless the new function bus_register_notifier() is called. > >>> > >>> Looking at my boot output on failure, there are those lines: > >>> > >>> "Driver 'xxx' needs updating - please use bus_type methods" > >>> > >>> which is printed in linux/drivers/base/driver.c:driver_register() > >>> if a complex set of circumstances are true. So clearly > >>> something is different. > >>> > >>> If that doesn't help, I can go add some printk's where that > >>> output is happening and see exactly what forces the failure. > >>> > >>> Dan > >>> > >>> > >>>> -----Original Message----- > >>>> From: Keir Fraser [mailto:keir.fraser@eu.citrix.com] > >>>> Sent: Wednesday, June 03, 2009 3:28 PM > >>>> To: Dan Magenheimer; Isaku Yamahata > >>>> Cc: Xen-Devel (E-mail) > >>>> Subject: Re: Dom0 crashing when built with c/s 881 (Was: > >> [Xen-devel] > >>>> blktap2: need more than 3 values to unpack) > >>>> > >>>> > >>>> On 03/06/2009 22:17, "Dan Magenheimer" > >>>> <dan.magenheimer@oracle.com> wrote: > >>>> > >>>>>> 1. It only adds extra functionality which by default would > >>>>>> not do anything. > >>>>>> Just reading the patch I can see it's harmless by itself > >>>> as it merely > >>>>>> introduces a new notifier chain which noone registers on. > >>>>> > >>>>> I won't pretend to understand the code, but I did > >>>>> reproduce the problem with 881 by itself and with > >>>>> 889 with 881 reverted. > >>>> > >>>> I can't explain that from reading the code. It looks like a > >>>> no-op to me > >>>> unless the new function bus_register_notifier() is called. > >>>> > >>>>>> 2. Changeset 882 depends on 881. If you revert just 881 then > >>>>>> the tree will not build. > >>>>> > >>>>> This doesn't appear to be the case for me, though > >>>>> I'm certainly willing to believe there's something > >>>>> wrong with my process: > >>>> > >>>> Actually I missed that the dependent code is only built if > >>>> CONFIG_PCI_IOMULTI && CONFIG_HOTPLUG_PCI. You've probably got > >>>> one or both > >>>> disabled and hence 882 doesn't break without 881 in your case. > >>>> > >>>> -- Keir > >>>> > >>>> > >>>> > > > ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Dom0 crashing when built with c/s 881 (Was: blktap2: need more than 3 values to unpack) 2009-06-03 22:12 ` Dan Magenheimer 2009-06-04 1:09 ` Dan Magenheimer @ 2009-06-04 4:18 ` Isaku Yamahata 2009-06-04 4:30 ` Isaku Yamahata 1 sibling, 1 reply; 20+ messages in thread From: Isaku Yamahata @ 2009-06-04 4:18 UTC (permalink / raw) To: Dan Magenheimer; +Cc: Xen-Devel (E-mail), Keir Fraser On Wed, Jun 03, 2009 at 03:12:10PM -0700, Dan Magenheimer wrote: > > Actually I missed that the dependent code is only built if > > CONFIG_PCI_IOMULTI && CONFIG_HOTPLUG_PCI. You've probably got > > one or both > > disabled and hence 882 doesn't break without 881 in your case. > > In case it helps, with 889 and 881 reverted, I am using the > default config which results in CONFIG_PCI_IOMULTI=y and > CONFIG_HOTPLUG_PCI=m. Ah, I tested it with CONFIG_HOTPLUG_PCI=y. So does it make difference to set it =y instead of =m? -- yamahata ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Dom0 crashing when built with c/s 881 (Was: blktap2: need more than 3 values to unpack) 2009-06-04 4:18 ` Isaku Yamahata @ 2009-06-04 4:30 ` Isaku Yamahata 0 siblings, 0 replies; 20+ messages in thread From: Isaku Yamahata @ 2009-06-04 4:30 UTC (permalink / raw) To: Dan Magenheimer; +Cc: Xen-Devel (E-mail), Keir Fraser On Thu, Jun 04, 2009 at 01:18:14PM +0900, Isaku Yamahata wrote: > On Wed, Jun 03, 2009 at 03:12:10PM -0700, Dan Magenheimer wrote: > > > Actually I missed that the dependent code is only built if > > > CONFIG_PCI_IOMULTI && CONFIG_HOTPLUG_PCI. You've probably got > > > one or both > > > disabled and hence 882 doesn't break without 881 in your case. > > > > In case it helps, with 889 and 881 reverted, I am using the > > default config which results in CONFIG_PCI_IOMULTI=y and > > CONFIG_HOTPLUG_PCI=m. > > Ah, I tested it with CONFIG_HOTPLUG_PCI=y. > So does it make difference to set it =y instead of =m? CONFIG_HOTPLUG_PCI=m works for me. The 'use bus_type' message wasn't printed out. -- yamahata ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Dom0 crashing when built with c/s 881 (Was: blktap2: need more than 3 values to unpack) 2009-06-03 18:45 ` Keir Fraser 2009-06-03 20:15 ` Dan Magenheimer @ 2009-06-04 4:13 ` Isaku Yamahata 1 sibling, 0 replies; 20+ messages in thread From: Isaku Yamahata @ 2009-06-04 4:13 UTC (permalink / raw) To: Keir Fraser; +Cc: Dan Magenheimer, Xen-Devel (E-mail), Dulloor The kernel behaves as same as before unless the kernel command line option, guestdev=...+iomul, is given to the kernel So it should be harmless to enable CONFIG_PCI_IOMULTI by default. Anyway I don't have strong opinion for its default value. On Wed, Jun 03, 2009 at 07:45:09PM +0100, Keir Fraser wrote: > Depends on the feature's impact when unused. > > -- Keir > > On 03/06/2009 18:57, "Dulloor" <dulloor@gmail.com> wrote: > > > Is it better to have the new option added by c/s(CONFIG_PCI_IOMULTI) default > > 'n' ? > > > > -dulloor > > > > On Wed, Jun 3, 2009 at 1:48 PM, Keir Fraser <keir.fraser@eu.citrix.com> wrote: > >> Perhaps post a diff of boot output with c/s 880 vs c/s 881. I've cc'ed > >> Isaku, who submitted the patch that's causing your problem. > >> > >> ?-- Keir > >> > >> On 03/06/2009 18:35, "Dan Magenheimer" <dan.magenheimer@oracle.com> wrote: > >> > >>> OK, it appears that linux-2.6.18-xen.hg c/s 881 is causing > >>> my dom0 to crash. ?Dom0 boots successfully at 880 and fails > >>> with 881 or anything after. > >>> > >>> Any ideas? > >>> > >>>> -----Original Message----- > >>>> From: Dan Magenheimer > >>>> Sent: Tuesday, June 02, 2009 10:45 PM > >>>> To: Dan Magenheimer; Keir Fraser; Dutch Meyer; Xen-Devel (E-mail) > >>>> Subject: RE: [Xen-devel] blktap2: need more than 3 values to unpack > >>>> > >>>> > >>>> Followup: my dom0 boots failed with 888, boots fine with 876, > >>>> then to ensure no pilot error, I rebuilt 888 again and it > >>>> failed again. > >>>> > >>>>> -----Original Message----- > >>>>> From: Dan Magenheimer > >>>>> Sent: Tuesday, June 02, 2009 5:50 PM > >>>>> To: Keir Fraser; Dutch Meyer; Xen-Devel (E-mail) > >>>>> Subject: RE: [Xen-devel] blktap2: need more than 3 values to unpack > >>>>> > >>>>> > >>>>> Thanks. ?It is indeed a pilot error on my part but a bit > >>>>> more bizarre. ?I apparently have a linux-2.6-xen.hg directory > >>>>> as both a sister and a child to xen-unstable.hg. ?In this > >>>>> case the build apparently chooses the child. ?I was > >>>>> looking at and modifying the un-updated child so > >>>>> blktap2 wasn't even present yet. ?Removing the child > >>>>> causes the sibling to build. ?BUT! Now dom0 is > >>>>> crashing early on during boot. ?(This is an Intel > >>>>> Weybridge box.) ?I'll look into this further tomorrow. > >>>>> > >>>>> ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > >>>>> ata2.00: ATAPI, max UDMA/100 > >>>>> ata2.00: configured for UDMA/100 > >>>>> scsi2 : ahci > >>>>> ata3: SATA link down (SStatus 0 SControl 300) > >>>>> scsi3 : ahci > >>>>> ata4: SATA link down (SStatus 0 SControl 300) > >>>>> ? Vendor: ATA ? ? ? Model: ST3320620AS ? ? ? Rev: 3.AA > >>>>> ? Type: ? Direct-Access ? ? ? ? ? ? ? ? ? ? ?ANSI SCSI revision: 05 > >>>>> ata1: EH pending after completion, repeating EH (cnt=4) > >>>>> ? Vendor: LITE-ON ? Model: DVDRW LH-20A1S ? ?Rev: 9L03 > >>>>> ? Type: ? CD-ROM ? ? ? ? ? ? ? ? ? ? ? ? ? ? ANSI SCSI revision: 05 > >>>>> (XEN) PCI add device 00:1f.5 > >>>>> ata_piix 0000:00:1f.5: MAP [ P0 P2 P1 P3 ] > >>>>> ACPI: PCI Interrupt 0000:00:1f.5[B] -> GSI 19 (level, low) -> IRQ 16 > >>>>> ata5: SATA max UDMA/133 cmd 0x0 ctl 0x2 bmdma 0x0 irq 16 > >>>>> ata6: SATA max UDMA/133 cmd 0x0 ctl 0x2 bmdma 0x0 irq 16 > >>>>> scsi4 : ata_piix > >>>>> scsi5 : ata_piix > >>>>> device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: > >>>>> dm-devel@redhat.com > >>>>> Kernel panic - not syncing: Attempted to kill init! > >>>>> ?(XEN) Domain 0 crashed: rebooting machine in 5 seconds. > >>>>> > >>>>>> -----Original Message----- > >>>>>> From: Keir Fraser [mailto:keir.fraser@eu.citrix.com] > >>>>>> Sent: Tuesday, June 02, 2009 4:45 PM > >>>>>> To: Dan Magenheimer; Dutch Meyer; Xen-Devel (E-mail) > >>>>>> Subject: Re: [Xen-devel] blktap2: need more than 3 values > >>>> to unpack > >>>>>> > >>>>>> > >>>>>> Probably you had an old .config hanging around in your build > >>>>>> tree somewhere. > >>>>>> c/s 889 should fix this for a fresh build. > >>>>>> > >>>>>> ?-- Keir > >>>>>> > >>>>>> On 02/06/2009 18:33, "Dan Magenheimer" > >>>>>> <dan.magenheimer@oracle.com> wrote: > >>>>>> > >>>>>>> Thanks. ?Looks like a partial configuration patch got checked > >>>>>>> in for blktap2 (cs 886)? ?CONFIG_XEN_BLKDEV_TAP2 must be > >>>>> configured > >>>>>>> but afaict is not turned on by default (yet?). ?So a fresh > >>>>>>> xen-unstable tip doesn't build the blktap2 driver. ?See: > >>>>>>> > >>>>>>> > >>>> http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/3e01555dd227 > >>>>>>> > >>>>>>> (I'm guessing since this was submitted by Isaku that blktap2 > >>>>>>> shouldn't be the default on ia64?) > >>>>>>> > >>>>>>> Should CONFIG_XEN_BLKDEV_TAP2 be turned on by default, instead > >>>>>>> of CONFIG_XEN_BLKDEV_TAP, at least on x86? > >>>>>>> > >>>>>>> I tried modifying > >>>>>>> > >>>>>>> linux-2.6.18-xen.hg/buildconfigs/linux-defconfig_xen0_x86_32 > >>>>>>> > >>>>>>> (and also > >>>>>>> > >>>>>>> linux-2.6.18-xen.hg/buildconfigs/linux-defconfig_xen_x86_32) > >>>>>>> > >>>>>>> followed by: > >>>>>>> > >>>>>>> KERNELS=linux-2.6-xen0 make linux-2.6-xen-config > >>>>>> CONFIGMODE=oldconfig > >>>>>>> > >>>>>>> (I don't need or want to go through a manual config process) > >>>>>>> > >>>>>>> but BLKDEV_TAP is always selected, not BLKDEV_TAP2. > >>>>>>> > >>>>>>> Finally, I resorted to manually changing > >>>>>>> > >>>>>>> linux-2.6.18-xen.hg/drivers/xen/Kconfig > >>>>>>> > >>>>>>> and this succeeds in turning it on, but it just reverses the > >>>>>>> above checked-in patch, so I suspect that's not the right > >>>>>>> answer either. > >>>>>>> > >>>>>>>> -----Original Message----- > >>>>>>>> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] > >>>>>>>> Sent: Tuesday, June 02, 2009 9:05 AM > >>>>>>>> To: Dan Magenheimer > >>>>>>>> Subject: RE: [Xen-devel] blktap2: need more than 3 > >>>>> values to unpack > >>>>>>>> > >>>>>>>> > >>>>>>>> I think that you don't have the blktap2 driver loaded in > >>>>>>>> dom0. ?A clean > >>>>>>>> build/install of the dom0 kernel image should sort you out. ?If > >>>>>>>> drivers/xen/blktap2 is compiled in it should be setting up > >>>>>>>> these paths. > >>>>>>>> > >>>>>>>> Let me know if that fixes things and I'll make python > >>>>> spit out more > >>>>>>>> meaningful errors, otherwise we can try to figure out the > >>>>>>>> blktap2 kernel > >>>>>>>> code isn't working. > >>>>>>>> > >>>>>>>> --Dutch > >>>>>>>> > >>>>>>>> On Tue, 2 Jun 2009, Dan Magenheimer wrote: > >>>>>>>> > >>>>>>>>> It replies with "didn't find blktap-control in /proc/misc" > >>>>>>>>> > >>>>>>>>> If that fails, perhaps the path doesn't exist, but I looked > >>>>>>>>> and /sys/class/blktap2 doesn't exist. > >>>>>>>>> > >>>>>>>>>> -----Original Message----- > >>>>>>>>>> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] > >>>>>>>>>> Sent: Monday, June 01, 2009 10:37 PM > >>>>>>>>>> To: Dan Magenheimer > >>>>>>>>>> Subject: RE: [Xen-devel] blktap2: need more than 3 > >>>>>> values to unpack > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> Can you try this from the command line: > >>>>>>>>>> > >>>>>>>>>> ? ? ?tapdisk2 -n aio:/pathto/file.img > >>>>>>>>>> > >>>>>>>>>> If successful, this will create your aio device and print a > >>>>>>>>>> /dev device > >>>>>>>>>> associated with it. > >>>>>>>>>> > >>>>>>>>>> In that case you'll then be able to remove it with: > >>>>>>>>>> > >>>>>>>>>> ? ? ?echo 1 > /sys/class/blktap2/<disk>/remove > >>>>>>>>>> > >>>>>>>>>> Where <disk> will be obvious from the output of the > >>>>>>>> tapdisk2 command. > >>>>>>>>>> > >>>>>>>>>> However, I expect that this will fail. > >>>>>>>>>> > >>>>>>>>>> --Dutch > >>>>>>>>>> > >>>>>>>>>> On Mon, 1 Jun 2009, Dan Magenheimer wrote: > >>>>>>>>>> > >>>>>>>>>>>> Then I might be able to help, but I'm not sure how to > >>>>>>>>>>>> reproduce it. ?If > >>>>>>>>>>>> you send a log file and config for this latter error I'll > >>>>>>>>>>>> take a look. > >>>>>>>>>>> > >>>>>>>>>>> Here ya go. > >>>>>>>>>>> > >>>>>>>>>>> Thanks, > >>>>>>>>>>> Dan > >>>>>>>>>>> > >>>>>>>>>>>> -----Original Message----- > >>>>>>>>>>>> From: Dutch Meyer [mailto:dmeyer@cs.ubc.ca] > >>>>>>>>>>>> Sent: Monday, June 01, 2009 8:32 PM > >>>>>>>>>>>> To: Dan Magenheimer > >>>>>>>>>>>> Cc: Xen-Devel (E-mail) > >>>>>>>>>>>> Subject: Re: [Xen-devel] blktap2: need more than 3 > >>>>>>>> values to unpack > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> The tap:aio:/pathto/file.img syntax that you're > >>>> using in your > >>>>>>>>>>>> config was > >>>>>>>>>>>> changed before blktap2 was introduced. > >>>>>>>>>>>> tap:tapdisk:aio:/pathto/file.img is > >>>>>>>>>>>> apparently the correct syntax now, though the README didn't > >>>>>>>>>>>> get updated to > >>>>>>>>>>>> reflect this. ?Our blktap2 documentation is no better - > >>>>>>>> I'll try to > >>>>>>>>>>>> remedy that this week. > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> If you're still seeing this error: > >>>>>>>>>>>> ? ? "Error: 'file' object has no attribute 'find'" > >>>>>>>>>>>> > >>>>>>>>>>>> Then I might be able to help, but I'm not sure how to > >>>>>>>>>>>> reproduce it. ?If > >>>>>>>>>>>> you send a log file and config for this latter error I'll > >>>>>>>>>>>> take a look. > >>>>>>>>>>>> Yang seems to be reporting the same thing in > >>>> another thread. > >>>>>>>>>>>> > >>>>>>>>>>>> --Dutch > >>>>>>>>>>>> > >>>>>>>>>>>> On Mon, 1 Jun 2009, Dan Magenheimer wrote: > >>>>>>>>>>>> > >>>>>>>>>>>>> Hmmm... trying blktap2 for the first time, using 19682. > >>>>>>>>>>>>> I had thought that the syntax hadn't changed, but I am > >>>>>>>>>>>>> getting what appears to be a parsing error on my vbd line. > >>>>>>>>>>>>> > >>>>>>>>>>>>> "ValueError: need more than 3 values to unpack" > >>>>>>>>>>>>> > >>>>>>>>>>>>> Thinking maybe that "w!" was the culprit, I changed > >>>>>>>>>>>>> it to "w" with no change in result. > >>>>>>>>>>>>> > >>>>>>>>>>>>> Looking at the python code that generated the error, > >>>>>>>>>>>>> I tried to figure out the syntax by experimentation > >>>>>>>>>>>>> but without luck. ?I tried: > >>>>>>>>>>>>> > >>>>>>>>>>>>> tap:tapdisk:aio:/pathto/file.img > >>>>>>>>>>>>> > >>>>>>>>>>>>> but got "Error: 'file' object has no attribute 'find'" > >>>>>>>>>>>>> > >>>>>>>>>>>>> To see if I could use the old blktap, I tried > >>>>>>>>>>>>> > >>>>>>>>>>>>> tap:tapdisk:ioemu:/pathto/file.img > >>>>>>>>>>>>> > >>>>>>>>>>>>> but got the dreaded "Error: Device 768 (tap) could not be > >>>>>>>>>>>>> connected. Hotplug scripts not working" > >>>>>>>>>>>>> > >>>>>>>>>>>>> Am I missing something in the syntax for blktap2? > >>>>>>>>>>>>> Is there a how-to or readme I didn't find? ?Or > >>>>>>>>>>>>> is there some required dependency I don't know about > >>>>>>>>>>>>> that is missing? > >>>>>>>>>>>>> > >>>>>>>>>>>>> I thought maybe I had a bad install, so rebuilt and > >>>>>>>>>>>>> reinstalled with the same result. > >>>>>>>>>>>>> > >>>>>>>>>>>>> xend.log and config file attached. > >>>>>>>>>>>>> > >>>>>>>>>>>>> Thanks, > >>>>>>>>>>>>> Dan > >>>>>>>>>>>>> > >>>>>>>>>>>>> P.S. I am trying blktap2 because both blktap and > >>>>>>>>>>>>> file-backed fail. ?Blktap sometimes reads garbage > >>>>>>>>>>>>> from the file and > >>>>>>>>>>>> > >>>>>>>>>>>> _______________________________________________ > >>>>>>>>>>>> Xen-devel mailing list > >>>>>>>>>>>> Xen-devel@lists.xensource.com > >>>>>>>>>>>> http://lists.xensource.com/xen-devel > >>>>>>>>>>>> > >>>>>>>>>> > >>>>>>>>> > >>>>>>>> > >>>>>>> > >>>>>>> _______________________________________________ > >>>>>>> Xen-devel mailing list > >>>>>>> Xen-devel@lists.xensource.com > >>>>>>> http://lists.xensource.com/xen-devel > >>>>>> > >>>>>> > >>>>>> > >>>>> > >>>>> _______________________________________________ > >>>>> Xen-devel mailing list > >>>>> Xen-devel@lists.xensource.com > >>>>> http://lists.xensource.com/xen-devel > >>>>> > >> > >> > >> > >> _______________________________________________ > >> Xen-devel mailing list > >> Xen-devel@lists.xensource.com > >> http://lists.xensource.com/xen-devel > > > > > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > -- yamahata ^ permalink raw reply [flat|nested] 20+ messages in thread
end of thread, other threads:[~2009-06-04 16:11 UTC | newest]
Thread overview: 20+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <Pine.GSO.4.60.0906020756360.23746@cascade.cs.ubc.ca>
2009-06-02 17:33 ` blktap2: need more than 3 values to unpack Dan Magenheimer
2009-06-02 22:44 ` Keir Fraser
2009-06-02 23:49 ` Dan Magenheimer
2009-06-03 4:45 ` Dan Magenheimer
2009-06-03 17:35 ` Dom0 crashing when built with c/s 881 (Was: blktap2: need more than 3 values to unpack) Dan Magenheimer
2009-06-03 17:48 ` Keir Fraser
2009-06-03 17:57 ` Dulloor
2009-06-03 18:45 ` Keir Fraser
2009-06-03 20:15 ` Dan Magenheimer
2009-06-03 20:46 ` Keir Fraser
2009-06-03 21:17 ` Dan Magenheimer
2009-06-03 21:27 ` Keir Fraser
2009-06-03 22:12 ` Dan Magenheimer
2009-06-04 1:09 ` Dan Magenheimer
2009-06-04 4:49 ` Dan Magenheimer
2009-06-04 7:34 ` Keir Fraser
2009-06-04 16:11 ` Dan Magenheimer
2009-06-04 4:18 ` Isaku Yamahata
2009-06-04 4:30 ` Isaku Yamahata
2009-06-04 4:13 ` Isaku Yamahata
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.